Formatting, Add partner URI section

Author: PatAltimore

articles/iot-edge/about-iot-edge.md

@@ -18,9 +18,7 @@ Azure IoT Edge is a device-focused runtime that enables you to deploy, run, and
 
 Analytics drives business value in IoT solutions, but not all analytics need to be in the cloud. Azure IoT Edge helps you bring the analytical power of the cloud closer to your devices to drive better business insights and enable offline decision making. For example, you can run anomaly detection workloads at the edge to respond as quickly as possible to emergencies happening on a production line. If you want to reduce bandwidth costs and avoid transferring terabytes of raw data, you can clean and aggregate the data locally then only send the insights to the cloud for analysis.
 
-Azure IoT Edge is a feature of [Azure IoT Hub](../iot-hub/iot-concepts-and-iot-hub.md) and enables you to scale out and manage an IoT solution from the cloud. By packaging your business logic into standard containers and using optional pre-built IoT Edge module images from partners or the [Microsoft Artifact Registry](https://mcr.microsoft.com/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name
-
-), you can easily compose, deploy, and maintain your solution.
+Azure IoT Edge is a feature of [Azure IoT Hub](../iot-hub/iot-concepts-and-iot-hub.md) and enables you to scale out and manage an IoT solution from the cloud. By packaging your business logic into standard containers and using optional pre-built IoT Edge module images from partners or the [Microsoft Artifact Registry](https://mcr.microsoft.com/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name), you can easily compose, deploy, and maintain your solution.
 
 Azure IoT Edge is made up of three components:
 

articles/iot-edge/how-to-collect-and-transport-metrics.md

@@ -58,7 +58,7 @@ To configure monitoring on your IoT Edge device, follow the [Tutorial: Monitor I
 
 A Microsoft-supplied metrics-collector module can be added to an IoT Edge deployment to collect module metrics and send them to Azure Monitor. The module code is open-source and available in the [IoT Edge GitHub repo](https://github.com/Azure/iotedge/tree/main/edge-modules/metrics-collector).
 
-The metrics-collector module is provided as a multi-arch Docker container image that supports Linux X64, ARM32, ARM64, and Windows X64 (version 1809). It's publicly available at **[`mcr.microsoft.com/azureiotedge-metrics-collector`](https://mcr.microsoft.com/product/azureiotedge-metrics-collector/tags)**.
+The metrics-collector module is provided as a multi-arch Docker container image that supports Linux X64, ARM32, ARM64, and Windows X64 (version 1809). It's publicly available at [`mcr.microsoft.com/azureiotedge-metrics-collector`](https://mcr.microsoft.com/product/azureiotedge-metrics-collector/tags).
 
 ## Metrics collector configuration
 

articles/iot-edge/how-to-deploy-at-scale.md

@@ -71,8 +71,6 @@ To add custom code as a module, or to manually add an Azure service module, foll
 1. Choose one of the types of modules from the drop-down menu:
 
    * **IoT Edge Module** - You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is `mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0`. For a list of Microsoft IoT Edge module images, see the [Microsoft Artifact Registry](https://mcr.microsoft.com/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name).
-
-You can deploy an IoT Edge module from the Azure Marketplace and from your IoT Hub.
    * **Azure Stream Analytics Module** - Modules generated from an Azure Stream Analytics workload.
 
 1. If needed, repeat steps 2 and 3 to add additional modules to your deployment.

articles/iot-edge/how-to-deploy-modules-portal.md

@@ -17,8 +17,7 @@ services: iot-edge
 > [!IMPORTANT]
 > Starting August 28th 2024, Azure Marketplace is updating the distribution model for IoT Edge modules. Partners (module publishers) will begin [hosting their IoT Edge modules](https://azuremarketplace.microsoft.com/marketplace/apps/category/internet-of-things?subcategories=iot-edge-modules&filters=partners&page=1) on publisher-owned container registries. IoT Edge module images won't be available for download from the Azure Marketplace container registry.
 >
-> Contact the [IoT Edge module publisher](https://azuremarketplace.microsoft.com/marketplace/apps/category/internet-of-things?filters=partners) to obtain the updated container image URI and [update your IoT Edge](how-to-update-iot-edge.md) device configurations with the new image URI provided by the publisher.
->
+> Contact the [IoT Edge module publisher](https://azuremarketplace.microsoft.com/marketplace/apps/category/internet-of-things?filters=partners) to obtain the updated container image URI and [update your IoT Edge device configurations](how-to-update-iot-edge.md#update-partner-module-uris) with the new image URI provided by the publisher.
 >
 > IoT Edge devices that don't use [partner modules](https://azuremarketplace.microsoft.com/marketplace/apps/category/internet-of-things?filters=partners&page=1&subcategories=iot-edge-modules) acquired from Azure Marketplace aren't affected and no action is required.
 
@@ -28,7 +27,7 @@ This article shows how the Azure portal guides you through creating a deployment
 
 ## Prerequisites
 
-* An [IoT hub](../iot-hub/iot-hub-create-through-portal.md) in your Azure subscription.
+* An [IoT Hub](../iot-hub/iot-hub-create-through-portal.md) in your Azure subscription.
 * An IoT Edge device.
 
   If you don't have an IoT Edge device set up, you can create one in an Azure virtual machine. Follow the steps in one of the quickstart articles to [Create a virtual Linux device](quickstart-linux.md) or [Create a virtual Windows device](quickstart.md).
@@ -46,7 +45,7 @@ The Azure portal has a wizard that walks you through creating the deployment man
 
 ### Select device and add modules
 
-1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your IoT hub.
+1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your IoT Hub.
 1. On the left pane, select **Devices** under the **Device management** menu.
 1. Select the target IoT Edge device from the list.
 1. On the upper bar, select **Set Modules**.
@@ -89,11 +88,11 @@ Use this option for modules generated from an Azure Stream Analytics workload.
 1. Select your subscription and the Azure Stream Analytics Edge job that you created.
 1. Select **Save**.
 
-For more information about deploying Azure Stream Analytics an an IoT Edge module, see [Tutorial: Deploy Azure Stream Analytics as an IoT Edge module](tutorial-deploy-stream-analytics.md).
+For more information about deploying Azure Stream Analytics in an IoT Edge module, see [Tutorial: Deploy Azure Stream Analytics as an IoT Edge module](tutorial-deploy-stream-analytics.md).
 
 ### Specify routes
 
-On the **Routes** tab, you define how messages are passed between modules and the IoT Hub. Messages are constructed using name/value pairs. By default, the first deployment for a new device includes a route called **route** and defined as **FROM /messages/\* INTO $upstream**, which means that any messages output by any modules are sent to your IoT hub.  
+On the **Routes** tab, you define how messages are passed between modules and the IoT Hub. Messages are constructed using name/value pairs. By default, the first deployment for a new device includes a route called **route** and defined as **FROM /messages/\* INTO $upstream**, which means that any messages output by any modules are sent to your IoT Hub.  
 
 The **Priority** and **Time to live** parameters are optional parameters that you can include in a route definition. The priority parameter allows you to choose which routes should have their messages processed first, or which routes should be processed last. Priority is determined by setting a number 0-9, where 0 is top priority. The time to live parameter allows you to declare how long messages in that route should be held until they're either processed or removed from the queue.
 

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

@@ -176,6 +176,19 @@ If you use specific tags in your deployment (for example, mcr.microsoft.com/azur
 
 1. Select **Review + create**, review the deployment as seen in the JSON file, and select **Create**.
 
+## Update partner module URIs
+
+If you use partner modules, update your module deployments with image URIs provided by the partner. Contact the [IoT Edge module publisher](https://azuremarketplace.microsoft.com/marketplace/apps/category/internet-of-things?filters=partners) to obtain the updated container image URI. Update your device configurations with the new image URI provided by the publisher.
+
+1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your IoT Hub.
+1. On the left pane, select **Devices** under the **Device management** menu.
+1. Select the IoT Edge device that uses the partner module from the list.
+1. On the upper bar, select **Set Modules**.
+1. Choose the IoT Edge partner module that you want to update with the new image URI.
+1. Update the **Image URI** value with the new image URI provided by the publisher.
+1. Select **Apply** to save changes.
+1. Select **Review + create**, review the deployment as seen in the JSON file, and select **Create**.
+
 ## Verify versions match
 
 1. On your device, use `iotedge version` to check the security subsystem version. The output includes the major, minor, and revision version numbers. For example,  *iotedge 1.4.2*.