Addressed Peer-review inputs

Author: AbhishekMallick01

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

@@ -33,7 +33,7 @@ This article summarizes the scenarios supported and limitations present when you
 | **Compression** | You can enable ASE Native compression via the Backup policy and when you take an on-demand Backup/Backup Now. In Preregistration Script, Compression Level is set to **Level 101** for Optimal results. |  |
 | **Striping Support** | You can increase your  backup throughput by enabling Striping configuration, which needs to be set in **Preregistration script** –  refer parameters **enable-striping** - Set to **true** and **stripesCount** set to 4 by Default and can be adjusted.  | |
 | **Azure CLI/PowerShell** |  | Azure CLI/PowerShell support is currently not available. |
-| **Security Capabilities** | Immutability, Soft Delete, MUA, Private Endpoint, Encryption at rest are supported. | |
+| **Security Capabilities** | Immutability, Soft Delete, MUA, Private Endpoint, and Encryption at rest are supported. | |
 
 >[!NOTE]
 >- Azure Backup doesn’t automatically adjust for daylight saving time changes when backing up an SAP ASE (Sybase) database running in an Azure VM. We recommend you to modify the policy manually as needed.
@@ -65,19 +65,19 @@ Learn more [about SAP ASE (Sybase) Azure Virtual Machine storage and SAP ASE (Sy
 Azure Backup now enables seamless backups for multiple ASE (Sybase) database instances on Azure VMs, utilizing Multi-SID support. This advancement is particularly useful for shared VM environments, such as non-production setups, where multiple users require efficient data protection and recovery. SAP ASE Multi-SID support includes the following configurations:
 | Sap ASE instance | Support |
 | --- |--- |
-| Standalone (SID1)+ Standalone (SID2) | Supported |
+| Standalone (SID1) + Standalone (SID2) | Supported |
 | HA (SID1) + Standalone (SID2) | Supported |
 | HA (SID1) + HA (SID2)| Supported |
 
-***SID1(HXE) and SID2 (HYE) represent two ASE instances running on the same host.**
+***SID1 (HXE) and SID2 (HYE) represent two ASE instances running on the same host.**
 
 The following table lists the required parameters for adding/removing SAP ASE instances:
 
 | Action | Parameter | Description | Example script |
 | --- | --- | --- | --- |
 | Add an instance | `--sid` | SAP ASE database instance that you want to protect. <br><br> By default, the first instance is selected. | `./PreReg.sh  --add --sid HXE` <br><br> Or <br><br> `./PreReg.sh --sid HXE` <br><br> (Default mode is `add` for the script.) <br><br> After you add instances, registration needs to be done on recovery services vault. If a new instance is added later, re-registration is required. |
 |    | `sudo` | Add 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 an instance | `--sid` | SAP ASE database instance that you want to remove protection. <br><br> SID is a mandate parameter for remove. | `./PreReg.sh --remove --sid HXE` |
+| Remove an instance | `--sid` | SAP ASE database instance that you want to remove protection from. <br><br> SID is a mandate parameter for remove. | `./PreReg.sh --remove --sid HXE` |
 |    | `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. |     |
 

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

@@ -92,7 +92,7 @@ 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.
+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.
 

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

@@ -34,7 +34,7 @@ Before you run the preregistration script, ensure that the following prerequisit
 
 The preregistration script is a Python script that you run on the VM where the SAP ASE database is installed. The script performs the following tasks:
 
-1. Creates the necessary group where the **plugin users** is added.
+1. Creates the necessary group where the **plugin users** are added.
 2. Installs and updates required packages such as waagent, Python, curl, unzip, Libicu, and PythonXML.
 3. Verifies the status of waagent, checks `wireserver` and `IMDS connectivity`, and tests **TCP connectivity** to  Microsoft Entra ID.
 4. Confirms if the geographic region is supported.

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

@@ -12,7 +12,7 @@ ms.author: jsuri
 
 # Tutorial: Back up SAP ASE (Sybase) database using Azure Business Continuity Center
 
-This tutorial describes how to back up an SAP Adaptive Server Enterprise (ASE) (Sybase) database that's running on an Azure virtual machine (VM) using [Azure Business Continuity Center](../business-continuity-center/business-continuity-center-overview.md).
+This tutorial describes how to back up an SAP Adaptive Server Enterprise (ASE) (Sybase) database that's running on an Azure Virtual Machine (VM) using [Azure Business Continuity Center](../business-continuity-center/business-continuity-center-overview.md).
 
 >[!Note]
 >- Currently, the SAP ASE is available only in non-US public regions. Learn about the [supported regions](sap-ase-backup-support-matrix.md#scenario-support-for-sap-ase-sybase-databases-on-azure-vms).
@@ -38,7 +38,7 @@ Before you set up the SAP ASE database for backup, review the following prerequi
   >[!Note]
   >Log backups aren't supported for the Master database. For other system databases, log backups can only be supported if the database's log files are stored separately from its data files. By default, system databases are created with both data and log files in the same database device, which prevents log backups. To enable log backups, the database administrator must change the location of the log files to a separate device.
 
-- Use the Azure built-in roles to configure backup- assignment of roles and scope to the resources. The following Contributor role allows you to run the **Configure Protection** operation on the database VM.
+- Use the Azure built-in roles to configure backup- assignment of roles and scope to the resources. The following Contributor role allows you to run the **Configure Protection** operation on the database VM:
 
   | Resource (Access control) | Role | User, group, or service principal |
   | --- | --- | --- |
@@ -58,7 +58,7 @@ To create a custom role for Azure Backup, run the following bash commands:
     isql -U sapsso -P <password> -S <sid> -X
    ```
 
-2. Create a new role.
+2. Create a role.
 
    ```bash
     create role azurebackup_role
@@ -100,7 +100,7 @@ To create a custom role for Azure Backup, run the following bash commands:
     isql -U sapsso -P <password> -S <sid> -X
    ```
 
-9. Create a new user.
+9. Create a user.
 
    ```bash
     sp_addlogin backupuser, <password>
@@ -176,7 +176,7 @@ The following sections detail about the usage of the connectivity options.
 Private endpoints allow you to connect securely from servers in a virtual network to your Recovery Services vault. The private endpoint uses an IP from the Virtual Network (VNET) address space for your vault. The network traffic between your resources in the virtual network and the vault travels over your virtual network and a private link on the Microsoft backbone network. This operation eliminates exposure from the public internet. Learn  more on [private endpoints for Azure Backup](private-endpoints.md).
 
 >[!Note]
->- Private endpoints are supported for Azure Backup and Azure storage. Microsoft Entra ID has support for private end-points. Until they are generally available, Azure backup supports setting up proxy for Microsoft Entra ID so that no outbound connectivity is required for ASE VMs. For more information, see the [proxy support section](backup-azure-sap-hana-database.md#use-an-http-proxy-server-to-route-traffic).
+>- Private endpoints are supported for Azure Backup and Azure storage. Microsoft Entra ID has support for private endpoints. Until they are generally available, Azure backup supports setting up proxy for Microsoft Entra ID so that no outbound connectivity is required for ASE VMs. For more information, see the [proxy support section](backup-azure-sap-hana-database.md#use-an-http-proxy-server-to-route-traffic).
 >- The download operation for SAP ASE Pre-registration script (ASE workload scripts) requires Internet access. However, on VMs with Private Endpoint (PE) enabled, the pre-registration script can't download these workload scripts directly. So, it’s necessary to download the script on a local VM or another VM with internet access, and then use SCP or any other transfer method to move it to the PE enabled VM.
 
 ### Network Security Group tags
@@ -191,7 +191,7 @@ To create a rule for the Azure Backup tag, follow these steps:
 4. Enter all the required details for [creating a new rule](/azure/virtual-network/manage-network-security-group#security-rule-settings). Ensure the **Destination** is set to **Service Tag** and **Destination service tag** is set to `AzureBackup`.
 5.	Select **Add** to save the newly created outbound security rule.
 
-You can similarly create NSG outbound security rules for Azure Storage and Microsoft Entra ID. Learn more [about service tags](/azure/virtual-network/service-tags-overview).
+You can similarly create NSG outbound security rules for Azure Storage and Microsoft Entra ID. Learn more about [service tags](/azure/virtual-network/service-tags-overview).
 
 ### Azure Firewall tags
 
@@ -346,7 +346,7 @@ To configure the backup operation for the SAP ASE database, follow these steps:
 
 1. On the **Retention Range**, define the retention range for the full backup.
    >[!Note]
-   >- By default all options are selected. Clear any retention range limits you don't want to use, and set those that you want.
+   >- By default, all options are selected. Clear any retention range limits you don't want to use, and set those that you want.
    >- The minimum retention period for any type of backup (full/differential/log) is seven days.
    >- Recovery points are tagged for retention based on their retention range. For example, if you select a daily full backup, only one full backup is triggered each day.
    >- The backup for a specific day is tagged and retained based on the weekly retention range and setting.
@@ -368,7 +368,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 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.
 
 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

@@ -12,7 +12,7 @@ ms.author: jsuri
 
 # Back up SAP ASE (Sybase) database on Azure VMs via Azure Backup
 
-This article describes how to configure backup for SAP Adaptive Server Enterprise (ASE) (Sybase) databases that are running on Azure virtual machines (VMs) on the Azure portal.
+This article describes how to configure backup for SAP Adaptive Server Enterprise (ASE) (Sybase) databases that are running on Azure Virtual Machines (VMs) on the Azure portal.
 
 >[!Note]
 >- Currently, the SAP ASE is available only in non-US public regions. Learn about the [supported regions](sap-ase-backup-support-matrix.md#scenario-support-for-sap-ase-sybase-databases-on-azure-vms).
@@ -38,7 +38,7 @@ Before you set up the SAP ASE database for backup, review the following prerequi
   >[!Note]
   >Log backups aren't supported for the Master database. For other system databases, log backups can only be supported if the database's log files are stored separately from its data files. By default, system databases are created with both data and log files in the same database device, which prevents log backups. To enable log backups, the database administrator must change the location of the log files to a separate device.
 
-- Use the Azure built-in roles to configure backup- assignment of roles and scope to the resources. The following Contributor role allows you to run the **Configure Protection** operation on the database VM.
+- Use the Azure built-in roles to configure backup- assignment of roles and scope to the resources. The following Contributor role allows you to run the **Configure Protection** operation on the database VM:
 
   | Resource (Access control) | Role | User, group, or service principal |
   | --- | --- | --- |
@@ -70,7 +70,7 @@ To discover the SAP ASE databases, follow these steps:
    >- 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.
  
-4. On the **Select Virtual Machines** pane, download the pre-post script that provides permissions for the Azure Backup service to access the SAP ASE VMs for database discovery.
+4. 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.
 5. Run the script on each VM hosting SAP ASE databases that you want to back up.
 6. After you run the script on the VMs, on the **Select Virtual Machines** pane, select the *VMs*, and then select **Discover DBs**.
 
@@ -121,7 +121,7 @@ To configure the backup operation for the SAP ASE database, follow these steps:
 
 5. On the **Retention Range**, define the retention range for the full backup.
    >[!Note]
-   >- By default all options are selected. Clear any retention range limits you don't want to use, and set those that you want.
+   >- By default, all options are selected. Clear any retention range limits you don't want to use, and set those that you want.
    >- The minimum retention period for any type of backup (full/differential/log) is seven days.
    >- Recovery points are tagged for retention based on their retention range. For example, if you select a daily full backup, only one full backup is triggered each day.
    >- The backup for a specific day is tagged and retained based on the weekly retention range and setting.
@@ -144,7 +144,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 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.
 
 12. On the **Configure Backup**, select the new policy under **Backup Policy**, and then select **Add**.
 13. Select **Configure backup**.
@@ -161,7 +161,7 @@ To configure the backup operation for the SAP ASE database, follow these steps:
 
 After the backup configuration is complete, Azure Backup takes backup of the SAP ASE database as per the backup schedule set in the backup policy. You can also [run an on-demand backup](sap-ase-database-backup-tutorial.md#run-an-on-demand-backup-for-sap-ase-database) to create the first full backup.
 
-## Next step
+## Next steps
 
 - [Restore the SAP ASE database on Azure VMs](sap-ase-database-restore.md).
 - [Manage the SAP ASE database on Azure VMs](sap-ase-database-manage.md).