replace image

Author: b-ahibbard

articles/azure-netapp-files/backup-configure-manual.md

@@ -28,7 +28,7 @@ This article shows you how to configure manual backups. For policy-based backup
 
 Every Azure NetApp Files volume must have the backup functionality enabled before any backups (policy-based or manual) can be taken.   
 
-After you enable the backup functionality, you have the option to manually back up a volume. A manual backup takes a point-in-time snapshot of the active file system and backs up   that snapshot to the Azure storage account.
+After you enable the backup functionality, you can choose to manually back up a volume. A manual backup takes a point-in-time snapshot of the active file system and backs up   that snapshot to the Azure storage account.
 
 The following list summarizes manual backup behaviors:  
 
@@ -49,7 +49,7 @@ If you haven’t done so, enable the backup functionality for the volume before
 2. Select **Configure**.
 3. In the Configure Backup page, toggle the **Enabled** setting to **On**.   
     The Vault field is prepopulated. <!-- If you have not migrated to Backup Vault, you will need to do so before proceeding.   -->
-4. Click **OK**.   
+4. Select **OK**.   
 
 ![Screenshot that shows the Enabled setting of Configure Backups window.](../media/azure-netapp-files/backup-configure-enabled.png)
 
@@ -74,9 +74,9 @@ If you haven’t done so, enable the backup functionality for the volume before
 
     2. If you want to use an existing snapshot for the backup, select the **Use Existing Snapshot** option.  When you use this option, ensure that the Name field matches the existing snapshot name that is being used for the backup. 
 
-4. Click **Create**. 
+4. Select **Create**. 
 
-    When you create a manual backup, a snapshot is also created on the volume using the same name you specified for the backup. This snapshot represents the current state of the active file system. It is transferred to Azure storage. When the backup is complete, the manual backup entry will appear in the list of backups for the volume.
+    When you create a manual backup, a snapshot is also created on the volume using the same name you specified for the backup. This snapshot represents the current state of the active file system. It is transferred to Azure storage. Once the backup completes, the manual backup entry appears in the list of backups for the volume.
 
 ![Screenshot that shows the New Backup window.](../media/azure-netapp-files/backup-new.png)
 

articles/azure-netapp-files/backup-configure-policy-based.md

@@ -78,7 +78,7 @@ You need to create a snapshot policy and associate the snapshot policy to the vo
     1. Go to the **Volumes** page, right-click the volume that you want to apply the snapshot policy to, and select **Edit**.   
         ![Screenshot that shows volume edit menu.](../media/azure-netapp-files/backup-volume-edit-menu.png)   
 
-    2. In the Edit window, under **Snapshot policy**, select the policy to apply. Click **OK**.   
+    2. In the Edit window, under **Snapshot policy**, select the policy to apply. Select **OK**.   
         ![Screenshot that shows Edit window with Snapshot Policy pull-down.](../media/azure-netapp-files/backup-volume-edit-snapshot-policy.png)    
 
 ## Configure a backup policy
@@ -110,7 +110,7 @@ To enable a policy-based (scheduled) backup:
 
 ### Example of a valid configuration
 
-The following example configuration shows you how to configure a data protection policy on the volume with 5 latest daily snapshots, 4 latest weekly snapshots, and 3 latest monthly snapshots on the volume. This configuration results in backing up 15 latest daily snapshots, 6 latest weekly snapshots, and 4 latest monthly snapshots.
+The following example configuration shows you how to configure a data protection policy on the volume with five latest daily snapshots, four latest weekly snapshots, and three latest monthly snapshots on the volume. This configuration results in backing up 15 latest daily snapshots, six latest weekly snapshots, and four latest monthly snapshots.
 
 * Snapshot policy:   
     Daily: `Number of Snapshots to Keep = 5`   
@@ -145,9 +145,9 @@ To enable the backup functionality for a volume:
 2. Select **Configure**.
 3. In the Configure Backups page, toggle the **Enabled** setting to **On**.
 4. In the **Snapshot Policy** drop-down menu, assign the snapshot policy to use for the volume. 
-5. In the **Backup Policy** drop-down menu, assign the backup policy to use for the volume. Click **OK**.
+5. In the **Backup Policy** drop-down menu, assign the backup policy to use for the volume. Select **OK**.
 
-    The Vault information is pre-populated.  
+    The Vault information is prepopulated.  
 
     :::image type="content" source="../media/azure-netapp-files/backup-configure-window.png" alt-text="Screenshot that shows Configure Backups window." lightbox="../media/azure-netapp-files/backup-configure-window.png":::
 

articles/azure-netapp-files/backup-introduction.md

@@ -18,7 +18,7 @@ ms.custom: references_regions
 ---
 # Understand Azure NetApp Files backup
 
-Azure NetApp Files backup expands the data protection capabilities of Azure NetApp Files by providing fully managed backup solution for long-term recovery, archive, and compliance. Backups created by the service are stored in Azure storage, independent of volume snapshots that are available for near-term recovery or cloning. Backups taken by the service can be restored to new Azure NetApp Files volumes within the region. Azure NetApp Files backup supports both policy-based (scheduled) backups and manual (on-demand) backups. For additional information, see [How Azure NetApp Files snapshots work](snapshots-introduction.md).
+Azure NetApp Files backup expands the data protection capabilities of Azure NetApp Files by providing fully managed backup solution for long-term recovery, archive, and compliance. Backups created by the service are stored in Azure storage, independent of volume snapshots that are available for near-term recovery or cloning. Backups taken by the service can be restored to new Azure NetApp Files volumes within the region. Azure NetApp Files backup supports both policy-based (scheduled) backups and manual (on-demand) backups. For more information, see [How Azure NetApp Files snapshots work](snapshots-introduction.md).
 
 > [!IMPORTANT]
 > The Azure NetApp Files backup feature is currently in preview. You need to submit a waitlist request for accessing the feature through the **[Azure NetApp Files Backup Public Preview](https://aka.ms/anfbackuppreviewsignup)** page. Wait for an official confirmation email from the Azure NetApp Files team before using the Azure NetApp Files backup feature.
@@ -58,14 +58,14 @@ Backup restore is priced based on the total amount of backup capacity restored d
 As a pricing example, assume the following situations:
 
 * Your source volume is from the Azure NetApp Files Premium service level. It has a volume quota size of 1000 GiB and a volume consumed size of 500 GiB at the beginning of the first day of a month. The volume is in the US South Central region.
-* You’ve configured a daily *snapshot* policy with 5 local snapshots to keep, and a daily *backup* policy to keep 30 backup copies.
+* You’ve configured a daily *snapshot* policy with five local snapshots to keep, and a daily *backup* policy to keep 30 backup copies.
 * For simplicity, assume your source volume has a constant 1% data change every day, but the total volume consumed size does not grow (remains at 500 GiB).
 
 When the backup policy is assigned to the volume, the baseline backup to service-managed Azure storage is initiated. When the backup is complete, the baseline backup of 500 GiB will be added to the backup list of the volume. After the baseline transfer, daily backups only back up changed blocks. Assume 5-GiB daily incremental backups added, the total backup storage consumed would be `500GiB + 30*5GiB = 650GiB`.
 
-You will be billed at the end of month for backup at the rate of $0.05 per month for the total amount of storage consumed by the backup.  That is, 650 GiB with a total monthly backup charge of `650*$0.05=$32.5`. Regular Azure NetApp Files storage capacity applies to local snapshots. See the [Azure NetApp Files Pricing](https://azure.microsoft.com/pricing/details/netapp/) page for more information.
+Billing occurs at the end of month for backup at the rate of $0.05 per month for the total amount of storage consumed by the backup.  That is, 650 GiB with a total monthly backup charge of `650*$0.05=$32.5`. Regular Azure NetApp Files storage capacity applies to local snapshots. See the [Azure NetApp Files Pricing](https://azure.microsoft.com/pricing/details/netapp/) page for more information.
 
-If you choose to restore a backup of, for example, 600 GiB to a new volume, you will be charged at the rate of $0.02 per GiB of backup capacity restores. In this case, it will be `600*$0.02 = $12` for the restore operation. 
+If you choose to restore a backup of, for example, 600 GiB to a new volume, you will be charged at the rate of $0.02 per GiB of backup capacity restores. In this case, billing is calculated as `600*$0.02 = $12` for the restore operation. 
 
 ## Next steps
 

articles/azure-netapp-files/backup-search.md

@@ -21,7 +21,7 @@ You can display backups and search for a particular backup at the volume level o
 
 The names used for snapshots are preserved when the snapshots are backed up. Snapshot names include the prefix `daily`, `weekly`, or `monthly`. They also include the timestamp when the snapshot was created. The first snapshot when the backup feature is enabled is called a *baseline snapshot*, and its name includes the prefix `snapmirror`.
 
-If a volume is deleted, its backups are still retained. The backups will be listed in the associated NetApp accounts, under the Backups section. This list will include all backups within the subscription (across NetApp accounts) in the region. It can be used to restore a backup to a volume in another NetApp account under the same subscription.
+If a volume is deleted, its backups are still retained. The backups are listed in the associated NetApp accounts, under the Backups section. This list includes all backups within the subscription (across NetApp accounts) in the region. It can be used to restore a backup to a volume in another NetApp account under the same subscription.
 
 >[!IMPORTANT]
 >All backups must be migrated to backup vaults. You can search for backups, but you will not be able to perform any operations on a backup until the backup has been migrated to a backup vault. For more information about this procedure, see [Manage a backup vault](backup-vault-manage.md).
@@ -33,7 +33,7 @@ You can display and search backups at the volume level:
 1. Select **Volumes**.
 
 1. If you have migrated to a backup vault, navigate to **Backup Vault**. Select the backup vault.
-    If you have not yet migrated to a backup vaults, navigate to **Backups**.   
+    If you have not yet migrated to a backup vault, navigate to **Backups**.   
     The **Type** column shows whether the backup is generated by a *Scheduled* (policy-based) or a *manual* backup.
 
 3. In the **Search Backups** field, enter the backup name that you want to search for.  
@@ -49,7 +49,7 @@ You can display and search backups that are associated with a subscription under
 1. Select **NetApp account**.
 
 1. If you have migrated to a backup vault, navigate to **Backup Vault**. Select the backup vault.
-    If you have not yet migrated to a backup vaults, navigate to **Backups**.
+    If you have not yet migrated to a backup vault, navigate to **Backups**.
     The **Type** column shows whether the backup is generated by a *Scheduled* (policy-based) or a *manual* backup. 
 
 1. In the **Search Backups** box, enter the backup name that you want to search for.

articles/azure-netapp-files/whats-new.md

@@ -19,6 +19,9 @@ ms.author: anfdocs
 
 Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements.
 
+* [Backup vault](backup-introduction.md#backup-vault)
+<!-- Content pending-->
+
 ## March 2023
 
 * [Disable showmount](disable-showmount.md) (Preview)
@@ -110,9 +113,6 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
 
     [Azure Virtual WAN](../virtual-wan/virtual-wan-about.md) is now supported on Azure NetApp Files with Standard network features. Azure Virtual WAN is a spoke-and-hub architecture, enabling cloud-hosted network hub connectivity between endpoints, creating networking, security, and routing functionalities in one interface. Use cases for Azure Virtual WAN include remote user VPN connectivity (point-to-site), private connectivity (ExpressRoute), intra-cloud connectivity, and VPN ExpressRoute inter-connectivity. 
 
-* [Backup vault](backup-introduction.md#backup-vault)
-<!-- Content pending-->
-
 ## November 2022 
 
 * [Azure NetApp Files datastores for Azure VMware Solution](../azure-vmware/attach-azure-netapp-files-to-azure-vmware-solution-hosts.md) is now generally available (GA) with expanded regional coverage.