Merge pull request #226011 from w-azure/winona-runtime

Freshness check - batch 5

Author: American-Dipper

articles/iot-edge/how-to-update-iot-edge.md

@@ -5,7 +5,7 @@ keywords:
 author: PatAltimore
 
 ms.author: patricka
-ms.date: 11/29/2022
+ms.date: 2/2/2023
 ms.topic: conceptual
 ms.service: iot-edge
 services: iot-edge
@@ -106,7 +106,7 @@ The way that you update the IoT Edge agent and IoT Edge hub containers depends o
 
 Check the version of the IoT Edge agent and IoT Edge hub modules currently on your device using the commands `iotedge logs edgeAgent` or `iotedge logs edgeHub`. If you're using IoT Edge for Linux on Windows, you need to SSH into the Linux virtual machine to check the runtime module versions.
 
-  ![Find container version in logs](./media/how-to-update-iot-edge/container-version.png)
+:::image type="content" source="./media/how-to-update-iot-edge/container-version.png" alt-text="Screenshot of where to find the container version in console logs." lightbox="./media/how-to-update-iot-edge/container-version.png":::
 
 ### Understand IoT Edge tags
 
@@ -137,21 +137,21 @@ If you use specific tags in your deployment (for example, mcr.microsoft.com/azur
 
 1. In the IoT Hub in the Azure portal, select your IoT Edge device, and select **Set Modules**.
 
-1. In the **IoT Edge Modules** section, select **Runtime Settings**.
+1. On the **Modules** tab, select **Runtime Settings**.
 
-   ![Configure runtime settings](./media/how-to-update-iot-edge/configure-runtime.png)
+   :::image type="content" source="./media/how-to-update-iot-edge/configure-runtime.png" alt-text="Screenshot that shows location of the Runtime Settings tab.":::
 
-1. In **Runtime Settings**, update the **Image** value for **Edge Hub** with the desired version. Don't select **Save** yet.
+1. In **Runtime Settings**, update the **Image URI** value in the **Edge Agent** section with the desired version. Don't select **Apply** yet.
 
-   ![Update Edge Hub Image version](./media/how-to-update-iot-edge/runtime-settings-edgehub.png)
+   :::image type="content" source="./media/how-to-update-iot-edge/runtime-settings-edgeagent.png" alt-text="Screenshot that shows where to update the image U R I with your version in the Edge Agent.":::
 
-1. Collapse the **Edge Hub** settings, or scroll down, and update the **Image** value for **Edge Agent** with the same desired version.
+1. Select the **Edge Hub** tab and update the **Image URI** value with the same desired version.
 
-   ![Update Edge Hub Agent version](./media/how-to-update-iot-edge/runtime-settings-edgeagent.png)
+   :::image type="content" source="./media/how-to-update-iot-edge/runtime-settings-edgehub.png" alt-text="Screenshot that shows where to update the image U R I with your version in the Edge Hub.":::
 
-1. Select **Save**.
+1. Select **Apply** to save changes.
 
-1. Select **Review + create**, review the deployment, and select **Create**.
+1. Select **Review + create**, review the deployment as seen in the JSON file, and select **Create**.
 
 ## Special case: Update from 1.0 or 1.1 to latest release
 
@@ -214,8 +214,7 @@ Currently, there's no support for IoT Edge version 1.4 running on Windows device
 
 ---
 
-Now that the IoT Edge service running on your devices has been updated, follow the steps in this article to also [Update the runtime containers](#update-the-runtime-containers).
-
+Now that the latest IoT Edge service is running on your devices, you also need to [Update the runtime containers](#update-the-runtime-containers) to the latest version. The updating process for runtime containers is the same as the updating process the IoT Edge service. 
 
 ## Next steps
 

articles/iot-edge/iot-edge-as-gateway.md

@@ -105,7 +105,7 @@ Custom or third-party modules that are often specific to the downstream device's
 
 There are two patterns for translation gateways: *protocol translation* and *identity translation*.
 
-![Diagram - translation gateway patterns](./media/iot-edge-as-gateway/edge-as-gateway-translation.png)
+:::image type="content" source="./media/iot-edge-as-gateway/edge-as-gateway-translation.png" alt-text="Diagram showing translation gateway patterns." lightbox="./media/iot-edge-as-gateway/edge-as-gateway-translation.png":::
 
 ### Protocol translation
 

articles/iot-edge/iot-edge-runtime.md

@@ -33,7 +33,7 @@ The IoT Edge runtime is responsible for the following functions on IoT Edge devi
   - An IoT Edge device and the cloud
   - IoT Edge devices
 
-![Runtime communicates insights and module health to IoT Hub](./media/iot-edge-runtime/Pipeline.png)
+:::image type="content" source="./media/iot-edge-runtime/Pipeline.png" alt-text="Screenshot of how runtime communicates insights and module health to I o T Hub." lightbox="./media/iot-edge-runtime/Pipeline.png":::
 
 The responsibilities of the IoT Edge runtime fall into two categories: communication and module management. These two roles are performed by two components that are part of the IoT Edge runtime. The *IoT Edge agent* deploys and monitors the modules, while the *IoT Edge hub* is responsible for communication.
 
@@ -74,7 +74,7 @@ The IoT Edge hub isn't a full version of IoT Hub running locally. IoT Edge hub s
 
 To reduce the bandwidth that your IoT Edge solution uses, the IoT Edge hub optimizes how many actual connections are made to the cloud. IoT Edge hub takes logical connections from modules or downstream devices and combines them for a single physical connection to the cloud. The details of this process are transparent to the rest of the solution. Clients think they have their own connection to the cloud even though they're all being sent over the same connection. The IoT Edge hub can either use the AMQP or the MQTT protocol to communicate upstream with the cloud, independently from protocols used by downstream devices. However, the IoT Edge hub currently only supports combining logical connections into a single physical connection by using AMQP as the upstream protocol and its multiplexing capabilities. AMQP is the default upstream protocol.
 
-![IoT Edge hub is a gateway between physical devices and IoT Hub](./media/iot-edge-runtime/gateway-communication.png)
+:::image type="content" source="./media/iot-edge-runtime/gateway-communication.png" alt-text="Screenshot showing relationships to  I o T Edge hub as a gateway between physical devices and I o T Hub." lightbox="./media/iot-edge-runtime/gateway-communication.png":::
 
 IoT Edge hub can determine whether it's connected to IoT Hub. If the connection is lost, IoT Edge hub saves messages or twin updates locally. Once a connection is reestablished, it syncs all the data. The location used for this temporary cache is determined by a property of the IoT Edge hub's module twin. The size of the cache isn't capped and will grow as long as the device has storage capacity. For more information, see [Offline capabilities](offline-capabilities.md).
 
@@ -86,7 +86,7 @@ IoT Edge hub facilitates local communication. It enables device-to-module and mo
 
 The brokering mechanism uses the same routing features as IoT Hub to specify how messages are passed between devices or modules. First devices or modules specify the inputs on which they accept messages and the outputs to which they write messages. Then a solution developer can route messages between a source (for example, outputs), and a destination (for example, inputs), with potential filters.
 
-![Routes between modules go through IoT Edge hub](./media/iot-edge-runtime/module-endpoints-routing.png)
+:::image type="content" source="./media/iot-edge-runtime/module-endpoints-routing.png" alt-text="Screenshot showing how routes between modules go through I o T Edge hub." lightbox="./media/iot-edge-runtime/module-endpoints-routing.png":::
 
 Routing can be used by devices or modules built with the Azure IoT Device SDKs using the AMQP protocol. All messaging IoT Hub primitives (for example, telemetry), direct methods, C2D, twins, are supported but communication over user-defined topics isn't supported.
 

articles/iot-edge/media/how-to-update-iot-edge/configure-runtime.png

@@ -49,7 +49,7 @@ Before you put any device in production you should know how you're going to mana
 * IoT Edge
 * CA certificates
 
-[Device Update for IoT Hub](../iot-hub-device-update/index.yml) (Preview) is a service that enables you to deploy over-the-air updates (OTA) for your IoT Edge devices. 
+[Device Update for IoT Hub](../iot-hub-device-update/index.yml) is a service that enables you to deploy over-the-air updates (OTA) for your IoT Edge devices. 
 
 Alternative methods for updating IoT Edge require physical or SSH access to the IoT Edge device. For more information, see [Update the IoT Edge runtime](how-to-update-iot-edge.md). To update multiple devices, consider adding the update steps to a script or use an automation tool like Ansible.