Update articles/cognitive-services/Anomaly-Detector/service-limits.md

Co-authored-by: Michael  <[email protected]>

Author: jr-MS

articles/cognitive-services/Anomaly-Detector/service-limits.md

@@ -56,7 +56,7 @@ The quotas and limits apply to all the versions within Azure Anomaly Detector se
 ## How to increase the limit for your resource?
 For the Standard pricing tier, this limit can be increased. Increasing the **concurrent request limit** does not directly affect your costs. Anomaly Detector service uses "Pay only for what you use" model. The limit defines how high the Service may scale before it starts throttle your requests.
 
-Existing value of Concurrent Request limit parameter is not visible via Azure portal, Command-Line tools, or API requests. To verify the existing value, create an Azure Support Request.
+The **concurrent request limit parameter** is not visible via Azure portal, Command-Line tools, or API requests. To verify the current value, create an Azure Support Request.
 
 If you would like to increase your limit, you can enable auto scaling on your resource. Follow this document to enable auto scaling on your resource [enable auto scaling](https://learn.microsoft.com/azure/cognitive-services/autoscale?view=form-recog-3.0.0&tabs=portal). You can also submit an increase TPS support request.