a -> an

Author: florent-leborgne

cloud-account/change-your-password.md

@@ -8,7 +8,7 @@ applies:
 
 # Change your password [ec-change-password]
 
-If you created a password when you signed up for a {{ecloud}} account, or you added the password-based login method to your account, then you can change your password if needed.
+If you created a password when you signed up for an {{ecloud}} account, or you added the password-based login method to your account, then you can change your password if needed.
 
 If you know your current password:
 

deploy-manage/maintenance/start-stop-services/restart-cloud-hosted-deployment.md

@@ -37,9 +37,9 @@ curl -XPOST \
 
 `REF_ID`  Name given to each resource type in the attribute `ref_id`. `main-elasticsearch` in the preceding example
 
-## Shut down a {{ech}} deployment [ec_shut_down_a_elasticsearch_service_deployment]
+## Shut down an {{ech}} deployment [ec_shut_down_a_elasticsearch_service_deployment]
 
-Shut down a {{ech}} deployment by calling the following API request:
+Shut down an {{ech}} deployment by calling the following API request:
 
 ```sh
 curl -XPOST \

manage-data/ingest/ingesting-data-from-applications/ingest-data-from-relational-database-into-elasticsearch-service.md

@@ -98,7 +98,7 @@ The Logstash JDBC input plugin does not include any database connection drivers.
 
 ## Prepare a source MySQL database [ec-db-logstash-database]
 
-Let’s look at a simple database from which you’ll import data and send it to a {{ech}} or {{ece}} deployment. This example uses a MySQL database with timestamped records. The timestamps enable you to determine easily what’s changed in the database since the most recent data transfer.
+Let’s look at a simple database from which you’ll import data and send it to an {{ech}} or {{ece}} deployment. This example uses a MySQL database with timestamped records. The timestamps enable you to determine easily what’s changed in the database since the most recent data transfer.
 
 
 ### Consider the database structure and design [ec-db-logstash-database-structure]

reference/glossary/index.md

@@ -65,7 +65,7 @@ $$$glossary-auto-follow-pattern$$$ auto-follow pattern
 :   [Index pattern](/reference/glossary/index.md#glossary-index-pattern) that automatically configures new [indices](/reference/glossary/index.md#glossary-index) as [follower indices](/reference/glossary/index.md#glossary-follower-index) for [{{ccr}}](/reference/glossary/index.md#glossary-ccr). See [Manage auto-follow patterns](/deploy-manage/tools/cross-cluster-replication/manage-auto-follow-patterns.md).
 
 $$$glossary-zone$$$ availability zone
-:   Contains resources available to a {{ece}} installation that are isolated from other availability zones to safeguard against failure. Could be a rack, a server zone or some other logical constraint that creates a failure boundary. In a highly available cluster, the nodes of a cluster are spread across two or three availability zones to ensure that the cluster can survive the failure of an entire availability zone. Also see [Fault Tolerance (High Availability)](/deploy-manage/deploy/cloud-enterprise/ece-ha.md).
+:   Contains resources available to an {{ece}} installation that are isolated from other availability zones to safeguard against failure. Could be a rack, a server zone or some other logical constraint that creates a failure boundary. In a highly available cluster, the nodes of a cluster are spread across two or three availability zones to ensure that the cluster can survive the failure of an entire availability zone. Also see [Fault Tolerance (High Availability)](/deploy-manage/deploy/cloud-enterprise/ece-ha.md).
 
 
 ## B [b-glos]