acrolinx

Author: b-ahibbard

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

@@ -84,4 +84,4 @@ If you haven’t done so, assign a backup vault to the volume before creating ma
 * [Restore a backup to a new volume](backup-restore-new-volume.md)
 * [Delete backups of a volume](backup-delete.md)
 * [Volume backup metrics](azure-netapp-files-metrics.md#volume-backup-metrics)
-* [Azure NetApp Files backup FAQs](faq-backup.md)
+* [Azure NetApp Files backup FAQs](faq-bachkup.md)

articles/azure-netapp-files/dynamic-change-volume-service-level.md

@@ -1,26 +1,26 @@
 ---
-title: Dynamically change the service level of a volume for Azure NetApp Files  | Microsoft Docs
-description: Describes how to dynamically change the service level of a volume.
+title: Dynamically change the service level of an Azure NetApp Files volume
+description: Learn about the benefits of changing the service level of an Azure NetApp Files volumes within your NetApp account.
 services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
 ms.date: 05/11/2023
 ms.author: anfdocs
 ---
-# Dynamically change the service level of a volume
+# Dynamically change the service level of an Azure NetApp Files volume
 
-You can change the service level of an existing volume by moving the volume to another capacity pool in the same NetApp account that uses the [service level](azure-netapp-files-service-levels.md) you want for the volume. This in-place service-level change for the volume does not require that you migrate data. It also does not affect access to the volume.  
+You can change the service level of an existing volume by moving the volume to another capacity pool in the same NetApp account that uses the [service level](azure-netapp-files-service-levels.md) you want for the volume. This in-place service-level change for the volume doesn't require that you migrate data. It also doesn't affect access to the volume. 
 
-This functionality enables you to meet your workload needs on demand.  You can change an existing volume to use a higher service level for better performance, or to use a lower service level for cost optimization. For example, if the volume is currently in a capacity pool that uses the *Standard* service level and you want the volume to use the *Premium* service level, you can move the volume dynamically to a capacity pool that uses the *Premium* service level.  
+This functionality enables you to meet your workload needs on demand. You can change an existing volume to use a higher service level for better performance, or to use a lower service level for cost optimization. For example, if the volume is currently in a capacity pool that uses the *Standard* service level and you want the volume to use the *Premium* service level, you can move the volume dynamically to a capacity pool that uses the *Premium* service level. 
 
-The capacity pool that you want to move the volume to must already exist. The capacity pool can contain other volumes.  If you want to move the volume to a brand-new capacity pool, you need to [create the capacity pool](azure-netapp-files-set-up-capacity-pool.md) before you move the volume.  
+The capacity pool that you want to move the volume to must already exist. The capacity pool can contain other volumes. If you want to move the volume to a brand-new capacity pool, you need to [create the capacity pool](azure-netapp-files-set-up-capacity-pool.md) before you move the volume. 
 
 ## Considerations
 
-* This functionality is supported within the same NetApp account. You can't move the volume to a capacity pool in a different NetApp Account.
+* Dynamically changing the service level of a volume is supported within the same NetApp account. You can't move the volume to a capacity pool in a different NetApp Account.
 
-* After the volume is moved to another capacity pool, you'll no longer have access to the previous volume activity logs and volume metrics. The volume starts with new activity logs and metrics under the new capacity pool.
+* After the volume is moved to another capacity pool, you no longer have access to the previous volume activity logs and volume metrics. The volume starts with new activity logs and metrics under the new capacity pool.
 
 * If you move a volume to a capacity pool of a higher service level (for example, moving from *Standard* to *Premium* or *Ultra* service level), you must wait at least 24 hours before you can move that volume *again* to a capacity pool of a lower service level (for example, moving from *Ultra* to *Premium* or *Standard*). You can always change to higher service level without wait time.
 
@@ -42,7 +42,6 @@ The capacity pool that you want to move the volume to must already exist. The ca
 
 3.	Select **OK**.
 
-
 ## Next steps  
 
 * [Service levels for Azure NetApp Files](azure-netapp-files-service-levels.md)