Apply suggestions from code review

Co-authored-by: shainaraskas <[email protected]>

Author: eedugon

deploy-manage/remote-clusters/_snippets/rcs-elasticsearch-api-snippet.md

@@ -15,7 +15,7 @@ To configure a deployment as a remote cluster, use the [cluster update settings
 * `proxy_address`: This value can be found on the **Security** page of the {{remote_type}} you want to use as a remote. Copy the **Proxy address** from the **Remote cluster parameters** section. Also, using the API, this value can be obtained from the {{es}} resource info, concatenating the field `metadata.endpoint` and port `9400` using a semicolon.
 
   ::::{note}
-  If you’re using API keys as security model, change the port into `9443`.
+  If you’re using API keys as security model, change the port to `9443`.
   ::::
 
 * `server_name`: This value can be found on the **Security** page of the {{remote_type}} you want to use as a remote. Copy the **Server name** from the **Remote cluster parameters** section. Also, using the API, this can be obtained from the {{es}} resource info field `metadata.endpoint`.

deploy-manage/remote-clusters/_snippets/rcs-kibana-api-snippet.md

@@ -9,7 +9,8 @@ This snippet is in use in the following locations:
 
 It requires remote_type substitution to be defined
 -->
-1. Open the {{kib}} main menu, and select **Stack Management > Data > Remote Clusters > Add a remote cluster**.
+1. Go to the **Remote Clusters** management page in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+2. Select **Add a remote cluster**.
 2. In **Select connection type**, choose the authentication mechanism you prepared earlier (**API keys** or **Certificates**), and then click **Next**.
 3. In **Add connection information**, fill in the following fields:
 
@@ -20,7 +21,7 @@ It requires remote_type substitution to be defined
     * **Remote address**: This value can be found on the **Security** page of the {{remote_type}} you want to use as a remote. Copy the **Proxy address** from the **Remote cluster parameters** section.
 
       ::::{note}
-      If you’re using API keys as security model, change the port into `9443`.
+      If you’re using API keys as security model, change the port to `9443`.
       ::::
 
     * **Configure advanced options** (optional): Expand this section if you need to customize additional settings.
@@ -30,7 +31,7 @@ It requires remote_type substitution to be defined
 
       * **Socket connections**: Define the number of connections to open with the remote cluster.
 
-    For a full list of available client connection settings, refer to [remote cluster settings reference](elasticsearch://reference/elasticsearch/configuration-reference/remote-clusters.md#remote-cluster-proxy-settings).
+    For a full list of available client connection settings, refer to the [remote cluster settings reference](elasticsearch://reference/elasticsearch/configuration-reference/remote-clusters.md#remote-cluster-proxy-settings).
 
 4. Click **Next**.
 5. In **Confirm setup**, click **Add remote cluster** (you have already established trust in a previous step).

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

@@ -180,7 +180,7 @@ snippet:
 :::{include} _snippets/rcs-elasticsearch-api-snippet.md
 :::
 
-### Using the {{ecloud}} RESTful API [ec_using_the_elasticsearch_service_restful_api]
+### Using the {{ecloud}} API [ec_using_the_elasticsearch_service_restful_api]
 ```{applies_to}
 deployment:
   ess: deprecated

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

@@ -191,7 +191,7 @@ If you’re having issues establishing the connection and the remote cluster is
 :::{include} _snippets/rcs-elasticsearch-api-snippet.md
 :::
 
-### Using the {{ece}} RESTful API [ece_using_the_elastic_cloud_enterprise_restful_api]
+### Using the {{ece}} API [ece_using_the_elastic_cloud_enterprise_restful_api]
 ```{applies_to}
 deployment:
   ece: deprecated