Merge pull request #187735 from JimacoMS4/fix-hub-ha-dr-link-text

Updated text for cloning to another region link

Author: PRMerger18

articles/iot-dps/iot-dps-understand-ip-address.md

@@ -27,7 +27,7 @@ The IP address prefixes for the public endpoints of an IoT Hub Device Provisioni
 
 * The IP address prefixes of IoT DPS instances are subject to change. These changes are published periodically via service tags before taking effect. It is therefore important that you develop processes to regularly retrieve and use the latest service tags. This process can be automated via the [service tags discovery API](../virtual-network/service-tags-overview.md#service-tags-on-premises). The Service tags discovery API is still in preview and in some cases may not produce the full list of tags and IP addresses. Until discovery API is generally available, consider using the [service tags in downloadable JSON format](../virtual-network/service-tags-overview.md#discover-service-tags-by-using-downloadable-json-files). 
 
-* Use the *AzureIoTHub.[region name]* tag to identify IP prefixes used by DPS endpoints in a specific region. To account for datacenter disaster recovery, or [regional failover](../iot-hub/iot-hub-ha-dr.md), ensure connectivity to IP prefixes of your DPS instance's geo-pair region is also enabled.
+* Use the *AzureIoTHub.[region name]* tag to identify IP prefixes used by DPS endpoints in a specific region. To account for datacenter disaster recovery, or [regional failover](iot-dps-ha-dr.md), ensure connectivity to IP prefixes of your DPS instance's geo-pair region is also enabled.
 
 * Setting up firewall rules for a DPS instance may block off connectivity needed to run Azure CLI and PowerShell commands against it. To avoid these connectivity issues, you can add ALLOW rules for your clients' IP address prefixes to re-enable CLI or PowerShell clients to communicate with your DPS instance.  
 

articles/iot-hub/iot-hub-ha-dr.md

@@ -146,7 +146,7 @@ Failover capability will not be available if you disable disaster recovery for a
 
 :::image type="content" source="media/iot-hub-ha-dr/disaster-recovery-disabled.png" alt-text="Screenshot that shows disaster recovery disabled for an IoT hub in Singapore region.":::
 
-You can only disable disaster recovery to avoid data replication outside of the paired region in Brazil South or Southeast Asia when you create an IoT hub. If you want to configure your existing IoT hub to disable disaster recovery, you need to create a new IoT hub with disaster recovery disabled and manually migrate your existing IoT hub by following the [How to clone an Azure IoT Hub to another region article](iot-hub-how-to-clone.md).
+You can only disable disaster recovery to avoid data replication outside of the paired region in Brazil South or Southeast Asia when you create an IoT hub. If you want to configure your existing IoT hub to disable disaster recovery, you need to create a new IoT hub with disaster recovery disabled and manually migrate your existing IoT hub. For guidance, see [How to clone an Azure IoT Hub to another region](iot-hub-how-to-clone.md). This article contains advice about migrating routes, custom endpoints, and other IoT Hub artifacts when migrating to a new Iot hub. You can ignore concerns that have to do with migrating across regions.
 
 ## Achieve cross region HA