minor change

Author: AbhishekMallick-MS

articles/backup/backup-azure-sap-hana-database-troubleshoot.md

@@ -266,7 +266,7 @@ Upgrades from SDC to MDC that cause a SID change can be handled as follows:
 - Ensure that the new MDC version is currently [supported by Azure Backup](sap-hana-backup-support-matrix.md#scenario-support)
 - **Stop protection with retain data** for the old SDC database
 - Perform the upgrade. After completion, the HANA system is now MDC with a system DB and tenant DBs
-- Move the _config.json_ file located at _/opt/msawb/etc/config/SAPHana//_.
+- Move the _config.json_ file located at _/opt/msawb/etc/config/SAPHana/_.
 - Rerun the [pre-registration script](https://aka.ms/scriptforpermsonhana) with correct details (new SID and MDC). Due to a change in SID, you may face issues with successfully running the script. Contact Azure Backup support if you face issues.
 - Re-register the extension for the same machine in the Azure portal (**Backup** -> **View details** -> Select the relevant Azure VM -> Re-register)
 - Select **Rediscover DBs** for the same VM. This action should show the new DBs in step 3 as SYSTEMDB and Tenant DB, not SDC