usage note

Author: gitName

articles/api-management/limit-concurrency-policy.md

@@ -16,7 +16,7 @@ ms.author: danlep
 
 The `limit-concurrency` policy prevents enclosed policies from executing by more than the specified number of requests at any time. When that number is exceeded, new requests will fail immediately with the `429` Too Many Requests status code.
 
-[!INCLUDE [api-management-rate-limit-accuracy](../../includes/api-management-rate-limit-accuracy.md)] > The limit enforced by API Management may be lower when multiple capacity units are deployed in a region.
+[!INCLUDE [api-management-rate-limit-accuracy](../../includes/api-management-rate-limit-accuracy.md)]
 
 [!INCLUDE [api-management-policy-generic-alert](../../includes/api-management-policy-generic-alert.md)]
 
@@ -42,6 +42,10 @@ The `limit-concurrency` policy prevents enclosed policies from executing by more
 - [**Policy scopes:**](./api-management-howto-policies.md#scopes) global, workspace, product, API, operation
 -  [**Gateways:**](api-management-gateways-overview.md) classic, v2, consumption, self-hosted, workspace
 
+### Usage notes
+
+* The maximum number of requests enforced by API Management is lower when multiple capacity units are deployed in a region.
+
 ## Example
 
 The following example demonstrates how to limit number of requests forwarded to a backend based on the value of a context variable.