acrolinx and fix warning

Author: Court72

articles/api-management/api-management-howto-deploy-multi-region.md

@@ -124,7 +124,7 @@ API Management routes the requests to a regional gateway based on [the lowest la
 
 Under some conditions, you might need to temporarily disable routing to one of the regional gateways. For example:
 
-* After adding a new region, to keep it disabled while you configure and test the regional back-end service 
+* After you add a new region, to keep it disabled while you configure and test the regional back-end service 
 * During regular back-end maintenance in a region
 * To redirect traffic to other regions during a planned disaster recovery drill that simulates an unavailable region, or during a regional failure 
 

articles/reliability/reliability-api-management.md

@@ -260,7 +260,7 @@ This section describes what to expect when API Management instances are configur
 
 - **Traffic routing between regions:** API Management automatically routes incoming requests to a regional gateway. A request is routed to the regional gateway with the lowest latency from the client. If you need to use a different routing approach, you can configure your own Traffic Manager with custom routing rules. For more information, see [Use custom routing to API Management regional gateways](../api-management/api-management-howto-deploy-multi-region.md#use-custom-routing-to-api-management-regional-gateways).
 
-    When a request reaches an API Management regional gateway, it's routed to the back-end API unless a policy returns a response directly from the gateway, such as a cached response or an error code. In a multiple-region solution, you need to take care to route to an instance of the back-end API that meets your performance requirements. For more information, see [Route API calls to regional back-end services](../api-management/api-management-howto-deploy-multi-region.md#route-api-calls-to-regional-backend-services).
+    When a request reaches an API Management regional gateway, it's routed to the back-end API unless a policy returns a response directly from the gateway, such as a cached response or an error code. In a multiple-region solution, you need to take care to route to an instance of the back-end API that meets your performance requirements. For more information, see [Route API calls to regional back-end services](../api-management/api-management-howto-deploy-multi-region.md#route-api-calls-to-regional-back-end-services).
 
 - **Data replication between regions:** Gateway configuration, such as APIs and policy definitions, are regularly synchronized between the primary and secondary regions you add. Propagation of updates to the regional gateways normally takes less than 10 seconds.