[BULK] DocuTune - Fix formatting issues

Author: alexbuckgit

articles/iot-develop/quickstart-devkit-stm-b-u585i-iot-hub.md

@@ -158,39 +158,39 @@ You can use the **Termite** app to monitor communication and confirm that your d
 
     ```output
     Starting Azure thread
-    
-    
+
+
     Initializing WiFi
-    	SSID: ***********
-    	Password: ***********
+        SSID: ***********
+        Password: ***********
     SUCCESS: WiFi initialized
-    
+
     Connecting WiFi
-    	FW: V2.1.11
-    	MAC address: ***********
-    	Connecting to SSID '***********'
-    	Attempt 1...
+        FW: V2.1.11
+        MAC address: ***********
+        Connecting to SSID '***********'
+        Attempt 1...
     SUCCESS: WiFi connected
-    
+
     Initializing DHCP
-    	IP address: 192.168.0.67
-    	Mask: 255.255.255.0
-    	Gateway: 192.168.0.1
+        IP address: 192.168.0.67
+        Mask: 255.255.255.0
+        Gateway: 192.168.0.1
     SUCCESS: DHCP initialized
-    
+
     Initializing DNS client
-    	DNS address: 192.168.0.1
+        DNS address: 192.168.0.1
     SUCCESS: DNS client initialized
-    
+
     Initializing SNTP time sync
-    	SNTP server 0.pool.ntp.org
-    	SNTP time update: Feb 24, 2023 21:20:23.71 UTC 
+        SNTP server 0.pool.ntp.org
+        SNTP time update: Feb 24, 2023 21:20:23.71 UTC
     SUCCESS: SNTP initialized
-    
+
     Initializing Azure IoT Hub client
-    	Hub hostname: ***********.azure-devices.net
-    	Device id: mydevice
-    	Model id: dtmi:azurertos:devkit:gsg;2
+        Hub hostname: ***********.azure-devices.net
+        Device id: mydevice
+        Model id: dtmi:azurertos:devkit:gsg;2
     SUCCESS: Connected to IoT Hub
     ```
     > [!IMPORTANT]
@@ -201,7 +201,7 @@ Keep Termite open to monitor device output in the following steps.
 
 ## View device properties
 
-You can use Azure IoT Explorer to view and manage the properties of your devices. In the following sections, you use the Plug and Play capabilities that are visible in IoT Explorer to manage and interact with the STM DevKit. These capabilities rely on the device model published for the STM DevKit in the public model repository. You configured IoT Explorer to search this repository for device models earlier in this quickstart. In many cases, you can perform the same action without using plug and play by selecting IoT Explorer menu options. However, using plug and play often provides an enhanced experience. IoT Explorer can read the device model specified by a plug and play device and present information specific to that device.  
+You can use Azure IoT Explorer to view and manage the properties of your devices. In the following sections, you use the Plug and Play capabilities that are visible in IoT Explorer to manage and interact with the STM DevKit. These capabilities rely on the device model published for the STM DevKit in the public model repository. You configured IoT Explorer to search this repository for device models earlier in this quickstart. In many cases, you can perform the same action without using plug and play by selecting IoT Explorer menu options. However, using plug and play often provides an enhanced experience. IoT Explorer can read the device model specified by a plug and play device and present information specific to that device.
 
 To access IoT Plug and Play components for the device in IoT Explorer:
 
@@ -228,15 +228,15 @@ To access IoT Plug and Play components for the device in IoT Explorer:
 
 To view device properties using Azure IoT Explorer:
 
-1. Select the **Properties (read-only)** tab. There's a single read-only property to indicate whether the led is on or off. 
+1. Select the **Properties (read-only)** tab. There's a single read-only property to indicate whether the led is on or off.
 1. Select the **Properties (writable)** tab. It displays the interval that telemetry is sent.
 1. Change the `telemetryInterval` to *5*, and then select **Update desired value**. Your device now uses this interval to send telemetry.
 
     :::image type="content" source="media/quickstart-devkit-stm-b-u585i-iot-hub/iot-explorer-set-telemetry-interval.png" alt-text="Screenshot of setting telemetry interval on STM DevKit in IoT Explorer.":::
 
 1. IoT Explorer responds with a notification. You can also observe the update in Termite.
 1. Set the telemetry interval back to 10.
- 
+
 To use Azure CLI to view device properties:
 
 1. Run the [az iot hub device-twin show](/cli/azure/iot/hub/device-twin#az-iot-hub-device-twin-show) command.
@@ -326,7 +326,7 @@ To use Azure CLI to call a method:
     {
         "payload": {},
         "status": 200
-    }    
+    }
     ```
 
 1. Check your device to confirm the LED state.
@@ -352,7 +352,7 @@ For debugging the application, see [Debugging with Visual Studio Code](https://g
 
 In this quickstart, you built a custom image that contains Azure RTOS sample code, and then flashed the image to the STM DevKit device. You connected the STM DevKit to Azure, and carried out tasks such as viewing telemetry and calling a method on the device.
 
-As a next step, explore the following articles to learn more about using the IoT device SDKs, or Azure RTOS to connect devices to Azure IoT. 
+As a next step, explore the following articles to learn more about using the IoT device SDKs, or Azure RTOS to connect devices to Azure IoT.
 
 > [!div class="nextstepaction"]
 > [Connect a general simulated device to IoT Hub](quickstart-send-telemetry-iot-hub.md)

articles/iot-hub-device-update/device-update-agent-provisioning.md

@@ -29,7 +29,7 @@ If you are migrating from a device level agent to adding the agent as a Module i
 The following IoT device over the air update types are currently supported with Device Update:
 
 * Linux devices (IoT Edge and Non-IoT Edge devices):
-    * [Image A/B update](device-update-raspberry-pi.md)  
+    * [Image A/B update](device-update-raspberry-pi.md)
     * [Package update](device-update-ubuntu-agent.md)
     * [Proxy update for downstream devices](device-update-howto-proxy-updates.md)
 
@@ -40,7 +40,7 @@ The following IoT device over the air update types are currently supported with
     * [Understand support for disconnected device update](connected-cache-disconnected-device-update.md)
 
 
-## Prerequisites  
+## Prerequisites
 
 If you're setting up the IoT device/IoT Edge device for [package based updates](./understand-device-update.md#support-for-a-wide-range-of-update-artifacts), add packages.microsoft.com to your machine’s repositories by following these steps:
 
@@ -73,13 +73,13 @@ If you're setting up the IoT device/IoT Edge device for [package based updates](
 ## How to provision the Device Update agent as a Module Identity
 
 This section describes how to provision the Device Update agent as a module identity on
-* IoT Edge enabled devices, or 
+* IoT Edge enabled devices, or
 * Non-Edge IoT devices, or
-* Other IoT devices. 
+* Other IoT devices.
 
 To check if you have IoT Edge enabled on your device, please refer to the [IoT Edge installation instructions](../iot-edge/how-to-provision-single-device-linux-symmetric.md?preserve-view=true&view=iotedge-2020-11).
- 
-Follow all or any of the below sections to add the Device update agent based on the type of IoT device you are managing. 
+
+Follow all or any of the below sections to add the Device update agent based on the type of IoT device you are managing.
 
 ### On IoT Edge enabled devices
 
@@ -89,58 +89,59 @@ Follow these instructions to provision the Device Update agent on [IoT Edge enab
 
 1. Install the Device Update image update agent.
 
-    We provide sample images in the [Assets here](https://github.com/Azure/iot-hub-device-update/releases) repository. The swUpdate file is the base image that you can flash onto a Raspberry Pi B3+ board. The .gz file is the update you would import through Device Update for IoT Hub. For an example, see [How to flash the image to your IoT Hub device](./device-update-raspberry-pi.md).  
+    We provide sample images in the [Assets here](https://github.com/Azure/iot-hub-device-update/releases) repository. The swUpdate file is the base image that you can flash onto a Raspberry Pi B3+ board. The .gz file is the update you would import through Device Update for IoT Hub. For an example, see [How to flash the image to your IoT Hub device](./device-update-raspberry-pi.md).
 
 1. Install the Device Update package update agent.
 
-    - For latest agent versions from packages.microsoft.com: Update package lists on your device and install the Device Update agent package and its dependencies using:	
+    - For latest agent versions from packages.microsoft.com: Update package lists on your device and install the Device Update agent package and its dependencies using:
 
         ```shell
         sudo apt-get update
         ```
-	
+
         ```shell
         sudo apt-get install deviceupdate-agent
         ```
-	
+
     - For any 'rc' i.e. release candidate agent versions from [Artifacts](https://github.com/Azure/iot-hub-device-update/releases) : Download the .deb file to the machine you want to install the Device Update agent on, then:
-   
+
         ```shell
         sudo apt-get install -y ./"<PATH TO FILE>"/"<.DEB FILE NAME>"
         ```
     - If you are setting up a [MCC for a disconnected device scenario](connected-cache-disconnected-device-update.md), then install the Delivery Optimization APT plugin:
 
-         ```shell
-        sudo apt-get install deliveryoptimization-plugin-apt
-        ```
-	
-1. After you've installed the device update agent, you will need to edit the configuration file for Device Update by running the command below. 
+      ```shell
+      sudo apt-get install deliveryoptimization-plugin-apt
+      ```
+
+1. After you've installed the device update agent, you will need to edit the configuration file for Device Update by running the command below.
 
     ```shell
-   	sudo nano /etc/adu/du-config.json
+    sudo nano /etc/adu/du-config.json
     ```
-   Change the connectionType to "AIS" for agents who will be using the IoT Identity Service for provisioning. The ConnectionData field must be an empty string. Please note that all values with the 'Place value here' tag must be set. See [Configuring a DU agent](./device-update-configuration-file.md#example-du-configjson-file-contents).
-	
-5. You are now ready to start the Device Update agent on your IoT device. 
+   
+    Change the connectionType to "AIS" for agents who will be using the IoT Identity Service for provisioning. The ConnectionData field must be an empty string. Please note that all values with the 'Place value here' tag must be set. See [Configuring a DU agent](./device-update-configuration-file.md#example-du-configjson-file-contents).
+
+1. You are now ready to start the Device Update agent on your IoT device.
 
 ### On Iot Linux devices without IoT Edge installed
 
 Follow these instructions to provision the Device Update agent on your IoT Linux devices.
 
 1. Install the IoT Identity Service and add the latest version to your IoT device by following instructions in [Installing the Azure IoT Identity Service](https://azure.github.io/iot-identity-service/installation.html#install-from-packagesmicrosoftcom).
 
-2. Configure the IoT Identity Service by following the instructions in [Configuring the Azure IoT Identity Service](https://azure.github.io/iot-identity-service/configuration.html). 
-    
+2. Configure the IoT Identity Service by following the instructions in [Configuring the Azure IoT Identity Service](https://azure.github.io/iot-identity-service/configuration.html).
+
 3. Finally install the Device Update agent. We provide sample images in [Assets here](https://github.com/Azure/iot-hub-device-update/releases), the swUpdate file is the base image that you can flash onto a Raspberry Pi B3+ board, and the .gz file is the update you would import through Device Update for IoT Hub. See example of [how to flash the image to your IoT Hub device](./device-update-raspberry-pi.md).
 
-4. After you've installed the device update agent, you will need to edit the configuration file for Device Update by running the command below. 
+4. After you've installed the device update agent, you will need to edit the configuration file for Device Update by running the command below.
 
     ```shell
-   	sudo nano /etc/adu/du-config.json
+    sudo nano /etc/adu/du-config.json
     ```
-   Change the connectionType to "AIS" for agents who will be using the IoT Identity Service for provisioning. The ConnectionData field must be an empty string. Please note that all values with the 'Place value here' tag must be set. See [Configuring a DU agent](./device-update-configuration-file.md#example-du-configjson-file-contents).
+    Change the connectionType to "AIS" for agents who will be using the IoT Identity Service for provisioning. The ConnectionData field must be an empty string. Please note that all values with the 'Place value here' tag must be set. See [Configuring a DU agent](./device-update-configuration-file.md#example-du-configjson-file-contents).
 
-5. You are now ready to start the Device Update agent on your IoT device. 
+5. You are now ready to start the Device Update agent on your IoT device.
 
 ### Other IoT devices
 
@@ -149,24 +150,24 @@ The Device Update agent can also be configured without the IoT Identity service
 1. We provide sample images in the [Assets here](https://github.com/Azure/iot-hub-device-update/releases) repository. The swUpdate file is the base image that you can flash onto a Raspberry Pi B3+ board. The .gz file is the update you would import through Device Update for IoT Hub. For an example, see [How to flash the image to your IoT Hub device](./device-update-raspberry-pi.md).
 
 1. Log onto the machine or IoT Edge device/IoT device.
-	
+
 1. Open a terminal window.
 
 1. Add the connection string to the [Device Update configuration file](device-update-configuration-file.md):
 
     1. Enter the below in the terminal window:
-   
-        - [For Ubuntu agent](device-update-ubuntu-agent.md) use: sudo nano /etc/adu/du-config.json
-        - [For Yocto reference image](device-update-raspberry-pi.md) use: sudo nano /adu/du-config.json 
-       
+
+       - [For Ubuntu agent](device-update-ubuntu-agent.md) use: sudo nano /etc/adu/du-config.json
+       - [For Yocto reference image](device-update-raspberry-pi.md) use: sudo nano /adu/du-config.json
+
     1. Copy the primary connection string
-    
-    	- If Device Update agent is configured as a module copy the module's primary connection string. 
-    	- Otherwise copy the device's primary connection string.
-     
-    3. Enter the copied primary connection string to the 'connectionData' field's value in the du-config.json file. Please note that all values with the 'Place value here' tag must be set. See [Configuring a DU agent](./device-update-configuration-file.md#example-du-configjson-file-contents)
- 
-1. Now you are now ready to start the Device Update agent on your IoT device. 
+
+       - If Device Update agent is configured as a module copy the module's primary connection string.
+       - Otherwise copy the device's primary connection string.
+
+    1. Enter the copied primary connection string to the 'connectionData' field's value in the du-config.json file. Please note that all values with the 'Place value here' tag must be set. See [Configuring a DU agent](./device-update-configuration-file.md#example-du-configjson-file-contents)
+
+1. Now you are now ready to start the Device Update agent on your IoT device.
 
 ## How to start the Device Update Agent
 
@@ -179,13 +180,13 @@ This section describes how to start and verify the Device Update agent as a modu
     ```shell
     sudo systemctl restart deviceupdate-agent
     ```
-    
+
 1. You can check the status of the agent using the command below. If you see any issues, refer to this [troubleshooting guide](troubleshoot-device-update.md).
-	
+
     ```shell
     sudo systemctl status deviceupdate-agent
     ```
-    
+
     You should see status OK.
 
 1. On the IoT Hub portal,  go to IoT device or IoT Edge devices to find the device that you configured with Device Update agent. There you will see the Device Update agent running as a module. For example:
@@ -211,11 +212,11 @@ If you run into issues, review the Device Update for IoT Hub [Troubleshooting Gu
 You can use the following tutorials for a simple demonstration of Device Update for IoT Hub:
 
 - [Image Update: Getting Started with Raspberry Pi 3 B+ Reference Yocto Image](device-update-raspberry-pi.md) extensible via open source to build your own images for other architecture as needed.
-	
+
 - [Package Update: Getting Started using Ubuntu Server 18.04 x64 Package agent](device-update-ubuntu-agent.md)
-	
+
 - [Proxy Update: Getting Started using Device Update binary agent for downstream devices](device-update-howto-proxy-updates.md)
-	
+
 - [Getting Started Using Ubuntu (18.04 x64) Simulator Reference Agent](device-update-simulator.md)
 
 - [Device Update for Azure IoT Hub tutorial for Azure-Real-Time-Operating-System](device-update-azure-real-time-operating-system.md)