Merge pull request #225103 from w-azure/winona-modules

Freshness check - batch 3

Author: v-stsavell

articles/iot-edge/media/troubleshoot/configure-dns.png

@@ -14,7 +14,7 @@ services: iot-edge
 
 [!INCLUDE [iot-edge-version-all-supported](includes/iot-edge-version-all-supported.md)]
 
-Each IoT Edge device runs at least two modules: $edgeAgent and $edgeHub, which are part of the IoT Edge runtime. IoT Edge device can run multiple additional modules for any number of processes. Use a deployment manifest to tell your device which modules to install and how to configure them to work together.
+Each IoT Edge device runs at least two modules: $edgeAgent and $edgeHub, which are part of the IoT Edge runtime. IoT Edge device can run multiple modules for any number of processes. Use a deployment manifest to tell your device which modules to install and how to configure them to work together.
 
 The *deployment manifest* is a JSON document that describes:
 
@@ -23,7 +23,7 @@ The *deployment manifest* is a JSON document that describes:
   * The credentials to access private container registries that contain module images.
   * Instructions for how each module should be created and managed.
 * The **IoT Edge hub** module twin, which includes how messages flow between modules and eventually to IoT Hub.
-* The desired properties of any additional module twins (optional).
+* The desired properties of any extra module twins (optional).
 
 All IoT Edge devices must be configured with a deployment manifest. A newly installed IoT Edge runtime reports an error code until configured with a valid manifest.
 
@@ -167,9 +167,9 @@ The edgeHub module and custom modules also have three properties that tell the I
 * **RestartPolicy**: When and if the IoT Edge agent should restart the module if it stops. If the module is stopped without any errors, it won't start automatically. For more information, see [Docker Docs - Start containers automatically](https://aka.ms/docker-container-restart-policy). Required.
 * **StartupOrder**: *Introduced in IoT Edge version 1.0.10.* Which order the IoT Edge agent should start the modules when first deployed. The order is declared with integers, where a module given a startup value of 0 is started first and then higher numbers follow. The edgeAgent module doesn't have a startup value because it always starts first. Optional.
 
-  The IoT Edge agent initiates the modules in order of the startup value, but does not wait for each module to finish starting before going to the next one.
+  The IoT Edge agent initiates the modules in order of the startup value, but doesn't wait for each module to finish starting before going to the next one.
 
-  Startup order is helpful if some modules depend on others. For example, you may want the edgeHub module to start first so that it's ready to route messages when the other modules start. Or you may want to start a storage module before the modules that send data to it. However, you should always design your modules to handle failures of other modules. It's the nature of containers that they may stop and restart at any time, and any number of times.
+  Startup order is helpful if some modules depend on others. For example, you may want the edgeHub module to start first so that it's ready to route messages when the other modules start. Or you may want to start a storage module before you start modules that send data to it. However, you should always design your modules to handle failures of other modules. It's the nature of containers that they may stop and restart at any time, and any number of times.
 
   > [!NOTE]
   > Changes to a module's properties will result in that module restarting. For example, a restart will happen if you change properties for the:
@@ -225,7 +225,7 @@ You can assign *priority* to routes that you want to make sure process their mes
 
 The source specifies where the messages come from. IoT Edge can route messages from modules or downstream devices.
 
-Using the IoT SDKs, modules can declare specific output queues for their messages using the ModuleClient class. Output queues aren't necessary, but are helpful for managing multiple routes. Downstream devices can use the DeviceClient class of the IoT SDKs to send messages to IoT Edge gateway devices in the same way that they would send messages to IoT Hub. For more information, see [Understand and use Azure IoT Hub SDKs](../iot-hub/iot-hub-devguide-sdks.md).
+With the IoT SDKs, modules can declare specific output queues for their messages using the ModuleClient class. Output queues aren't necessary, but are helpful for managing multiple routes. Downstream devices can use the DeviceClient class of the IoT SDKs to send messages to IoT Edge gateway devices in the same way that they would send messages to IoT Hub. For more information, see [Understand and use Azure IoT Hub SDKs](../iot-hub/iot-hub-devguide-sdks.md).
 
 The source property can be any of the following values:
 
@@ -253,7 +253,7 @@ You can build queries around any of the three parameters with the following synt
 
 For examples about how to create queries for message properties, see [Device-to-cloud message routes query expressions](../iot-hub/iot-hub-devguide-routing-query-syntax.md).
 
-An example that is specific to IoT Edge is when you want to filter for messages that arrived at a gateway device from a downstream device. Messages that come from modules include a system property called **connectionModuleId**. So if you want to route messages from downstream devices directly to IoT Hub, use the following route to exclude module messages:
+An example that is specific to IoT Edge is when you want to filter for messages that arrived at a gateway device from a downstream device. Messages sent from modules include a system property called **connectionModuleId**. So if you want to route messages from downstream devices directly to IoT Hub, use the following route to exclude module messages:
 
 ```query
 FROM /messages/* WHERE NOT IS_DEFINED($connectionModuleId) INTO $upstream
@@ -304,7 +304,7 @@ For detailed information about how priority queues are managed, see the referenc
 
 The deployment manifest specifies desired properties for each module deployed to the IoT Edge device. Desired properties in the deployment manifest overwrite any desired properties currently in the module twin.
 
-If you do not specify a module twin's desired properties in the deployment manifest, IoT Hub won't modify the module twin in any way. Instead, you can set the desired properties programmatically.
+If you don't specify a module twin's desired properties in the deployment manifest, IoT Hub won't modify the module twin in any way. Instead, you can set the desired properties programmatically.
 
 The same mechanisms that allow you to modify device twins are used to modify module twins. For more information, see the [module twin developer guide](../iot-hub/iot-hub-devguide-module-twins.md).
 

articles/iot-edge/media/troubleshoot/optimizeforperformance-false.png

@@ -23,7 +23,7 @@ If you experience problems while using the Azure IoT Edge service, there are sev
 
 **Microsoft Customer Support team** - Users who have a [support plan](https://azure.microsoft.com/support/plans/) can engage the Microsoft Customer Support team by creating a support ticket directly from the [Azure portal](https://portal.azure.com/signin/index/?feature.settingsportalinstance=mpac).
 
-**Feature requests** - The Azure IoT Edge product tracks feature requests via the product's [User Voice page](https://feedback.azure.com/d365community/forum/0e2fff5d-f524-ec11-b6e6-000d3a4f0da0).
+**Feature requests** - The Azure IoT Edge product tracks feature requests via the product's [Azure feedback](https://feedback.azure.com/d365community/forum/0e2fff5d-f524-ec11-b6e6-000d3a4f0da0) community.
 
 ## Container engines
 
@@ -114,7 +114,7 @@ The following table lists the currently supported releases. IoT Edge release ass
 | [1.4](https://github.com/Azure/azure-iotedge/releases/tag/1.4.0) | Long-term support (LTS) | August 2022 | November 12, 2024 |
 | [1.1](https://github.com/Azure/azure-iotedge/releases/tag/1.1.0) | Long-term support (LTS) | February 2021 | December 13, 2022 |
 
-For more information on IoT Edge version history see, [Version history](version-history.md#version-history).
+For more information on IoT Edge version history, see, [Version history](version-history.md#version-history).
 
 IoT Edge 1.1 is the first long-term support (LTS) release channel. This version introduced no new features, but will receive security updates and fixes to regressions. IoT Edge 1.1 LTS uses .NET Core 3.1, and will be supported until December 13, 2022 to match the [.NET Core and .NET 5 release lifecycle](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
 
@@ -139,7 +139,7 @@ IoT Edge uses the Microsoft.Azure.Devices.Client SDK. For more information, see
 
 ## Virtual Machines
 
-Azure IoT Edge can be run in virtual machines. Using a virtual machine as an IoT Edge device is common when customers want to augment existing infrastructure with edge intelligence. The family of the host VM OS must match the family of the guest OS used inside a module's container. This requirement is the same as when Azure IoT Edge is run directly on a device. Azure IoT Edge is agnostic of the underlying virtualization technology and works in VMs powered by platforms like Hyper-V and vSphere.
+Azure IoT Edge can be run in virtual machines, such as an [Azure Virtual Machine](../virtual-machines/index.yml). Using a virtual machine as an IoT Edge device is common when customers want to augment existing infrastructure with edge intelligence. The family of the host VM OS must match the family of the guest OS used inside a module's container. This requirement is the same as when Azure IoT Edge is run directly on a device. Azure IoT Edge is agnostic of the underlying virtualization technology and works in VMs powered by platforms like Hyper-V and vSphere.
 
 <center>
 

articles/iot-edge/module-composition.md

@@ -173,9 +173,9 @@ In the Azure portal:
 
 4. Select **Runtime Settings**.
 
-5. In the **Edge Hub** module settings, delete everything from the **Create Options** text box.
+5. In the **Edge Hub** module settings, delete everything from the **Container Create Options** text box.
 
-6. Save your changes and create the deployment.
+6. Select **Apply** to save your changes and create the deployment.
 
 In the deployment.json file:
 
@@ -184,31 +184,30 @@ In the deployment.json file:
 2. Find the `edgeHub` settings in the edgeAgent desired properties section:
 
    ```json
-   "edgeHub": {
-       "settings": {
-           "image": "mcr.microsoft.com/azureiotedge-hub:1.1",
-           "createOptions": "{\"HostConfig\":{\"PortBindings\":{\"8883/tcp\":[{\"HostPort\":\"8883\"}],\"443/tcp\":[{\"HostPort\":\"443\"}]}}}"
-       },
-       "type": "docker",
-       "status": "running",
-       "restartPolicy": "always"
-   }
+     "edgeHub": {
+         "restartPolicy": "always",
+         "settings": {
+            "image": "mcr.microsoft.com/azureiotedge-hub:1.4",
+            "createOptions": "{\"HostConfig\":{\"PortBindings\":{\"443/tcp\":[{\"HostPort\":\"443\"}],\"5671/tcp\":[{\"HostPort\":\"5671\"}],\"8883/tcp\":[{\"HostPort\":\"8883\"}]}}}"
+         },
+         "status": "running",
+         "type": "docker"
+      }
    ```
 
 3. Remove the `createOptions` line, and the trailing comma at the end of the `image` line before it:
 
    ```json
-   "edgeHub": {
-       "settings": {
-           "image": "mcr.microsoft.com/azureiotedge-hub:1.1"
-       },
-       "type": "docker",
-       "status": "running",
-       "restartPolicy": "always"
+     "edgeHub": {
+         "restartPolicy": "always",
+         "settings": {
+         "image": "mcr.microsoft.com/azureiotedge-hub:1.4",
+         "status": "running",
+         "type": "docker"
    }
    ```
 
-4. Save the file and apply it to your IoT Edge device again.
+4. Select **Create** to apply it to your IoT Edge device again.
 
 ### IoT Edge module fails to send a message to edgeHub with 404 error
 
@@ -248,25 +247,33 @@ For the IoT Edge hub, set an environment variable **OptimizeForPerformance** to
 
 In the Azure portal:
 
-In your IoT Hub, select your IoT Edge device and from the device details page and select **Set Modules** > **Runtime Settings**. Create an environment variable for the IoT Edge hub module called *OptimizeForPerformance* that is set to *false*.
+1. In your IoT Hub, select your IoT Edge device and from the device details page and select **Set Modules** > **Runtime Settings**. 
+1. Create an environment variable for the IoT Edge hub module called *OptimizeForPerformance* with type *True/False* that is set to *False*. 
 
-![OptimizeForPerformance set to false](./media/troubleshoot/optimizeforperformance-false.png)
+   :::image type="content" source="./media/troubleshoot/optimizeforperformance-false.png" alt-text="Screenshot that shows where to add the OptimizeForPerformance environment variable in the Azure portal.":::
 
-In the deployment manifest:
+1. Select **Apply** to save changes, then select **Review + create**. 
 
-```json
-"edgeHub": {
-  "type": "docker",
-  "settings": {
-    "image": "mcr.microsoft.com/azureiotedge-hub:1.1",
-    "createOptions": <snipped>
-  },
-  "env": {
-    "OptimizeForPerformance": {
-      "value": "false"
-    }
-  },
-```
+   The environment variable is now in the `edgeHub` property of the deployment manifest:
+   
+   ```json
+      "edgeHub": {
+         "env": {
+               "OptimizeForPerformance": {
+                  "value": false
+               }
+         },
+         "restartPolicy": "always",
+         "settings": {
+               "image": "mcr.microsoft.com/azureiotedge-hub:1.4",
+               "createOptions": "{\"HostConfig\":{\"PortBindings\":{\"443/tcp\":[{\"HostPort\":\"443\"}],\"5671/tcp\":[{\"HostPort\":\"5671\"}],\"8883/tcp\":[{\"HostPort\":\"8883\"}]}}}"
+         },
+         "status": "running",
+         "type": "docker"
+      }
+    ```
+
+1. Select **Create** to save your changes and deploy the module.
 
 ### Security daemon couldn't start successfully
 
@@ -313,13 +320,14 @@ When you see this error, you can resolve it by configuring the DNS name of your
 
 1. In the Azure portal, navigate to the overview page of your virtual machine.
 
-2. Select **configure** under DNS name. If your virtual machine already has a DNS name configured, you don't need to configure a new one.
+2. Open the configuration panel by selecting **Not configured** (if your virtual machine is new) under DNS name, or select your existing DNS name. If your virtual machine already has a DNS name configured, you don't need to configure a new one.
 
-   ![Configure DNS name of virtual machine](./media/troubleshoot/configure-dns.png)
+   :::image type="content" source="./media/troubleshoot/configure-dns.png" alt-text="Screenshot of how to open the configuration panel of your DNS name.":::
 
-3. Provide a value for **DNS name label** and select **Save**.
+3. Provide a value for **DNS name label** if you don't have one already and select **Save**.
 
-4. Copy the new DNS name, which should be in the format **\<DNSnamelabel\>.\<vmlocation\>.cloudapp.azure.com**.
+4. Copy the new DNS name, which should be in the format: <br>
+   **\<DNSnamelabel\>.\<vmlocation\>.cloudapp.azure.com**.
 
 5. On the IoT Edge device, open the config file.