edits

Author: gitName

includes/api-management-multi-region-concepts.md

@@ -21,5 +21,5 @@ ms.author: danlep
 
 * If the primary region goes offline, the API Management management plane and developer portal become unavailable, but secondary regions continue to serve API requests using the most recent gateway configuration.
 
-* If configured, the [rate-limit](/azure/api-management/rate-limit-policy) and [rate-limit-by-key](/azure/api-management/rate-limit-by-key-policy) policies count calls separately at each regional gateway in the deployment. The policies don't aggregate all call data for the instance. 
+* If configured, the [rate-limit](/azure/api-management/rate-limit-policy) and [rate-limit-by-key](/azure/api-management/rate-limit-by-key-policy) policies count calls separately at each regional gateway in the deployment. The policies don't aggregate all call data for the instance. Similarly, the [azure-openai-token-limit](/azure/api-management/azure-openai-token-limit-policy) and [llm-token-limit](/azure/api-management/llm-token-limit-policy) policies count token usage separately at each regional gateway in the deployment. 
 

includes/api-management-rate-limit-gateway-calls.md

@@ -6,4 +6,4 @@ ms.date: 04/09/2025
 ms.author: danlep
 ---
 
-This policy tracks calls independently at each gateway where it is applied, including regional gateways in a [multi-region deployment](../articles/api-management/api-management-howto-deploy-multi-region.md) and [workspace gateways](../articles/api-management/workspaces-overview.md#workspace-gateway). It doesn't aggregate call data across the entire instance. 
+This policy tracks calls independently at each gateway where it is applied, including [workspace gateways](../articles/api-management/workspaces-overview.md#workspace-gateway) and regional gateways in a [multi-region deployment](../articles/api-management/api-management-howto-deploy-multi-region.md). It doesn't aggregate call data across the entire instance.