acrolinx

Author: b-ahibbard

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

@@ -10,9 +10,9 @@ ms.author: anfdocs
 ---
 # Delete backups of a volume 
 
-You can delete individual backups that you no longer need to keep for a volume. Deleting backups will delete the associated objects in your Azure Storage account, resulting in space saving.  
+You can delete individual backups that you no longer need to keep for a volume. Deleting backups deletes the associated objects in your Azure Storage account, resulting in space saving.  
 
-By design, Azure NetApp Files prevents you from deleting the latest backup. If the latest backup consists of multiple snapshots taken at the same time (for example, the same daily and weekly schedule configuration), they are all considered as the latest snapshot, and deleting those is prevented.
+By design, Azure NetApp Files prevents you from deleting the latest backup. If the latest backup consists of multiple snapshots taken at the same time (for example, the same daily and weekly schedule configuration), they're all considered as the latest snapshot; deleting the snapshots with the same time is prevented.
 
 Deleting the latest backup is permitted only when either of the following conditions are met:
 

articles/azure-netapp-files/backup-manage-policies.md

@@ -10,9 +10,9 @@ ms.author: anfdocs
 ---
 # Manage backup policies for Azure NetApp Files 
 
-After you have set up Azure NetApp Files backups using [a backup policy](backup-configure-policy-based.md), you can modify or suspend a backup policy as needed.  
+After you've configured Azure NetApp Files backups using [a backup policy](backup-configure-policy-based.md), you can modify or suspend a backup policy as needed.  
 
-Manual backups are not affected by changes in the backup policy.
+Manual backups aren't affected by changes in the backup policy.
 
 >[!IMPORTANT]
 >All backups require a backup vault. If you have existing backups, you must migrate backups to a backup vault before you can perform any operation with a backup. For more information about this procedure, see [Manage backup vaults](backup-vault-manage.md).
@@ -29,7 +29,7 @@ To modify the backup policy settings:
 
     :::image type="content" source="./media/backup-manage-policies/backup-policies-edit.png" alt-text="Screenshot that shows context sensitive menu of Backup Policies." lightbox="./media/backup-manage-policies/backup-policies-edit.png":::
 
-3. In the Modify Backup Policy window, update the number of backups you want to keep for daily, weekly, and monthly backups. Enter the backup policy name to confirm the action. Click **Save**.  
+3. In the Modify Backup Policy window, update the number of backups you want to keep for daily, weekly, and monthly backups. Enter the backup policy name to confirm the action. Select **Save**.  
 
     :::image type="content" source="./media/backup-manage-policies/backup-modify-policy.png" alt-text="Screenshot showing the Modify Backup Policy window." lightbox="./media/backup-manage-policies/backup-modify-policy.png":::
 
@@ -38,7 +38,7 @@ To modify the backup policy settings:
 
 ## Suspend a backup policy  
 
-A backup policy can be suspended so that it does not perform any new backup operations against the associated volumes. This action enables you to temporarily suspend backups, in the event that existing backups need to be maintained but not retired because of versioning.   
+A backup policy can be suspended so that it does not perform any new backup operations against the associated volumes. This action enables you to temporarily suspend backups if existing backups need to be maintained but not retired because of versioning.   
 
 ### Suspend a backup policy for all volumes associated with the policy
 
@@ -48,7 +48,7 @@ A backup policy can be suspended so that it does not perform any new backup oper
 
 1. Select the three dots (`…`) to the right of the backup policy you want to modify, then select **Edit**. 
 
-1. Toggle **Policy State** to **Disabled**, enter the policy name to confirm, and click **Save**. 
+1. Toggle **Policy State** to **Disabled**, enter the policy name to confirm, then select **Save**. 
 
 ### Suspend a backup policy for a specific volume 
 
@@ -57,7 +57,7 @@ A backup policy can be suspended so that it does not perform any new backup oper
 3. From the selected volume, select **Backup** then **Configure**.
 4. In the Configure Backups page, toggle **Policy State** to **Suspend**, enter the volume name to confirm, then select **OK**.   
 
-    :::image type="content" source="./media/backup-manage-policies/backup-modify-policy-suspend.png" alt-text="Screenshot that shows the Configure Backups window with the Suspend Policy State.":::
+    :::image type="content" source="./media/backup-manage-policies/backup-modify-policy-suspend.png" alt-text="Screenshot of a backup with a suspended policy.":::
 
 ## Next steps  
 

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

@@ -13,15 +13,15 @@ This article answers frequently asked questions (FAQs) about using the [Azure Ne
 
 ## When do my backups occur?   
 
-Azure NetApp Files backups start within a randomized time frame after the frequency of a backup policy is entered. For example, weekly backups are initiated Sunday within a randomly assigned interval after 12:00 a.m. midnight. This timing cannot be modified by the users at this time. The baseline backup is initiated as soon as you assign the backup policy to the volume.
+Azure NetApp Files backups start within a randomized time frame after the frequency of a backup policy is entered. For example, weekly backups are initiated Sunday within a randomly assigned interval after 12:00 a.m. midnight. This timing can't be modified by the users at this time. The baseline backup is initiated as soon as you assign the backup policy to the volume.
 
 ## What happens if a backup operation encounters a problem?
 
-If a problem occurs during a backup operation, Azure NetApp Files backup automatically retries the operation, without requiring user interaction. If the retries continue to fail, Azure NetApp Files backup will report the failure of the operation.
+If a problem occurs during a backup operation, Azure NetApp Files backup automatically retries the operation, without requiring user interaction. If the retries continue to fail, Azure NetApp Files backup reports the failure of the operation.
 
 ## Can I change the location or storage tier of my backup vault?
 
-No, Azure NetApp Files automatically manages the backup data location within Azure storage. This location or Azure storage tier cannot be modified by the user.
+No, Azure NetApp Files automatically manages the backup data location within Azure storage. This location or Azure storage tier can't be modified by the user.
 
 ## What types of security are provided for the backup data?
 
@@ -31,7 +31,7 @@ Azure NetApp Files uses AES-256 bit encryption during the encoding of the receiv
 
 When you delete an Azure NetApp Files volume, the backups are retained under the backup vault. If you don’t want to retain the backups, first delete the older backups followed by the most recent backup.
 
-If you wish to delete the backup vault, ensure that all the backups under the backup vault are deleted prior to deleting the backup vault.
+If you wish to delete the backup vault, ensure that all the backups under the backup vault are deleted before deleting the backup vault.
 
 ## What’s the system’s maximum backup retries for a volume?  
 

articles/azure-netapp-files/includes/disable-delete-backup.md

@@ -1,6 +1,4 @@
 ---
-title: include file
-description: include file
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: include

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

@@ -38,7 +38,7 @@ The following diagrams illustrate the concepts:
 
    [ ![The latest changes are captured in Snapshot2 for a second point in time view of the volume (and the files within).](./media/snapshots-introduction/single-file-snapshot-restore-four.png) ](./media/snapshots-introduction/single-file-snapshot-restore-four.png#lightbox)
 
-When a snapshot is taken, the pointers to the data blocks are copied, and modifications are written to new data locations. The snapshot pointers continue to point to the original data blocks that the file occupied when the snapshot was taken, giving you a live and a historical view of the data. If you were to create a new snapshot, the current pointers (that is, the ones created after the most recent additions and modifications) are copied to a new snapshot `Snapshot2`. This creates access to three generations of data (the live data, `Snapshot2`, and `Snapshot1`, in order of age) without taking up the volume space that three full copies would require.
+When a snapshot is taken, the pointers to the data blocks are copied, and modifications are written to new data locations. The snapshot pointers continue to point to the original data blocks that the file occupied when the snapshot was taken, providing both live and historical views of the data. If you were to create a new snapshot, the current pointers (that is, the ones created after the most recent additions and modifications) are copied to a new snapshot `Snapshot2`. This creates access to three generations of data (the live data, `Snapshot2`, and `Snapshot1`, in order of age) without taking up the volume space that three full copies would require.
 
 A snapshot takes only a copy of the volume metadata (*inode table*). It takes just a few seconds to create, regardless of the volume size, the capacity used, or the level of activity on the volume. As such, taking a snapshot of a 100-TiB volume takes the same (next to zero) amount of time as taking a snapshot of a 100-GiB volume. After a snapshot is created, changes to data files are reflected in the active version of the files, as normal.