Merge pull request #226748 from kgremban/feb7-hubpricing

update, clarify pricing and scale

Author: American-Dipper

articles/azure-percept/quickstart-percept-dk-set-up.md

@@ -151,7 +151,7 @@ To verify if your Azure account is an “owner” or “contributor” within th
     - Select the **S1 (standard) pricing tier**.
 
     > [!NOTE]
-    > It may take a few minutes for your IoT Hub deployment to complete. If you need a higher [message throughput](../iot-hub/iot-hub-scaling.md#message-throughput) for your edge AI applications, you may [upgrade your IoT Hub to a higher standard tier](../iot-hub/iot-hub-upgrade.md) in the Azure Portal at any time. B and F tiers do NOT support Azure Percept.
+    > It may take a few minutes for your IoT Hub deployment to complete. If you need a higher [message throughput](../iot-hub/iot-hub-scaling.md#tier-editions-and-units) for your edge AI applications, you may [upgrade your IoT Hub to a higher standard tier](../iot-hub/iot-hub-upgrade.md) in the Azure Portal at any time. B and F tiers do NOT support Azure Percept.
 
 1. When the deployment is complete, select **Register**.
 

articles/iot-hub-device-update/create-update-group.md

@@ -77,7 +77,7 @@ You can schedule a job on multiple devices to add or update a Device Update tag.
 For more information, see [Schedule and broadcast jobs](../iot-hub/iot-hub-csharp-csharp-schedule-jobs.md).
 
 > [!NOTE]
-> This action counts against your IoT Hub messages quota. We recommend only changing up to 50,000 device or module twin tags at a time, otherwise you may need to buy more IoT Hub units if you exceed your daily IoT Hub message quota. For more information, see [Quotas and throttling](../iot-hub/iot-hub-devguide-quotas-throttling.md#quotas-and-throttling).
+> This action counts against your IoT Hub messages quota. We recommend only changing up to 50,000 device or module twin tags at a time, otherwise you may need to buy more IoT Hub units if you exceed your daily IoT Hub message quota. For more information, see [Quotas and throttling](../iot-hub/iot-hub-devguide-quotas-throttling.md).
 
 ### Add tags by updating twins
 
@@ -195,14 +195,14 @@ az iot du device group show \
 
 ## Deleting device groups
 
-While device groups are automatically created, groups, device classes and deployments are not automatically cleaned up so as to retain them for historical records or other user needs. Device groups can be deleted through Azure Portal by individually selecting and deleting the desired groups, or by calling the DELETE API on the group. [Learn more](/cli/azure/iot/du/device/group#az-iot-du-device-group-delete)
+While device groups are automatically created, groups, device classes and deployments are not automatically cleaned up so as to retain them for historical records or other user needs. Device groups can be deleted through Azure portal by individually selecting and deleting the desired groups, or by calling the DELETE API on the group. [Learn more](/cli/azure/iot/du/device/group#az-iot-du-device-group-delete)
 
 If a device is ever connected again for this group after the group is deleted, while the group will be automatically re-created there will be no associated device or deployment history. 
 
 To be deleted, a group must meet the following requirements: 
 * The group must have NO member devices. This means that no device provisioned in the Device Update instance should have a ADUGroup tag with a value matching the selected group's name. 
 * The group must NOT be a default group. 
-* The group must have NO active or cancelled deployments associated with it. 
+* The group must have NO active or canceled deployments associated with it. 
 
 > [!NOTE]
 > If you are still unable to delete a group after meeting the above requirements, then validate whether you have any Unhealthy devices that are tagged as part of the group. Unhealthy devices are devices that cannot receive a deployment, and as a result don't show up directly in the list of member devices within a group. You can validate whether you have any unhealthy devices by going to "Find missing devices" within the Diagnostics tab in the Device Update Portal experience. In case you have Unhealthy devices that are tagged as part of the group, you will need to modify the tag value or delete the device entirely before attempting to delete your group. 

articles/iot-hub/TOC.yml

@@ -96,9 +96,6 @@
           href: query-twins.md
         - name: Job queries
           href: query-jobs.md
-      - name: Quotas and throttling
-        displayName: operations, traffic, connections, latency
-        href: iot-hub-devguide-quotas-throttling.md
       - name: Compare IoT Hub and Event Hubs
         href: iot-hub-compare-event-hubs.md
       - name: React to IoT Hub events with Event Grid
@@ -114,6 +111,9 @@
       - name: Choose the right IoT Hub tier
         displayName: basic, standard, partitions, message throughput
         href: iot-hub-scaling.md
+      - name: Quotas and throttling
+        displayName: operations, traffic, connections, latency
+        href: iot-hub-devguide-quotas-throttling.md
       - name: Pricing examples
         href: iot-hub-devguide-pricing.md
     - name: Messaging