incorporated reviewer edits

Author: ScarlettFalls

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

@@ -5,7 +5,7 @@ keywords:
 author: kgremban
 manager: philmea
 ms.author: kgremban
-ms.date: 4/17/2020
+ms.date: 4/21/2020
 ms.topic: conceptual
 ms.service: iot-edge
 services: iot-edge
@@ -191,17 +191,6 @@ When you modify a deployment, the changes immediately replicate to all targeted
 
 1. Select the **Labels** tab and make any desired changes and select **Save**.
 
-### Modify tags and desired properties
-
-If you developed custom code modules to your devices, you can add or modify tags and desired properties in the module twin. For an overview of IoT Edge properties, see [Properties of the IoT Edge agent and IoT Edge hub module twins](module-edgeagent-edgehub.md).
-
-1. In your IoT hub, select **IoT Edge** from the left pane menu.
-1. Select the device with the module you want to edit.
-1. On the **Modules** tab, select the module.
-1. On the module details page, on the upper menu bar select **Module Identity Twin**. Edit the JSON as needed and select **Save**.
-
-    ![Edit properties on the module identity twin](./media/how-to-deploy-monitor/module-twin.png)
-
 ## Delete a deployment
 
 When you delete a deployment, any deployed devices take on their next highest priority deployment. If your devices don't meet the target condition of any other deployment, then the modules are not removed when the deployment is deleted.

articles/iot-edge/how-to-monitor-iot-edge-deployments.md

@@ -4,7 +4,7 @@ description: High-level monitoring including edgeHub and edgeAgent reported prop
 author: kgremban
 manager: philmea
 ms.author: kgremban
-ms.date: 04/17/2020
+ms.date: 04/21/2020
 ms.topic: conceptual
 ms.reviewer: veyalla
 ms.service: iot-edge
@@ -14,16 +14,6 @@ services: iot-edge
 
 Azure IoT Edge provides reporting that lets you monitor real-time information on the modules deployed to your IoT Edge devices. The IoT Hub service retrieves the status from the devices and makes them available to the operator. Monitoring is also important for [deployments made at scale](module-deployment-monitoring.md) that include automatic deployments and layered deployments.
 
-Successful deployments require monitoring the following information:
-
-* The last time the device or module connected or disconnected.
-
-* Connectivity status of the device or module.
-
-* Status codes of the IoT Edge runtime modules.
-
-* Versions of the deployed modules.
-
 Both devices and modules have similar data, such as connectivity, so values are obtained according to the device ID or the module ID.
 
 The IoT Hub service collects data reported by device and module twins and provides counts of the various states that devices may have. The IoT Hub service organizes this data into four groups of metrics:
@@ -62,10 +52,13 @@ To view the details of a deployment and monitor the devices running it, use the
 
    ![View targeted devices for a deployment](./media/how-to-monitor-iot-edge-deployments/target-devices.png)
 
-1. Select the **Metrics** tab. If you choose a metric from the **Select Metric** drop-down, a **View** button appears for you to display the results. You can also select **Edit Metics** to adjust the criteria for any custom metrics that you have defined. Select **Save** if you made changes.
+1. Select the **Metrics** tab. If you choose a metric from the **Select Metric** drop-down, a **View** button appears for you to display the results. You can also select **Edit Metrics** to adjust the criteria for any custom metrics that you have defined. Select **Save** if you made changes.
 
    ![View metrics for a deployment](./media/how-to-monitor-iot-edge-deployments/deployment-metrics-tab.png)
 
+
+To make changes to your deployment, see [Modify a deployment](how-to-deploy-at-scale.md#modify-a-deployment).
+
 ## Monitor a deployment with Azure CLI
 
 Use the [az IoT Edge deployment show](https://docs.microsoft.com/cli/azure/ext/azure-cli-iot-ext/iot/edge/deployment?view=azure-cli-latest#ext-azure-cli-iot-ext-az-iot-edge-deployment-show) command to display the details of a single deployment: