addressed PM comments

Author: AbhishekMallick-MS

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

@@ -173,6 +173,20 @@ Refer to the [prerequisites](tutorial-backup-sap-hana-db.md#prerequisites) and [
 **Possible causes** | System databases restore failed as the **<sid>adm** user environment couldn't find the **HDBsettings.sh** file to trigger restore.
 **Recommended action** | Work with the SAP HANA team to fix this issue.<br><br>If HXE is the SID, ensure that environment variable HOME is set to _/usr/sap/HXE/home_ as **sid-adm** user.
 
+### CloudDosAbsoluteLimitReached
+
+**Error message** | `Operation is blocked as you have reached the limit on number of operations permitted in 24 hours.` |
+------ | -----------
+**Possible causes** | When you've reached the maximum permissible limit for an operation in a span of 24 hours, this error appears. <br><br> For example: If you've hit the limit for the number of configure backup jobs that can be triggered per day, and you try to configure backup on a new item, you'll see this error.
+**Recommended action** | Typically, retrying the operation after 24 hours resolves this issue. However, if the issue persists, you can contact Microsoft support for help.
+
+### CloudDosAbsoluteLimitReachedWithRetry
+
+**Error message** | `Operation is blocked as the vault has reached its maximum limit for such operations permitted in a span of 24 hours.`
+------ | -----------
+**Possible causes** | When you've reached the maximum permissible limit for an operation in a span of 24 hours, this error appears. This error usually appears when there are at-scale operations such as modify policy or auto-protection. Unlike the case of CloudDosAbsoluteLimitReached, there isn't much you can do to resolve this state. In fact, Azure Backup service will retry the operations internally for all the items in question.<br><br> For example, if you've a large number of datasources protected with a policy and you try to modify that policy, it will trigger configure protection jobs for each of the protected items and sometimes may hit the maximum limit permissible for such operations per day.
+**Recommended action** | Azure Backup service will automatically retry this operation after 24 hours.
+
 ## Restore checks
 
 ### Single Container Database (SDC) restore
@@ -273,20 +287,6 @@ Upgrades from SDC to MDC that cause a SID change can be handled as follows:
 - The older SDC database continues to exist in the vault and have old backed up data retained according to the policy
 - Configure backup for these databases
 
-## Error messages
-
-### CloudDosAbsoluteLimitReached
-
-| Error message | Possible causes | Recommended actions |
-|---|---|---|
-Operation is blocked as you have reached the limit on number of operations permitted in 24 hours. | When you've reached the maximum permissible limit for an operation in a span of 24 hours, this error appears. <br> For example: If you've hit the limit for the number of configure backup jobs that can be triggered per day, and you try to configure backup on a new item, you'll see this error. | Typically, retrying the operation after 24 hours resolves this issue. However, if the issue persists, you can contact Microsoft support for help.
-
-### CloudDosAbsoluteLimitReachedWithRetry
-
-| Error message | Possible causes | Recommended actions |
-|---|---|---|
-Operation is blocked as the vault has reached its maximum limit for such operations permitted in a span of 24 hours. | When you've reached the maximum permissible limit for an operation in a span of 24 hours, this error appears. This error usually appears when there are at-scale operations such as modify policy or auto-protection. Unlike the case of CloudDosAbsoluteLimitReached, there isn't much you can do to resolve this state. In fact, Azure Backup service will retry the operations internally for all the items in question.<br> For example: If you have a large number of datasources protected with a policy and you try to modify that policy, it will trigger configure protection jobs for each of the protected items and sometimes may hit the maximum limit permissible for such operations per day.| Azure Backup service will automatically retry this operation after 24 hours.
-
 ## Re-registration failures
 
 Check for one or more of the following symptoms before you trigger the re-register operation: