fixing issues

Author: georgewallace

deploy-manage/deploy/self-managed/install-elasticsearch-from-archive-on-linux-macos.md

@@ -69,11 +69,10 @@ curl https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-9.0.0-be
 tar -xzf elasticsearch-9.0.0-beta1-darwin-x86_64.tar.gz
 cd elasticsearch-9.0.0-beta1/ <2>
 ```
-%  NOTCONSOLE
 
 1. Compares the SHA of the downloaded `.tar.gz` archive and the published checksum, which should output `elasticsearch-{{version}}-darwin-x86_64.tar.gz: OK`.
 2. This directory is known as `$ES_HOME`.
-
+%  NOTCONSOLE
 
 
 ## Enable automatic creation of system indices [targz-enable-indices]
@@ -165,11 +164,10 @@ You can test that your {{es}} node is running by sending an HTTPS request to por
 ```sh
 curl --cacert $ES_HOME/config/certs/http_ca.crt -u elastic:$ELASTIC_PASSWORD https://localhost:9200 <1>
 ```
-%  NOTCONSOLE
 
 1. Ensure that you use `https` in your call, or the request will fail.`--cacert`
 :   Path to the generated `http_ca.crt` certificate for the HTTP layer.
-
+%  NOTCONSOLE
 
 
 The call returns a response like this:

deploy-manage/deploy/self-managed/install-elasticsearch-with-debian-package.md

@@ -211,11 +211,10 @@ You can test that your {{es}} node is running by sending an HTTPS request to por
 ```sh
 curl --cacert /etc/elasticsearch/certs/http_ca.crt -u elastic:$ELASTIC_PASSWORD https://localhost:9200 <1>
 ```
-%  NOTCONSOLE
 
 1. Ensure that you use `https` in your call, or the request will fail.`--cacert`
 :   Path to the generated `http_ca.crt` certificate for the HTTP layer.
-
+%  NOTCONSOLE
 
 
 The call returns a response like this:

deploy-manage/deploy/self-managed/install-elasticsearch-with-rpm.md

@@ -215,11 +215,10 @@ You can test that your {{es}} node is running by sending an HTTPS request to por
 ```sh
 curl --cacert /etc/elasticsearch/certs/http_ca.crt -u elastic:$ELASTIC_PASSWORD https://localhost:9200 <1>
 ```
-%  NOTCONSOLE
 
 1. Ensure that you use `https` in your call, or the request will fail.`--cacert`
 :   Path to the generated `http_ca.crt` certificate for the HTTP layer.
-
+%  NOTCONSOLE
 
 
 The call returns a response like this:

deploy-manage/deploy/self-managed/install-elasticsearch-with-zip-on-windows.md

@@ -142,11 +142,10 @@ You can test that your {{es}} node is running by sending an HTTPS request to por
 ```sh
 curl --cacert %ES_HOME%\config\certs\http_ca.crt -u elastic:$ELASTIC_PASSWORD https://localhost:9200 <1>
 ```
-%  NOTCONSOLE
 
 1. Ensure that you use `https` in your call, or the request will fail.`--cacert`
 :   Path to the generated `http_ca.crt` certificate for the HTTP layer.
-
+%  NOTCONSOLE
 
 
 The call returns a response like this:

deploy-manage/remote-clusters/remote-clusters-api-key.md

@@ -167,12 +167,11 @@ PUT /_cluster/settings
   }
 }
 ```
-%  TEST[setup:host]
-%  TEST[s/127.0.0.1:{{remote-interface-default-port}}/${transport_host}/]
 
 1. The cluster alias of this remote cluster is `cluster_one`.
 2. Specifies the hostname and remote cluster port of a seed node in the remote cluster.
-
+%  TEST[setup:host]
+%  TEST[s/127.0.0.1:{{remote-interface-default-port}}/${transport_host}/]
 
 You can use the [remote cluster info API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-remote-info) to verify that the local cluster is successfully connected to the remote cluster:
 
@@ -199,15 +198,14 @@ The API response indicates that the local cluster is connected to the remote clu
   }
 }
 ```
-%  TESTRESPONSE[s/127.0.0.1:{{remote-interface-default-port}}/$body.cluster_one.seeds.0/]
-%  TESTRESPONSE[s/ifeval::(.|\n)*endif::[]//]
-%  TEST[s/"connected" : true/"connected" : $body.cluster_one.connected/]
-%  TEST[s/"num_nodes_connected" : 1/"num_nodes_connected" : $body.cluster_one.num_nodes_connected/]
 
 1. The number of nodes in the remote cluster the local cluster is connected to.
 2. Indicates whether to skip the remote cluster if searched through {{ccs}} but no nodes are available.
 3. If present, indicates the remote cluster has connected using API key authentication.
-
+%  TESTRESPONSE[s/127.0.0.1:{{remote-interface-default-port}}/$body.cluster_one.seeds.0/]
+%  TESTRESPONSE[s/ifeval::(.|\n)*endif::[]//]
+%  TEST[s/"connected" : true/"connected" : $body.cluster_one.connected/]
+%  TEST[s/"num_nodes_connected" : 1/"num_nodes_connected" : $body.cluster_one.num_nodes_connected/]
 
 ### Dynamically configure remote clusters [_dynamically_configure_remote_clusters]
 

deploy-manage/remote-clusters/remote-clusters-cert.md

@@ -85,12 +85,11 @@ PUT /_cluster/settings
   }
 }
 ```
-%  TEST[setup:host]
-%  TEST[s/127.0.0.1:{{remote-interface-default-port}}/${transport_host}/]
 
 1. The cluster alias of this remote cluster is `cluster_one`.
 2. Specifies the hostname and transport port of a seed node in the remote cluster.
-
+%  TEST[setup:host]
+%  TEST[s/127.0.0.1:{{remote-interface-default-port}}/${transport_host}/]
 
 You can use the [remote cluster info API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-remote-info) to verify that the local cluster is successfully connected to the remote cluster:
 
@@ -116,15 +115,14 @@ The API response indicates that the local cluster is connected to the remote clu
   }
 }
 ```
+
+1. The number of nodes in the remote cluster the local cluster is connected to.
+2. Indicates whether to skip the remote cluster if searched through {{ccs}} but no nodes are available.
 %  TESTRESPONSE[s/127.0.0.1:{{remote-interface-default-port}}/$body.cluster_one.seeds.0/]
 %  TESTRESPONSE[s/ifeval::(.|\n)*endif::[]//]
 %  TEST[s/"connected" : true/"connected" : $body.cluster_one.connected/]
 %  TEST[s/"num_nodes_connected" : 1/"num_nodes_connected" : $body.cluster_one.num_nodes_connected/]
 
-1. The number of nodes in the remote cluster the local cluster is connected to.
-2. Indicates whether to skip the remote cluster if searched through {{ccs}} but no nodes are available.
-
-
 ### Dynamically configure remote clusters [_dynamically_configure_remote_clusters_2]
 
 Use the [cluster update settings API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-put-settings) to dynamically configure remote settings on every node in the cluster. The following request adds three remote clusters: `cluster_one`, `cluster_two`, and `cluster_three`.

deploy-manage/tools/snapshot-and-restore/create-snapshots.md

@@ -353,11 +353,10 @@ PUT _slm/policy/nightly-cluster-state-snapshots
   }
 }
 ```
-%  TEST[s/my_secure_repository/my_repository/]
 
 1. Includes the cluster state. This also includes all feature states by default.
 2. Excludes regular data streams and indices.
-
+%  TEST[s/my_secure_repository/my_repository/]
 
 If you take dedicated snapshots of the cluster state, you’ll need to exclude the cluster state from your other snapshots. For example:
 

deploy-manage/tools/snapshot-and-restore/restore-snapshot.md

@@ -198,15 +198,14 @@ POST _snapshot/my_repository/my_snapshot_2099.05.06/_restore
   "indices": "-*"                   <2>
 }
 ```
+
+1. Exclude the cluster state from the restore operation.
+2. Exclude the other indices and data streams in the snapshot from the restore operation.
 %  TEST[setup:setup-snapshots]
 %  TEST[s/^/DELETE my-index\nDELETE _data_stream/logs-my_app-default\n/]
 %  TEST[s/_restore/_restore?wait_for_completion=true/]
 %  TEST[s/"feature_states": [ "geoip" ],//]
 
-1. Exclude the cluster state from the restore operation.
-2. Exclude the other indices and data streams in the snapshot from the restore operation.
-
-
 
 ## Restore an entire cluster [restore-entire-cluster]
 

deploy-manage/tools/snapshot-and-restore/shared-file-system-repository.md

@@ -78,7 +78,6 @@ PUT _snapshot/my_fs_backup
 ```
 %  TEST[skip:no access to path]
 ::::::
-::::::
 
 ::::::{tab-item} Windows
 Windows installations support both DOS and Microsoft UNC paths. Escape any backslashes in the paths. For UNC paths, provide the server and share name as a prefix.
@@ -141,7 +140,6 @@ PUT _snapshot/my_fs_backup
 ```
 %  TEST[skip:no access to path]
 ::::::
-::::::
 
 :::::::
 ## Repository settings [filesystem-repository-settings]

deploy-manage/users-roles/cluster-or-deployment-auth/service-accounts.md

@@ -103,9 +103,8 @@ A successful authentication response includes a `token` field, which contains a
   "authentication_type": "token"
 }
 ```
-%  NOTCONSOLE
 
 1. Name of the service account token.
 2. Type of service account token. The value always begins with `_service_account_` and is followed by a string that indicates the service token backend in use (can be either `file` or `index`).
-
+%  NOTCONSOLE