review corrections

v-thepet · v-thepet · commit e51a09a11dbd · 2024-12-17T16:15:33.000-08:00
diff --git a/articles/iot-hub-device-update/device-update-raspberry-pi.md b/articles/iot-hub-device-update/device-update-raspberry-pi.md
@@ -3,7 +3,7 @@ title: Azure Device Update for IoT Hub using a Raspberry Pi image
 description: Do an end-to-end image-based Azure Device Update for IoT Hub update using a Raspberry Pi 3 B+ Yocto image.
 author: eshashah
 ms.author: eshashah
-ms.date: 12/09/2024
+ms.date: 12/17/2024
 ms.topic: tutorial
 ms.service: azure-iot-hub
 ms.subservice: device-update
@@ -47,7 +47,7 @@ Add your device to the device registry in your IoT hub and get the connection st
 > [!NOTE]
 > For demonstration purposes, this tutorial uses a device connection string to authenticate and connect with the IoT hub. For production scenarios, it's better to use module identity and [IoT Identity Service](https://azure.github.io/iot-identity-service/) to provision devices. For more information, see [Device Update agent provisioning](device-update-agent-provisioning.md).
    
-## Get the update files and flash the Raspberry Pi board
+## Set up Raspberry Pi
 
 The *Tutorial_RaspberryPi3.zip* file has all the required files for the tutorial. Download the file from the **Assets** section of the latest release on the [GitHub Device Update Releases page](https://github.com/Azure/iot-hub-device-update/releases), and unzip it.
 
@@ -61,6 +61,14 @@ The update files you import through Device Update are:
 
 ### Use bmaptool to flash the SD card
 
+>[!IMPORTANT]
+>Azure Device Update for IoT Hub software is subject to the following license terms:
+>
+>- [Device update for IoT Hub license](https://github.com/Azure/iot-hub-device-update/blob/main/LICENSE)
+>- [Delivery optimization client license](https://github.com/microsoft/do-client/blob/main/LICENSE)
+>
+>Read the license terms before using the agent. Agent installation and use constitutes acceptance of these terms. If you don't agree with the license terms, don't use the Device Update agent.
+
 Use an OS flashing tool to install the Device Update base image on the SD card you use in the Raspberry Pi device. The following instructions use `bmaptool` to flash to the SD card. Replace the `<device>` placeholder with your device name and the `<path to image>` placeholder with the path to the downloaded image file.
 
 1. Install the `bmap-tools` utility if you don't have it.
@@ -91,22 +99,14 @@ Use an OS flashing tool to install the Device Update base image on the SD card y
    >[!TIP]
    >For faster flashing, you can download the bimap file and the image file and put them in the same directory.
 
-## Install the Device Update agent on Raspberry Pi
-
->[!IMPORTANT]
->Azure Device Update for IoT Hub software is subject to the following license terms:
->
->- [Device update for IoT Hub license](https://github.com/Azure/iot-hub-device-update/blob/main/LICENSE)
->- [Delivery optimization client license](https://github.com/microsoft/do-client/blob/main/LICENSE)
->
->Read the license terms before using the agent. Agent installation and use constitutes acceptance of these terms. If you don't agree with the license terms, don't use the Device Update agent.
+## Configure the Device Update agent on Raspberry Pi
 
 1. Make sure that the Raspberry Pi is connected to the network.
 
 1. Secure shell (SSH) into the Raspberry Pi by using the following command in a PowerShell window:
 
    ```shell
-     ssh raspberrypi3 -l root
+   ssh raspberrypi3 -l root
    ```
 
 ### Create the Device Update configuration files
@@ -116,7 +116,7 @@ The Device Update *du-config.json* and *du-diagnostics-config.json* configuratio
 1. To create the *du-config.json* file or open it for editing, run the following command:
 
    ```bash
-     nano /adu/du-config.json
+   nano /adu/du-config.json
    ```
 
 1. The editor opens the *du-config.json* file. If you're creating the file, it's empty. Copy and paste the following code into the file, replacing the example values with any required configurations for your device. Replace the example `connectionData` string with the device connection string you copied in the device registration step.
@@ -150,7 +150,7 @@ The Device Update *du-config.json* and *du-diagnostics-config.json* configuratio
 1. Create the *du-diagnostics-config.json* file by using similar commands. Create and open the file:
 
    ```bash
-     nano /adu/du-diagnostics-config.json
+   nano /adu/du-diagnostics-config.json
    ```
 
 1. Copy and paste the following *du-diagnostics-config.json* code into the file. The values are the default Device Update log locations, and you need to change them only if your configuration differs from the default.
@@ -176,29 +176,29 @@ The Device Update *du-config.json* and *du-diagnostics-config.json* configuratio
 1. Use the following command to show the files located in the */adu/* directory. You should see both configuration files.
 
    ```bash
-     ls -la /adu/
+   ls -la /adu/
    ```
 
 1. Use the following command to restart the Device Update system daemon and ensure configurations are applied.
 
    ```bash
-     systemctl start deviceupdate-agent
+   systemctl start deviceupdate-agent
    ```
 
 1. Check that the agent is live by running the following command:
   
    ```bash
-     systemctl status deviceupdate-agent
+   systemctl status deviceupdate-agent
    ```
 
    Status should appear as alive and green.
 
 ## Connect to the device in IoT Hub and add a group tag
 
 1. On the [Azure portal](https://portal.azure.com) IoT hub page for your Device Update instance, select **Device management** > **Devices** from the left navigation.
-1. On the **Devices** page, select the link with your device name.
+1. On the **Devices** page, select your device's name.
 1. At the top of the device page, select **Device twin**.
-1. On the **Device twin** page, under the `"reported"` section of the device twin`"properties"` section, look for the Linux kernel version for your device.
+1. On the **Device twin** page, under the `"reported"` section of the device twin `"properties"` section, look for the Linux kernel version for your device.
 
    For a new device that hasn't received an update from Device Update, the [DeviceManagement:DeviceInformation:1.swVersion](device-update-plug-and-play.md#device-information-interface) property value represents the firmware version running on the device. After the device has an update applied, the [AzureDeviceUpdateCore:ClientMetadata:4.installedUpdateId](device-update-plug-and-play.md#agent-metadata) property value represents the firmware version.
 
@@ -227,15 +227,21 @@ Device Update automatically organizes devices into groups based on their assigne
 1. On the [Azure portal](https://portal.azure.com) IoT hub page for your Device Update instance, select **Device Management** > **Updates** from the left navigation.
 1. On the **Updates** page, select **Import a new update**.
 1. On the **Import update** page, select **Select from storage container**.
-1. On the **Storage accounts** page, select an existing storage account or create a new account by using **+ Storage account**.
-1. On the **Containers** page, select an existing container or create a new container by using **+ Container**. You use the container to stage the update files for import.
+1. On the **Storage accounts** page, select an existing storage account or create a new account by selecting **Storage account**.
+1. On the **Containers** page, select an existing container or create a new container by selecting **Container**. You use the container to stage the update files for import.
 
    :::image type="content" source="media/import-update/storage-account-ppr.png" alt-text="Screenshot that shows Storage accounts and Containers.":::
 
    > [!TIP]
    > To avoid accidentally importing files from previous updates, use a new container each time you import an update. If you don't use a new container, be sure to delete any files from the existing container.
 
-1. On the container page, select **Upload**. Drag and drop, or browse to and select, the update files you downloaded, and then select **Upload**. After they upload, the files appear on the container page.
+1. On the container page, select **Upload**. Drag and drop, or browse to and select, the following update files from the *Tutorial_RaspberryPi3* folder you downloaded:
+
+   - *adu-update-image-raspberrypi3-1.2.0.swu* 
+   - *example-a-b-update.sh* 
+   - *EDS-ADUClient.yocto-update.1.2.0.importmanifest.json*
+
+1. Select **Upload**. After they upload, the files appear on the container page.
 
 1. On the container page, review and select the files to import, and then select **Select**.
 
diff --git a/articles/iot-hub-device-update/device-update-simulator.md b/articles/iot-hub-device-update/device-update-simulator.md
@@ -1,9 +1,9 @@
 ---
 title: Azure Device Update for IoT Hub using a simulator agent
-description: Get started with Device Update for Azure IoT Hub using the Ubuntu simulator agent.
+description: Get started with Device Update for Azure IoT Hub using the Ubuntu 18.04 simulator agent.
 author: kgremban
 ms.author: kgremban
-ms.date: 12/09/2024
+ms.date: 12/17/2024
 ms.topic: tutorial
 ms.service: azure-iot-hub
 ms.subservice: device-update
@@ -22,17 +22,16 @@ In this tutorial, you:
 > - Download and install an image update.
 > - Import the image update.
 > - Deploy the image update.
-> - View update deployment history.
+> - View the update deployment history.
 
 ## Prerequisites
 
-- An IoT device
-- An Ubuntu 18.04 or higher x64 physical or virtual machine
+- An Ubuntu 18.04 x64 physical or virtual machine
 - A [Device Update account and instance configured with an IoT hub](create-device-update-account.md)
 
 ## Register and configure a device and module
 
-Add the device to the device registry in your IoT hub. Every device that connects to IoT Hub must be registered.
+Add a device to the device registry in your IoT hub. Every device that connects to IoT Hub must be registered.
 
 1. In the [Azure portal](https://portal.azure.com), open the IoT hub page associated with your Device Update instance.
 1. In the navigation pane, select **Device management** > **Devices**.
@@ -63,15 +62,18 @@ You can assign a tag to any device that Device Update manages to assign the devi
 
    ```json
    "tags": {
-       "DeviceUpdateGroup": "simulator-tutorial"
+       "DeviceUpdateGroup": "DU-simulator-tutorial"
    },
    ```
 
 1. Select **Save**. The portal reformats the module twin to incorporate the tag into the JSON structure.
 
 ## Install and configure the Device Update agent
 
-The Device Update agent runs on every device that Device Update manages. In this tutorial, you install the Device Update agent on your device and configure it to run as a simulator, demonstrating how you can apply an update to a device without changing the device configuration.
+The Device Update agent runs on every device that Device Update manages. In this tutorial, you install the Device Update agent on the Ubuntu 18.04 device and configure it to run as a simulator, demonstrating how you can apply an update to a device without changing the device configuration.
+
+>[!NOTE]
+>You can also use the Azure IoT Identity Service to provision the device. To do that, [install the Azure IoT Identity Service](https://azure.github.io/iot-identity-service/installation.html) before installing the Device Update agent. Then configure the Device Update agent with `"connectionType": "AIS"` and leave `connectionData` as a blank string in the configuration file.
 
 1. Add the Microsoft package repository, and then add the Microsoft package signing key to your list of trusted keys.
 
@@ -131,9 +133,6 @@ The Device Update agent runs on every device that Device Update manages. In this
 
 1. Press **Ctrl**+**X** to exit the editor, and enter *y* to save your changes.
 
-   >[!NOTE]
-   >You can also use the Azure IoT Identity Service to provision the device. To do that, [install the Azure IoT Identity Service](https://azure.github.io/iot-identity-service/installation.html) before installing the Device Update agent. Then configure the Device Update agent with `"connectionType": "AIS"` and leave `connectionData` as a blank string in the configuration file.
-
 1. To set up the agent to run as a simulator, run the following command on the IoT device. The Device Update agent invokes the simulator handler to process updates that use the Microsoft SWUpdate extension.
 
    ```bash
@@ -142,7 +141,7 @@ The Device Update agent runs on every device that Device Update manages. In this
 
 ### Get the simulator files
 
-1. Download and extract the *Tutorial_Simulator.zip* archive from the [GitHub Device Update Releases](https://github.com/Azure/iot-hub-device-update/releases) latest release **Assets** section. If your test device and development machine are separate devices, download and extract the ZIP file onto both devices.
+1. Download and extract the *Tutorial_Simulator.zip* archive from the [GitHub Device Update Releases](https://github.com/Azure/iot-hub-device-update/releases) latest release **Assets** section onto your Ubuntu 18.04 machine.
 
    You can use `wget` to download the ZIP file. Replace `<release_version>` with the latest release, for example `1.0.0`.
 
@@ -180,19 +179,21 @@ The Device Update agent runs on every device that Device Update manages. In this
 
 ## Import the update
 
-This section uses the *TutorialImportManifest_Sim.importmanifest.json* and *adu-update-image-raspberrypi3.swu* files from the downloaded *Tutorial_Simulator* folder. The update file is the same one as in the [Raspberry Pi tutorial](device-update-raspberry-pi.md). Because the update in this tutorial is simulated, the specific file content doesn't matter.
+Download and extract the *Tutorial_Simulator.zip* archive from the [GitHub Device Update Releases](https://github.com/Azure/iot-hub-device-update/releases) latest release **Assets** section onto your development machine if it's different from your Ubuntu 18.04 IoT device. This section uses the *TutorialImportManifest_Sim.importmanifest.json* and *adu-update-image-raspberrypi3.swu* files from the *Tutorial_Simulator* folder.
+
+The update file is the same one as in the [Raspberry Pi tutorial](device-update-raspberry-pi.md). Because the update in this tutorial is simulated, the specific file content doesn't matter.
 
 1. On your development machine, sign in to the [Azure portal](https://portal.azure.com/) and go to the IoT hub configured with your Device Update instance.
 1. In the navigation pane, select **Device Management** > **Updates**.
 1. On the **Updates** page, select **Import a new update**.
 1. On the **Import update** page, select **Select from storage container**.
-1. Select an existing storage account, or create a new account by selecting **+ Storage account**.
-1. Select an existing container, or create a new container by selecting **+ Container**. This container is used to stage the update files for importing.
+1. Select an existing storage account, or create a new account by selecting **Storage account**.
+1. Select an existing container, or create a new container by selecting **Container**. This container is used to stage the update files for importing.
 
    > [!NOTE]
    > To avoid accidentally importing files from previous updates, use a new container each time you import an update. If you don't use a new container, be sure to delete any files from the existing container.
 
-1. On the container page, select **Upload**, browse to and select the *TutorialImportManifest_Sim.importmanifest.json* and *adu-update-image-raspberrypi3.swu* files, and then select **Upload**.
+1. On the container page, select **Upload**. Browse to and select the *TutorialImportManifest_Sim.importmanifest.json* and *adu-update-image-raspberrypi3.swu* files, and then select **Upload**.
 
 1. Select the checkboxes by both files and then select **Select** to return to the **Import update** page.
 
@@ -246,7 +247,7 @@ You should see the device group that contains the simulated device you set up in
 
 ## Clean up resources
 
-When you no longer need the resources you created for this tutorial, you can delete them.
+If you're going to continue to the next tutorial, keep your Device Update and IoT Hub resources. When you no longer need the resources you created for this tutorial, you can delete them.
 
 1. In the [Azure portal](https://portal.azure.com), navigate to the resource group that contains the resources.
 1. If you want to delete all the resources in the group, select **Delete resource group**.
diff --git a/articles/iot-hub-device-update/device-update-ubuntu-agent.md b/articles/iot-hub-device-update/device-update-ubuntu-agent.md
@@ -3,7 +3,7 @@ title: Azure Device Update for IoT Hub using the Ubuntu package agent
 description: Perform an end-to-end package update using the Device Update Ubuntu Server 22.04 x64 package agent to update Azure IoT Edge.
 author: eshashah
 ms.author: eshashah
-ms.date: 12/09/2024
+ms.date: 12/17/2024
 ms.topic: tutorial
 ms.service: azure-iot-hub
 ms.subservice: device-update
@@ -31,9 +31,9 @@ In this tutorial, you:
 ## Prerequisites
 
 - A [Device Update account and instance configured with an IoT hub](create-device-update-account.md).
-- An [Azure IoT Edge Device in the IoT hub with the connection string copied](../iot-edge/how-to-provision-single-device-linux-symmetric.md?view=iotedge-2020-11&preserve-view=true#view-registered-devices-and-retrieve-provisioning-information).
+- An [Azure IoT Edge device registered in the IoT hub with the connection string copied](../iot-edge/how-to-provision-single-device-linux-symmetric.md?view=iotedge-2020-11&preserve-view=true#view-registered-devices-and-retrieve-provisioning-information).
 
-## Prepare the VM and device
+## Prepare the device
 
 For convenience, this tutorial uses a [cloud-init](/azure/virtual-machines/linux/using-cloud-init) based [Azure Resource Manager (ARM) template](/azure/azure-resource-manager/templates/overview) to quickly set up an Ubuntu 22.04 LTS virtual machine (VM). The template installs both the IoT Edge runtime and the Device Update package agent, and automatically configures the device with provisioning information by using the IoT Edge device connection string you supply. Using the ARM template also avoids the need to start a secure shell (SSH) session to complete setup.
 
@@ -125,15 +125,15 @@ Device Update uses groups to organize devices. Device Update automatically sorts
 
 ## Import the update
 
-The *Tutorial_IoTEdge_PackageUpdate.zip* file has the required files for the tutorial. Download the file from the **Assets** section of the latest release on the [GitHub Device Update Releases page](https://github.com/Azure/iot-hub-device-update/releases), and unzip it.
-
-The extracted *Tutorial_IoTEdge_PackageUpdate* folder contains the *sample-defender-iot-apt-manifest.json* sample APT manifest and its corresponding *sample-defender-iot--importManifest.json* import manifest.
+The *Tutorial_IoTEdge_PackageUpdate.zip* file has the required files for the tutorial.
 
+1. Download the *Tutorial_IoTEdge_PackageUpdate.zip* file from the **Assets** section of the latest release on the [GitHub Device Update Releases page](https://github.com/Azure/iot-hub-device-update/releases).
+1. Unzip the file. The extracted *Tutorial_IoTEdge_PackageUpdate* folder contains the *sample-defender-iot-apt-manifest.json* sample APT manifest and its corresponding *sample-defender-iot--importManifest.json* import manifest.
 1. On the [Azure portal](https://portal.azure.com) IoT hub page for your Device Update instance, select **Device Management** > **Updates** from the left navigation.
 1. On the **Updates** page, select **Import a new update**.
 1. On the **Import update** page, select **Select from storage container**.
-1. On the **Storage accounts** page, select an existing storage account or create a new account by selecting **+ Storage account**.
-1. On the **Containers** page, select an existing container or create a new container by using **+ Container**. You use the container to stage the update files for import.
+1. On the **Storage accounts** page, select an existing storage account or create a new account by selecting **Storage account**.
+1. On the **Containers** page, select an existing container or create a new container by selecting **Container**. You use the container to stage the update files for import.
 
    :::image type="content" source="media/import-update/storage-account-ppr.png" alt-text="Screenshot that shows Storage accounts and Containers.":::
 
