couple more touchups

Author: v-thepet

articles/iot-hub-device-update/configure-access-control-device-update.md

@@ -11,7 +11,7 @@ ms.subservice: device-update
 
 # Configure access control for Device Update resources
 
-For users to access Azure Device Update for IoT Hub, you must grant them access to the Device Update account and instance. You must also grant the Device Update service principal access to the linked IoT hub so it can manage updates and gather information. This article describes how to grant the necessary access by using the Azure portal or the Azure CLI.
+For users to access Azure Device Update for IoT Hub, you must grant them access to the Device Update account and instance. You must also grant the Device Update service principal access to the linked IoT hub so it can manage updates and gather information. This article describes how to grant the necessary access by using Azure role-based access control (RBAC) in the Azure portal or Azure CLI.
 
 ## Prerequisites
 
@@ -21,7 +21,7 @@ For users to access Azure Device Update for IoT Hub, you must grant them access
 
 ## Configure access control for Device Update account
 
-The following roles are available through Azure role-based access control (RBAC) for assigning access to Device Update:
+The following roles are available for assigning access to Device Update:
 
 - Device Update Administrator
 - Device Update Reader
@@ -48,7 +48,7 @@ For more information, see [Azure role-based access control (RBAC) and Device Upd
 
 1. Select **Review + assign**.
 1. Review the new role assignments and select **Review + assign** again.
-1. Azure role-based access control (RBAC) adds the role assignments, and the selected members can now use Device Update from within your IoT Hub.
+1. Azure RBAC adds the role assignments, and the selected members can now use Device Update from within your IoT Hub.
 
 # [Azure CLI](#tab/cli)
 
@@ -90,7 +90,7 @@ Device Update communicates with IoT Hub to manage deployments and updates and to
 
    :::image type="content" source="media/create-device-update-account/assign-role-to-du-service-principal.png" alt-text="Screenshot of access Control member selection for IoT Hub." lightbox="media/create-device-update-account/assign-role-to-du-service-principal.png":::
 
-6. Select **Review + Assign** and then select **Review + Assign** again.
+6. Select **Review + assign** and then select **Review + assign** again.
 
 To validate that you set permissions correctly:
 
@@ -114,4 +114,4 @@ az role assignment create --role "IoT Hub Data Contributor" --assignee https://a
 ## Related content
 
 - [Azure role-based access control (RBAC) and Device Update](device-update-control-access.md)
-- [az role assignment](/cli/azure/role/assignment)
+- [Command reference for az role assignment](/cli/azure/role/assignment)

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

@@ -1,6 +1,6 @@
 ---
 title: Prepare an update to import into Azure Device Update for IoT Hub | Microsoft Docs
-description: Learn how to prepare a new update to import into Azure Device Update for IoT Hub.
+description: Learn how to prepare an update for import into Azure Device Update for IoT Hub by creating an import manifest to describe the update.
 author: andrewbrownmsft
 ms.author: andbrown
 ms.date: 12/20/2024
@@ -12,7 +12,7 @@ ms.subservice: device-update
 
 # Prepare an update to import into Device Update
 
-This article describes how to get a new update and prepare it for importing into Azure Device Update for IoT Hub.
+This article describes how to get a new update and prepare it for importing into Azure Device Update for IoT Hub by creating an import manifest.
 
 ## Prerequisites
 
@@ -31,30 +31,26 @@ This article describes how to get a new update and prepare it for importing into
 >[!TIP]
 >The Azure CLI commands in this article use the backslash \\ character for line continuation so that the command arguments are easier to read. This syntax works in Bash environments. If you run these commands in PowerShell, replace each backslash with a backtick \`, or remove them entirely.
 
-## Obtain an update for your device
+<a name="obtain-an-update-for-your-device"></a>
+## Get the update files for your device
 
-Get one or more update files to deploy to your device.
+Get the update file or files to deploy to your device using Device Update. If you purchased devices from an original equipment manufacturer (OEM) or solution integrator, that organization probably provides updates without you having to create update files. Contact the OEM or solution integrator to find out how they make updates available. If your organization creates software for your devices, it also creates the updates for that software.
 
-If you purchased devices from an Original Equipment Manufacturer (OEM) or solution integrator, that organization probably provides updates without you having to create update files. Contact the OEM or solution integrator to find out how they make updates available. If your organization creates software for the devices you use, the same organization creates the updates for that software.
-
-When you create an update to deploy using Device Update, use either the [image-based or package-based approach](understand-device-update.md#support-for-a-wide-range-of-update-artifacts), depending on your scenario.
+To create the update, choose either the [image-based or package-based update type](understand-device-update.md#support-for-a-wide-range-of-update-artifacts), depending on your scenario.
 
 > [!TIP]
 > You can try the [image-based](device-update-raspberry-pi.md), [package-based](device-update-ubuntu-agent.md), or [proxy update](device-update-howto-proxy-updates.md) tutorials, or just view sample import manifest files from those tutorials for reference.
 
 ## Create a basic Device Update import manifest
 
-Once you have your update files and are familiar with basic [Device Update import concepts](import-concepts.md), create an import manifest to describe the update. While you can author a JSON import manifest manually using a text editor, the Azure CLI [az iot du init v5](/cli/azure/iot/du/update/init#az-iot-du-update-init-v5) command simplifies the process, as shown in the following examples. For more information, see [Device Update import schema and API information](import-schema.md).
+Once you have your update files and are familiar with basic [Device Update import concepts](import-concepts.md), create an import manifest to describe the update. While you can author a JSON import manifest manually using a text editor, the Azure CLI [az iot du init v5](/cli/azure/iot/du/update/init#az-iot-du-update-init-v5) command simplifies the process. For more information about the import manifest schema, see [Device Update import schema and API information](import-schema.md).
 
 The `az iot du init v5` command takes the following arguments. All are required except `--file`, which is derived from `--step` if not specified. There is positional sensitivity between `--step` and `--file`.
 
 - The `--update-provider`, `--update-name`, and `--update-version` parameters define the `updateId` object that's a unique identifier for each update.
 - The `--compat` compatibility object is a set of name-value pairs that describe the properties of a device that this update is compatible with. You can use a specific set of compatibility properties with only one provider and name combination.
-- `--step` specifies the update `handler` on the device, such as `microsoft/script:1`, `microsoft/swupdate:1`, or `microsoft/apt:1`, and its associated `properties` for this update. You can use `--step` more than one time.
-- `--file` specifies the `path` to your update files. You can use `--file` one or more times.
-
-> [!TIP]
-> For handler properties, you might need to escape certain characters in your JSON. For example, use `'\'` to escape double quotes if you run the Azure CLI in PowerShell.
+- The `--step` parameter specifies the update `handler` on the device, such as `microsoft/script:1`, `microsoft/swupdate:1`, or `microsoft/apt:1`, and its associated `properties` for this update. You can use `--step` more than once.
+- The `--file` parameter specifies the `path` to your update files. You can use `--file` one or more times.
 
 ```azurecli
 az iot du update init v5 \
@@ -66,7 +62,7 @@ az iot du update init v5 \
     --file path=<paths and full file names of your update files> 
 ```
 
-For example:
+The following `az iot du update init v5` command shows example values:
 
 ```azurecli
 az iot du update init v5 \
@@ -78,6 +74,9 @@ az iot du update init v5 \
     --file path=/my/apt/manifest/file
 ```
 
+> [!TIP]
+> For handler properties, you might need to escape certain characters in your JSON. For example, use `'\'` to escape double quotes if you run the Azure CLI in PowerShell.
+
 The `az iot du init v5` command supports advanced scenarios, including the [related files feature](related-files.md) that allows you to define the relationship between different update files. For more examples and a complete list of optional parameters, see the [az iot du init v5](/cli/azure/iot/du/update/init#az-iot-du-update-init-v5) command reference.
 
 Once you create your import manifest and save it as a JSON file, you can [import the update](import-update.md). If you plan to use the Azure portal for importing, be sure to name your import manifest with the format *\<manifestname\>.importmanifest.json*.
@@ -86,7 +85,7 @@ Once you create your import manifest and save it as a JSON file, you can [import
 
 If your update is more complex, such as a [proxy update](device-update-proxy-updates.md), you might need to create multiple import manifests. For complex updates, you can use the `az iot du update init v5` Azure CLI command to create a *parent* import manifest and some number of *child* import manifests.
 
-Run the following Azure CLI commands after replacing the placeholder values. For details on the values you can use, see [Import schema and API information](import-schema.md). The following example shows three updates to deploy to the device, a parent update and two child updates.
+Replace the placeholder values in the following Azure CLI commands. For details on the values you can use, see [Import schema and API information](import-schema.md). The following example shows three updates to deploy to the device, a parent update and two child updates.
 
 ```azurecli
 az iot du update init v5 \