Merge pull request #295838 from PhilKang0704/broken-link-fix-kgremban

Broken links fixing - kgremban

Author: prmerger-automator[bot]

articles/iot-hub/how-to-routing-arm.md

@@ -411,12 +411,12 @@ Add a route definition to your Resource Manager template. For more information,
    | Property | Value |
    | -------- | ----- |
    | name | Provide a unique value to name your route. |
-   | source | Select the message or event logs source to route to the endpoint. For a list of source options, see [az iot hub route](/cli/azure/iot/hub/route#az-iot-hub-route-create-required-parameters). |
+   | source | Select the message or event logs source to route to the endpoint. For a list of source options, see [az iot hub message-route](/cli/azure/iot/hub/message-route). |
    | condition | A query to filter the source data. If no condition is required, say `true`. For more information, see [IoT Hub message routing query syntax](./iot-hub-devguide-routing-query-syntax.md). |
    | endpointNames | The name of the existing endpoint where this data will be routed. Currently only one endpoint is allowed. |
    | isEnabled | Set to `true` to enable the route, or `false` to disable the route. |
 
-1. Save your JSON file.
+2. Save your JSON file.
 
 ## Deploy the Resource Manager template
 

articles/iot-hub/how-to-routing-azure-cli.md

@@ -89,7 +89,7 @@ Create a Cosmos DB account for SQL API and a Cosmos DB container. For more infor
 All IoT Hub routes point to an endpoint, which will receive the routed device and event data. More than one route can point to the same endpoint. Currently, IoT Hub supports endpoints for Event hubs, Service Bus queues or topics, Storage, and Cosmos DB. An instance of the service that you use for your endpoint must exist in your Azure subscription before you create the endpoint.
 
 > [!NOTE]
-> This article uses the [az iot hub message-endpoint](/cli/azure/iot/hub/message-endpoint) command group, which was introduced in version 0.19.0 of the azure-iot extension for the Azure CLI. Previous versions of the azure-iot extension used the [az iot hub routing-endpoint](/cli/azure/iot/hub/routing-endpoint) command group, which is similar and still supported but does not support creating Cosmos DB endpoints.
+> This article uses the [az iot hub message-endpoint](/cli/azure/iot/hub/message-endpoint) command group, which was introduced in version 0.19.0 of the azure-iot extension for the Azure CLI. Previous versions of the azure-iot extension used the `az iot hub routing-endpoint` command group, which is no longer supported.
 >
 > Use the following command to update to the latest version of the azure-iot extension:
 >
@@ -273,7 +273,7 @@ az iot hub message-endpoint delete --hub-name {iothub_name} --endpoint-type stor
 In IoT Hub, you can create a route to send messages or capture events. Each route has a data source and an endpoint. The data source is where messages or event logs originate. The endpoint is where the messages or event logs end up. You choose locations for the data source and endpoint when you create a new route in your IoT hub. Optionally, you can [Add queries to message routes](iot-hub-devguide-routing-query-syntax.md) to filter messages or events before they go to the endpoint.
 
 > [!NOTE]
-> This article uses the [az iot hub message-route](/cli/azure/iot/hub/message-route) command group, which was introduced in version 0.19.0 of the azure-iot extension for the Azure CLI. Previous versions of the azure-iot extension used the [az iot hub route](/cli/azure/iot/hub/route) command group, which is similar and still supported.
+> This article uses the [az iot hub message-route](/cli/azure/iot/hub/message-route) command group, which was introduced in version 0.19.0 of the azure-iot extension for the Azure CLI. Previous versions of the azure-iot extension used the `az iot hub route` command group, which is no longer supported.
 >
 > Use the following command to update to the latest version of the azure-iot extension:
 >