final minor updates from reviews

Author: eedugon

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

@@ -37,4 +37,6 @@ PUT /_cluster/settings
 
 ::::{note}
 When using API key authentication, the cluster alias must match the one you configured when adding the API key in the Cloud UI.
-::::
+::::
+
+For a full list of available client connection settings in proxy mode, refer to [remote cluster settings reference](elasticsearch://reference/elasticsearch/configuration-reference/remote-clusters.md#remote-cluster-proxy-settings).

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

@@ -24,7 +24,5 @@ This snippet is in use in the following locations:
       * **TLS server name**: Specify a value if the certificate presented by the remote cluster is signed for a different name than the remote address.
       * **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).
-
 4. Click **Next**.
 5. In **Confirm setup**, click **Add remote cluster** (you have already established trust in a previous step).

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

@@ -68,7 +68,7 @@ To add a remote cluster from Stack Management in {{kib}}:
 2. Enter a name (*cluster alias*) for the remote cluster.
 3. Specify the {{es}} endpoint URL, the IP address, or host name of the remote cluster followed by the transport port (defaults to `9300`). For example, `cluster.es.eastus2.staging.azure.foundit.no:9300` or `192.168.1.1:9300`.
 
-    Both IPv4 and IPv6 ({applies_to}`stack: ga 9.2`) addresses are supported.
+    Starting with {{kib}} 9.2, you can also specify IPv6 addresses.
 
 ### Using the {{es}} API