Apply suggestions from code review

Author: georgewallace

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

@@ -87,11 +87,8 @@ The response contains buckets with document counts for each filter and combinati
   }
 }
 ```
-
 %  TESTRESPONSE[s/"took": 9/"took": $body.took/]
-
 %  TESTRESPONSE[s/"_shards": \.\.\./"_shards": $body._shards/]
-
 %  TESTRESPONSE[s/"hits": \.\.\./"hits": $body.hits/]
 
 

docs/reference/data-analysis/aggregations/search-aggregations-bucket-autodatehistogram-aggregation.md

@@ -28,7 +28,6 @@ POST /sales/_search?size=0
   }
 }
 ```
-
 %  TEST[setup:sales]
 
 ## Keys [_keys]
@@ -56,7 +55,6 @@ POST /sales/_search?size=0
   }
 }
 ```
-
 %  TEST[setup:sales]
 
 1. Supports expressive date [format pattern](/reference/data-analysis/aggregations/search-aggregations-bucket-daterange-aggregation.md#date-format-pattern)
@@ -91,7 +89,6 @@ Response:
   }
 }
 ```
-
 %  TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
 
 
@@ -188,7 +185,6 @@ UTC is used if no time zone is specified, three 1-hour buckets are returned star
   }
 }
 ```
-
 %  TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
 
 If a `time_zone` of `-01:00` is specified, then midnight starts at one hour before midnight UTC:
@@ -207,7 +203,6 @@ GET my-index-000001/_search?size=0
   }
 }
 ```
-
 %  TEST[continued]
 
 Now three 1-hour buckets are still returned but the first bucket starts at 11:00pm on 30 September 2015 since that is the local time for the bucket in the specified time zone.
@@ -239,7 +234,6 @@ Now three 1-hour buckets are still returned but the first bucket starts at 11:00
   }
 }
 ```
-
 %  TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
 
 1. The `key_as_string` value represents midnight on each day in the specified time zone.
@@ -280,7 +274,6 @@ POST /sales/_search?size=0
   }
 }
 ```
-
 %  TEST[setup:sales]
 
 
@@ -304,7 +297,6 @@ POST /sales/_search?size=0
   }
 }
 ```
-
 %  TEST[setup:sales]
 
 1. Documents without a value in the `publish_date` field will fall into the same bucket as documents that have the value `2000-01-01`.

docs/reference/data-analysis/aggregations/search-aggregations-bucket-children-aggregation.md

@@ -52,7 +52,6 @@ PUT child_example/_doc/1
   ]
 }
 ```
-
 %  TEST[continued]
 
 Examples of `answer` documents:
@@ -88,7 +87,6 @@ PUT child_example/_doc/3?routing=1&refresh
   "creation_date": "2009-05-05T13:45:37.030"
 }
 ```
-
 %  TEST[continued]
 
 The following request can be built that connects the two together:
@@ -121,7 +119,6 @@ POST child_example/_search?size=0
   }
 }
 ```
-
 %  TEST[continued]
 
 1. The `type` points to type / mapping with the name `answer`.
@@ -222,7 +219,6 @@ Possible response:
   }
 }
 ```
-
 %  TESTRESPONSE[s/"took": 25/"took": $body.took/]
 
 1. The number of question documents with the tag `file-transfer`, `windows-server-2003`, etc.

docs/reference/data-analysis/aggregations/search-aggregations-bucket-composite-aggregation.md

@@ -84,7 +84,6 @@ For example, consider the following document:
   "number": [23, 65, 76]
 }
 ```
-
 %  NOTCONSOLE
 
 Using `keyword` and `number` as source fields for the aggregation results in the following composite buckets:
@@ -97,7 +96,6 @@ Using `keyword` and `number` as source fields for the aggregation results in the
 { "keyword": "bar", "number": 65 }
 { "keyword": "bar", "number": 76 }
 ```
-
 %  NOTCONSOLE
 
 ## Value sources [_value_sources]
@@ -423,7 +421,6 @@ Instead of a single bucket starting at midnight, the above request groups the do
   }
 }
 ```
-
 %  TESTRESPONSE[s/\.\.\./"took": $body.took,"timed_out": false,"_shards": $body._shards,"hits": $body.hits,/]
 
 ::::{note}
@@ -628,7 +625,6 @@ GET /_search
   }
 }
 ```
-
 %  TEST[s/_search/_search\?filter_path=aggregations/]
 
 ... returns:
@@ -662,7 +658,6 @@ GET /_search
   }
 }
 ```
-
 %  TESTRESPONSE[s/\.\.\.//]
 
 To get the next set of buckets, resend the same aggregation with the `after` parameter set to the `after_key` value returned in the response. For example, this request uses the `after_key` value provided in the previous response:
@@ -828,7 +823,6 @@ GET /_search
   }
 }
 ```
-
 %  TEST[s/_search/_search\?filter_path=aggregations/]
 
 ... returns:
@@ -888,7 +882,6 @@ GET /_search
   }
 }
 ```
-
 %  TESTRESPONSE[s/\.\.\.//]
 
 

docs/reference/elasticsearch/mapping-reference/search-as-you-type.md

@@ -51,7 +51,7 @@ PUT my-index-000001/_doc/1?refresh
 
 %  TEST[continued]
 
-The most efficient way of querying to serve a search-as-you-type use case is usually a [`multi_match`](query-dsl-multi-match-query.md) query of type [`bool_prefix`](query-dsl-match-bool-prefix-query.md) that targets the root `search_as_you_type` field and its shingle subfields. This can match the query terms in any order, but will score documents higher if they contain the terms in order in a shingle subfield.
+The most efficient way of querying to serve a search-as-you-type use case is usually a [`multi_match`](/reference/query-languages/query-dsl-multi-match-query.md) query of type [`bool_prefix`](/reference/query-languages/query-dsl-match-bool-prefix-query.md) that targets the root `search_as_you_type` field and its shingle subfields. This can match the query terms in any order, but will score documents higher if they contain the terms in order in a shingle subfield.
 
 ```console
 GET my-index-000001/_search
@@ -123,7 +123,7 @@ GET my-index-000001/_search
 
 %  TESTRESPONSE[s/"_score" : 0.8630463/"_score" : $body.hits.hits.0._score/]
 
-To search for documents that strictly match the query terms in order, or to search using other properties of phrase queries, use a [`match_phrase_prefix` query](query-dsl-match-query-phrase-prefix.md) on the root field. A [`match_phrase` query](query-dsl-match-query-phrase.md) can also be used if the last term should be matched exactly, and not as a prefix. Using phrase queries may be less efficient than using the `match_bool_prefix` query.
+To search for documents that strictly match the query terms in order, or to search using other properties of phrase queries, use a [`match_phrase_prefix` query](/reference/query-languages/query-dsl-match-query-phrase-prefix.md) on the root field. A [`match_phrase` query](/reference/query-languages/query-dsl-match-query-phrase.md) can also be used if the last term should be matched exactly, and not as a prefix. Using phrase queries may be less efficient than using the `match_bool_prefix` query.
 
 ```console
 GET my-index-000001/_search
@@ -155,8 +155,8 @@ More subfields enables more specific queries but increases index size.
 
 The following parameters are accepted in a mapping for the `search_as_you_type` field due to its nature as a text-like field, and behave similarly to their behavior when configuring a field of the [`text`](text.md) data type. Unless otherwise noted, these options configure the root fields subfields in the same way.
 
-[`analyzer`](analyzer.md)
-:   The [analyzer](analysis.md) which should be used for `text` fields, both at index-time and at search-time (unless overridden by the [`search_analyzer`](search-analyzer.md)). Defaults to the default index analyzer, or the [`standard` analyzer](analysis-standard-analyzer.md).
+[`analyzer`](/reference/elasticsearch/mapping-reference/analyzer.md)
+: The [analyzer](docs-content://manage-data/data-store/text-analysis.md) which should be used for `text` fields, both at index-time and at search-time (unless overridden by the [`search_analyzer`](/reference/elasticsearch/mapping-reference/search-analyzer.md)). Defaults to the default index analyzer, or the [`standard` analyzer](/reference/data-analysis/text-analysis/analysis-standard-analyzer.md).
 
 [`index`](mapping-index.md)
 :   Should the field be searchable? Accepts `true` (default) or `false`.
@@ -185,7 +185,7 @@ The following parameters are accepted in a mapping for the `search_as_you_type`
 
 ## Optimization of prefix queries [prefix-queries]
 
-When making a [`prefix`](query-dsl-prefix-query.md) query to the root field or any of its subfields, the query will be rewritten to a [`term`](query-dsl-term-query.md) query on the `._index_prefix` subfield. This matches more efficiently than is typical of `prefix` queries on text fields, as prefixes up to a certain length of each shingle are indexed directly as terms in the `._index_prefix` subfield.
+When making a [`prefix`](/reference/query-languages/query-dsl-prefix-query.md) query to the root field or any of its subfields, the query will be rewritten to a [`term`](/reference/query-languages/query-dsl-term-query.md) query on the `._index_prefix` subfield. This matches more efficiently than is typical of `prefix` queries on text fields, as prefixes up to a certain length of each shingle are indexed directly as terms in the `._index_prefix` subfield.
 
 The analyzer of the `._index_prefix` subfield slightly modifies the shingle-building behavior to also index prefixes of the terms at the end of the field’s value that normally would not be produced as shingles. For example, if the value `quick brown fox` is indexed into a `search_as_you_type` field with `max_shingle_size` of 3, prefixes for `brown fox` and `fox` are also indexed into the `._index_prefix` subfield even though they do not appear as terms in the `._3gram` subfield. This allows for completion of all the terms in the field’s input.