Merge pull request #228119 from w-azure/winona-images2

Updating the image markdown

Author: v-ccolin

articles/iot-edge/how-to-configure-multiple-nics.md

@@ -29,13 +29,13 @@ For more information about networking concepts and configurations, see [Azure Io
 - Virtual switch different from the default one used during EFLOW installation. For more information on creating a virtual switch, see [Create a virtual switch for Azure IoT Edge for Linux on Windows](./how-to-create-virtual-switch.md).
 
 ## Create and assign a virtual switch
-During the EFLOW VM deployment, the VM had a switched assigned for all the communications between the Windows host OS and the virtual machine. This will always be the switch used for VM lifecycle management communications, and it's not possible to delete it. 
+During the EFLOW VM deployment, the VM had a switch assigned for all communications between the Windows host OS and the virtual machine. You always use the switch for VM lifecycle management communications, and it's not possible to delete it. 
 
-The following steps in this section show how to assign a network interface to the EFLOW virtual machine. Ensure that the virtual switch being used and the networking configuration aligns with your networking environment. For more information about networking concepts like type of switches, DHCP and DNS, see [Azure IoT Edge for Linux on Windows networking](./iot-edge-for-linux-on-windows-networking.md).
+The following steps in this section show how to assign a network interface to the EFLOW virtual machine. Ensure that the virtual switch and the networking configuration align with your networking environment. For more information about networking concepts like type of switches, DHCP and DNS, see [Azure IoT Edge for Linux on Windows networking](./iot-edge-for-linux-on-windows-networking.md).
 
 1. Open an elevated _PowerShell_ session by starting with **Run as Administrator**.
 
-1. Check the virtual switch to be assigned to the EFLOW VM is available.
+1. Check that the virtual switch you assign to the EFLOW VM is available.
     ```powershell
     Get-VMSwitch -Name "{switchName}" -SwitchType {switchType}
     ```
@@ -49,7 +49,7 @@ The following steps in this section show how to assign a network interface to th
     ```
     :::image type="content" source="./media/how-to-configure-multiple-nics/ps-cmdlet-add-eflow-network.png" alt-text="EFLOW attach virtual switch":::
 
-1. Check that the virtual switch was correctly assigned to the EFLOW VM.
+1. Check that you correctly assigned the virtual switch to the EFLOW VM.
     ```powershell
     Get-EflowNetwork -vSwitchName "{switchName}"
     ```
@@ -58,13 +58,13 @@ For more information about attaching a virtual switch to the EFLOW VM, see [Powe
 
 
 ## Create and assign a network endpoint
-Once the virtual switch was successfully assigned to the EFLOW VM, you need to create a networking endpoint assigned to virtual switch to finalize the network interface creation. If you're using Static IP, ensure to use the appropriate parameters: _ip4Address_, _ip4GatewayAddress_ and _ip4PrefixLength_.
+Once you successfully assign the virtual switch to the EFLOW VM, create a networking endpoint assigned to virtual switch to finalize the network interface creation. If you're using Static IP, ensure to use the appropriate parameters: _ip4Address_, _ip4GatewayAddress_ and _ip4PrefixLength_.
 
 1. Open an elevated _PowerShell_ session by starting with **Run as Administrator**.
 
 1. Create the EFLOW VM network endpoint
 
-    - If you're using DHCP, no Static IP parameters are needed.
+    - If you're using DHCP, you don't need Static IP parameters.
         ```powershell
         Add-EflowVmEndpoint -vSwitchName "{switchName}" -vEndpointName "{EndpointName}"
         ```
@@ -81,7 +81,7 @@ Once the virtual switch was successfully assigned to the EFLOW VM, you need to c
 
         :::image type="content" source="./media/how-to-configure-multiple-nics/ps-cmdlet-add-eflow-endpoint.png" alt-text="EFLOW attach network endpoint":::
 
-1. Check that the network endpoint was correctly created and assigned to the EFLOW VM. You should see the two network interfaces assigned to the virtual machine.
+1. Check that you correctly created the network endpoint and assigned it to the EFLOW VM. You should see two network interfaces assigned to the virtual machine.
     ```powershell
     Get-EflowVmEndpoint
     ``` 
@@ -92,7 +92,7 @@ For more information about creating and attaching a network endpoint to the EFLO
 
 
 ## Check the VM network configurations
-The final step is to make sure the networking configurations were applied correctly and the EFLOW VM has the new network interface configured. The new interface will show up as _"eth1"_ if it's the first extra interface added to the VM. 
+The final step is to make sure the networking configurations applied correctly and the EFLOW VM has the new network interface configured. The new interface shows up as _"eth1"_ if it's the first extra interface added to the VM. 
 
 1. Open PowerShell in an elevated session. You can do so by opening the **Start** pane on Windows and typing in "PowerShell". Right-click the **Windows PowerShell** app that shows up and select **Run as administrator**.
 
@@ -105,9 +105,9 @@ The final step is to make sure the networking configurations were applied correc
     ifconfig
     ``` 
     
-    The default interface **eth0** is the one used for all the VM management. You should see another interface, like **eth1**, which is the new interface that was assigned to the VM. Following the examples above, if you previously assigned a new endpoint with the static IP 192.168.0.103 you should see the interface **eth1** with the _inet addr: 192.168.0.103_.
+    The default interface **eth0** is the one used for all the VM management. You should see another interface, like **eth1**, which is the new interface you assigned to the VM. Following the examples, if you previously assigned a new endpoint with the static IP 192.168.0.103 you should see the interface **eth1** with the _inet addr: 192.168.0.103_.
 
-   ![EFLOW VM network interfaces](./media/how-to-configure-multiple-nics/ps-cmdlet-eflow-ifconfig.png)
+   :::image type="content" source="./media/how-to-configure-multiple-nics/ps-cmdlet-eflow-ifconfig.png" alt-text="Screenshot of EFLOW virtual machine network interfaces.":::
 
 ## Next steps
-Follow the steps in [How to configure networking for Azure IoT Edge for Linux on Windows](./how-to-configure-iot-edge-for-linux-on-windows-networking.md) to make sure all the networking configurations were applied correctly.
+Follow the steps in [How to configure networking for Azure IoT Edge for Linux on Windows](./how-to-configure-iot-edge-for-linux-on-windows-networking.md) to make sure you applied all the networking configurations correctly.

articles/iot-edge/how-to-configure-proxy-support.md

@@ -284,11 +284,11 @@ When you use the **Set modules** wizard to create deployments for IoT Edge devic
 
 To configure the IoT Edge agent and IoT Edge hub modules, select **Runtime Settings** on the first step of the wizard.
 
-![Configure advanced Edge Runtime settings](./media/how-to-configure-proxy-support/configure-runtime.png)
+:::image type="content" source="./media/how-to-configure-proxy-support/configure-runtime.png" alt-text="Screenshot of how to configure advanced Edge Runtime settings.":::
 
 Add the **https_proxy** environment variable to both the IoT Edge agent and IoT Edge hub module definitions. If you included the **UpstreamProtocol** environment variable in the config file on your IoT Edge device, add that to the IoT Edge agent module definition too.
 
-![Set https_proxy environment variable](./media/how-to-configure-proxy-support/edgehub-environmentvar.png)
+:::image type="content" source="./media/how-to-configure-proxy-support/edgehub-environmentvar.png" alt-text="Screenshot of how to set the https_proxy environment variable.":::
 
 All other modules that you add to a deployment manifest follow the same pattern. Select **Apply** to save your changes.
 

articles/iot-edge/how-to-connect-downstream-device.md

@@ -72,7 +72,7 @@ When a device connects to an IoT Edge gateway, the downstream device is the clie
 
 When you use a self-signed root CA certificate for an IoT Edge gateway, it needs to be installed on or provided to all the downstream devices attempting to connect to the gateway.
 
-![Gateway certificate setup](./media/how-to-create-transparent-gateway/gateway-setup.png)
+:::image type="content" source="./media/how-to-create-transparent-gateway/gateway-setup.png" alt-text="Screenshot of the gateway certificate setup.":::
 
 To learn more about IoT Edge certificates and some production implications, see [IoT Edge certificate usage details](iot-edge-certs.md).
 
@@ -209,7 +209,7 @@ This command tests connections over MQTTS (port 8883). If you're using a differe
 
 The output of this command may be long, including information about all the certificates in the chain. If your connection is successful, you'll see a line like `Verification: OK` or `Verify return code: 0 (ok)`.
 
-![Verify gateway connection](./media/how-to-connect-downstream-device/verification-ok.png)
+:::image type="content" source="./media/how-to-connect-downstream-device/verification-ok.png" alt-text="Screenshot of how to verify a gateway connection.":::
 
 ## Troubleshoot the gateway connection
 

articles/iot-edge/how-to-continuous-integration-continuous-deployment-classic.md

@@ -16,7 +16,7 @@ services: iot-edge
 
 Azure Pipelines includes a built-in Azure IoT Edge task that helps you adopt DevOps with your Azure IoT Edge applications. This article demonstrates how to use the continuous integration and continuous deployment features of Azure Pipelines to build, test, and deploy applications quickly and efficiently to your Azure IoT Edge using the classic editor. Alternatively, you can [use YAML](how-to-continuous-integration-continuous-deployment.md).
 
-![Diagram - CI and CD branches for development and production](./media/how-to-continuous-integration-continuous-deployment-classic/model.png)
+:::image type="content" source="./media/how-to-continuous-integration-continuous-deployment-classic/model.png" alt-text="Diagram of the continuous integration and continuous development branches for development and production .":::
 
 In this article, you learn how to use the built-in [Azure IoT Edge tasks](/azure/devops/pipelines/tasks/build/azure-iot-edge) for Azure Pipelines to create build and release pipelines for your IoT Edge solution. Each Azure IoT Edge task added to your pipeline implements one of the following four actions:
 
@@ -56,25 +56,25 @@ In this section, you create a new build pipeline. You configure the pipeline to
 
 1. Sign in to your Azure DevOps organization (`https://dev.azure.com/{your organization}`) and open the project that contains your IoT Edge solution repository.
 
-    ![Open your DevOps project](./media/how-to-continuous-integration-continuous-deployment-classic/initial-project.png)
+   :::image type="content" source="./media/how-to-continuous-integration-continuous-deployment-classic/initial-project.png" alt-text="Screenshot that shows how to open your DevOps project.":::
 
 2. From the left pane menu in your project, select **Pipelines**. Select **Create Pipeline** at the center of the page. Or, if you already have build pipelines, select the **New pipeline** button in the top right.
 
-    ![Create a new build pipeline](./media/how-to-continuous-integration-continuous-deployment-classic/add-new-pipeline.png)
+   :::image type="content" source="./media/how-to-continuous-integration-continuous-deployment-classic/add-new-pipeline.png" alt-text="Screenshot that shows how to create a new build pipeline.":::
 
 3. At the bottom of the **Where is your code?** page, select **Use the classic editor**. If you wish to use YAML to create your project's build pipelines, see the [YAML guide](how-to-continuous-integration-continuous-deployment.md).
 
-    ![Select Use the classic editor](./media/how-to-continuous-integration-continuous-deployment-classic/create-without-yaml.png)
+   :::image type="content" source="./media/how-to-continuous-integration-continuous-deployment-classic/create-without-yaml.png" alt-text="Screenshot that shows how to use the classic editor.":::
 
 4. Follow the prompts to create your pipeline.
 
    1. Provide the source information for your new build pipeline. Select **Azure Repos Git** as the source, then select the project, repository, and branch where your IoT Edge solution code is located. Then, select **Continue**.
 
-      ![Select your pipeline source](./media/how-to-continuous-integration-continuous-deployment-classic/pipeline-source.png)
+      :::image type="content" source="./media/how-to-continuous-integration-continuous-deployment-classic/pipeline-source.png" alt-text="Screenshot showing how to select your pipeline source.":::
 
    2. Select **Empty job** instead of a template.
 
-      ![Start with an empty job for your build pipeline](./media/how-to-continuous-integration-continuous-deployment-classic/start-with-empty-build-job.png)
+      :::image type="content" source="./media/how-to-continuous-integration-continuous-deployment-classic/start-with-empty-build-job.png" alt-text="Screenshot showing how to start with an empty job for your build pipeline.":::
 
 5. Once your pipeline is created, you are taken to the pipeline editor. Here, you can change the pipeline's name, agent pool, and agent specification.
 
@@ -157,7 +157,7 @@ In this section, you create a new build pipeline. You configure the pipeline to
 
 11. Open the **Triggers** tab and check the box to **Enable continuous integration**. Make sure the branch containing your code is included.
 
-    ![Turn on continuous integration trigger](./media/how-to-continuous-integration-continuous-deployment-classic/configure-trigger.png)
+   :::image type="content" source="./media/how-to-continuous-integration-continuous-deployment-classic/configure-trigger.png" alt-text="Screenshot showing how to turn on continuous integration trigger.":::
 
 12. Select **Save** from the **Save & queue** dropdown.
 

articles/iot-edge/how-to-continuous-integration-continuous-deployment.md

@@ -16,7 +16,7 @@ services: iot-edge
 
 You can easily adopt DevOps with your Azure IoT Edge applications with the built-in Azure IoT Edge tasks in Azure Pipelines. This article demonstrates how you can use Azure Pipelines to build, test, and deploy Azure IoT Edge modules using YAML. Alternatively, you can [use the classic editor](how-to-continuous-integration-continuous-deployment-classic.md).
 
-![Diagram - CI and CD branches for development and production](./media/how-to-continuous-integration-continuous-deployment/model.png)
+:::image type="content" source="./media/how-to-continuous-integration-continuous-deployment/model.png" alt-text="Diagram of continuous integration and continuous development branches for development and production.":::
 
 In this article, you learn how to use the built-in [Azure IoT Edge tasks](/azure/devops/pipelines/tasks/build/azure-iot-edge) for Azure Pipelines to create build and release pipelines for your IoT Edge solution. Each Azure IoT Edge task added to your pipeline implements one of the following four actions:
 
@@ -57,17 +57,17 @@ In this section, you create a new build pipeline. You configure the pipeline to
 
 1. Sign in to your Azure DevOps organization (`https://dev.azure.com/{your organization}`) and open the project that contains your IoT Edge solution repository.
 
-   ![Open your DevOps project](./media/how-to-continuous-integration-continuous-deployment/initial-project.png)
+   :::image type="content" source="./media/how-to-continuous-integration-continuous-deployment/initial-project.png" alt-text="Screenshot showing how to open your DevOps project.":::
 
 2. From the left pane menu in your project, select **Pipelines**. Select **Create Pipeline** at the center of the page. Or, if you already have build pipelines, select the **New pipeline** button in the top right.
 
-    ![Create a new build pipeline using the New pipeline button](./media/how-to-continuous-integration-continuous-deployment/add-new-pipeline.png)
+   :::image type="content" source="./media/how-to-continuous-integration-continuous-deployment/add-new-pipeline.png" alt-text="Screenshot showing how to create a new build pipeline using the New pipeline button .":::
 
 3. On the **Where is your code?** page, select **Azure Repos Git `YAML`**. If you wish to use the classic editor to create your project's build pipelines, see the [classic editor guide](how-to-continuous-integration-continuous-deployment-classic.md).
 
 4. Select the repository you are creating a pipeline for.
 
-    ![Select the repository for your build pipeline](./media/how-to-continuous-integration-continuous-deployment/select-repository.png)
+   :::image type="content" source="./media/how-to-continuous-integration-continuous-deployment/select-repository.png" alt-text="Screenshot showing how to select the repository for your build pipeline.":::
 
 5. On the **Configure your pipeline** page, select **Starter pipeline**. If you have a preexisting Azure Pipelines YAML file you wish to use to create this pipeline, you can select **Existing Azure Pipelines YAML file** and provide the branch and path in the repository to the file.
 
@@ -77,7 +77,7 @@ In this section, you create a new build pipeline. You configure the pipeline to
 
    Select **Show assistant** to open the **Tasks** palette.
 
-    ![Select Show assistant to open Tasks palette](./media/how-to-continuous-integration-continuous-deployment/show-assistant.png)
+   :::image type="content" source="./media/how-to-continuous-integration-continuous-deployment/show-assistant.png" alt-text="Screenshot that shows how to select Show assistant to open Tasks palette.":::
 
 7. To add a task, place your cursor at the end of the YAML or wherever you want the instructions for your task to be added. Search for and select **Azure IoT Edge**. Fill out the task's parameters as follows. Then, select **Add**.
 
@@ -89,7 +89,7 @@ In this section, you create a new build pipeline. You configure the pipeline to
 
    For more information about this task and its parameters, see [Azure IoT Edge task](/azure/devops/pipelines/tasks/build/azure-iot-edge).
 
-   ![Use Tasks palette to add tasks to your pipeline](./media/how-to-continuous-integration-continuous-deployment/add-build-task.png)
+   :::image type="content" source="./media/how-to-continuous-integration-continuous-deployment/add-build-task.png" alt-text="Screenshot of the Use Tasks palette and how to add tasks to your pipeline.":::
 
    >[!TIP]
    > After each task is added, the editor will automatically highlight the added lines. To prevent accidental overwriting, deselect the lines and provide a new space for your next task before adding additional tasks.
@@ -133,7 +133,7 @@ In this section, you create a new build pipeline. You configure the pipeline to
 
 10. The trigger for continuous integration is enabled by default for your YAML pipeline. If you wish to edit these settings, select your pipeline and click **Edit** in the top right. Select **More actions** next to the **Run** button in the top right and go to **Triggers**. **Continuous integration** shows as enabled under your pipeline's name. If you wish to see the details for the trigger, check the **Override the YAML continuous integration trigger from here** box.
 
-    ![To review your pipeline's trigger settings, see Triggers under More actions](./media/how-to-continuous-integration-continuous-deployment/check-trigger-settings.png)
+   :::image type="content" source="./media/how-to-continuous-integration-continuous-deployment/check-trigger-settings.png" alt-text="Screenshot showing how to review your pipeline's trigger settings from the Triggers menu under More actions.":::
 
 Continue to the next section to build the release pipeline.