fix syntax and rendering errors

Author: colleenmcginnis

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

@@ -94,7 +94,7 @@ The response contains buckets with document counts for each filter and combinati
 `filters`
 :   (Required, object) Filters used to create buckets.
 
-    ::::{dropdown} Properties of `filters`
+    ::::{dropdown} Properties of filters
     `<filter>`
     :   (Required, [Query DSL object](/reference/query-languages/querydsl.md)) Query used to filter documents. The key is the filter name.
 

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

@@ -26,7 +26,7 @@ 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`
+    :::::{dropdown} 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).
 

docs/reference/aggregations/search-aggregations-bucket-correlation-aggregation.md

@@ -11,43 +11,33 @@ A sibling pipeline aggregation which executes a correlation function on the conf
 
 ## Parameters [bucket-correlation-agg-syntax]
 
-`buckets_path`
-:   (Required, string) Path to the buckets that contain one set of values to correlate. For syntax, see [`buckets_path` Syntax](/reference/aggregations/pipeline.md#buckets-path-syntax).
+### `buckets_path`
 
-`function`
-:   (Required, object) The correlation function to execute.
+(Required, string) Path to the buckets that contain one set of values to correlate. For syntax, see [`buckets_path` Syntax](/reference/aggregations/pipeline.md#buckets-path-syntax).
 
-    ::::{dropdown} Properties of `function`
-    `count_correlation`
-    :   (Required*, object) The configuration to calculate a count correlation. This function is designed for determining the correlation of a term value and a given metric. Consequently, it needs to meet the following requirements.
+### `function`
 
-        * The `buckets_path` must point to a `_count` metric.
-        * The total count of all the `bucket_path` count values must be less than or equal to `indicator.doc_count`.
-        * When utilizing this function, an initial calculation to gather the required `indicator` values is required.
+(Required, object) The correlation function to execute.
 
-        ::::{dropdown} Properties of `count_correlation`
-        `indicator`
-        :   (Required, object) The indicator with which to correlate the configured `bucket_path` values.
+#### `count_correlation`
 
-            ::::{dropdown} Properties of `indicator`
-            `doc_count`
-            :   (Required, integer) The total number of documents that initially created the `expectations`. It’s required to be greater than or equal to the sum of all values in the `buckets_path` as this is the originating superset of data to which the term values are correlated.
+(Required*, object) The configuration to calculate a count correlation. This function is designed for determining the correlation of a term value and a given metric. Consequently, it needs to meet the following requirements.
 
-            `expectations`
-            :   (Required, array) An array of numbers with which to correlate the configured `bucket_path` values. The length of this value must always equal the number of buckets returned by the `bucket_path`.
+* The `buckets_path` must point to a `_count` metric.
+* The total count of all the `bucket_path` count values must be less than or equal to `indicator.doc_count`.
+* When utilizing this function, an initial calculation to gather the required `indicator` values is required.
 
-            `fractions`
-            :   (Optional, array) An array of fractions to use when averaging and calculating variance. This should be used if the pre-calculated data and the `buckets_path` have known gaps. The length of `fractions`, if provided, must equal `expectations`.
+`indicator`
+:   (Required, object) The indicator with which to correlate the configured `bucket_path` values.
 
-            ::::
-
-
-        ::::
-
-
-    ::::
+    `doc_count`
+    :   (Required, integer) The total number of documents that initially created the `expectations`. It’s required to be greater than or equal to the sum of all values in the `buckets_path` as this is the originating superset of data to which the term values are correlated.
 
+    `expectations`
+    :   (Required, array) An array of numbers with which to correlate the configured `bucket_path` values. The length of this value must always equal the number of buckets returned by the `bucket_path`.
 
+    `fractions`
+    :   (Optional, array) An array of fractions to use when averaging and calculating variance. This should be used if the pre-calculated data and the `buckets_path` have known gaps. The length of `fractions`, if provided, must equal `expectations`.
 
 ## Syntax [_syntax_8]
 

docs/reference/aggregations/search-aggregations-bucket-significantterms-aggregation.md

@@ -196,7 +196,7 @@ Picking a free-text field as the subject of a significant terms analysis can be
 ::::
 
 
-::::{admonition} Use the *"like this but not this"* pattern
+::::{admonition} Use the "like this but not this" pattern
 You can spot mis-categorized content by first searching a structured field e.g. `category:adultMovie` and use significant_terms on the free-text "movie_description" field. Take the suggested words (I’ll leave them to your imagination) and then search for all movies NOT marked as category:adultMovie but containing these keywords. You now have a ranked list of badly-categorized movies that you should reclassify or at least remove from the "familyFriendly" category.
 
 The significance score from each term can also provide a useful `boost` setting to sort matches. Using the `minimum_should_match` setting of the `terms` query with the keywords will help control the balance of precision/recall in the result set i.e a high setting would have a small number of relevant results packed full of keywords and a setting of "1" would produce a more exhaustive results set with all documents containing *any* keyword.

docs/reference/aggregations/search-aggregations-bucket-significanttext-aggregation.md

@@ -265,7 +265,7 @@ The numbers returned for scores are primarily intended for ranking different sug
 ::::
 
 
-::::{admonition} Use the *"like this but not this"* pattern
+::::{admonition} Use the "like this but not this" pattern
 You can spot mis-categorized content by first searching a structured field e.g. `category:adultMovie` and use significant_text on the text "movie_description" field. Take the suggested words (I’ll leave them to your imagination) and then search for all movies NOT marked as category:adultMovie but containing these keywords. You now have a ranked list of badly-categorized movies that you should reclassify or at least remove from the "familyFriendly" category.
 
 The significance score from each term can also provide a useful `boost` setting to sort matches. Using the `minimum_should_match` setting of the `terms` query with the keywords will help control the balance of precision/recall in the result set i.e a high setting would have a small number of relevant results packed full of keywords and a setting of "1" would produce a more exhaustive results set with all documents containing *any* keyword.

docs/reference/aggregations/search-aggregations-metrics-geocentroid-aggregation.md

@@ -201,7 +201,7 @@ POST /places/_search?size=0
 }
 ```
 
-::::{admonition} Using `geo_centroid` as a sub-aggregation of `geohash_grid`
+::::{admonition} Using geo_centroid as a sub-aggregation of geohash_grid
 :class: warning
 
 The [`geohash_grid`](/reference/aggregations/search-aggregations-bucket-geohashgrid-aggregation.md) aggregation places documents, not individual geopoints, into buckets. If a document’s `geo_point` field contains [multiple values](/reference/elasticsearch/mapping-reference/array.md), the document could be assigned to multiple buckets, even if one or more of its geopoints are outside the bucket boundaries.

docs/reference/elasticsearch-plugins/mapper-size-usage.md

@@ -72,7 +72,7 @@ GET my-index-000001/_search
 5. Uses a [script field](/reference/elasticsearch/rest-apis/retrieve-selected-fields.md#script-fields) to return the `_size` field in the search response.
 
 
-::::{admonition} Using `_size` in {kib}
+::::{admonition} Using _size in {{kib}}
 :class: note
 
 To use the `_size` field in {{kib}}, update the `metaFields` setting and add `_size` to the list of meta fields. `metaFields` can be configured in {{kib}} from the Advanced Settings page in Management.

docs/reference/elasticsearch/command-line-tools/service-tokens-command.md

@@ -39,58 +39,50 @@ To ensure that {{es}} can read the service account token information at startup,
 
 ## Parameters [service-tokens-command-parameters]
 
-`create`
-:   Creates a service account token for the specified service account.
+### `create`
 
-    ::::{dropdown} Properties of `create`
-    `<service_account_principal>`
-    :   (Required, string) Service account principal that takes the format of `<namespace>/<service>`, where the `namespace` is a top-level grouping of service accounts, and `service` is the name of the service. For example, `elastic/fleet-server`.
+Creates a service account token for the specified service account.
 
-        The service account principal must match a known service account.
+**Properties of `create`**:
 
+`<service_account_principal>`
+:   (Required, string) Service account principal that takes the format of `<namespace>/<service>`, where the `namespace` is a top-level grouping of service accounts, and `service` is the name of the service. For example, `elastic/fleet-server`.
 
-    `<token_name>`
-    :   (Required, string) An identifier for the token name.
+    The service account principal must match a known service account.
 
-        Token names must be at least 1 and no more than 256 characters. They can contain alphanumeric characters (`a-z`, `A-Z`, `0-9`), dashes (`-`), and underscores (`_`), but cannot begin with an underscore.
+`<token_name>`
+:   (Required, string) An identifier for the token name.
 
-        ::::{note}
-        Token names must be unique in the context of the associated service account.
-        ::::
+    Token names must be at least 1 and no more than 256 characters. They can contain alphanumeric characters (`a-z`, `A-Z`, `0-9`), dashes (`-`), and underscores (`_`), but cannot begin with an underscore.
 
+    :::::{note}
+    Token names must be unique in the context of the associated service account.
+    :::::
 
-    ::::
+### `list`
 
+Lists all service account tokens defined in the `service_tokens` file. If you specify a service account principal, the command lists only the tokens that belong to the specified service account.
 
-`list`
-:   Lists all service account tokens defined in the `service_tokens` file. If you specify a service account principal, the command lists only the tokens that belong to the specified service account.
+**Properties of `list`**:
 
-    ::::{dropdown} Properties of `list`
-    `<service_account_principal>`
-    :   (Optional, string) Service account principal that takes the format of `<namespace>/<service>`, where the `namespace` is a top-level grouping of service accounts, and `service` is the name of the service. For example, `elastic/fleet-server`.
+`<service_account_principal>`
+:   (Optional, string) Service account principal that takes the format of `<namespace>/<service>`, where the `namespace` is a top-level grouping of service accounts, and `service` is the name of the service. For example, `elastic/fleet-server`.
 
-        The service account principal must match a known service account.
+    The service account principal must match a known service account.
 
+### `delete`
 
-    ::::
+Deletes a service account token for the specified service account.
 
+**Properties of `delete`**:
 
-`delete`
-:   Deletes a service account token for the specified service account.
+`<service_account_principal>`
+:   (Required, string) Service account principal that takes the format of `<namespace>/<service>`, where the `namespace` is a top-level grouping of service accounts, and `service` is the name of the service. For example, `elastic/fleet-server`.
 
-    ::::{dropdown} Properties of `delete`
-    `<service_account_principal>`
-    :   (Required, string) Service account principal that takes the format of `<namespace>/<service>`, where the `namespace` is a top-level grouping of service accounts, and `service` is the name of the service. For example, `elastic/fleet-server`.
-
-        The service account principal must match a known service account.
-
-
-    ::::
-
-
-    `<token_name>`
-    :   (Required, string) Name of an existing token.
+    The service account principal must match a known service account.
 
+`<token_name>`
+:   (Required, string) Name of an existing token.
 
 
 ## Examples [_examples_21]

docs/reference/elasticsearch/configuration-reference/monitoring-settings.md

@@ -220,26 +220,16 @@ You can configure the following TLS/SSL settings.
 `xpack.monitoring.exporters.$NAME.ssl.verification_mode`
 :   ([Static](docs-content://deploy-manage/deploy/self-managed/configure-elasticsearch.md#static-cluster-setting))  [7.16.0] Controls the verification of certificates.
 
-    ::::{dropdown} Valid values
-    `full`
-    :   Validates that the provided certificate: has an issue date that’s within the `not_before` and `not_after` dates; chains to a trusted Certificate Authority (CA); has a `hostname` or IP address that matches the names within the certificate.
-
-    `certificate`
-    :   Validates the provided certificate and verifies that it’s signed by a trusted authority (CA), but doesn’t check the certificate `hostname`.
-
-    `none`
-    :   Performs no certificate validation.
-
-        ::::{important}
-        Setting certificate validation to `none` disables many security benefits of SSL/TLS, which is very dangerous. Only set this value if instructed by Elastic Support as a temporary diagnostic mechanism when attempting to resolve TLS errors.
-        ::::
-
-
-    ::::
-
-
     Defaults to `full`.
 
+    **Valid values**:
+    * `full`: Validates that the provided certificate: has an issue date that’s within the `not_before` and `not_after` dates; chains to a trusted Certificate Authority (CA); has a `hostname` or IP address that matches the names within the certificate.
+    * `certificate`: Validates the provided certificate and verifies that it’s signed by a trusted authority (CA), but doesn’t check the certificate `hostname`.
+    * `none`: Performs no certificate validation.
+
+      ::::{important}
+      Setting certificate validation to `none` disables many security benefits of SSL/TLS, which is very dangerous. Only set this value if instructed by Elastic Support as a temporary diagnostic mechanism when attempting to resolve TLS errors.
+      ::::
 
 `xpack.monitoring.exporters.$NAME.ssl.cipher_suites`
 :   ([Static](docs-content://deploy-manage/deploy/self-managed/configure-elasticsearch.md#static-cluster-setting))  [7.16.0] Supported cipher suites vary depending on which version of Java you use. For example, for version 12 the default value is `TLS_AES_256_GCM_SHA384`, `TLS_AES_128_GCM_SHA256`, `TLS_CHACHA20_POLY1305_SHA256`, `TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384`, `TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256`, `TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384`, `TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256`, `TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256`, `TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256`, `TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384`, `TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256`, `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384`, `TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256`, `TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA`, `TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA`, `TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA`, `TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA`, `TLS_RSA_WITH_AES_256_GCM_SHA384`, `TLS_RSA_WITH_AES_128_GCM_SHA256`, `TLS_RSA_WITH_AES_256_CBC_SHA256`, `TLS_RSA_WITH_AES_128_CBC_SHA256`, `TLS_RSA_WITH_AES_256_CBC_SHA`, `TLS_RSA_WITH_AES_128_CBC_SHA`.