Update monitor-device-update-iot-hub

Author: eshashah-msft

articles/iot-hub-device-update/monitor-device-update-iot-hub

@@ -16,23 +16,21 @@ When you have critical applications and business processes relying on Azure reso
 
 This article describes the monitoring data generated by Device Update for IoT Hub (DU). Device Update uses [Azure Monitor](../azure-monitor/overview.md). If you are unfamiliar with the features of Azure Monitor common to all Azure services that use it, read [Monitoring Azure resources with Azure Monitor](../azure-monitor/essentials/monitor-azure-resource.md).
 
-## Activity log
+## Activity log Collection and Routing
 
-The Activity log displays recent administrative activity for the device update account, instances, including any creation, updates, deletion and change in access permissions. View the Activity log in the Azure portal, or create a diagnostic setting to send it to a Log Analytics workspace, where you can view events over time or analyze them with other collected data.
+The Activity log displays recent administrative activity for the device update account, instances, including any creation, updates, deletion and change in access permissions. Activity logs are collected and stored automatically, but can be routed to other locations by using a diagnostic setting.  
 
-## Collection and routing
+In Azure portal, you can select **Activity Logs** in the Device Update account menu, and the **Time range** for which you want to see activity logs
 
-Activity logs are collected and stored automatically, but can be routed to other locations by using a diagnostic setting.  
+To create a diagnostic setting to send it to a destination of your choice (Log Analytics workspace, storage account, Event Hub, etc.), select **Export Activity Logs** followed by **Add diagnostic setting** and scope it to the logs and platform metrics emitted by your account.
 
-In Azure portal, you can select **Activity Logs**, select  **Export Activity Logs** followed by **Add diagnostic setting** to create diagnostic settings scoped to the logs and platform metrics emitted by your instance.
-
-See [Create diagnostic setting to collect platform logs and metrics in Azure](/azure/azure-monitor/platform/diagnostic-settings) for the detailed process for creating a diagnostic setting using the Azure portal, CLI, or PowerShell. When you create a diagnostic setting, you specify which categories of logs to collect.
+See [Create diagnostic setting to collect platform logs and metrics in Azure](../azure-monitor/essentials/diagnostic-settings.md) for the detailed process for creating a diagnostic setting using the Azure portal, CLI, or PowerShell. When you create a diagnostic setting, you specify which categories of logs to collect.
 
 ## Analyzing logs
 
 Data in Azure Monitor Logs is stored in tables where each table has its own set of unique properties.  
 
-To route data to Azure Monitor Logs, you must create a diagnostic setting to send resource logs or platform metrics to a Log Analytics workspace. To learn more, see [Collection and routing](#collection-and-routing).
+To route data to Azure Monitor Logs, you must create a diagnostic setting to send resource logs or platform metrics to a Log Analytics workspace. 
 
 In Azure portal, you can select **Logs** under **Monitoring** on the left-pane of your Device Update account to perform Log Analytics queries scoped, by default, to the logs and metrics collected in Azure Monitor Logs for your account.