Addressed PLR review inputs

Author: AbhishekMallick01

articles/backup/sap-ase-backup-support-matrix.md

@@ -82,6 +82,13 @@ The following table lists the required parameters for adding/removing SAP ASE in
 |    | `sudo` | Remove a `SID` from the **Config** file. | `"<Path_to_the_Pre-Reg_Script" -aw SAPAse --sid "<SID>" --sid-user "<sidUser>" --db-port "<dbPort>" --db-user <dbUser> --db-host "<dbHost>" --enable-striping <true/false> --skip-network-checks --remove` |
 |    | `--dbHost` | The private IP of the specific SID instance that you intend to register. <br><br> In multi-instance setups, each System ID (SID) might have a different private IP. Use the IP available in `/sybase/<SID>/interfaces` for the correct instance. |     |
 
+
+>[!Note]
+>If you have the preregistration script already installed, update the script name by running the following bash command:
+>
+> `sudo ./<script name> -us`
+
+
 ## Next steps
 
 - [Configure backup for SAP ASE (Sybase) databases on Azure VMs using Azure portal](sap-ase-database-backup.md).

articles/backup/sap-ase-database-about.md

@@ -85,11 +85,10 @@ For example, if you protect a 1.2 TB ASE database in an East US2 instance, you
 
 ## Cross Subscription Restore for SAP ASE (Sybase) database
 
-Azure Backup now supports restoring SAP ASE databases to any subscription, provided the [necessary Azure role-based access control (Azure RBAC) permissions](backup-rbac-rs-vault.md#minimum-role-requirements-for-sap-ase-sybase-database--cross-subscription-restore) are met. By default, restores are performed within the same subscription where the restore points are located.
-
-With Cross-Subscription Restore (CSR), you can restore SAP ASE databases to any subscription and Recovery Services vault within the same tenant, as long as they have the required restore permissions. CSR is enabled by default on all Recovery Services vaults, including both existing and newly created vaults.
+Azure Backup now supports restoring SAP ASE databases to any subscription and Recovery Services vault, provided they are in the same tenant and  the necessary [Azure role-based access control (Azure RBAC) permissions for restore](backup-rbac-rs-vault.md#minimum-role-requirements-for-sap-ase-sybase-database--cross-subscription-restore) are met. By default, restores are performed within the same subscription where the restore points are located.
 
 >[!Note]
+>- CSR is enabled by default on all Recovery Services vaults, including both existing and newly created vaults.
 >- Cross-Subscription Restore can be initiated directly from the Recovery Services vault.
 >- Cross Regional Restore (CRR) with CSR isn't supported.
 

articles/backup/sap-ase-database-backup-run-preregistration-quickstart.md

@@ -46,12 +46,12 @@ The preregistration script is a Python script that you run on the VM where the S
 
 ## Run the preregistration script
 
-Before you execute the preregistration script, [download the ASE preregistration script file](https://aka.ms/preregscriptsapase) and copy it to the virtual machine (VM).
+After you [download the ASE preregistration script file](https://aka.ms/preregscriptsapase), copy it to the virtual machine (VM).
+
+To execute the preregistration script for SAP ASE database backup, run the following bash commands:
 
 >[!NOTE]
 >Replace `<script name>` in the following commands with the name of the script file you downloaded and copied to the VM.
-
-To execute the preregistration script for SAP ASE database backup, run the following bash commands:
  
 1. Convert the script to the Unix format.
 
@@ -68,12 +68,6 @@ To execute the preregistration script for SAP ASE database backup, run the follo
     sudo chmod -R 777 /path/to/script/file
    ```
 
-1. Update the script name.
-
-   ```bash
-    sudo ./<script name> -us
-   ```
-
 1. Run the script.
 
     >[!Note]

articles/backup/sap-ase-database-backup-tutorial.md

@@ -290,7 +290,7 @@ To discover the SAP ASE databases, follow these steps:
    >[!Note]
    >- After discovery, unprotected VMs appear in the portal, listed by name and resource group.
    >- If a VM isn't listed as expected, check if it's already backed up in a vault.
-   >- Multiple VMs can have the same name but they belong to different resource groups.
+   >- If you have multiple VMs with the same name, ensure that they belong to different resource groups.
  
 1. On the **Select Virtual Machines** pane, download the prepost script that provides permissions for the Azure Backup service to access the SAP ASE VMs for database discovery.
 
@@ -311,7 +311,7 @@ To configure the backup operation for the SAP ASE database, follow these steps:
  
      :::image type="content" source="./media/sap-ase-database-backup-tutorial/configure-backup.png" alt-text="Screenshot shows how to start the backup configuration." lightbox="./media/sap-ase-database-backup-tutorial/configure-backup.png":::
 
-1. On the **Configure Backup** pane, on the **Backup policy** tab, under the **Backup policy**, select **Create a new policy** for the databases. 
+1. On the **Configure Backup** pane, on the **Backup policy** tab, under **Backup policy**, select **Create a new policy** for the databases. 
 
    :::image type="content" source="./media/sap-ase-database-backup-tutorial/create-backup-policy.png" alt-text="Screenshot shows how to start creating the backup policy." lightbox="./media/sap-ase-database-backup-tutorial/create-backup-policy.png":::
 
@@ -366,7 +366,7 @@ To configure the backup operation for the SAP ASE database, follow these steps:
 
      >[!Note]
      >- Log backups only begin to flow after a successful full backup is completed.
-     >- Each log backup is chained to the previous full backup to form a recovery chain. This full backup is retained until the retention of the last log backup has expired. This might mean that the full backup is retained for an extra period to make sure all the logs can be recovered. Let's assume a user has a weekly full backup, daily differential and 2-hour logs. All of them are retained for 30 days. But the weekly full can be really cleaned up/deleted only after the next full backup is available, that is, after 30 + 7 days. For example, a weekly full backup happens on Nov 16th. According to the retention policy, it should be retained until Dec 16th. The last log backup for this full happens before the next scheduled full, on Nov 22nd. Until this log is available until Dec 22nd, the Nov 16th full can't be deleted. So, the Nov 16th full is retained until Dec 22nd.
+     >- Each log backup is chained to the previous full backup to form a recovery chain. This full backup is retained until the retention of the last log backup has expired. This might mean that the full backup is retained for an extra period to make sure all the logs can be recovered. Let's assume a user has a weekly full backup, daily differential and 2-hour logs. All of them are retained for 30 days. But the weekly full can be cleaned up/deleted only after the next full backup is available, that is, after 30 + seven days. For example, if a weekly full backup is performed on November 16th, it remains stored until December 16th in accordance with the retention policy. The final log backup for this full occurs on November 22nd, before the next scheduled full backup. Since this log backup remains accessible until December 22nd, the November 16th full backup cannot be deleted until that date. As a result, the November 16th full backup is retained until December 22nd.
 
 1. Select **OK** to save the log backup policy configuration.
 1. On the **Create Policy** pane, select **OK** to complete the backup policy creation.

articles/backup/sap-ase-database-backup.md

@@ -87,7 +87,7 @@ To configure the backup operation for the SAP ASE database, follow these steps:
 
      :::image type="content" source="./media/sap-ase-database-backup/configure-backup.png" alt-text="Screenshot shows how to start the backup configuration." lightbox="./media/sap-ase-database-backup/configure-backup.png":::
 
-2.Under the **Backup Policy**, select **Create a new policy** for the databases. 
+2.Under **Backup Policy**, select **Create a new policy** for the databases. 
 
    :::image type="content" source="./media/sap-ase-database-backup/create-backup-policy.png" alt-text="Screenshot shows how to start creating the backup policy." lightbox="./media/sap-ase-database-backup/create-backup-policy.png":::
 
@@ -142,7 +142,7 @@ To configure the backup operation for the SAP ASE database, follow these steps:
 
      >[!Note]
      >- Log backups only begin to flow after a successful full backup is completed.
-     >- Each log backup is chained to the previous full backup to form a recovery chain. This full backup is retained until the retention of the last log backup has expired. This might mean that the full backup is retained for an extra period to make sure all the logs can be recovered. Let's assume a user has a weekly full backup, daily differential and 2-hour logs. All of them are retained for 30 days. But, the weekly full can be really cleaned up/deleted only after the next full backup is available, that is, after 30 + 7 days. For example, a weekly full backup happens on Nov 16th. According to the retention policy, it should be retained until Dec 16th. The last log backup for this full happens before the next scheduled full, on Nov 22nd. Until this log is available until Dec 22nd, the Nov 16th full can't be deleted. So, the Nov 16th full is retained until Dec 22nd.
+     >- Each log backup is chained to the previous full backup to form a recovery chain. This full backup is retained until the retention of the last log backup has expired. This might mean that the full backup is retained for an extra period to make sure all the logs can be recovered. Let's assume a user has a weekly full backup, daily differential and 2-hour logs. All of them are retained for 30 days. But, the weekly full can be cleaned up/deleted only after the next full backup is available, that is, after 30 + seven days. For example, if a weekly full backup is performed on November 16th, it remains stored until December 16th in accordance with the retention policy. The final log backup for this full occurs on November 22nd, before the next scheduled full backup. Since this log backup remains accessible until December 22nd, the November 16th full backup cannot be deleted until that date. As a result, the November 16th full backup is retained until December 22nd.
 
 12. On the **Configure Backup**, select the new policy under **Backup Policy**, and then select **Add**.
 13. Select **Configure backup**.

articles/backup/sap-ase-database-restore.md

@@ -164,14 +164,14 @@ Before you do Cross Subscription Restore (CSR), ensure that the Recovery Service
 
 To trigger Cross Subscription Restore to a private endpoint enabled vault, follow these steps:
 
-1. In the [Azure portal](https://portal.azure.com/), go to the source **Recovery Services vault** , and then [create Private Endpoints](private-endpoints.md#create-private-endpoints-for-azure-backup).
+1. In the [Azure portal](https://portal.azure.com/), go to the source **Recovery Services vault** , and then [create private endpoints](private-endpoints.md#create-private-endpoints-for-azure-backup).
 
    During private endpoint creation, ensure that you enter the following details:
 
    - Select the subscription of the target vault in which you want to restore.
    - Select the VNet of the target VM that you want to restore across subscription.
 
-1. After the Private Endpoint is created, [trigger restore](#restore-a-user-database).
+1. After the private endpoint is created, [trigger restore](#restore-a-user-database).
 
 >[!Note]
 >By default, CSR is enabled on the Recovery Services vault. To update the Recovery Services vault restore settings, go to the **Recovery Services vault** > **Properties** > **Cross Subscription Restore** and then select **Update** to implement the required changes.

articles/business-continuity-center/index.yml

@@ -65,6 +65,14 @@ landingContent:
           - text: Manage BCDR estate (preview)
             url: tutorial-manage-data-using-copilot.md
 
+  # Card (optional)
+  - title: Supported workloads
+    linkLists:
+      - linkListType: tutorial
+        links:
+          - text: Back up SAP ASE database
+            url: ../backup/sap-ase-database-about.md
+  
   # Card (optional)
   - title: Architecture
     linkLists: