further edits

Author: v-thepet

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

@@ -11,28 +11,18 @@ ms.subservice: device-update
 
 # Manage device groups for Azure Device Update for IoT Hub
 
-Azure Device Update for IoT Hub deploys updates to devices based on their assignment to a device group. You can deploy updates to your IoT devices by using the default group that Device Update creates, or optionally by defining groups of devices to deploy to.
+Azure Device Update for IoT Hub deploys updates to devices based on their device group. You can use the default device group that Device Update provides, or you can define and assign your own device groups to deploy updates to.
 
-You can create and assign user-defined tag values to devices, and Device Update automatically creates groups based on the assigned tags and device compatibility properties. A device group can have multiple subgroups that have different device classes.
+If you create and assign user-defined tag values to devices, Device Update automatically creates groups based on the assigned tags and device compatibility properties. A device group can have multiple subgroups that have different device classes.
 
-This article describes how to use the Azure portal or Azure CLI to manage user-defined Device Update groups and tags. To deploy updates to user-defined groups, or to deploy to the default group without specifying user-defined groups and tags, see [Deploy a device update](deploy-update.md).
+This article describes how to use the Azure portal or Azure CLI to create and manage user-defined Device Update groups and tags. To deploy updates to user-defined or default device groups, see [Deploy a device update](deploy-update.md).
 
 ## Prerequisites
 
 - A Standard (S1) or higher instance of [Azure IoT Hub](/azure/iot-hub/create-hub?tabs=portal) with [Device Update for IoT Hub enabled](create-device-update-account.md).
 - An IoT device or simulator [provisioned for Device Update](device-update-agent-provisioning.md) within the IoT hub. Install and start the Device Update agent on your device either as a module- or device-level identity.
 - An [imported update for the provisioned device](import-update.md).
 
-## Tag properties and limitations
-
-The `ADUGroup` tag that determines Device Update group assignment has the following properties and limitations:
-
-- You can add any value to the tag except the reserved values `Uncategorized` and `$default`.
-- A device can only have one `ADUGroup` tag and belong to only one Device Update group at a time. Adding another tag named `ADUGroup` overrides the existing `ADUGroup` value.
-- The tag value can't exceed 200 characters.
-- The tag value can contain alphanumeric characters and the following special characters: `. - _ ~`.
-- The `ADUGroup` tag name and group name values are case-sensitive.
-
 ## Add tags to your devices
 
 To create a Device Update device group, you add an `ADUGroup` tag to the target set of devices in IoT Hub. The devices must be connected to Device Update.
@@ -51,6 +41,14 @@ The Device Update `ADUGroup` tag uses a key-value format, as shown in the follow
 }
 ```
 
+The `ADUGroup` tag has the following properties and limitations:
+
+- You can add any value to the tag except the reserved values `Uncategorized` and `$default`.
+- A device can only have one `ADUGroup` tag and belong to only one Device Update group at a time. Adding another tag named `ADUGroup` overrides the existing `ADUGroup` value.
+- The tag value can't exceed 200 characters.
+- The tag value can contain alphanumeric characters and the following special characters: `. - _ ~`.
+- The `ADUGroup` tag name and group name values are case-sensitive.
+
 The following sections describe several ways to add and update the tag.
 
 ### Add tags with SDKs
@@ -62,10 +60,10 @@ You can update the device or module twin with the appropriate tag using Registry
 
 ### Add tags using jobs
 
-You can schedule a job to add or update Device Update tags on multiple devices. For examples of job operations, see [Schedule jobs on multiple devices](../iot-hub/iot-hub-devguide-jobs.md). You can update either device twins or module twins using jobs, depending on whether the Device Update agent is provisioned with a device or module identity. For more information, see [Schedule and broadcast jobs](../iot-hub/iot-hub-csharp-csharp-schedule-jobs.md).
+You can schedule jobs to add or update Device Update tags on multiple devices. For examples of job operations, see [Schedule jobs on multiple devices](../iot-hub/iot-hub-devguide-jobs.md). You can update either device twins or module twins using jobs, depending on whether the Device Update agent is provisioned with a device or module identity. For more information, see [Schedule and broadcast jobs](../iot-hub/iot-hub-csharp-csharp-schedule-jobs.md).
 
 > [!NOTE]
-> This job operation counts against your IoT Hub messages quota. If you change 50,000 or more device or module twin tags at a time, you might exceed your daily IoT Hub message quota and need to buy more IoT Hub units. For more information, see [Quotas and throttling](../iot-hub/iot-hub-devguide-quotas-throttling.md).
+> This operation counts against your IoT Hub messages quota. If you change 50,000 or more device or module twin tags at a time, you might exceed your daily IoT Hub message quota and need to buy more IoT Hub units. For more information, see [Quotas and throttling](../iot-hub/iot-hub-devguide-quotas-throttling.md).
 
 ### Add tags by updating twins
 
@@ -174,6 +172,8 @@ az iot du device group show \
     --account <Device Update account name> \
     --instance <Device Update instance name> \
     --group-id <value of the ADUGroup tag for this group>
+    --best-updates
+    --update-compliance
 ```
 
 ---

articles/iot-hub-device-update/deploy-update.md

@@ -12,7 +12,7 @@ ms.subservice: device-update
 
 # Deploy an update by using Azure Device Update for IoT Hub
 
-In this article, you learn how to deploy an update to IoT devices by using Azure Device Update for IoT Hub in the Azure portal or with Azure CLI.
+In this article, you learn how to use the Azure portal or Azure CLI to deploy an update to IoT devices by using Azure Device Update for IoT Hub.
 
 ## Prerequisites
 
@@ -32,11 +32,11 @@ This section describes how to deploy the update by using the Azure portal or Azu
 
    :::image type="content" source="media/deploy-update/device-update-iot-hub.png" alt-text="Screenshot that shows the Get started with the Device Update for IoT Hub page." lightbox="media/deploy-update/device-update-iot-hub.png":::
 
-1. On the **Updates** page, select the **Groups and Deployments** tab and view the [update compliance chart](device-update-compliance.md) and [device group list](device-update-groups.md).
+1. On the **Updates** page, select the **Groups and Deployments** tab and view the [update compliance chart](device-update-compliance.md) and [device group list](device-update-groups.md). You might need to refresh the view to see the new imported update available for your device group.
 
-   :::image type="content" source="media/deploy-update/updated-view.png" alt-text="Screenshot that shows the Groups and Deployments tab." lightbox="media/deploy-update/updated-view.png":::
+   Under **Status** in the group list, select **Deploy** next to **One or more new updates are available for this group**.
 
-1.  You might need to refresh the view to see the new imported update available for your device group. Under **Status** in the group list, select **Deploy** next to **One or more new updates are available for this group**.
+   :::image type="content" source="media/deploy-update/updated-view.png" alt-text="Screenshot that shows the Groups and Deployments tab." lightbox="media/deploy-update/updated-view.png":::
 
 1. On the **Group details** page, confirm that the correct group and imported update appear. To start the deployment, on the **Current deployment** tab, select the **Deploy** link next to the desired update in the **Available updates** section. The best available update for a given group is denoted with a **Best** highlight.
 
@@ -78,30 +78,30 @@ Or, if you prefer, you can run the Azure CLI commands locally:
 
 ### Verify update availability
 
-1. Use the [`az iot du device group list`](/cli/azure/iot/du/device/group#az-iot-du-device-group-list) command to find your device group information.
+1. Use the [`az iot du device group list`](/cli/azure/iot/du/device/group#az-iot-du-device-group-list) command to identify your device group.
 
    ```azurecli
    az iot du device group list \
        --account <Device Update account name> \
        --instance <Device Update instance name>\
    ```
 
-1. Then use [`az iot du device group show`](/cli/azure/iot/du/device/group#az-iot-du-device-group-show) to verify the best available update for your group. The command takes the following arguments:
+1. Then use [`az iot du device group show`](/cli/azure/iot/du/device/group#az-iot-du-device-group-show) to show the best available update for your group. The command takes the following arguments:
 
    - `--account`: The Device Update account name.
    - `--instance`: The Device Update instance name.
-   - `--resource-group`: Device Update account resource group name.
-   - `--group-id`: The device group ID that you're targeting with this deployment, either the value of the `ADUGroup` tag, or `$default` for devices with no tag.
-   - `--best-updates`: Fetches the best available updates for the device group, including a count of how many devices need each update.
-   - `--update-compliance`: Fetches device group update compliance information, such as how many devices are on their latest update, how many need new updates, and how many are currently receiving a new update.
+   - `--group-id`: The device group ID that you're targeting with this deployment, which is either the value of the `ADUGroup` tag, or `$default` for devices with no tag.
+   - `--resource-group`: The Device Update account resource group name.
+   - `--best-updates`: Returns the best available updates for the device group, including a count of how many devices need each update.
+   - `--update-compliance`: Returns device group update compliance information, such as how many devices are on their latest update, how many need new updates, and how many are currently receiving a new update.
 
-   Run the command as follows:
+   To verify the best available update for your group, run the command as follows:
 
    ```azurecli
    az iot du device group show \
        --account <Device Update account name> \
        --instance <Device Update instance name>\
-       --gid <device group id>\
+       --group-id <device group ID>\
        --best-updates
    ```
 
@@ -111,7 +111,7 @@ Use [`az iot du device deployment create`](/cli/azure/iot/du/device/deployment#a
 
 - `--account`: The Device Update account name.
 - `--instance`: The Device Update instance name.
-- `--group-id`: The device group ID that you're targeting with this deployment, either the value of the `ADUGroup` tag, or `$default` for devices with no tag.
+- `--group-id`: The device group ID that you're targeting with this deployment, which is either the value of the `ADUGroup` tag, or `$default` for devices with no tag.
 - `--deployment-id`: An ID to identify this deployment.
 - `--update-name`, `--update-provider`, and `--update-version`: The parameters that define the `updateId` object, a unique identifier for the update in this deployment.
 
@@ -121,8 +121,8 @@ Run the command as follows:
 az iot du device deployment create \
     --account <Device Update account name> \
     --instance <Device Update instance name> \
-    --group-id <device group id> \
-    --deployment-id <deployment id> \
+    --group-id <device group ID> \
+    --deployment-id <deployment ID> \
     --update-name <update name> \
     --update-provider <update provider> \
     --update-version <update version>
@@ -144,8 +144,8 @@ Run the command as follows:
 az iot du device deployment create \
     --account <Device Update account name> \
     --instance <Device Update instance name> \
-    --group-id <device group id> \
-    --deployment-id <deployment id> \
+    --group-id <device group ID> \
+    --deployment-id <deployment ID> \
     --update-name <update name> \
     --update-provider <update provider> \
     --update-version <update version> \

articles/iot-hub-device-update/device-update-groups.md

@@ -11,13 +11,13 @@ ms.subservice: device-update
 
 # Azure Device Update for IoT Hub device groups
 
-An Azure Device Update for IoT Hub device group is a collection of IoT devices that Device Update uses to target deployments. All devices that have the Device Update agent installed and provisioned belong to a device group, either a default group or a user-defined group. A device can belong to only one Device Update device group at a time.
+An Azure Device Update for IoT Hub device group is a collection of IoT devices that Device Update uses to target update deployments. All devices that have the Device Update agent installed and provisioned belong to a device group, either a default group or a user-defined group. A device can belong to only one Device Update device group at a time.
 
-To organize and deploy to your devices, you can use the default device group that Device Update assigns, or you can use multiple user-defined device groups. For example, the Contoso organization might assign the devices in its test laboratory to a "Flighting" device group and assign the devices its operations center field team uses to an "Evaluation" device group. Contoso might also choose to group their production devices based on geographic regions, so they can update devices on a schedule that aligns with their regional timezones.
+To deploy updates to your devices, you can use the default device group that Device Update provides, or you can define and assign multiple device groups to organize your devices. For example, the Contoso organization might assign the devices in its test laboratory to a "Flighting" device group and assign the devices its operations center field team uses to an "Evaluation" device group. Contoso might also choose to group their production devices based on geographic regions, so they can update devices on a schedule that aligns with their regional timezones.
 
 ## User-defined device groups
 
-You use *tags* to group devices. The `ADUGroup` key with a user-defined value in the `"tags"` section of the device twin or module twin specifies a user-defined device group for Device Update.
+You use *tags* to group devices. Device Update creates user-defined groups for devices that have an `ADUGroup` tag with a user-defined value in the `"tags"` section of their device twins or module twins.
 
 ```json
 "tags": {
@@ -31,7 +31,7 @@ Devices that have the Device Update agent installed and provisioned but don't ha
 
 Users can't delete or recreate default groups, change their definitions, or add or remove devices from default groups manually. Default group names have the format `Default-<deviceClassID>`, and are reserved within an IoT solution.
 
-The default groups help reduce the overhead of tagging and grouping devices and make it easier to deploy updates to untagged devices. All deployment features that are available for user-defined groups are also available for default, system-assigned groups.
+Default groups help reduce the overhead of tagging and grouping devices and make it easier to deploy updates to untagged devices. All deployment features that are available for user-defined groups are also available for default, system-assigned groups.
 
 ## Example device group assignments