Merge pull request #277852 from timlt/update-device-tutorials

Update IoT Explorer include, review freshness, Acro updates

Author: prmerger-automator[bot]

articles/iot/tutorial-devkit-espressif-esp32-freertos-iot-hub.md

@@ -6,7 +6,7 @@ ms.author: timlt
 ms.service: iot
 ms.devlang: c
 ms.topic: tutorial
-ms.date: 04/04/2024
+ms.date: 06/11/2024
 #Customer intent: As a device builder, I want to see a working IoT device sample using FreeRTOS to connect to Azure IoT Hub.  The device should be able to send telemetry and respond to commands. As a solution builder, I want to use a tool to view the properties, commands, and telemetry an IoT Plug and Play device reports to the IoT hub it connects to.
 ---
 
@@ -67,7 +67,7 @@ To connect the ESP32 DevKit to Azure, you modify configuration settings, build t
 
 ### Set up the environment
 To launch the ESP-IDF environment:
-1. Select Windows **Start**, find **ESP-IDF 5.0 CMD** and run it. 
+1. Select Windows **Start**, find **ESP-IDF 5.0 CMD**, and run it. 
 1. In **ESP-IDF 5.0 CMD**, navigate to the *iot-middleware-freertos-samples* directory that you cloned previously.
 1. Navigate to the ESP32-Azure IoT Kit project directory *demos\projects\ESPRESSIF\aziotkit*.
 1. Run the following command to launch the configuration menu:
@@ -211,7 +211,7 @@ To view and edit device properties using Azure IoT Explorer:
 
 To use Azure CLI to view device properties:
 
-1. In your CLI console, run the [az iot hub device-twin show](/cli/azure/iot/hub/device-twin#az-iot-hub-device-twin-show) command.
+1. Run the [az iot hub device-twin show](/cli/azure/iot/hub/device-twin#az-iot-hub-device-twin-show) command.
 
     ```azurecli
     az iot hub device-twin show --device-id mydevice --hub-name {YourIoTHubName}
@@ -267,17 +267,17 @@ To use Azure CLI to view device telemetry:
 
 ## Call a direct method on the device
 
-You can also use Azure IoT Explorer to call a direct method that you've implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that turns an LED on or off. Optionally, you can do the same task using Azure CLI.
+You can also use Azure IoT Explorer to call a direct method that you implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that turns an LED on or off. Optionally, you can do the same task using Azure CLI.
 
 To call a method in Azure IoT Explorer:
 
 1. From the **IoT Plug and Play components** (Default Component) pane for your device in IoT Explorer, select the **Commands** tab.
-1. For the **ToggleLed1** command, select **Send command**. The LED on the ESP32 DevKit toggles on or off.  You should also see a notification in IoT Explorer. 
+1. For the **ToggleLed1** command, select **Send command**. The LED on the ESP32 DevKit toggles on or off. You should also see a notification in IoT Explorer. 
 
     :::image type="content" source="media/tutorial-devkit-espressif-esp32-iot-hub/iot-explorer-invoke-method.png" alt-text="Screenshot of calling a method in IoT Explorer.":::
 
 1. For the **DisplayText** command, enter some text in the **content** field. 
-1. Select **Send command**.  The text displays on the ESP32 DevKit screen. 
+1. Select **Send command**. The text displays on the ESP32 DevKit screen. 
 
 
 To use Azure CLI to call a method:

articles/iot/tutorial-devkit-mxchip-az3166-iot-hub.md

@@ -6,7 +6,7 @@ ms.author: timlt
 ms.service: iot
 ms.devlang: c
 ms.topic: tutorial
-ms.date: 04/08/2024
+ms.date: 06/11/2024
 ms.custom: devx-track-azurecli
 
 #Customer intent: As a device builder, I want to see a working IoT device sample connecting to IoT Hub and sending properties and telemetry, and responding to commands. As a solution builder, I want to use a tool to view the properties, commands, and telemetry an IoT Plug and Play device reports to the IoT hub it connects to.
@@ -66,11 +66,11 @@ resources
 
 To install the tools:
 
-1. From File Explorer, navigate to the following path in the repo and run the setup script named *get-toolchain.bat*:
+1. Navigate to the following path in the repo and run the setup script named *get-toolchain.bat*:
 
     *getting-started\tools\get-toolchain.bat*
 
-1. After the installation, open a new console window to recognize the configuration changes made by the setup script. Use this console to complete the remaining programming tasks in the tutorial. You can use Windows CMD, PowerShell, or Git Bash for Windows.
+1. Open a new console window to recognize the configuration changes made by the setup script. Use this console to complete the remaining programming tasks in the tutorial. You can use Windows CMD, PowerShell, or Git Bash for Windows.
 1. Run the following code to confirm that CMake version 3.14 or later is installed.
 
    ```shell
@@ -295,7 +295,7 @@ To use Azure CLI to view device telemetry:
 
 ## Call a direct method on the device
 
-You can also use Azure IoT Explorer to call a direct method that you've implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that turns an LED on or off. Optionally, you can do the same task using Azure CLI.
+You can also use Azure IoT Explorer to call a direct method that you implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that turns an LED on or off. Optionally, you can do the same task using Azure CLI.
 
 To call a method in Azure IoT Explorer:
 

articles/iot/tutorial-devkit-stm-b-l475e-iot-hub.md

@@ -6,7 +6,7 @@ ms.author: timlt
 ms.service: iot
 ms.devlang: c
 ms.topic: tutorial
-ms.date: 04/08/2024
+ms.date: 06/11/2024
 
 #Customer intent: As a device builder, I want to see a working IoT device sample connecting to IoT Hub and sending properties and telemetry, and responding to commands. As a solution builder, I want to use a tool to view the properties, commands, and telemetry an IoT Plug and Play device reports to the IoT hub it connects to. 
 ---
@@ -64,11 +64,11 @@ The cloned repo contains a setup script that installs and configures the require
 
 To install the tools:
 
-1. From File Explorer, navigate to the following path in the repo and run the setup script named *get-toolchain.bat*:
+1. Navigate to the following path in the repo and run the setup script named *get-toolchain.bat*:
 
     *getting-started\tools\get-toolchain.bat*
 
-1. After the installation, open a new console window to recognize the configuration changes made by the setup script. Use this console to complete the remaining programming tasks in the tutorial. You can use Windows CMD, PowerShell, or Git Bash for Windows.
+1. Open a new console window to recognize the configuration changes made by the setup script. Use this console to complete the remaining programming tasks in the tutorial. You can use Windows CMD, PowerShell, or Git Bash for Windows.
 1. Run the following code to confirm that CMake version 3.14 or later is installed.
 
     ```shell
@@ -136,7 +136,7 @@ To connect the STM DevKit to Azure, you modify a configuration file for Wi-Fi an
 
 1. Copy the binary file named *stm32l475_azure_iot.bin*.
 
-1. In File Explorer, find the STM Devkit that's connected to your computer. The device appears as a drive on your system with the drive label **DIS_L4IOT**.
+1. In File Explorer, find the STM Devkit connected to your computer. The device appears as a drive on your system with the drive label **DIS_L4IOT**.
 
 1. Paste the binary file into the root folder of the STM Devkit. Flashing starts automatically and completes in a few seconds.
 
@@ -300,7 +300,7 @@ To use Azure CLI to view device telemetry:
 
 ## Call a direct method on the device
 
-You can also use Azure IoT Explorer to call a direct method that you've implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that turns an LED on or off. Optionally, you can do the same task using Azure CLI.
+You can also use Azure IoT Explorer to call a direct method that you implemented on your device. Direct methods have a name, and can optionally have a JSON payload, configurable connection, and method timeout. In this section, you call a method that turns an LED on or off. Optionally, you can do the same task using Azure CLI.
 
 To call a method in Azure IoT Explorer:
 

includes/iot-develop-create-cloud-components.md

@@ -57,7 +57,7 @@ In the rest of this quickstart, you use IoT Explorer to register a device to you
 
 To add a connection to your IoT hub:
 
-1. Install [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer/releases).  This tool is a cross-platform utility to monitor and manage Azure IoT resources.
+1. Install [Azure IoT Explorer](https://github.com/Azure/azure-iot-explorer/releases). This tool is a cross-platform utility to monitor and manage Azure IoT resources.
 
 1. In your CLI app, run the [az iot hub connection-string show](/cli/azure/iot/hub/connection-string#az-iot-hub-connection-string-show) command to get the connection string for your IoT hub.
 
@@ -78,12 +78,15 @@ If the connection succeeds, IoT Explorer switches to the **Devices** view.
 To add the public model repository:
 
 1. In IoT Explorer, select **Home** to return to the home view.
-1. On the left menu, select **IoT Plug and Play Settings**, then select **+Add** and select **Public repository** from the drop-down menu.
-1. An entry appears for the public model repository at `https://devicemodels.azure.com`.
+1. On the left menu, select **IoT Plug and Play Settings**.
+1. Confirm that there's an existing **Public Repository** entry with an endpoint of `https://devicemodels.azure.com`. 
+    > [!NOTE]
+    > If there's not an entry the public repository, select **+Add**, select **Public repository** from the drop-down menu, specify the `https://devicemodels.azure.com` endpoint value, and then select **Save**.
+
+    The completed entry for the public repository looks like the following screenshot: 
 
     :::image type="content" source="media/iot-develop-create-cloud-components/iot-explorer-add-public-repository.png" alt-text="Screenshot of adding the public model repository in IoT Explorer.":::
 
-1. Select **Save**.
 
 ### Register a device