Update for Acrolinx

Author: zhenlan

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

@@ -88,18 +88,20 @@ To delete a replica in the portal, follow the steps below.
 
 Each replica you create has its dedicated endpoint. If your application resides in multiple geolocations, 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 is not accessible, you can let your application failover to another replica for improved resiliency. App Configuration provider libraries have built-in failover support. The provider library accepts multiple endpoints. You can provide a list of your replica endpoints in the order of how you prefer your application to connect, from the most to the least. When one endpoint is not accessible, the provider library will failover to a less preferred endpoint, but it will try to connect to the more preferred endpoints from time to time. When a more preferred endpoint becomes available, it will switch to it for future requests. You can update your application to take advantage of this failover support.
+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 provider libraries have built-in failover support. The provider library accepts multiple endpoints. You can provide a list of your replica endpoints in the order of how you prefer your application to connect, from the most to the least. When one endpoint isn't accessible, the provider library will fail over to a less preferred endpoint, but it will try to connect to the more preferred endpoints from time to time. When a more preferred endpoint becomes available, it will switch to it for future requests. You can update your application as the sample code below to take advantage of the failover feature.
 
 <!-- ### [.NET](#tab/dotnet) -->
 
 ```csharp
 configurationBuilder.AddAzureAppConfiguration(options =>
 {
-    // Provide an ordered list of replica endpoints and use AAD authentication
-    options.Connect(new Uri[] {
-                    new Uri("https://<first-replica-endpoint>.azconfig.io"),
-                    new Uri("https://<second-replica-endpoint>.azconfig.io") },
-                new DefaultAzureCredential());
+    // Provide an ordered list of replica endpoints
+    var endpoints = new Uri[] {
+        new Uri("https://<first-replica-endpoint>.azconfig.io"),
+        new Uri("https://<second-replica-endpoint>.azconfig.io") };
+    
+    // Connect to replica endpoints using AAD authentication
+    options.Connect(endpoints, new DefaultAzureCredential());
 
     // Other changes to options
 });
@@ -112,11 +114,13 @@ configurationBuilder.AddAzureAppConfiguration(options =>
 Placeholder for Java Spring instructions
 --- -->
 
-The failover in the App Configuration provider occurs in the following conditions. It will not happen for client errors like authentication failures.
+The failover in the App Configuration provider occurs in the following conditions.
 - Service unavailable responses (HTTP status code 500 or above)
 - Network connectivity issues
 - Throttled requests (HTTP status code 429)
 
+The failover won't happen for client errors like authentication failures.
+
 ## Next steps
 
 > [!div class="nextstepaction"]