apache · vtlim · Mar 2, 2023 · Feb 2, 2023 · Feb 10, 2023 · Feb 22, 2023
diff --git a/docs/development/extensions-core/druid-basic-security.md b/docs/development/extensions-core/druid-basic-security.md
diff --git a/docs/ingestion/ingestion-spec.md b/docs/ingestion/ingestion-spec.md
@@ -477,7 +477,7 @@ The `indexSpec` object can include the following properties:
 |-----|-----------|-------|
 |bitmap|Compression format for bitmap indexes. Should be a JSON object with `type` set to `roaring` or `concise`. For type `roaring`, the boolean property `compressRunOnSerialization` (defaults to true) controls whether or not run-length encoding will be used when it is determined to be more space-efficient.|`{"type": "roaring"}`|
 |dimensionCompression|Compression format for dimension columns. Options are `lz4`, `lzf`, `zstd`, or `uncompressed`.|`lz4`|
-|stringDictionaryEncoding|Encoding format for STRING value dictionaries used by STRING and COMPLEX&lt;json&gt; columns. <br>Example to enable front coding: `{"type":"frontCoded", "bucketSize": 4}`<br>`bucketSize` is the number of values to place in a bucket to perform delta encoding. Must be a power of 2, maximum is 128. Defaults to 4.<br>See [Front coding](#front-coding) for more information.|`{"type":"utf8"}`|
+|stringDictionaryEncoding|Encoding format for STRING value dictionaries used by STRING and COMPLEX&lt;json&gt; columns. <br /><br />Example to enable front coding: `{"type":"frontCoded", "bucketSize": 4}`<br />`bucketSize` is the number of values to place in a bucket to perform delta encoding. Must be a power of 2, maximum is 128. Defaults to 4.<br /><br />See [Front coding](#front-coding) for more information.|`{"type":"utf8"}`|
 |metricCompression|Compression format for primitive type metric columns. Options are `lz4`, `lzf`, `zstd`, `uncompressed`, or `none` (which is more efficient than `uncompressed`, but not supported by older versions of Druid).|`lz4`|
 |longEncoding|Encoding format for long-typed columns. Applies regardless of whether they are dimensions or metrics. Options are `auto` or `longs`. `auto` encodes the values using offset or lookup table depending on column cardinality, and store them with variable size. `longs` stores the value as-is with 8 bytes each.|`longs`|
 |jsonCompression|Compression format to use for nested column raw data. Options are `lz4`, `lzf`, `zstd`, or `uncompressed`.|`lz4`|

diff --git a/docs/ingestion/migrate-from-firehose-ingestion.md b/docs/ingestion/migrate-from-firehose-ingestion.md
@@ -53,7 +53,7 @@ Edit the new file as follows:
 4. Move the `format` definition from `parser.parseSpec` to an `inputFormat` definition in `ioConfig`.
 5. Delete the `parser` definition.
 6. Save the file.
-<br>You can check the format of your new ingestion file against the [migrated example](#example-ingestion-spec-after-migration) below.
+You can check the format of your new ingestion file against the [migrated example](#example-ingestion-spec-after-migration) below.
 7. Test the new ingestion spec with a temporary data source.
 8. Once you've successfully ingested sample data with the new spec, stop firehose ingestion and switch to the new spec.
 

diff --git a/docs/operations/rule-configuration.md b/docs/operations/rule-configuration.md
@@ -153,9 +153,10 @@ Set the following properties:
 
 - `period`: a JSON object representing [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) periods. The period is from some time in the past to the present, or into the future if `includeFuture` is set to `true`.
 - `includeFuture`: a boolean flag to instruct Druid to match a segment if:
-<br>- the segment interval overlaps the rule interval, or
-<br>- the segment interval starts any time after the rule interval starts.
-<br>You can use this property to load segments with future start and end dates, where "future" is relative to the time when the Coordinator evaluates data against the rule. Defaults to `true`.
+  - the segment interval overlaps the rule interval, or
+  - the segment interval starts any time after the rule interval starts.
+
+  You can use this property to load segments with future start and end dates, where "future" is relative to the time when the Coordinator evaluates data against the rule. Defaults to `true`.
 - `tieredReplicants`: a map of tier names to the number of segment replicas for that tier.
 
 ### Interval load rule
@@ -215,10 +216,12 @@ Period drop rules have type `dropByPeriod` and the following JSON structure:
 Set the following properties:
 
 - `period`: a JSON object representing [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) periods. The period is from some time in the past to the future or to the current time, depending on the `includeFuture` flag.
-- `includeFuture`: a boolean flag to instruct Druid to match a segment if:
-<br>- the segment interval overlaps the rule interval, or
-<br>- the segment interval starts any time after the rule interval starts.
-<br>You can use this property to drop segments with future start and end dates, where "future" is relative to the time when the Coordinator evaluates data against the rule. Defaults to `true`.
+- `includeFuture`: a boolean flag to instruct Druid to match a segment if one of the following conditions apply:
+
+  - the segment interval overlaps the rule interval
+  - the segment interval starts any time after the rule interval starts
+
+  You can use this property to drop segments with future start and end dates, where "future" is relative to the time when the Coordinator evaluates data against the rule. Defaults to `true`.
 
 ### Period drop before rule
 
@@ -289,10 +292,11 @@ Period broadcast rules have type `broadcastByPeriod` and the following JSON stru
 Set the following properties:
 
 - `period`: a JSON object representing [ISO-8601](https://en.wikipedia.org/wiki/ISO_8601) periods. The period is from some time in the past to the future or to the current time, depending on the `includeFuture` flag.
-- `includeFuture`: a boolean flag to instruct Druid to match a segment if:
-<br>- the segment interval overlaps the rule interval, or
-<br>- the segment interval starts any time after the rule interval starts.
-<br>You can use this property to broadcast segments with future start and end dates, where "future" is relative to the time when the Coordinator evaluates data against the rule. Defaults to `true`.
+- `includeFuture`: a boolean flag to instruct Druid to match a segment if one of the following conditions apply:
+  - the segment interval overlaps the rule interval
+  - the segment interval starts any time after the rule interval starts.
+
+  You can use this property to broadcast segments with future start and end dates, where "future" is relative to the time when the Coordinator evaluates data against the rule. Defaults to `true`.
 
 ### Interval broadcast rule
 

diff --git a/docs/querying/caching.md b/docs/querying/caching.md
@@ -1,7 +1,7 @@
 ---
 id: caching
 title: "Query caching"
-description: "Describes Apache Druid per-segment and whole-query cache types. Identifies services where you can enable caching and suggestions for caching strategy." 
+description: "Describes Apache Druid per-segment and whole-query cache types. Identifies services where you can enable caching and suggestions for caching strategy."
 ---
 
 <!--

diff --git a/docs/tutorials/tutorial-jdbc.md b/docs/tutorials/tutorial-jdbc.md
@@ -24,7 +24,7 @@ sidebar_label: JDBC connector
   -->
 
 Redirecting you to the JDBC connector examples...
-
+<head>
 <script>window.location.replace("https://druid.apache.org/docs/latest/querying/sql-jdbc.html#examples")</script>
 </head>
 <a href="https://druid.apache.org/docs/latest/querying/sql-jdbc.html#examples">Click here if you are not redirected.</a>

diff --git a/docs/tutorials/tutorial-jupyter-index.md b/docs/tutorials/tutorial-jupyter-index.md
@@ -38,7 +38,7 @@ Make sure you meet the following requirements before starting the Jupyter-based
    pip3 install requests
    ````
 
-- JupyterLab (recommended) or Jupyter Notebook running on a non-default port. By default, Druid and Jupyter both try to use port `8888,` so start Jupyter on a different port.
+- JupyterLab (recommended) or Jupyter Notebook running on a non-default port. By default, Druid and Jupyter both try to use port `8888`, so start Jupyter on a different port.
 
   - Install JupyterLab or Notebook:
 

diff --git a/docs/tutorials/tutorial-kafka.md b/docs/tutorials/tutorial-kafka.md
@@ -45,8 +45,9 @@ Before you follow the steps in this tutorial, download Druid as described in the
    ```
 2. If you're already running Kafka on the machine you're using for this tutorial, delete or rename the `kafka-logs` directory in `/tmp`.
 
-   > Druid and Kafka both rely on [Apache ZooKeeper](https://zookeeper.apache.org/) to coordinate and manage services. Because Druid is already running, Kafka attaches to the Druid ZooKeeper instance when it starts up.<br>
-   In a production environment where you're running Druid and Kafka on different machines, [start the Kafka ZooKeeper](https://kafka.apache.org/quickstart) before you start the Kafka broker.
+   > Druid and Kafka both rely on [Apache ZooKeeper](https://zookeeper.apache.org/) to coordinate and manage services. Because Druid is already running, Kafka attaches to the Druid ZooKeeper instance when it starts up.<br />
+   > 
+   > In a production environment where you're running Druid and Kafka on different machines, [start the Kafka ZooKeeper](https://kafka.apache.org/quickstart) before you start the Kafka broker.
 
 3. In the Kafka root directory, run this command to start a Kafka broker:
-Original file line number
+Diff line change
@@ Expand Up / @@ -24,7 +24,7 @@ sidebar_label: JDBC connector @@
       -->
     Redirecting you to the JDBC connector examples...
+    <head>
     <script>window.location.replace("https://druid.apache.org/docs/latest/querying/sql-jdbc.html#examples")</script>
     </head>
     <a href="https://druid.apache.org/docs/latest/querying/sql-jdbc.html#examples">Click here if you are not redirected.</a>
@@ Expand Down @@