Merge pull request #104012 from Karishma-Tiwari-MSFT/patch-146

(ForumsTeam) fixes MicrosoftDocs/azure-docs#47807

Author: PRMerger10

articles/virtual-machines/workloads/sap/hana-failover-procedure.md

@@ -31,12 +31,12 @@ There are two cases to consider when you fail over to a DR site:
 >[!NOTE]
 >The following steps must be done on the HANA Large Instance unit, which represents the DR unit. 
  
-To restore to the latest replicated storage snapshots, follow the steps in "Perform full DR failover - azure_hana_dr_failover" in [Microsoft snapshot tools for SAP HANA on Azure](https://github.com/Azure/hana-large-instances-self-service-scripts/blob/master/snapshot_tools_v4.1/Microsoft%20Snapshot%20Tools%20for%20SAP%20HANA%20on%20Azure%20v4.1.pdf). 
+To restore to the latest replicated storage snapshots, follow the steps in "Perform full DR failover - azure_hana_dr_failover" in [Microsoft snapshot tools for SAP HANA on Azure](https://github.com/Azure/hana-large-instances-self-service-scripts/blob/master/snapshot_tools_v4.2/Microsoft%20Snapshot%20Tools%20for%20SAP%20HANA%20on%20Azure%20v4.2.1.pdf). 
 
 If you want to have multiple SAP HANA instances failed over, run the azure_hana_dr_failover command several times. When requested, enter the SAP HANA SID you want to fail over and restore. 
 
 
-You can test the DR failover also without impacting the actual replication relationship. To perform a test failover, follow the steps in "Perform a test DR failover - azure_hana_test_dr_failover" in [Microsoft snapshot tools for SAP HANA on Azure](https://github.com/Azure/hana-large-instances-self-service-scripts/blob/master/snapshot_tools_v4.1/Microsoft%20Snapshot%20Tools%20for%20SAP%20HANA%20on%20Azure%20v4.1.pdf). 
+You can test the DR failover also without impacting the actual replication relationship. To perform a test failover, follow the steps in "Perform a test DR failover - azure_hana_test_dr_failover" in [Microsoft snapshot tools for SAP HANA on Azure](https://github.com/Azure/hana-large-instances-self-service-scripts/blob/master/snapshot_tools_v4.2/Microsoft%20Snapshot%20Tools%20for%20SAP%20HANA%20on%20Azure%20v4.2.1.pdf). 
 
 >[!IMPORTANT]
 >Do *not* run any production transactions on the instance that you created in the DR site through the process of **testing a failover**. The command azure_hana_test_dr_failover creates a set of volumes that have no relationship to the primary site. As a result, synchronization back to the primary site is *not* possible. 
@@ -114,7 +114,7 @@ Follow these steps:
 
 To monitor the status of your storage replication progress, run the script `azure_hana_replication_status`. This command must be run from a unit that runs in the disaster recovery location to function as expected. The command works no matter whether replication is active. The command can be run for every HANA Large Instance unit of your tenant in the disaster recovery location. It can't be used to obtain details about the boot volume. 
 
-For more information on the command and its output, see "Get DR replication status - azure_hana_replication_status" in [Microsoft snapshot tools for SAP HANA on Azure](https://github.com/Azure/hana-large-instances-self-service-scripts/blob/master/snapshot_tools_v4.0/Microsoft%20Snapshot%20Tools%20for%20SAP%20HANA%20on%20Azure%20v4.0.pdf).
+For more information on the command and its output, see "Get DR replication status - azure_hana_replication_status" in [Microsoft snapshot tools for SAP HANA on Azure](https://github.com/Azure/hana-large-instances-self-service-scripts/blob/master/snapshot_tools_v4.2/Microsoft%20Snapshot%20Tools%20for%20SAP%20HANA%20on%20Azure%20v4.2.1.pdf).
 
 
 ## Next steps