Merge pull request #270519 from b-ahibbard/cool-access-change

cool access snapshots

Author: prmerger-automator[bot]

articles/azure-netapp-files/cool-access-introduction.md

@@ -12,7 +12,7 @@ ms.custom: references_regions
 
 # Standard storage with cool access in Azure NetApp Files 
 
-Using Azure NetApp Files standard storage with cool access, you can configure inactive data to move from Azure NetApp Files Standard service-level storage (the *hot tier*) to an Azure storage account (the *cool tier*). In doing so, data blocks that haven't been accessed for some time will be kept and stored in the cool tier, resulting in cost savings.
+Using Azure NetApp Files standard storage with cool access, you can configure inactive data to move from Azure NetApp Files Standard service-level storage (the *hot tier*) to an Azure storage account (the *cool tier*). Enabling cool access moves inactive data blocks from the volume and the volume's snapshots snapshots to the cool tier, resulting in cost savings.
 
 Most cold data is associated with unstructured data. It can account for more than 50% of the total storage capacity in many storage environments. Infrequently accessed data associated with productivity software, completed projects, and old datasets are an inefficient use of a high-performance storage. 
 

articles/azure-netapp-files/includes/large-volumes-notice.md

@@ -1,6 +1,4 @@
 ---
-title: include file
-description: include file
 author: b-ahibbard
 ms.service: azure-netapp-files
 ms.topic: include
@@ -16,4 +14,4 @@ ms.custom: include file
 >[!IMPORTANT]
 > Large volumes are currently in preview. If this is your first time using large volumes, you must first [register the feature](../azure-netapp-files-understand-storage-hierarchy.md#large-volumes) and request [an increase in regional capacity quota](../azure-netapp-files-resource-limits.md#request-limit-increase).
 >
->Volumes are considered large if they are between 50 TiB and 500 TiB in size. Regular volumes cannot be converted to large volumes. Large volumes cannot be resized to less than 50 TiB. To understand the requirements and considerations of large volumes, refer to for using [Requirements and considerations for large volumes](../large-volumes-requirements-considerations.md).
+>Volumes are considered large if they are between 50 TiB and 500 TiB in size. Regular volumes cannot be converted to large volumes. Large volumes cannot be resized to less than 50 TiB. To understand the requirements and considerations of large volumes, refer to for using [Requirements and considerations for large volumes](../large-volumes-requirements-considerations.md). For other limits, see [Resource limits](../azure-netapp-files-resource-limits.md#resource-limits).

articles/azure-netapp-files/manage-cool-access.md

@@ -13,7 +13,7 @@ ms.author: anfdocs
 
 Using Azure NetApp Files [standard storage with cool access](cool-access-introduction.md), you can configure inactive data to move from Azure NetApp Files Standard service-level storage (the *hot tier*) to an Azure storage account (the *cool tier*). In doing so, you reduce the total cost of ownership of your data stored in Azure NetApp Files.
 
-The standard storage with cool access feature allows you to configure a Standard capacity pool with cool access. The Standard storage service level with cool access feature moves cold (infrequently accessed) data to the Azure storage account to help you reduce the cost of storage. Throughput requirements remain the same for the Standard service level enabled with cool access. However, there can be a difference in data access latency because the data needs to be read from the Azure storage account.
+The standard storage with cool access feature allows you to configure a Standard capacity pool with cool access. The Standard storage service level with cool access feature moves cold (infrequently accessed) data from the volume and the volume's snapshots to the Azure storage account to help you reduce the cost of storage. Throughput requirements remain the same for the Standard service level enabled with cool access. However, there can be a difference in data access latency because the data needs to be read from the Azure storage account.
 
 The standard storage with cool access feature provides options for the “coolness period” to optimize the network transfer cost, based on your workload and read/write patterns. This feature is provided at the volume level. See the [Set options for coolness period section](#modify_cool) for details. The standard storage with cool access feature also provides metrics on a per-volume basis. See the [Metrics section](cool-access-introduction.md#metrics) for details.