minor changes

Author: AbhishekMallick-MS

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

@@ -88,24 +88,7 @@ Restores triggered from HANA native clients to restore to another machine are no
 #### Delete
 
 Delete operation from HANA native is **NOT** supported by Azure Backup since the backup policy determines the lifecycle of backups in Azure Recovery services vault.
-
-### Manage or clean-up the HANA catalog for a database with Azure Backup enabled
-
-If you want to edit or clean up the backup catalog, do the following:
-
-1. Wait for any full or log backups for the database to finish. Check the status in SAP HANA Studio/ Cockpit.
-2. For the relevant database:
-    1. Unset the backint parameters. To do this, double-click **systemdb** > **Configuration** > **Select Database** > **Filter (Log)**.
-        * enable_auto_log_backup: No
-        * log_backup_using_backint: False
-        * catalog_backup_using_backint:False
-3. Edit the catalog and remove the older entries
-4. Then reverse the steps. For the same relevant DB mentioned above,
-    1. Re-enable the backint parameters
-        1. catalog_backup_using_backint:True
-        1. log_backup_using_backint: True
-        1. enable_auto_log_backup: Yes
-
+.
 ### Change policy
 
 You can change the underlying policy for an SAP HANA backup item.

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

@@ -135,11 +135,11 @@ sections:
       - question: |
           How can I manage or clean-up the HANA catalog for database with Azure Backup enabled?
         answer: |
-          - SAP recommends the catalog retention should be determined by your business need (, retention policy). The most common is the _30 days_ retention.
+          - SAP recommends the catalog retention should be determined by your business need (retention policy). The most common is _30 days_ retention.
           - You can trigger clean-up/pruning of HANA catalog through HANA native clients (such as cockpit or studio) or through SQL commands.
           - This clean-up task generates a catalog backup that's not moved to the Azure Backup vault (as there is no associated data backup).
           - The catalog backup is therefore shown as a failure in the Cockpit/Studio. However, note that this catalog backup failure doesn't mean  the catalog clean-up activity has failed.
-          - Note that this catalog backup failure also doesn't affect your Point-in-time recoverability.
+          - Note that this catalog backup failure also doesn't affect your point-in-time recoverability.
           - The catalog clean-up activity may cause the log backups triggered at the same time to be queued. These logs are then moved to the vault after the catalog backup (triggered by catalog clean-up) fails.
           - Manually check the success of the catalog clean-up activity.