Merge pull request #40994 from v-viksur/patch-5

(ForumsTeam) Updated Hyper Link

Author: PRMerger18

articles/site-recovery/site-recovery-test-failover-to-azure.md

@@ -36,7 +36,7 @@ This procedure describes how to run a test failover for a recovery plan.
 
 	- Site Recovery attempts to create test VMs in a subnet with the same name and same IP address as that provided in the **Compute and Network** settings of the VM.
 	- If a subnet with the same name isn't available in the Azure virtual network used for test failover, then the test VM is created in the first subnet alphabetically.
-	- If same IP address isn't available in the subnet, then the VM receives another available IP address in the subnet. [Learn more](#creating-a-network-for-test-failover).
+	- If same IP address isn't available in the subnet, then the VM receives another available IP address in the subnet. [Learn more](#create-a-network-for-test-failover).
 4. If you're failing over to Azure and data encryption is enabled, in **Encryption Key**, select the certificate that was issued when you enabled encryption during Provider installation. You can ignore this step encryption isn't enabled.
 5. Track failover progress on the **Jobs** tab. You should be able to see the test replica machine in the Azure portal.
 6. To initiate an RDP connection to the Azure VM, you need to [add a public IP address](https://aka.ms/addpublicip) on the network interface of the failed over VM.