acrolinx updates

Author: mrm9084

articles/azure-app-configuration/howto-geo-replication.md

@@ -16,7 +16,7 @@ ms.custom: devx-track-azurecli
 
 # Enable geo-replication
 
-This article covers replication of Azure App Configuration stores. You'll learn about how to create, use and delete a replica in your configuration store.
+This article covers replication of Azure App Configuration stores. You learn about how to create, use, and delete a replica in your configuration store.
 
 To learn more about the concept of geo-replication, see [Geo-replication in Azure App Configuration](./concept-geo-replication.md).
 
@@ -90,7 +90,7 @@ To delete a replica in the portal, follow the steps below.
 
 ## Automatic replica discovery
 
-The App Configuration providers can automatically discover any additional replicas from a given App Configuration endpoint and attempt to connect to them. This feature allows you to benefit from geo-replication without having to change your code or redeploy your application. This means you can enable geo-replication or add extra replicas even after your application has been deployed.
+The App Configuration providers can automatically discover any replicas from a given App Configuration endpoint and attempt to connect to them. This feature allows you to benefit from geo-replication without having to change your code or redeploy your application. This means you can enable geo-replication or add extra replicas even after your application has been deployed.
 
 Automatic replica discovery is enabled by default, but you can refer to the following sample code to disable it (not recommended).
 
@@ -165,7 +165,7 @@ config = load(endpoint=endpoint, credential=credential, replica_discovery_enable
 
 Each replica you create has its dedicated endpoint. If your application resides in multiple geo-locations, you can update each deployment of your application in a location to connect to the replica closer to that location, which helps minimize the network latency between your application and App Configuration. Since each replica has its separate request quota, this setup also helps the scalability of your application while it grows to a multi-region distributed service.
 
-When geo-replication is enabled, and if one replica isn't accessible, you can let your application failover to another replica for improved resiliency. App Configuration providers have built-in failover support through user provided replicas as well as additional automatically discovered replicas. You can provide a list of your replica endpoints in the order of the most preferred to the least preferred endpoint. When the current endpoint isn't accessible, the provider will fail over to a less preferred endpoint, but it will try to connect to the more preferred endpoints from time to time. If all user provided replicas are not accessible, the automatically discovered replicas will be randomly selected and used. When a more preferred endpoint becomes available, the provider will switch to it for future requests.
+When geo-replication is enabled, and if one replica isn't accessible, you can let your application failover to another replica for improved resiliency. App Configuration providers have built-in failover support through user provided replicas and/or additional automatically discovered replicas. You can provide a list of your replica endpoints in the order of the most preferred to the least preferred endpoint. When the current endpoint isn't accessible, the provider will fail over to a less preferred endpoint, but it tries to connect to the more preferred endpoints from time to time. If all user provided replicas aren't accessible, the automatically discovered replicas will be randomly selected and used. When a more preferred endpoint becomes available, the provider will switch to it for future requests.
 
 Assuming you have an application using Azure App Configuration, you can update it as the following sample code to take advantage of the failover feature. You can either provide a list of endpoints for Microsoft Entra authentication or a list of connection strings for access key-based authentication.
 
@@ -239,11 +239,11 @@ spring.cloud.azure.appconfiguration.stores[0].connection-strings[1]="${SECOND_RE
 
 ### [Kubernetes](#tab/kubernetes)
 
-The Azure App Configuration Kubernetes Provider supports failover with automatically discovered replicas by default, as long as automatic replica discovery is not disabled. It does not support or require user-provided replicas.
+The Azure App Configuration Kubernetes Provider supports failover with automatically discovered replicas by default, as long as automatic replica discovery isn't disabled. It doesn't support or require user-provided replicas.
 
 ### [Python](#tab/python)
 
-The Azure App Configuration Python Provider supports failover with automatically discovered replicas by default, as long as automatic replica discovery is not disabled. It does not support or require user-provided replicas.
+The Azure App Configuration Python Provider supports failover with automatically discovered replicas by default, as long as automatic replica discovery isn't disabled. It doesn't support or require user-provided replicas.
 
 ---
 
@@ -282,15 +282,15 @@ configurationBuilder.AddAzureAppConfiguration(options =>
 
 ### [Java Spring](#tab/spring)
 
-This feature is not yet supported in the Azure App Configuration Java Spring Provider.
+This feature isn't yet supported in the Azure App Configuration Java Spring Provider.
 
 ### [Kubernetes](#tab/kubernetes)
 
-This feature is not yet supported in the Azure App Configuration Kubernetes Provider.
+This feature isn't yet supported in the Azure App Configuration Kubernetes Provider.
 
 ### [Python](#tab/python)
 
-This feature is not yet supported in the Azure App Configuration Python Provider.
+This feature isn't yet supported in the Azure App Configuration Python Provider.
 
 ---