linting fixes

Author: eedugon

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

@@ -1,4 +1,4 @@
-By default, the remote cluster server interface is disabled on ECK-managed clusters. To use the API key–based security model for cross-cluster connections, you must first enable it on the remote {{es}} cluster:
+By default, the remote cluster server interface is deactivated on ECK-managed clusters. To use the API key–based security model for cross-cluster connections, you must first enable it on the remote {{es}} cluster:
 
 ```yaml subs=true
 apiVersion: elasticsearch.k8s.elastic.co/v1

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

@@ -1,6 +1,6 @@
 The certificate authority (CA) used by ECK to issue certificates for the remote cluster server interface is stored in the `ca.crt` key of the secret named `<cluster_name>-es-transport-certs-public`.
 
-If the external connections reach the {{es}} Pods on port `9443` without any intermediate TLS termination, you need to retrieve this CA because it will be required in the local cluster configuration to establish trust.
+If the external connections reach the {{es}} Pods on port `9443` without any intermediate TLS termination, you need to retrieve this CA because it is required in the local cluster configuration to establish trust.
 
 If TLS is terminated by any intermediate component and the certificate presented is not the ECK-managed one, use the CA associated with that component, or omit the CA entirely if it uses a publicly trusted certificate.