Acrolinx

kgremban · kgremban · commit 8a582c58e346 · 2024-06-17T14:27:52.000-07:00
diff --git a/articles/iot-hub/iot-hub-devguide-quotas-throttling.md b/articles/iot-hub/iot-hub-devguide-quotas-throttling.md
@@ -17,7 +17,7 @@ This article explains the limits that apply to IoT Hub resources.
 
 Each Azure subscription can have at most 50 IoT hubs, and at most 1 hub in the free tier.
 
-Each IoT hub is provisioned with units in a specific tier. The tier and number of units determine the maximum daily quota of messages. The message size used to calculate the daily quota is 0.5 KB for a free tier hub and 4KB for all other tiers. For more information, see [Azure IoT Hub pricing](https://azure.microsoft.com/pricing/details/iot-hub/) or [Choose the right IoT Hub tier for your solution](./iot-hub-scaling.md).
+Each IoT hub is provisioned with units in a specific tier. The tier and number of units determine the maximum daily quota of messages. The message size used to calculate the daily quota is 0.5 KB for a free tier hub and 4 KB for all other tiers. For more information, see [Azure IoT Hub pricing](https://azure.microsoft.com/pricing/details/iot-hub/) or [Choose the right IoT Hub tier for your solution](./iot-hub-scaling.md).
 
 You can find your hub's quota limit in the Azure portal. Your IoT hub's **Overview** page lists the **Daily message quota**. You can also view and adjust this limit in **Hub settings** > **Pricing and scale**.
 
@@ -27,7 +27,7 @@ The tier also determines the throttling limits that IoT Hub enforces on all oper
 
 Operation throttles are rate limitations that are applied in minute ranges and are intended to prevent abuse. They're also subject to [traffic shaping](#traffic-shaping).
 
-It's a good practice to throttle your calls so that you don't hit/exceed the throttling limits. If you do hit the limit, IoT Hub responds with error code 429 and the client should back-off and retry. These limits are per hub (or in some cases per hub per unit). For more information, see [Retry patterns](../iot/concepts-manage-device-reconnections.md#retry-patterns).
+It's a good practice to throttle your calls so that you don't hit/exceed the throttling limits. If you do hit the limit, IoT Hub responds with error code 429, and the client should back-off and retry. These limits are per hub (or in some cases per hub per unit). For more information, see [Retry patterns](../iot/concepts-manage-device-reconnections.md#retry-patterns).
 
 For pricing details about which operations are charged and under what circumstances, see [billing information](iot-hub-devguide-pricing.md).
 
@@ -61,11 +61,11 @@ The following table shows the enforced throttles for operations that are availab
 | Maximum number of concurrently connected device streams | 50 | 50 | 50 |
 | Maximum device stream data transfer (aggregate volume per day) | 300 MB | 300 MB | 300 MB |
 
-<sup>1</sup>Throttling meter size is 4 KB. Throttling is based on request payload size only.
+<sup>1</sup> Throttling meter size is 4 KB. Throttling is based on request payload size only.
 
 ### Throttling details
 
-* The meter size determines at what increments your throttling limit is consumed. If your direct call's payload is between 0 KB and 4 KB, it's counted as 4 KB. You can make up to 40 calls per second per unit before hitting the limit of 160 KB/sec/unit.
+* The meter size determines at what increments your throttling limit is consumed. If your direct call's payload is between 0 KB and 4 KB, it counts as 4 KB. You can make up to 40 calls per second per unit before hitting the limit of 160 KB/sec/unit.
 
    Similarly, if your payload is between 4 KB and 8 KB, each call accounts for 8 KB and you can make up to 20 calls per second per unit before hitting the max limit.
 
@@ -85,7 +85,7 @@ For example, you send 200 device-to-cloud messages per second to your S1 IoT Hub
 
 Device identity registry operations are intended for run-time use in device management and provisioning scenarios. Reading or updating a large number of device identities is supported through [import and export jobs](iot-hub-devguide-identity-registry.md#import-and-export-device-identities).
 
-When initiating identity operations through [bulk registry update operations](/rest/api/iothub/service/bulkregistry/updateregistry) (*not* bulk import and export jobs), the same throttle limits apply. For example, if you submit multiple bulk operations to create 50 devices each, and you have an S1 IoT Hub with one unit, only two of these bulk requests are accepted per minute. This limitation is because the identity operation throttle for an S1 IoT Hub with one unit is 100/min/unit. Also in this case, a third request (and beyond) in the same minute would be rejected because the limit has been reached.
+The same throttle limits apply to identity operations made through [bulk registry update operations](/rest/api/iothub/service/bulkregistry/updateregistry) (*not* bulk import and export jobs). For example, if you submit multiple bulk operations to create 50 devices each, and you have an S1 IoT Hub with one unit, only two of these bulk requests are accepted per minute. This limitation is because the identity operation throttle for an S1 IoT Hub with one unit is 100/min/unit. Also in this case, a third request (and beyond) in the same minute would be rejected because the limit has been reached.
 
 ### Device connections throttle
 
@@ -102,11 +102,11 @@ IoT Hub enforces other operational limits:
 | Device and module identities | The total number of devices plus modules that can be registered to a single IoT hub is capped at 1,000,000. |
 | File uploads | 10 concurrent file uploads per device. |
 | Jobs<sup>1</sup> | Maximum concurrent jobs are 1 (for free and S1), 5 (for S2), and 10 (for S3). However, the max concurrent [device import/export jobs](iot-hub-bulk-identity-mgmt.md) is 1 for all tiers. <br/>Job history is retained up to 30 days. |
-| Additional endpoints | Basic and standard SKU hubs may have 10 additional endpoints. Free SKU hubs may have one additional endpoint. |
-| Message routing queries | Basic and standard SKU hubs may have 100 routing queries. Free SKU hubs may have five routing queries. |
+| Additional endpoints | Basic and standard SKU hubs can have 10 additional endpoints. Free SKU hubs can have one additional endpoint. |
+| Message routing queries | Basic and standard SKU hubs can have 100 routing queries. Free SKU hubs can have five routing queries. |
 | Message enrichments | Basic and standard SKU hubs can have up to 10 message enrichments. Free SKU hubs can have up to two message enrichments.|
 | Device-to-cloud messaging | Maximum message size 256 KB |
-| Cloud-to-device messaging<sup>1</sup> | Maximum message size 64 KB. Maximum pending messages for delivery is 50 per device. |
+| Cloud-to-device messaging<sup>1</sup> | Maximum message size 64 KB. Maximum pending messages for delivery count is 50 per device. |
 | Direct method<sup>1</sup> | Maximum direct method payload size is 128 KB for the request and 128 KB for the response. |
 | Automatic device and module configurations<sup>1</sup> | 100 configurations per basic or standard SKU hub. 10 configurations per free SKU hub. |
 | IoT Edge automatic deployments<sup>1</sup> | 50 modules per deployment. 100 deployments (including layered deployments) per basic or standard SKU hub. 10 deployments per free SKU hub. |
@@ -115,7 +115,7 @@ IoT Hub enforces other operational limits:
 | Restrict outbound network access | Maximum number of allowed FQDNs is 20. |
 | x509 CA certificates | Maximum number of x509 CA certificates that can be registered on IoT Hub is 25. |
 
-<sup>1</sup>This feature isn't available in the basic tier of IoT Hub. For more information, see [How to choose the right IoT Hub](iot-hub-scaling.md).
+<sup>1</sup> This feature isn't available in the basic tier of IoT Hub. For more information, see [How to choose the right IoT Hub](iot-hub-scaling.md).
 
 ## Increase the quota or throttle limit
 
