edits

Author: khdownie

articles/storage/file-sync/file-sync-throttling.md

@@ -11,21 +11,21 @@ ms.author: kendownie
 
 # Understand Azure File Sync throttling
 
-Azure File Sync now integrates with Azure Throttling Service (ATS) to implement throttling on key APIs to protect against unexpected load surges. This article explains how throttling works for Azure File Sync, and lists the throttling limits for the resource provider and storage sync service.
+Azure File Sync now integrates with Azure Throttling Service (ATS) to implement throttling on key APIs to protect against unexpected load surges. This article explains how throttling works for Azure File Sync, and lists the throttling limits.
 
 ## Azure Resource Manager (ARM) throttling behavior
 
-Azure Resource Manager [implements throttling](/azure/azure-resource-manager/management/request-limits-and-throttling) at two levels: subscription and tenant. This is done to manage the number of requests made to Azure services, ensuring fair usage and preventing overloading. If requests are within the limits for these levels, they are routed to the resource provider. 
+Azure Resource Manager [implements throttling](/azure/azure-resource-manager/management/request-limits-and-throttling) at two levels: subscription and tenant. This is done to manage the number of requests made to Azure services, ensuring fair usage and preventing overloading. If requests are within the limits for these levels, they are routed to the resource provider.
 
 ## Azure File Sync throttling behavior
 
 Azure File Sync uses the Microsoft.StorageSync resource provider, which applies its own throttling limits.
 
 Azure File Sync enforces throttling in two ways:
 
-- Regionally at the scope of individual resource types, such as storage sync service, registered server, sync group, cloud endpoint, or server endpoint. If too many operations are performed on a specific resource such as a server endpoint, further actions on that resource are temporarily blocked until the throttling period ends.
+- **At the scope of individual resource types**, such as storage sync service, registered server, sync group, cloud endpoint, or server endpoint. If too many operations are performed on a specific resource such as a server endpoint, further actions on that resource are temporarily blocked until the enforcement period expires.
 
-- Using the storage sync service resource as a scope. Excessive operations across resources within a storage sync service will result in a temporary block on all resources under that service until the enforcement period expires.
+- **Using the storage sync service resource as a scope.** Excessive operations across resources within a storage sync service will result in a temporary block on all resources under that service until the enforcement period expires.
 
 By throttling in this manner, we can better control consumption of our APIs to protect customers from potential outages.
 
@@ -39,10 +39,10 @@ The following table lists the per-resource limits for Azure File Sync.
 | PATCH requests                             | Enabling/disabling tiering on a server endpoint, or updating tiering policies | 12    | 3 minutes         | 4 tokens/min     |
 | DELETE requests                            | Deleting a server endpoint                                               | 12    | 3 minutes         | 4 tokens/min     |
 | GET requests                               | Browsing a server endpoint resource in the Azure portal                  | 400   | 3 minutes         | ~2 tokens/s      |
-| GET list requests                          | Browsing the list of server endpoints under a sync group in the Azure portal | 1800  | 3 minutes         | ~10 tokens/s     |
+| GET list requests                          | Browsing the list of server endpoints under a sync group in the Azure portal | 1,800  | 3 minutes         | ~10 tokens/s     |
 | Cloud endpoint trigger change detection request\* | Triggering change detection on a specific cloud endpoint                 | 5     | 30 minutes        | 1 per 6 mins     |
 
-\*The trigger change detection feature for cloud endpoints is powerful, but also resource-intensive. Running it too often can slow things down and even cancel previous operations. For this reason, we’ve set a specific limit to ensure the system has enough time to process each request.
+\*The trigger change detection feature for cloud endpoints is powerful, but also resource-intensive. Running it too often can degrade performance and even cancel previous operations. For this reason, we’ve set a specific limit to ensure the system has enough time to process each change detection request.
 
 ## Storage sync service limits
 
@@ -60,11 +60,14 @@ The following table lists the per-storage sync service limits for Azure File Syn
 
 The following are common questions about throttling in Azure File Sync.
 
-- **What's the reasoning behind these limits?**
-- Azure File Sync is designed for reliability and smooth operation. Most customers only need to make a few changes at a time, such setting up resources or adjusting settings. That’s why limits on actions like creating, updating, or deleting resources are set fairly low. This helps prevent accidental overloads and keeps the service running smoothly.
+### What's the reasoning behind these limits?
 
-- **What about normal operations like browsing files and reading data?**
-- You can freely browse and read your resources in the Azure portal or programmatically. The limits for these operations are generous, so you shouldn’t run into issues during normal use.
+Most customers only run a few PUT/PATCH/DELETE operations at a time, such as setting up resources or adjusting settings. That’s why limits on actions like creating, updating, or deleting resources are set fairly low. This helps prevent accidental overloads and keeps the service running smoothly.
 
-- **What happens if you hit a limit?**
-- If you reach a throttling limit, further actions on that resource will be temporarily paused. Once the throttling period ends, you’ll be able to continue as normal.
+### Do I need to worry about day-to-day operations like browsing and reading files?
+
+You can freely browse and read your resources in the Azure portal or programmatically. The limits for GET and GET list operations are generous, so you shouldn’t run into issues during normal use.
+
+### What happens if you hit a throttling limit?
+
+If you reach a throttling limit, further actions on that resource or within that storage sync service will be temporarily paused. Once the enforcement period ends, you can continue as normal.