little formatting thingies

Author: shainaraskas

deploy-manage/remote-clusters/ec-enable-ccs-for-eck.md

@@ -78,7 +78,7 @@ The first step is to establish trust between the two clusters.
 
 
 
-## Setup CCS/R [ec_setup_ccsr]
+## Set up CCS/R [ec_setup_ccsr]
 
 Now that trust has been established, you can set up CCS/R from the ECK cluster to the {{ech}} cluster or from the {{ech}} cluster to the ECK cluster.
 

deploy-manage/remote-clusters/ec-remote-cluster-ece.md

@@ -34,20 +34,20 @@ On the local cluster side, not every local user needs to access every piece of d
 If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsearch/remote-clusters.md).
 
 
-#### Prerequisites and limitations [ec_prerequisites_and_limitations_3]
+### Prerequisites and limitations [ec_prerequisites_and_limitations_3]
 
 * The local and remote deployments must be on {{stack}} 8.14 or later.
 * API key authentication can’t be used in combination with traffic filters.
 * Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other.
 
 
-#### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment_3]
+### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment_3]
 
 * On the deployment you will use as remote, use the [{{es}} API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-create-cross-cluster-api-key) or [{{kib}}](../api-keys/elasticsearch-api-keys.md) to create a cross-cluster API key. Configure it with access to the indices you want to use for {{ccs}} or {{ccr}}.
 * Copy the encoded key (`encoded` in the response) to a safe location. You will need it in the next step.
 
 
-#### Configure the local deployment [ec_configure_the_local_deployment]
+### Configure the local deployment [ec_configure_the_local_deployment]
 
 The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
 
@@ -126,7 +126,7 @@ If you later need to update the remote connection with different permissions, yo
 ::::::
 
 ::::::{tab-item} TLS certificate (deprecated)
-#### Configuring trust with clusters of an {{ece}} environment [ec-trust-ece]
+### Configuring trust with clusters of an {{ece}} environment [ec-trust-ece]
 
 A deployment can be configured to trust all or specific deployments in a remote ECE environment:
 

deploy-manage/remote-clusters/ec-remote-cluster-other-ess.md

@@ -33,20 +33,20 @@ On the local cluster side, not every local user needs to access every piece of d
 If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsearch/remote-clusters.md).
 
 
-#### Prerequisites and limitations [ec_prerequisites_and_limitations_2]
+### Prerequisites and limitations [ec_prerequisites_and_limitations_2]
 
 * The local and remote deployments must be on {{stack}} 8.14 or later.
 * API key authentication can’t be used in combination with traffic filters.
 * Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other.
 
 
-#### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment_2]
+### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment_2]
 
 * On the deployment you will use as remote, use the [{{es}} API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-create-cross-cluster-api-key) or [{{kib}}](../api-keys/elasticsearch-api-keys.md) to create a cross-cluster API key. Configure it with access to the indices you want to use for {{ccs}} or {{ccr}}.
 * Copy the encoded key (`encoded` in the response) to a safe location. You will need it in the next step.
 
 
-#### Add the cross-cluster API key to the keystore of the local deployment [ec_add_the_cross_cluster_api_key_to_the_keystore_of_the_local_deployment_2]
+### Add the cross-cluster API key to the keystore of the local deployment [ec_add_the_cross_cluster_api_key_to_the_keystore_of_the_local_deployment_2]
 
 The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
 
@@ -76,7 +76,7 @@ If you later need to update the remote connection with different permissions, yo
 ::::::
 
 ::::::{tab-item} TLS certificate (deprecated)
-#### Specify the deployments trusted to be used as remote clusters [ec-trust-other-organization]
+### Specify the deployments trusted to be used as remote clusters [ec-trust-other-organization]
 
 A deployment can be configured to trust all or specific deployments in another {{ech}} [organization](../users-roles/cloud-organization.md). To add cross-organization trust:
 

deploy-manage/remote-clusters/ec-remote-cluster-self-managed.md

@@ -34,20 +34,20 @@ On the local cluster side, not every local user needs to access every piece of d
 If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsearch/remote-clusters.md).
 
 
-#### Prerequisites and limitations [ec_prerequisites_and_limitations_4]
+### Prerequisites and limitations [ec_prerequisites_and_limitations_4]
 
 * The local and remote deployments must be on {{stack}} 8.14 or later.
 * API key authentication can’t be used in combination with traffic filters.
 * Contrary to the certificate security model, the API key security model does not require that both local and remote clusters trust each other.
 
 
-#### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment_4]
+### Create a cross-cluster API key on the remote deployment [ec_create_a_cross_cluster_api_key_on_the_remote_deployment_4]
 
 * On the deployment you will use as remote, use the [{{es}} API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-create-cross-cluster-api-key) or [{{kib}}](../api-keys/elasticsearch-api-keys.md) to create a cross-cluster API key. Configure it with access to the indices you want to use for {{ccs}} or {{ccr}}.
 * Copy the encoded key (`encoded` in the response) to a safe location. You will need it in the next step.
 
 
-#### Configure the local deployment [ec_configure_the_local_deployment_2]
+### Configure the local deployment [ec_configure_the_local_deployment_2]
 
 The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
 
@@ -116,7 +116,7 @@ If you later need to update the remote connection with different permissions, yo
 ::::::
 
 ::::::{tab-item} TLS certificate (deprecated)
-#### Specify the deployments trusted to be used as remote clusters [ec-trust-self-managed]
+### Specify the deployments trusted to be used as remote clusters [ec-trust-self-managed]
 
 A deployment can be configured to trust all or specific deployments in any environment:
 
@@ -176,7 +176,7 @@ Generate new node certificates for an entire cluster using the file input mode o
 ::::
 
 
-::::{dropdown} **Using the API**
+::::{dropdown} Using the API
 You can update a deployment using the appropriate trust settings for the {{es}} payload.
 
 In order to trust a cluster whose nodes present certificates with the subject names: "CN = node1.example.com", "CN = node2.example.com" and "CN = node3.example.com" in a self-managed environment, you could update the trust settings with an additional direct trust relationship like this:

deploy-manage/remote-clusters/ece-enable-ccs-for-eck.md

@@ -78,7 +78,7 @@ The first step is to establish trust between the two clusters.
 
 
 
-## Setup CCS/R [ece_setup_ccsr]
+## Set up CCS/R [ece_setup_ccsr]
 
 Now that trust has been established, you can set up CCS/R from the ECK cluster to the {{ece}} cluster or from the {{ece}} cluster to the ECK cluster.
 

deploy-manage/remote-clusters/ece-remote-cluster-other-ece.md

@@ -2,7 +2,7 @@
 applies_to:
   deployment:
     ece: ga
-navigation_title: With a different {{ece}} environment
+navigation_title: With a different ECE environment
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-remote-cluster-other-ece.html
 ---

deploy-manage/remote-clusters/ece-remote-cluster-same-ece.md

@@ -2,7 +2,7 @@
 applies_to:
   deployment:
     ece: ga
-navigation_title: Within the same {{ece}} environment
+navigation_title: Within the same ECE environment
 mapped_pages:
   - https://www.elastic.co/guide/en/cloud-enterprise/current/ece-remote-cluster-same-ece.html
 ---

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

@@ -22,7 +22,7 @@ The remote clusters feature requires a valid Enterprise license or Enterprise tr
 
 To create a remote cluster connection to another {{es}} cluster deployed within the same Kubernetes cluster, specify the `remoteClusters` attribute in your {{es}} spec.
 
-### Security Models [k8s_security_models]
+### Security models [k8s_security_models]
 
 Before you start, consider the security model that you would prefer to use for authenticating remote connections between clusters, and follow the corresponding steps.
 

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

@@ -253,7 +253,7 @@ The following requests use the [create or update roles API](https://www.elastic.
 The {{ccr}} user requires different cluster and index privileges on the remote cluster and local cluster. Use the following requests to create separate roles on the local and remote clusters, and then create a user with the required roles.
 
 
-##### Remote cluster [_remote_cluster]
+#### Remote cluster [_remote_cluster]
 
 On the remote cluster that contains the leader index, the {{ccr}} role requires the `read_ccr` cluster privilege, and `monitor` and `read` privileges on the leader index.
 
@@ -290,7 +290,7 @@ POST /_security/role/remote-replication
 ```
 
 
-##### Local cluster [_local_cluster]
+#### Local cluster [_local_cluster]
 
 On the local cluster that contains the follower index, the `remote-replication` role requires the `manage_ccr` cluster privilege, and `monitor`, `read`, `write`, and `manage_follow_index` privileges on the follower index.
 
@@ -341,7 +341,7 @@ You can then [configure {{ccr}}](../tools/cross-cluster-replication/set-up-cross
 The {{ccs}} user requires different cluster and index privileges on the remote cluster and local cluster. The following requests create separate roles on the local and remote clusters, and then create a user with the required roles.
 
 
-##### Remote cluster [_remote_cluster_2]
+#### Remote cluster [_remote_cluster_2]
 
 On the remote cluster, the {{ccs}} role requires the `read` and `read_cross_cluster` privileges for the target indices.
 
@@ -375,7 +375,7 @@ POST /_security/role/remote-search
 ```
 
 
-##### Local cluster [_local_cluster_2]
+#### Local cluster [_local_cluster_2]
 
 On the local cluster, which is the cluster used to initiate cross cluster search, a user only needs the `remote-search` role. The role privileges can be empty.
 
@@ -418,7 +418,7 @@ To grant users read access on the remote data streams and indices, you must crea
 For example, you might be actively indexing {{ls}} data on a local cluster and and periodically offload older time-based indices to an archive on your remote cluster. You want to search across both clusters, so you must enable {{kib}} users on both clusters.
 
 
-##### Local cluster [_local_cluster_3]
+#### Local cluster [_local_cluster_3]
 
 On the local cluster, create a `logstash-reader` role that grants `read` and `view_index_metadata` privileges on the local `logstash-*` indices.
 
@@ -458,7 +458,7 @@ PUT /_security/user/cross-cluster-kibana
 ```
 
 
-##### Remote cluster [_remote_cluster_3]
+#### Remote cluster [_remote_cluster_3]
 
 On the remote cluster, create a `logstash-reader` role that grants the `read_cross_cluster` privilege and `read` and `view_index_metadata` privileges for the `logstash-*` indices.