Bookmarks.

Author: TimShererWithAquent

articles/iot-hub/monitor-iot-hub-reference.md

@@ -71,7 +71,7 @@ For most metrics, all aggregation types are valid. For count metrics with a **Un
 | Result         | Either `success` or `failure` |
 | RoutingSource  | `Device Messages`, `Twin Change Events`, `Device Lifecycle Events` |
 
-<a name="device-telemetry-metrics"></a><a name="routing-metric"></a><a name="device-metrics"></a>
+<a name="device-telemetry-metrics"></a><a name="routing-metrics"></a><a name="device-metrics"></a>
 ### Metrics display name and aggregation
 
 The following tables provide more information about the metrics described in the preceding table. They show the IoT Hub platform metrics by general category and list metrics by their display name as assigned in the Azure portal.

articles/iot-hub/troubleshoot-message-routing.md

@@ -15,7 +15,7 @@ This article provides monitoring and troubleshooting guidance for common issues
 
 ## Monitoring message routing
 
-We recommend you monitor [IoT Hub metrics related to message routing and endpoints](monitor-iot-hub-reference.md#routing-metrics) to give you an overview of the messages sent. You can also create a diagnostic setting to send operations for [**routes** in IoT Hub resource logs](monitor-iot-hub-reference.md#routes) to Azure Monitor Logs, Event Hubs or Azure Storage for custom processing. To learn more about using metrics, resource logs, and diagnostic settings, see [Monitor IoT Hub](monitor-iot-hub.md). For a tutorial, see [Set up and use metrics and resource logs with an IoT hub](tutorial-use-metrics-and-diags.md).
+We recommend you monitor [IoT Hub metrics related to message routing and endpoints](monitor-iot-hub-reference.md#routing-metrics) to give you an overview of the messages sent. You can also create a diagnostic setting to send operations for [**routes** in IoT Hub resource logs](monitor-iot-hub-reference.md#routes-category) to Azure Monitor Logs, Event Hubs or Azure Storage for custom processing. To learn more about using metrics, resource logs, and diagnostic settings, see [Monitor IoT Hub](monitor-iot-hub.md). For a tutorial, see [Set up and use metrics and resource logs with an IoT hub](tutorial-use-metrics-and-diags.md).
 
 We also recommend enabling the [fallback route](iot-hub-devguide-messages-d2c.md#fallback-route) if you want to maintain messages that don't match the query on any of the routes. These can be retained in the [built-in endpoint](iot-hub-devguide-messages-read-builtin.md) for the amount of retention days configured.
 
@@ -36,7 +36,7 @@ All the [IoT Hub metrics related to routing](monitor-iot-hub-reference.md#routin
 
 #### The resource logs for any operational issues
 
-Observe the [**Routes** resource logs](monitor-iot-hub-reference.md#routes) to get more information on the routing and endpoint [operations](#operation-names) or identify errors and relevant [error code](#common-error-codes) to understand the issue further. For example, the operation name **RouteEvaluationError** in the log indicates the route could not be evaluated because of an issue with the message format. Use the tips provided for the specific [operation names](#operation-names) to mitigate the issue. When an event is logged as an error, the log will also provide more information on why the evaluation failed. For example, if the operation name is **EndpointUnhealthy**, an [Error code](#common-error-codes) of 403004 indicates the endpoint ran out of space.
+Observe the [**Routes** resource logs](monitor-iot-hub-reference.md#routes-category) to get more information on the routing and endpoint [operations](#operation-names) or identify errors and relevant [error code](#common-error-codes) to understand the issue further. For example, the operation name **RouteEvaluationError** in the log indicates the route could not be evaluated because of an issue with the message format. Use the tips provided for the specific [operation names](#operation-names) to mitigate the issue. When an event is logged as an error, the log will also provide more information on why the evaluation failed. For example, if the operation name is **EndpointUnhealthy**, an [Error code](#common-error-codes) of 403004 indicates the endpoint ran out of space.
 
 #### The health of the endpoint
 
@@ -63,7 +63,7 @@ You can enable or disable the fallback route in the Azure portal by using the Me
 
 ## Routes resource logs
 
-The following are the operation names and error codes logged in the [routes resource logs](monitor-iot-hub-reference.md#routes).
+The following are the operation names and error codes logged in the [routes resource logs](monitor-iot-hub-reference.md#routes-category).
 
 <a id="diagnostics-operation-names"></a>
 ### Operation Names