[a11y] Fix "read more" occurrence

docs/operating-eck/installing-eck.asciidoc

@@ -112,7 +112,7 @@ helm show values elastic/eck-operator
 [id="{p}-migrate-to-helm"]
 === Migrate an existing installation to Helm
 
-CAUTION: Migrating an existing installation to Helm is essentially an upgrade operation and any <<{p}-beta-to-ga-rolling-restart,caveats associated with normal operator upgrades>> are applicable. Read the <<{p}-ga-upgrade,upgrade documentation>> before proceeding.
+CAUTION: Migrating an existing installation to Helm is essentially an upgrade operation and any <<{p}-beta-to-ga-rolling-restart,caveats associated with normal operator upgrades>> are applicable. Check the <<{p}-ga-upgrade,upgrade documentation>> before proceeding.
 
 
 You can migrate an existing operator installation to Helm by adding the `meta.helm.sh/release-name`, `meta.helm.sh/release-namespace` annotations and the `app.kubernetes.io/managed-by` label to all the resources you want to be adopted by Helm. You _must_ do this for the Elastic Custom Resource Definitions (CRD) because deleting them would trigger the deletion of all deployed Elastic applications as well. All other resources are optional and can be deleted.

docs/orchestrating-elastic-stack-applications/agent-fleet.asciidoc

@@ -397,7 +397,7 @@ To deploy Elastic Agent in clusters with the Pod Security Policy admission contr
 [id="{p}-elastic-agent-fleet-configuration-customize-fleet-server-service"]
 === Customize Fleet Server Service
 
-By default, ECK creates a Service for Fleet Server that Elastic Agents can connect through. You can customize it using the `http` configuration element. You can read more about link:k8s-services.html[making changes] to the Service and link:k8s-tls-certificates.html[customizing] TLS configuration in the documentation.
+By default, ECK creates a Service for Fleet Server that Elastic Agents can connect through. You can customize it using the `http` configuration element. Check more information on how to link:k8s-services.html[make changes] to the Service and link:k8s-tls-certificates.html[customize] the TLS configuration.
 
 [id="{p}-elastic-agent-fleet-configuration-override-default-fleet-configuration-settings"]
 === Override default Fleet configuration settings

docs/orchestrating-elastic-stack-applications/security/saml-authentication.asciidoc

@@ -11,7 +11,7 @@ The Elastic Stack supports SAML single sign-on (SSO) into Kibana, using Elastics
 
 NOTE: Elastic Stack SSO requires a valid Enterprise license or Enterprise trial license. Check <<{p}-licensing,the license documentation>> for more details about managing licenses.
 
-TIP: Make sure you read the complete link:https://www.elastic.co/guide/en/elasticsearch/reference/current/saml-guide-stack.html[Configuring SAML single sign-on on the Elastic Stack] guide before setting up SAML SSO for Kibana and Elasticsearch deployments managed by ECK.
+TIP: Make sure you check the complete link:https://www.elastic.co/guide/en/elasticsearch/reference/current/saml-guide-stack.html[Configuring SAML single sign-on on the Elastic Stack] guide before setting up SAML SSO for Kibana and Elasticsearch deployments managed by ECK.
 
 == Add a SAML realm to X-Pack security settings 
 

docs/quickstart.asciidoc

@@ -29,7 +29,7 @@ include::supported-versions.asciidoc[]
 [id="{p}-deploy-eck"]
 == Deploy ECK in your Kubernetes cluster
 
-IMPORTANT: Read the <<{p}-upgrading-eck,upgrade notes>> first if you are attempting to upgrade an existing ECK deployment.
+IMPORTANT: Check the <<{p}-upgrading-eck,upgrade notes>> first if you are attempting to upgrade an existing ECK deployment.
 
 [NOTE]
 ====