addressed review comments

Author: AbhishekMallick-MS

articles/backup/backup-azure-vms-troubleshoot.md

@@ -543,7 +543,7 @@ VM backup relies on issuing snapshot commands to underlying storage. Not having
    ```
 
   >[!Note]
-  >From December 12, 2022, Azure VM backup automatically sets the registry key in all Azure VMs registered as SQL VMs. Now, you don't need  to explicitly set this registry key. This ensures that snapshots aren't delayed and any log chains managed by other backup products are also not broken. Azure VM backup now also set the registry key in any new SQL VMs automatically.
+  >From December 12, 2022, Azure VM backup automatically sets the registry key in the existing protected Azure VMs that are registered as SQL VMs. Now, you don't need  to explicitly set this registry key. This ensures that snapshots aren't delayed and any log chains managed by other backup products are also not broken. Azure VM backup now also set the registry key in any new SQL VMs automatically during the configuration of backup.
 
 * **VM status is reported incorrectly because the VM is shut down in RDP**. If you used the remote desktop to shut down the virtual machine, verify that the VM status in the portal is correct. If the status isn't correct, use the **Shutdown** option in the portal VM dashboard to shut down the VM.
 * **If more than four VMs share the same cloud service, spread the VMs across multiple backup policies**. Stagger the backup times, so no more than four VM backups start at the same time. Try to separate the start times in the policies by at least an hour.

articles/backup/sap-hana-database-manage.md

@@ -20,6 +20,30 @@ You'll learn how to monitor jobs and alerts, trigger an on-demand backup, edit p
 
 If you haven't configured backups yet for your SAP HANA databases, see [Back up SAP HANA databases on Azure VMs](./backup-azure-sap-hana-database.md). To earn more about the supported configurations and scenarios, see [Support matrix for backup of SAP HANA databases on Azure VMs](sap-hana-backup-support-matrix.md).
 
+## Run on-demand backups
+
+Backups run according to the policy schedule.
+
+To run on-demand backups, follow these steps:
+
+1. On the left pane of the Recovery Services vault, select **Backup items**.
+
+   ![Screenshot that shows the 'Backup items' link on the Recovery Services vault dashboard.](./media/sap-hana-db-manage/backup-items.png)
+
+1. On the **Backup Items** pane, select the VM that's running the SAP HANA database, and then select **Backup now**.
+
+1. On the **Backup Now** pane, choose the type of backup that you want to perform, and then select **OK**.
+
+   The retention period of this backup is determined by the type of on-demand backup you want to run.
+
+   - *On-demand full backups* are retained for a minimum of *45 days* and a maximum of *99 years*.
+   - *On-demand differential backups* are retained as per the *log retention set in the policy*.
+   - *On-demand incremental backups* aren't currently supported.
+
+1. Monitor the Azure portal notifications. To do so, on the Recovery Services vault dashboard, select **Backup Jobs**, and then select **In progress**. 
+
+   Depending on the size of your database, creating the initial backup might take a while.
+
 ## Monitor manual backup jobs
 
 Azure Backup shows all manually triggered jobs in the **Backup jobs** section of **Backup center**.
@@ -207,28 +231,6 @@ Unregister an SAP HANA instance after you disable protection but before you dele
 
    ![Select unregister](./media/sap-hana-db-manage/unregister.png)
 
-### Run on-demand backups
-
-Backups run according to the policy schedule. You can run on-demand backups by doing the following:
-
-1. On the left pane of the Recovery Services vault, select **Backup items**.
-
-   ![Screenshot that shows the 'Backup items' link on the Recovery Services vault dashboard.](./media/sap-hana-db-manage/backup-items.png)
-
-1. On the **Backup Items** pane, select the VM that's running the SAP HANA database, and then select **Backup now**.
-
-1. On the **Backup Now** pane, choose the type of backup that you want to perform, and then select **OK**.
-
-   The retention period of this backup is determined by the type of on-demand backup you want to run.
-
-   - *On-demand full backups* are retained for a minimum of *45 days* and a maximum of *99 years*.
-   - *On-demand differential backups* are retained as per the *log retention set in the policy*.
-   - *On-demand incremental backups* aren't currently supported.
-
-1. Monitor the Azure portal notifications. To do so, on the Recovery Services vault dashboard, select **Backup Jobs**, and then select **In progress**. 
-
-   Depending on the size of your database, creating the initial backup might take a while.
-
 ## Manage operations using SAP HANA native clients
 
 This section describes how to manage various operations from non-Azure clients, such as HANA Studio.

articles/backup/sap-hana-faq-backup-azure-vm.yml

@@ -34,7 +34,7 @@ sections:
         answer: |
           You can check the status of your backups (scheduled/on-demand) from any of the following locations:
 
-          1. **Backup jobs**: Azure Backup shows all manually triggered jobs in the Backup jobs section in the Azure portal.  <br><br>   The jobs you see in the Azure portal includes database discovery and registering operations, and backup and restore operations. Scheduled jobs, including log backups aren't shown in this section. Manually triggered backups from the SAP HANA native clients (Studio/Cockpit/DBA Cockpit), are also not shown here.
+          1. **Backup jobs**: Azure Backup shows all manually triggered jobs in the Backup jobs section in the Azure portal.  <br><br>   The jobs you see in the Azure portal include database discovery and registering operations, and backup and restore operations. Scheduled jobs, including log backups aren't shown in this section. Manually triggered backups from the SAP HANA native clients (Studio/Cockpit/DBA Cockpit), are also not shown here.
 
              :::image type="content" source="./media/sap-hana-faq-backup-azure-vm/manually-triggered-jobs.png" alt-text="Screenshot showing manually triggered jobs in the Backup jobs section in the Azure portal.":::
 
@@ -120,7 +120,7 @@ sections:
       - question: |
           How can I manage or clean up the HANA catalog for database with the Azure Backup enabled?
         answer: |
-          Prune the HANA catalog using SAP recommended methods such as BACKUP CATALOG DELETE statements or HANA stnudio/Cockpit. Learn more how to [manage operations using SAP native clients](sap-hana-database-manage.md#manage-operations-using-sap-hana-native-clients).
+          You can prune the HANA catalog using SAP recommended methods, such as BACKUP CATALOG DELETE statements or HANA Studio/Cockpit. Learn more how to [manage operations using SAP native clients](sap-hana-database-manage.md#manage-operations-using-sap-hana-native-clients).
 
       - question: |
           How can I use SAP HANA Backup with my HANA Replication set-up?
@@ -167,7 +167,7 @@ sections:
           
           1. Once you run the pre-registration script, the user information is updated with new password on the primary node. Then  the connection to attempt backup will be re-established. But, you might again experience the same scenario.
           
-          1. Also, the backups (full backups) that fails on the secondary node create alerts.
+          1. Also, the backups (full backups) that fail on the secondary node create alerts.
           
           To avoid the above issues, we recommend you to stop protection for a node after it becomes secondary (so that connections aren’t attempted and user is not locked) and resume protection on it, once it becomes primary. If you don’t face this locking situation on their HSR setups and are comfortable with alerts being raised, you can configure backups on both the nodes so that the service handles the take-over and fail-back.