Update api-management-howto-deploy-multi-region.md

Fixes https://github.com/MicrosoftDocs/azure-docs/issues/87644

Author: dlepow

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

@@ -50,7 +50,7 @@ A new Azure API Management service initially contains only one [unit][unit] in a
 
 ## <a name="route-backend"> </a>Route API calls to regional backend services
 
-Azure API Management features only one backend service URL. Even though there are Azure API Management instances in various regions, the API gateway will still forward requests to the same backend service, which is deployed in only one region. In this case, the performance gain will come only from responses cached within Azure API Management in a region specific to the request, but contacting the backend across the globe may still cause high latency.
+By default, each API routes requests to a single backend service URL. Even though there are Azure API Management instances in various regions, the API gateway will still forward requests to the same backend service, which is deployed in only one region. In this case, the performance gain will come only from responses cached within Azure API Management in a region specific to the request, but contacting the backend across the globe may still cause high latency.
 
 To fully leverage geographical distribution of your system, you should have backend services deployed in the same regions as Azure API Management instances. Then, using policies and `@(context.Deployment.Region)` property, you can route the traffic to local instances of your backend.