more clean up

Author: colleenmcginnis

docs/reference/aggregations/search-aggregations-bucket-adjacency-matrix-aggregation.md

@@ -99,8 +99,6 @@ The response contains buckets with document counts for each filter and combinati
     :   (Required, [Query DSL object](/reference/query-languages/querydsl.md)) Query used to filter documents. The key is the filter name.
 
         At least one filter is required. The total number of filters cannot exceed the [`indices.query.bool.max_clause_count`](/reference/elasticsearch/configuration-reference/search-settings.md#indices-query-bool-max-clause-count) setting. See [Filter limits](#adjacency-matrix-agg-filter-limits).
-
-
     ::::
 
 

docs/reference/aggregations/search-aggregations-bucket-categorize-text-aggregation.md

@@ -26,7 +26,8 @@ The algorithm used for categorization was completely changed in version 8.3.0. A
 
     The `categorization_analyzer` field can be specified either as a string or as an object. If it is a string it must refer to a [built-in analyzer](/reference/text-analysis/analyzer-reference.md) or one added by another plugin. If it is an object it has the following properties:
 
-    :::::{dropdown} Properties of categorization_analyzer
+    **Properties of `categorization_analyzer`**:
+
     `char_filter`
     :   (array of strings or objects) One or more [character filters](/reference/text-analysis/character-filter-reference.md). In addition to the built-in character filters, other plugins can provide more character filters. This property is optional. If it is not specified, no character filters are applied prior to categorization. If you are customizing some other aspect of the analyzer and you need to achieve the equivalent of `categorization_filters` (which are not permitted when some other aspect of the analyzer is customized), add them here as [pattern replace character filters](/reference/text-analysis/analysis-pattern-replace-charfilter.md).
 
@@ -41,8 +42,6 @@ The algorithm used for categorization was completely changed in version 8.3.0. A
     `filter`
     :   (array of strings or objects) One or more [token filters](/reference/text-analysis/token-filter-reference.md). In addition to the built-in token filters, other plugins can provide more token filters. This property is optional. If it is not specified, no token filters are applied prior to categorization.
 
-    :::::
-
 
 `categorization_filters`
 :   (Optional, array of strings) This property expects an array of regular expressions. The expressions are used to filter out matching sequences from the categorization field values. You can use this functionality to fine tune the categorization by excluding sequences from consideration when categories are defined. For example, you can exclude SQL statements that appear in your log files. This property cannot be used at the same time as `categorization_analyzer`. If you only want to define simple regular expression filters that are applied prior to tokenization, setting this property is the easiest method. If you also want to customize the tokenizer or post-tokenization filtering, use the `categorization_analyzer` property instead and include the filters as `pattern_replace` character filters.

docs/reference/aggregations/search-aggregations-change-point-aggregation.md

@@ -46,15 +46,14 @@ A `change_point` aggregation looks like this in isolation:
 `bucket`
 :   (Optional, object) Values of the bucket that indicates the discovered change point. Not returned if no change point was found. All the aggregations in the bucket are returned as well.
 
-    ::::{dropdown} Properties of bucket
+    **Properties of `bucket**:
+
     `key`
     :   (value) The key of the bucket matched. Could be string or numeric.
 
     `doc_count`
     :   (number) The document count of the bucket.
 
-    ::::
-
 
 `type`
 :   (object) The found change point type and its related values. Possible types:

docs/reference/elasticsearch-plugins/discovery-ec2.md

@@ -7,7 +7,7 @@ mapped_pages:
 
 The EC2 discovery plugin provides a list of seed addresses to the [discovery process](docs-content://deploy-manage/distributed-architecture/discovery-cluster-formation/discovery-hosts-providers.md) by querying the [AWS API](https://github.com/aws/aws-sdk-java) for a list of EC2 instances matching certain criteria determined by the [plugin settings](/reference/elasticsearch-plugins/discovery-ec2-usage.md).
 
-**If you are looking for a hosted solution of {{es}} on AWS, please visit [https://www.elastic.co/cloud.**](https://www.elastic.co/cloud.**)
+**If you are looking for a hosted solution of {{es}} on AWS, please visit [https://www.elastic.co/cloud](https://www.elastic.co/cloud).**
 
 
 ## Installation [discovery-ec2-install]

docs/reference/elasticsearch/rest-apis/api-conventions.md

@@ -324,8 +324,9 @@ Some multi-target APIs that can target indices also support the following query
 `ignore_throttled`
 :   (Optional, Boolean) If `true`, concrete, expanded or aliased indices are ignored when frozen. Defaults to `true`.
 
-    [7.16.0]
-
+    :::{admonition} Deprecated in 7.16.0
+    This parameter was deprecated in 7.16.0.
+    :::
 
 ::::{note}
 APIs with a single target, such as the [get document API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-get), do not support multi-target syntax.

docs/reference/query-languages/query-dsl/query-dsl-prefix-query.md

@@ -41,8 +41,12 @@ GET /_search
 `rewrite`
 :   (Optional, string) Method used to rewrite the query. For valid values and more information, see the [`rewrite` parameter](/reference/query-languages/query-dsl/query-dsl-multi-term-rewrite.md).
 
-`case_insensitive` [7.10.0]
-:   (Optional, Boolean) Allows ASCII case insensitive matching of the value with the indexed field values when set to true. Default is false which means the case sensitivity of matching depends on the underlying field’s mapping.
+`case_insensitive`
+:   :::{admonition} Added in 7.10.0
+    This parameter was added in 7.10.0.
+    :::
+
+    (Optional, Boolean) Allows ASCII case insensitive matching of the value with the indexed field values when set to true. Default is false which means the case sensitivity of matching depends on the underlying field’s mapping.
 
 
 ## Notes [prefix-query-notes]

docs/reference/query-languages/query-dsl/query-dsl-range-query.md

@@ -31,30 +31,30 @@ GET /_search
 ## Top-level parameters for `range` [range-query-top-level-params]
 
 `<field>`
-&nbsp;&nbsp;&nbsp;&nbsp; (Required, object) Field you wish to search.
+:   (Required, object) Field you wish to search.
 
 
 ## Parameters for `<field>` [range-query-field-params]
 
 `gt`
-&nbsp;&nbsp;&nbsp;&nbsp; (Optional) Greater than.
+:   (Optional) Greater than.
 
 `gte`
-&nbsp;&nbsp;&nbsp;&nbsp; (Optional) Greater than or equal to.
+:   (Optional) Greater than or equal to.
 
 `lt`
-&nbsp;&nbsp;&nbsp;&nbsp; (Optional) Less than.
+:   (Optional) Less than.
 
 `lte`
-&nbsp;&nbsp;&nbsp;&nbsp; (Optional) Less than or equal to.
+:   (Optional) Less than or equal to.
 
 `format`
-&nbsp;&nbsp;&nbsp;&nbsp; (Optional, string) Date format used to convert `date` values in the query.
+:   (Optional, string) Date format used to convert `date` values in the query.
 
-&nbsp;&nbsp;&nbsp;&nbsp; By default, {{es}} uses the [date `format`](/reference/elasticsearch/mapping-reference/mapping-date-format.md) provided in the `<field>`'s
-&nbsp;&nbsp;&nbsp;&nbsp; mapping. This value overrides that mapping format.
+    By default, {{es}} uses the [date `format`](/reference/elasticsearch/mapping-reference/mapping-date-format.md) provided in the `<field>`'s
+    mapping. This value overrides that mapping format.
 
-&nbsp;&nbsp;&nbsp;&nbsp; For valid syntax, see [`format`](/reference/elasticsearch/mapping-reference/mapping-date-format.md).
+    For valid syntax, see [`format`](/reference/elasticsearch/mapping-reference/mapping-date-format.md).
 
 ::::{warning}
 If a format or date value is incomplete, the range query replaces any missing components with default values. See [Missing date components](#missing-date-components).
@@ -65,29 +65,28 @@ If a format or date value is incomplete, the range query replaces any missing co
 $$$querying-range-fields$$$
 
 `relation`
-&nbsp;&nbsp;&nbsp;&nbsp; (Optional, string) Indicates how the range query matches values for `range`
-&nbsp;&nbsp;&nbsp;&nbsp; fields. Valid values are:
+:   (Optional, string) Indicates how the range query matches values for `range`
+    fields. Valid values are:
 
-&nbsp;&nbsp;&nbsp;&nbsp; `INTERSECTS` (Default)
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Matches documents with a range field value that intersects the query’s range.
+    `INTERSECTS` (Default)
+    :   Matches documents with a range field value that intersects the query’s range.
 
-&nbsp;&nbsp;&nbsp;&nbsp; `CONTAINS`
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Matches documents with a range field value that entirely contains the
-&nbsp;&nbsp;&nbsp;&nbsp; query’s range.
+    `CONTAINS`
+    :   Matches documents with a range field value that entirely contains the query’s range.
 
-&nbsp;&nbsp;&nbsp;&nbsp; `WITHIN`
-&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Matches documents with a range field value entirely within the query’s range.
+    `WITHIN`
+    :   Matches documents with a range field value entirely within the query’s range.
 
 
 `time_zone`
-&nbsp;&nbsp;&nbsp;&nbsp; (Optional, string) [Coordinated Universal Time (UTC) offset](https://en.wikipedia.org/wiki/List_of_UTC_time_offsets) or [IANA time zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
-&nbsp;&nbsp;&nbsp;&nbsp; used to convert `date` values in the query to UTC.
+:   (Optional, string) [Coordinated Universal Time (UTC) offset](https://en.wikipedia.org/wiki/List_of_UTC_time_offsets) or [IANA time zone](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones)
+    used to convert `date` values in the query to UTC.
 
-&nbsp;&nbsp;&nbsp;&nbsp; Valid values are ISO 8601 UTC offsets, such as `+01:00` or -`08:00`, and IANA
-&nbsp;&nbsp;&nbsp;&nbsp; time zone IDs, such as `America/Los_Angeles`.
+    Valid values are ISO 8601 UTC offsets, such as `+01:00` or -`08:00`, and IANA
+    time zone IDs, such as `America/Los_Angeles`.
 
-&nbsp;&nbsp;&nbsp;&nbsp; For an example query using the `time_zone` parameter, see
-&nbsp;&nbsp;&nbsp;&nbsp; [Time zone in `range` queries](#range-query-time-zone).
+    For an example query using the `time_zone` parameter, see
+    [Time zone in `range` queries](#range-query-time-zone).
 
 ::::{note}
 The `time_zone` parameter does **not** affect the [date math](/reference/elasticsearch/rest-apis/common-options.md#date-math) value of `now`. `now` is always the current system time in UTC.
@@ -99,15 +98,15 @@ However, the `time_zone` parameter does convert dates calculated using `now` and
 
 
 `boost`
-&nbsp;&nbsp;&nbsp;&nbsp; (Optional, float) Floating point number used to decrease or increase the
-&nbsp;&nbsp;&nbsp;&nbsp; [relevance scores](/reference/query-languages/query-dsl/query-filter-context.md#relevance-scores) of a query. Defaults to `1.0`.
+:   (Optional, float) Floating point number used to decrease or increase the
+    [relevance scores](/reference/query-languages/query-dsl/query-filter-context.md#relevance-scores) of a query. Defaults to `1.0`.
 
-&nbsp;&nbsp;&nbsp;&nbsp; You can use the `boost` parameter to adjust relevance scores for searches
-&nbsp;&nbsp;&nbsp;&nbsp; containing two or more queries.
+    You can use the `boost` parameter to adjust relevance scores for searches
+    containing two or more queries.
 
-&nbsp;&nbsp;&nbsp;&nbsp; Boost values are relative to the default value of `1.0`. A boost value between `0`
-&nbsp;&nbsp;&nbsp;&nbsp; and `1.0` decreases the relevance score. A value greater than `1.0`
-&nbsp;&nbsp;&nbsp;&nbsp; increases the relevance score.
+    Boost values are relative to the default value of `1.0`. A boost value between `0`
+    and `1.0` decreases the relevance score. A value greater than `1.0`
+    increases the relevance score.
 
 
 
@@ -169,31 +168,31 @@ When no date format is specified and the range query is targeting a date field,
 {{es}} rounds [date math](/reference/elasticsearch/rest-apis/common-options.md#date-math) values in parameters as follows:
 
 `gt`
-&nbsp;&nbsp;&nbsp;&nbsp; Rounds up to the first millisecond not covered by the rounded date.
+:   Rounds up to the first millisecond not covered by the rounded date.
 
-&nbsp;&nbsp;&nbsp;&nbsp; For example, `2014-11-18||/M` rounds up to `2014-12-01T00:00:00.000`,
-&nbsp;&nbsp;&nbsp;&nbsp; excluding the entire month of November.
+    For example, `2014-11-18||/M` rounds up to `2014-12-01T00:00:00.000`,
+    excluding the entire month of November.
 
 
 `gte`
-&nbsp;&nbsp;&nbsp;&nbsp; Rounds down to the first millisecond.
+:   Rounds down to the first millisecond.
 
-&nbsp;&nbsp;&nbsp;&nbsp; For example, `2014-11-18||/M` rounds down to `2014-11-01T00:00:00.000`,
-&nbsp;&nbsp;&nbsp;&nbsp; including the entire month.
+    For example, `2014-11-18||/M` rounds down to `2014-11-01T00:00:00.000`,
+    including the entire month.
 
 
 `lt`
-&nbsp;&nbsp;&nbsp;&nbsp; Rounds down to the last millisecond before the rounded value.
+:   Rounds down to the last millisecond before the rounded value.
 
-&nbsp;&nbsp;&nbsp;&nbsp; For example, `2014-11-18||/M` rounds down to `2014-10-31T23:59:59.999`,
-&nbsp;&nbsp;&nbsp;&nbsp; excluding the entire month of November.
+    For example, `2014-11-18||/M` rounds down to `2014-10-31T23:59:59.999`,
+    excluding the entire month of November.
 
 
 `lte`
-&nbsp;&nbsp;&nbsp;&nbsp; Rounds up to the latest millisecond in the rounding interval.
+:   Rounds up to the latest millisecond in the rounding interval.
 
-&nbsp;&nbsp;&nbsp;&nbsp; For example, `2014-11-18||/M` rounds up to `2014-11-30T23:59:59.999`,
-&nbsp;&nbsp;&nbsp;&nbsp; including the entire month.
+    For example, `2014-11-18||/M` rounds up to `2014-11-30T23:59:59.999`,
+    including the entire month.
 
 
 

docs/reference/query-languages/query-dsl/query-dsl-regexp-query.md

@@ -55,8 +55,12 @@ GET /_search
 `flags`
 :   (Optional, string) Enables optional operators for the regular expression. For valid values and more information, see [Regular expression syntax](/reference/query-languages/query-dsl/regexp-syntax.md#regexp-optional-operators).
 
-`case_insensitive` [7.10.0]
-:   (Optional, Boolean) Allows case insensitive matching of the regular expression value with the indexed field values when set to true. Default is false which means the case sensitivity of matching depends on the underlying field’s mapping.
+`case_insensitive`
+:   :::{admonition} Added in 7.10.0
+    This parameter was added in 7.10.0.
+    :::
+
+    (Optional, Boolean) Allows case insensitive matching of the regular expression value with the indexed field values when set to true. Default is false which means the case sensitivity of matching depends on the underlying field’s mapping.
 
 `max_determinized_states`
 :   (Optional, integer) Maximum number of [automaton states](https://en.wikipedia.org/wiki/Deterministic_finite_automaton) required for the query. Default is `10000`.

docs/reference/query-languages/query-dsl/query-dsl-term-query.md

@@ -57,8 +57,12 @@ GET /_search
     Boost values are relative to the default value of `1.0`. A boost value between `0` and `1.0` decreases the relevance score. A value greater than `1.0` increases the relevance score.
 
 
-`case_insensitive` [7.10.0]
-:   (Optional, Boolean) Allows ASCII case insensitive matching of the value with the indexed field values when set to true. Default is false which means the case sensitivity of matching depends on the underlying field’s mapping.
+`case_insensitive`
+:   :::{admonition} Added in 7.10.0
+    This parameter was added in 7.10.0.
+    :::
+
+    (Optional, Boolean) Allows ASCII case insensitive matching of the value with the indexed field values when set to true. Default is false which means the case sensitivity of matching depends on the underlying field’s mapping.
 
 
 ## Notes [term-query-notes]

docs/reference/query-languages/query-dsl/query-dsl-wildcard-query.md

@@ -47,8 +47,12 @@ GET /_search
     Boost values are relative to the default value of `1.0`. A boost value between `0` and `1.0` decreases the relevance score. A value greater than `1.0` increases the relevance score.
 
 
-`case_insensitive` [7.10.0]
-:   (Optional, Boolean) Allows case insensitive matching of the pattern with the indexed field values when set to true. Default is false which means the case sensitivity of matching depends on the underlying field’s mapping.
+`case_insensitive`
+:   :::{admonition} Added in 7.10.0
+    This parameter was added in 7.10.0.
+    :::
+
+    (Optional, Boolean) Allows case insensitive matching of the pattern with the indexed field values when set to true. Default is false which means the case sensitivity of matching depends on the underlying field’s mapping.
 
 `rewrite`
 :   (Optional, string) Method used to rewrite the query. For valid values and more information, see the [`rewrite` parameter](/reference/query-languages/query-dsl/query-dsl-multi-term-rewrite.md).