clean up

Author: colleenmcginnis

docs/reference/elasticsearch/index-settings/index-block.md

@@ -131,6 +131,7 @@ The following example shows how to add an index block:
 ```console
 PUT /my-index-000001/_block/write
 ```
+%  TEST[setup:my_index]
 
 The API returns following response:
 

docs/reference/elasticsearch/mapping-reference/aggregate-metric-double.md

@@ -250,7 +250,6 @@ PUT idx/_doc/1
   }
 }
 ```
-%  TEST[s/^/{"_source":/ s/\n$/}/]
 %  TEST[s/$/\nGET idx/_doc/1?filter_path=_source\n/]
 
 Will become:

docs/reference/elasticsearch/mapping-reference/keyword.md

@@ -151,7 +151,6 @@ PUT idx/_doc/1
   "kwd": ["foo", "foo", "bar", "baz"]
 }
 ```
-%  TEST[s/^/{"_source":/ s/\n$/}/]
 %  TEST[s/$/\nGET idx/_doc/1?filter_path=_source\n/]
 
 Will become:
@@ -199,6 +198,7 @@ Will become:
   "kwd": ["foo", "foo", "bar", "baz"]
 }
 ```
+%  TEST[s/^/{"_source":/ s/\n$/}/]
 
 Values longer than `ignore_above` are preserved but sorted to the end. For example:
 

docs/reference/elasticsearch/mapping-reference/mapping-source-field.md

@@ -246,7 +246,6 @@ PUT idx_keep/_doc/1
   "ids": [ 200, 100, 300, 100 ]
 }
 ```
-%  TEST[s/^/{"_source":/ s/\n$/}/]
 %  TEST[s/$/\nGET idx_keep/_doc/1?filter_path=_source\n/]
 
 returns the original source, with no array deduplication and sorting:
@@ -263,6 +262,7 @@ returns the original source, with no array deduplication and sorting:
   "ids": [ 200, 100, 300, 100 ]
 }
 ```
+%  TEST[s/^/{"_source":/ s/\n$/}/]
 
 The option for capturing the source of arrays can be applied at index level, by setting `index.mapping.synthetic_source_keep` to `arrays`. This applies to all objects and fields in the index, except for the ones with explicit overrides of `synthetic_source_keep` set to `none`. In this case, the storage overhead grows with the number and sizes of arrays present in source of each document, naturally.
 

docs/reference/elasticsearch/mapping-reference/range.md

@@ -121,7 +121,6 @@ The result produced by the above query.
 }
 ```
 %  TESTRESPONSE[s/"took": 13/"took" : $body.took/]
-%  TESTRESPONSE[s/"took": 13/"took" : $body.took/]
 
 The following is an example of a `date_range` query over the `date_range` field named "time_frame".
 
@@ -180,6 +179,7 @@ This query produces a similar result:
   }
 }
 ```
+%  TESTRESPONSE[s/"took": 13/"took" : $body.took/]
 
 ## IP Range [ip-range]
 

docs/reference/elasticsearch/mapping-reference/text.md

@@ -144,7 +144,6 @@ PUT idx/_doc/1
   ]
 }
 ```
-%  TEST[s/^/{"_source":/ s/\n$/}/]
 %  TEST[s/$/\nGET idx/_doc/1?filter_path=_source\n/]
 
 Will become:

docs/reference/enrich-processor/ingest-geo-grid-processor.md

@@ -125,7 +125,6 @@ PUT geocells/_doc/1?pipeline=geohex2shape
 GET geocells/_doc/1
 ```
 %  TEST[continued]
-%  TEST[continued]
 
 The response shows how the ingest-processor has replaced the `geocell` field with an indexable `geo_shape`:
 
@@ -183,6 +182,7 @@ PUT geocells/_doc/1?pipeline=geohex2shape
 
 GET geocells/_doc/1
 ```
+%  TEST[continued]
 
 The response from this index request:
 

docs/reference/search-connectors/api-tutorial.md

@@ -349,7 +349,6 @@ Use the [Get sync job API](https://www.elastic.co/docs/api/doc/elasticsearch/ope
 GET _connector/_sync_job?connector_id=my-connector-id&size=1
 ```
 %  TEST[skip:TODO]
-%  TEST[skip:TODO]
 
 The job document will be updated as the sync progresses, you can check it as often as you’d like to poll for updates.
 
@@ -377,6 +376,7 @@ Use the following command to inspect the latest sync job’s status:
 ```console
 GET _connector/_sync_job?connector_id=my-connector-id&size=1
 ```
+%  TEST[skip:TODO]
 
 If the connector encountered any errors during the sync, you’ll find these in the `error` field.
 

docs/reference/search-connectors/es-connectors-confluence.md

@@ -311,7 +311,6 @@ This connector supports [advanced sync rules](/reference/search-connectors/es-sy
 ]
 ```
 %  NOTCONSOLE
-%  NOTCONSOLE
 
 **Example 2**: Queries for indexing data based on `created` and `lastmodified` time.
 
@@ -326,7 +325,6 @@ This connector supports [advanced sync rules](/reference/search-connectors/es-sy
 ]
 ```
 %  NOTCONSOLE
-%  NOTCONSOLE
 
 **Example 3**: Query for indexing only given types in a **Space** with key *SD*.
 
@@ -338,7 +336,6 @@ This connector supports [advanced sync rules](/reference/search-connectors/es-sy
 ]
 ```
 %  NOTCONSOLE
-%  NOTCONSOLE
 
 ::::{note}
 Syncing recently created/updated items in Confluence may be delayed when using advanced sync rules, because the search endpoint used for CQL queries returns stale results in the response. For more details refer to the following issue in the [Confluence documentation](https://jira.atlassian.com/browse/CONFCLOUD-73997).

docs/reference/search-connectors/es-connectors-dropbox.md

@@ -341,7 +341,6 @@ $$$es-connectors-dropbox-client-sync-rules-advanced-example-1$$$
 ]
 ```
 %  NOTCONSOLE
-%  NOTCONSOLE
 
 $$$es-connectors-dropbox-client-sync-rules-advanced-example-2$$$
 **Example: Query with file extension filter**
@@ -360,7 +359,6 @@ $$$es-connectors-dropbox-client-sync-rules-advanced-example-2$$$
 ]
 ```
 %  NOTCONSOLE
-%  NOTCONSOLE
 
 $$$es-connectors-dropbox-client-sync-rules-advanced-example-3$$$
 **Example: Query with file category filter**
@@ -383,7 +381,6 @@ $$$es-connectors-dropbox-client-sync-rules-advanced-example-3$$$
 ]
 ```
 %  NOTCONSOLE
-%  NOTCONSOLE
 
 $$$es-connectors-dropbox-client-sync-rules-advanced-limitations$$$
 **Limitations**