acrolinx

Author: b-ahibbard

articles/azure-netapp-files/azure-netapp-files-understand-storage-hierarchy.md

@@ -20,7 +20,7 @@ ms.author: anfdoc
 Before creating a volume in Azure NetApp Files, you must purchase and set up a pool for provisioned capacity.  To set up a capacity pool, you must have a NetApp account. Understanding the storage hierarchy helps you set up and manage your Azure NetApp Files resources.
 
 > [!IMPORTANT] 
-> Azure NetApp Files currently does not support resource migration between subscriptions.
+> Azure NetApp Files currently doesn't support resource migration between subscriptions.
 
 ## <a name="conceptual_diagram_of_storage_hierarchy"></a>Conceptual diagram of storage hierarchy 
 The following example shows the relationships of the Azure subscription, NetApp accounts, capacity pools,  and volumes.   
@@ -30,7 +30,7 @@ The following example shows the relationships of the Azure subscription, NetApp
 ## <a name="azure_netapp_files_account"></a>NetApp accounts
 
 - A NetApp account serves as an administrative grouping of the constituent capacity pools.  
-- A NetApp account is not the same as your general Azure storage account. 
+- A NetApp account isn't the same as your general Azure storage account. 
 - A NetApp account is regional in scope.   
 - You can have multiple NetApp accounts in a region, but each NetApp account is tied to only a single region.
 
@@ -41,33 +41,33 @@ Understanding how capacity pools work helps you select the right capacity pool t
 ### General rules of capacity pools
 
 - A capacity pool is measured by its provisioned capacity.   
-    See [QoS types](#qos_types) for additional information.  
+    For more information, see [QoS types](#qos_types).
 - The capacity is provisioned by the fixed SKUs that you purchased (for example, a 4-TiB capacity).
 - A capacity pool can have only one service level.  
 - Each capacity pool can belong to only one NetApp account. However, you can have multiple capacity pools within a NetApp account.  
-- A capacity pool cannot be moved across NetApp accounts.   
-  For example, in the [Conceptual diagram of storage hierarchy](#conceptual_diagram_of_storage_hierarchy) below, Capacity Pool 1 cannot be moved from US East NetApp account to US West 2 NetApp account.  
-- A capacity pool cannot be deleted until all volumes within the capacity pool have been deleted.
+- You can't move a capacity pool across NetApp accounts.   
+  For example, in the [Conceptual diagram of storage hierarchy](#conceptual_diagram_of_storage_hierarchy), you can't move Capacity Pool 1 US East NetApp account to US West 2 NetApp account.  
+- You can't delete a capacity pool until you delete all volumes within the capacity pool. 
 
 ### <a name="qos_types"></a>Quality of Service (QoS) types for capacity pools
 
-The QoS type is an attribute of a capacity pool. Azure NetApp Files provides two QoS types of capacity pools -- *auto (default)* and *manual*. 
+The QoS type is an attribute of a capacity pool. Azure NetApp Files provides two QoS types of capacity pools--*auto (default)* and *manual*. 
 
 #### *Automatic (or auto)* QoS type  
 
 When you create a capacity pool, the default QoS type is auto.
 
 In an auto QoS capacity pool, throughput is assigned automatically to the volumes in the pool, proportional to the size quota assigned to the volumes. 
 
-The maximum throughput allocated to a volume depends on the service level of the capacity pool and the size quota of the volume. See [Service levels for Azure NetApp Files](azure-netapp-files-service-levels.md) for example calculation.
+The maximum throughput allocated to a volume depends on the service level of the capacity pool and the size quota of the volume. See [Service levels for Azure NetApp Files](azure-netapp-files-service-levels.md) for an example calculation.
 
 For performance considerations about QoS types, see [Performance considerations for Azure NetApp Files](azure-netapp-files-performance-considerations.md).
 
 #### *Manual* QoS type  
 
-When you [create a capacity pool](azure-netapp-files-set-up-capacity-pool.md), you can specify for the capacity pool to use the manual QoS type. You can also [change an existing capacity pool](manage-manual-qos-capacity-pool.md#change-to-qos) to use the manual QoS type. *Setting the capacity type to manual QoS is a permanent change.* You cannot convert a manual QoS type capacity tool to an auto QoS capacity pool. 
+When you [create a capacity pool](azure-netapp-files-set-up-capacity-pool.md), you can specify for the capacity pool to use the manual QoS type. You can also [change an existing capacity pool](manage-manual-qos-capacity-pool.md#change-to-qos) to use the manual QoS type. *Setting the capacity type to manual QoS is a permanent change.* You can't convert a manual QoS type capacity tool to an auto QoS capacity pool. 
 
-In a manual QoS capacity pool, you can assign the capacity and throughput for a volume independently. For minimum and maximum throughput levels, see [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md#resource-limits). The total throughput of all volumes created with a manual QoS capacity pool is limited by the total throughput of the pool.  It is determined by the combination of the pool size and the service-level throughput.  For instance, a 4-TiB capacity pool with the Ultra service level has a total throughput capacity of 512 MiB/s (4 TiB x 128 MiB/s/TiB) available for the volumes.
+In a manual QoS capacity pool, you can assign the capacity and throughput for a volume independently. For minimum and maximum throughput levels, see [Resource limits for Azure NetApp Files](azure-netapp-files-resource-limits.md#resource-limits). The total throughput of all volumes created with a manual QoS capacity pool is limited by the total throughput of the pool. It's determined by the combination of the pool size and the service-level throughput.  For instance, a 4-TiB capacity pool with the Ultra service level has a total throughput capacity of 512 MiB/s (4 TiB x 128 MiB/s/TiB) available for the volumes.
 
 ##### Example of using manual QoS
 

articles/azure-netapp-files/includes/2-tib-capacity-pool.md

@@ -13,4 +13,5 @@ ms.custom: include file
 # azure-netapp-files-resize-capacity-pools-or-volumes.md
 ---
 
-2 TiB capacity pool sizing is currently in preview. The 2-TiB minimum is only supported with Standard network features. With Basic network features, the minimum size is 4 TiB.
+2-TiB capacity pool sizing is currently in preview. You can only take advantage of the 2-TiB minimum if you are using Standard network features. With Basic network features, the minimum size is 4 TiB.
+

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

@@ -12,14 +12,14 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: overview
-ms.date: 01/25/2023
+ms.date: 02/21/2023
 ms.author: anfdocs
 ---
 # What's new in Azure NetApp Files
 
 Azure NetApp Files is updated regularly. This article provides a summary about the latest new features and enhancements. 
 
-## January 2023
+## February 2023
 
 * [Capacity pool enhancement](azure-netapp-files-set-up-capacity-pool.md) (Preview)