extra snippet and refinement

Author: eedugon

deploy-manage/remote-clusters/_snippets/apikeys-local-ece-remote-private.md

@@ -18,13 +18,13 @@ It requires remote_type substitution to be defined
 
     1. Fill both fields.
 
-        * For the **Setting name**, enter the alias of your choice. You will use this alias to connect to the remote cluster later. It must be lowercase and only contain letters, numbers, dashes and underscores.
-        * For the **Secret**, paste the encoded cross-cluster API key.
+        * For the **Remote cluster name**, enter the alias of your choice. You will use this alias to connect to the remote cluster later. It must be lowercase and only contain letters, numbers, dashes and underscores.
+        * For the **Cross-cluster API key**, paste the encoded cross-cluster API key.
 
     2. Click **Add** to save the API key to the keystore.
     3. Repeat these steps for each API key you want to add. For example, if you want to use several clusters of the remote environment for CCR or CCS.
 
-8. Add the CA certificate of the remote deployment or cluster.
+8. Add the CA certificate of the remote environment.
 9. Provide a name for the trusted environment. That name will appear in the trust summary of your deployment's **Security** page.
 10. Select **Create trust** to complete the configuration.
 11. Restart the local deployment to reload the keystore with its new setting. To do that, go to the deployment's main page, locate the **Actions** menu, and select **Restart {{es}}**.

deploy-manage/remote-clusters/_snippets/apikeys-local-ech-remote-private.md

@@ -24,7 +24,7 @@ It requires remote_type substitution to be defined
     2. Click **Add** to save the API key to the keystore.
     3. Repeat these steps for each API key you want to add. For example, if you want to use several clusters of the remote environment for CCR or CCS.
 
-8. Add the CA certificate of the remote deployment or cluster.
+8. Add the CA certificate of the remote environment.
 9. Provide a name for the trusted environment. That name will appear in the trust summary of your deployment's **Security** page.
 10. Select **Create trust** to complete the configuration.
 11. Restart the local deployment to reload the keystore with its new setting. To do that, go to the deployment's main page, locate the **Actions** menu, and select **Restart {{es}}**.

deploy-manage/remote-clusters/_snippets/retrieve-ece-ca.md

@@ -0,0 +1,14 @@
+Before configuring the local deployment, retrieve the CA certificate of the remote ECE proxy. To find this certificate:
+
+1. In the remote ECE environment, go to **Platform > Settings > TLS certificates**.
+2. Select **Show certificate chain** under **Proxy**.
+3. Click **Copy root certificate** and paste it into a new file. The root certificate is the last certificate shown in the chain.
+
+    :::{image} /deploy-manage/images/cloud-remote-clusters-proxy-certificate.png
+    :alt: Certificate to copy from the chain
+    :::
+
+4. Save that file as `.crt`.
+
+You can now proceed to configure the local deployment. The CA file you just saved will be used in one of the following steps.
+

deploy-manage/remote-clusters/ec-edit-remove-trusted-environment.md

@@ -72,13 +72,13 @@ If you need to update the permissions granted by a cross-cluster API key for a r
 4. Locate the API key currently used for connecting to the remote cluster, copy its current alias, and delete it.
 5. Add the new API key by selecting **Add API key**.
 
-    * For the **Setting name**, enter the same alias that was used for the previous key.
+    * For the **Remote cluster name**, enter the same alias that was used for the previous key.
 
       ::::{note}
       If you use a different alias, you also need to re-create the remote cluster in {{kib}} with a **Name** that matches the new alias.
       ::::
 
-    * For the **Secret**, paste the encoded cross-cluster API key, then click **Add** to save the API key to the keystore.
+    * For the **Cross-cluster API key**, paste the encoded cross-cluster API key, then click **Add** to save the API key to the keystore.
 
 6. Restart the local deployment to reload the keystore with its new setting. To do that, go to the deployment’s main page (named after your deployment’s name), locate the **Actions** menu, and select **Restart {{es}}**.<br>
 

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

@@ -63,19 +63,8 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo
 
 ::::{dropdown} The CA is private
 
-Before configuring the local deployment, retrieve the CA certificate of the remote {{ece}} environment’s proxy or load-balancing infrastructure. To find this certificate:
-
-1. In the remote {{ece}} environment, go to **Platform > Settings > TLS certificates**.
-2. Select **Show certificate chain** under **Proxy**.
-3. Click **Copy root certificate** and paste it into a new file. The root certificate is the last certificate shown in the chain.
-
-    :::{image} /deploy-manage/images/cloud-remote-clusters-proxy-certificate.png
-    :alt: Certificate to copy from the chain
-    :::
-
-4. Save that file as `.crt`.
-
-You can now proceed to configure the local deployment. The CA file you just saved will be used in one of the following steps.
+:::{include} _snippets/retrieve-ece-ca.md
+:::
 
 :::{include} _snippets/apikeys-local-ech-remote-private.md
 :::

deploy-manage/remote-clusters/ece-edit-remove-trusted-environment.md

@@ -68,17 +68,17 @@ If you need to update the permissions granted by a cross-cluster API key for a r
 
 1. 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 with the appropriate permissions. Configure it with access to the indices you want to use for {{ccs}} or {{ccr}}.
 2. Copy the encoded key (`encoded` in the response) to a safe location. You will need it in the next steps.
-3. Go to the **Security** page of the local deployment and locate the **Remote connections** section.
+3. From the navigation menu, select **Security** and locate the **Remote connections** section.
 4. Locate the API key currently used for connecting to the remote cluster, copy its current alias, and delete it.
-5. Add the new API key by selecting **Add an API key**.
+5. Add the new API key by selecting **Add API key**.
 
-   * For the **Setting name**, enter the same alias that was used for the previous key.
+    * For the **Remote cluster name**, enter the same alias that was used for the previous key.
 
-     ::::{note}
-     If you use a different alias, you also need to re-create the remote cluster in {{kib}} with a **Name** that matches the new alias.
-     ::::
+      ::::{note}
+      If you use a different alias, you also need to re-create the remote cluster in {{kib}} with a **Name** that matches the new alias.
+      ::::
 
-   * For the **Secret**, paste the encoded cross-cluster API key, then click **Add** to save the API key to the keystore.
+    * For the **Cross-cluster API key**, paste the encoded cross-cluster API key, then click **Add** to save the API key to the keystore.
 
 6. Restart the local deployment to reload the keystore with its new setting. To do that, go to the deployment’s main page (named after your deployment’s name), locate the **Actions** menu, and select **Restart {{es}}**.<br>
 

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

@@ -62,19 +62,8 @@ The steps to follow depend on whether the Certificate Authority (CA) of the remo
 
 ::::{dropdown} The CA is private
 
-Before configuring the local deployment, retrieve the CA certificate of the remote {{ece}} environment's proxy or load-balancing infrastructure. To find this certificate:
-
-1. In the remote {{ece}} environment, go to **Platform > Settings > TLS certificates**.
-2. Select **Show certificate chain** under **Proxy**.
-3. Click **Copy root certificate** and paste it into a new file. The root certificate is the last certificate shown in the chain.
-
-    :::{image} /deploy-manage/images/cloud-enterprise-remote-clusters-proxy-certificate.png
-    :alt: Certificate to copy from the chain
-    :::
-
-4. Save that file as `.crt`.
-
-You can now proceed to configure the local deployment. The CA file you just saved will be used in one of the following steps.
+:::{include} _snippets/retrieve-ece-ca.md
+:::
 
 :::{include} _snippets/apikeys-local-ece-remote-private.md
 :::