Apply suggestions from code review

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

Author: eedugon

deploy-manage/remote-clusters/_snippets/eck_expose_transport.md

@@ -12,4 +12,4 @@ spec:
         type: LoadBalancer <1>
 ```
 
-1. On cloud providers which support external load balancers, setting the type field to LoadBalancer provisions a load balancer for your service. Alternatively, expose the service `<cluster-name>-es-transport` through one of the Kubernetes Ingress controllers that support TCP services.
+1. On cloud providers which support external load balancers, setting the type field to `LoadBalancer` provisions a load balancer for your service. Alternatively, expose the service `<cluster-name>-es-transport` through one of the Kubernetes Ingress controllers that support TCP services.

deploy-manage/remote-clusters/_snippets/eck_rcs_expose.md

@@ -15,15 +15,15 @@ kubectl expose service quickstart-es-remote-cluster \
   --port=9443 --target-port=9443
 ```
 
-1. On cloud providers which support external load balancers, setting the type to LoadBalancer provisions a load balancer for your service. Alternatively, expose the service `<cluster-name>-es-remote-cluster` through one of the Kubernetes Ingress controllers that support TCP services.
+1. On cloud providers that support external load balancers, setting the type to `LoadBalancer` provisions a load balancer for your service. Alternatively, expose the service `<cluster-name>-es-remote-cluster` through one of the Kubernetes Ingress controllers that support TCP services.
 
 
 :::{admonition} About exposing the service and TLS certificates
 When exposing the remote cluster service, determine which TLS certificate will be presented to clients and whether a certificate authority (CA) is required to establish trust. This depends on how traffic to port `9443` is routed in your environment and which component terminates the TLS connection:
 
 * **{{es}} TLS termination**
 
-  If the connection reaches the {{es}} Pods without intermediate TLS termination, the {{es}} nodes present their transport certificates managed by ECK. The local cluster must therefore trust these certificates by including the ECK-managed transport CA, which you can retrieve in the next section.
+  If the connection reaches the {{es}} Pods without intermediate TLS termination, the {{es}} nodes present transport certificates managed by ECK. The local cluster must therefore trust these certificates by including the ECK-managed transport CA, which you can retrieve in the next section.
 
   This setup is typical when using standard `LoadBalancer` services provided by most cloud providers.
 

deploy-manage/remote-clusters/_snippets/eck_rcs_retrieve_ca.md

@@ -2,14 +2,14 @@ The certificate authority (CA) used by ECK to issue certificates for the remote
 
 If the external connections reach the {{es}} Pods on port `9443` without any intermediate TLS termination, you must retrieve this CA, as it will be required in the local cluster configuration to establish trust.
 
-For example, to save the transport CA certificate of a cluster named `quickstart` into a local file, run:
+For example, to save the transport CA certificate of a cluster named `quickstart` into a local file, run the following command:
 
 ```sh
 kubectl get secret quickstart-es-transport-certs-public \
 -o go-template='{{index .data "ca.crt" | base64decode}}' > eck_transport_ca.crt
 ```
 
-You can verify that the file contains a valid CA certificate by running:
+You can verify that the file contains a valid CA certificate by running the following command:
 
 ```bash
 openssl x509 -in eck_transport_ca.crt -noout -text
@@ -18,6 +18,6 @@ openssl x509 -in eck_transport_ca.crt -noout -text
 ::::{important}
 ECK-managed CA certificates are automatically rotated after one year by default, but you can [configure](/deploy-manage/deploy/cloud-on-k8s/configure-eck.md) a different validity period.
 
-Ensure that this CA is updated in all environments where it's used after rotation to preserve trust.
+When the CA certificate is rotated, ensure that this CA is updated in all environments where it's used to preserve trust.
 ::::