edit pass: mysql-flexible-server-backup

Author: ShawnJackson

articles/backup/backup-azure-mysql-flexible-server-about.md

@@ -13,7 +13,7 @@ ms.author: v-abhmallick
 
 [!INCLUDE [Azure Database for MySQL - Flexible Server backup advisory](../../includes/backup-mysql-flexible-server-advisory.md)]
 
-If you have an Azure Database for MySQL flexible server, you can extend the retention of backups beyond the current limit of 35 days with the built-in operational-tier backup capability of Azure Database for MySQL - Flexible Server. Azure Backup and Azure database services together allow you to build an enterprise-class backup solution for Azure Database for MySQL flexible servers that retain backups for *up to 10 years*.
+If you have an Azure Database for MySQL flexible server, you can extend the retention of backups beyond the current limit of 35 days with the built-in operational-tier backup capability of Azure Database for MySQL - Flexible Server. Azure Backup and Azure database services together allow you to build an enterprise-class backup solution for Azure Database for MySQL flexible servers that retains backups for *up to 10 years*.
 
 Extending backup retention from 35 days to 10 years can help your organization meet compliance and regulatory requirements. The backups are copied to an isolated storage environment outside your tenant and subscription to help protect against ransomware attacks. In addition to long-term retention, this feature enhances backup resiliency by protecting the source data from different levels of data loss, such as accidental deletions and ransomware.
 
@@ -33,7 +33,7 @@ After the configuration is complete:
 - Azure Backup invokes the backup based on the policy schedules on the Resource Manager API of Azure Database for MySQL - Flexible Server. It writes data to a secure blob container with a statistical analysis system (SAS) for enhanced security.
 - The backup job runs independently to prevent disruptions during long-running tasks.
 - The life cycles of the retention and recovery point align with the backup policies for effective management.
-- Azure Backup invokes the restore on the Resource Manager API of the Azure Database for MySQL flexible server by using the SAS for asynchronous, nondisruptive recovery.
+- Azure Backup invokes the restore on the Resource Manager API of Azure Database for MySQL - Flexible Server by using the SAS for asynchronous, nondisruptive recovery.
 
 :::image type="content" source="./media/backup-azure-mysql-flexible-server-about/mysql-flexible-server-backup-architecture.png" alt-text="Diagram that shows the backup flow for Azure Database for MySQL - Flexible Server." lightbox="./media/backup-azure-mysql-flexible-server-about/mysql-flexible-server-backup-architecture.png":::
 
@@ -47,16 +47,16 @@ The following table lists permissions that the vault MSI requires for successful
 
 | Operation | Permission |
 | --- | --- |
-| **Backup** | - Azure Database for MySQL - Flexible Server Long-Term Retention Backup role <br><br> - Reader role on the server's resource group. |
-| **Restore** | Storage Blob Data Contributor role on the target storage account. |
+| **Backup** | Azure Database for MySQL - Flexible Server Long-Term Retention Backup role <br><br> Reader role on the server's resource group |
+| **Restore** | Storage Blob Data Contributor role on the target storage account |
 
 ## Pricing
 
 You incur charges for:
 
 - **Protected instance fee**: When you configure a backup for an Azure Database for MySQL flexible server, a protected instance is created. Azure Backup for MySQL - Flexible Server charges a protected instance fee according to the size of the database (in gigabytes) on a per-unit (250-GB) basis.
 
-- **Backup storage fee**: Azure Backup for MySQL flexible servers store backups in the Standard vault tier. Restore points stored in the Standard vault tier are charged a separate backup storage fee according to the total data stored (in gigabytes) and the redundancy type enabled on the Backup vault.
+- **Backup storage fee**: Azure Backup for MySQL flexible servers store backups in the Standard vault tier. Restore points stored in the Standard vault tier are charged a separate backup storage fee according to the total data stored (in gigabytes) and the redundancy type enabled on the Azure Backup vault.
 
 ## Related content
 

articles/backup/backup-azure-mysql-flexible-server-restore.md

@@ -17,7 +17,7 @@ Learn more about the [supported scenarios, considerations, and limitations](back
 
 ## Prerequisites
 
-Backup data is stored in the Backup vault as a blob within the Microsoft tenant. During a restore operation, the backup data is copied from one storage account to another across tenants. Ensure that the target storage account for the restore has the `AllowCrossTenantReplication` property set to `true`.
+Backup data is stored in the Azure Backup vault as a blob within the Microsoft tenant. During a restore operation, the backup data is copied from one storage account to another across tenants. Ensure that the target storage account for the restore has the `AllowCrossTenantReplication` property set to `true`.
 
 ## Restore an Azure Database for MySQL - Flexible Server database
 

articles/backup/backup-azure-mysql-flexible-server-troubleshoot.md

@@ -70,7 +70,7 @@ This article provides recommended actions to troubleshoot issues that you might
 
 **Cause**: The required set of permissions isn't present to perform the restore operation.
 
-**Recommended action**: Assign the [appropriate permissions](backup-azure-mysql-flexible-server-about.md#permissions-for-an-azure-database-for-mysql---flexible-server-backup) and retrigger backup operation.
+**Recommended action**: Assign the [appropriate permissions](backup-azure-mysql-flexible-server-about.md#permissions-for-an-azure-database-for-mysql---flexible-server-backup) and retrigger the backup operation.
 
 ## Related content
 

articles/backup/backup-azure-mysql-flexible-server.md

@@ -23,7 +23,7 @@ Here are important considerations for this preview feature:
 
 - The retention rules are evaluated in a predetermined order of priority. The priority is the highest for the yearly rule, followed by the monthly rule, and then the weekly rule.
 
-  Default retention settings are applied when no other rules qualify. For example, the same recovery point might be the first successful backup taken every week in addition to the first successful backup taken every month. However, because the monthly rule priority is higher than that of the weekly rule, the retention that corresponds to the first successful backup taken every month applies.
+  Default retention settings are applied when no other rules qualify. For example, the same recovery point might be the first successful backup taken every week in addition to the first successful backup taken every month. However, because the priority of the monthly rule is higher than the priority of the weekly rule, the retention that corresponds to the first successful backup taken every month applies.
 
 - By default, the retention rule is set to 3 months if no retention rule is set.
 
@@ -36,7 +36,8 @@ To create a backup policy, follow these steps:
 1. [Create an Azure Backup vault](create-manage-backup-vault.md#create-a-backup-vault).
 
 2. Go to the Azure Backup vault, and then select **+Backup** to open the **Configure backup** pane.
-3. To create a new backup policy, under **Backup policy**, select **Create new**.
+
+3. Under **Backup policy**, select **Create new**.
 
    :::image type="content" source="./media/backup-azure-mysql-flexible-server/create-backup-policy.png" alt-text="Screenshot that shows how to start creating a new backup policy." lightbox="./media/backup-azure-mysql-flexible-server/create-backup-policy.png":::
 
@@ -107,6 +108,7 @@ To trigger an on-demand backup (a backup that's not in the schedule specified in
    :::image type="content" source="./media/backup-azure-mysql-flexible-server/backup-instances.png" alt-text="Screenshot that shows how to run an on-demand backup." lightbox="./media/backup-azure-mysql-flexible-server/backup-instances.png":::
 
 3. On the **MySQL database instance** pane, choose a retention rule from the list.
+
 4. Select **Backup now**.
 
 ## Monitor a backup job