formatting

Author: b-ahibbard

articles/azure-netapp-files/includes/cool-access-options.md

@@ -9,19 +9,24 @@ ms.custom: include file
 # manage-cool-access.md // 2 workflows
 ---
 
-* **Enable Cool Access**: The coolness period defines the minimum number of days before data is transitioned to the cold tier. The default value is 31 days. The supported values are between 2 and 183 days.
+* **Enable Cool Access**:
+
+    The coolness period defines the minimum number of days before data is transitioned to the cold tier. The default value is 31 days. The supported values are between 2 and 183 days.
 
     >[!NOTE]
-    > The coolness period is calculated from the time of volume creation. If any existing volumes are enabled with cool access, the coolness period is applied retroactively on those volumes. This means if certain data blocks on the volumes have been infrequently accessed for the number of days specified in the coolness period, those blocks move to the cool tier once the feature is enabled. Once the coolness period is reached, background jobs can take up to 48 hours to initiate the data transfer to the cool tier.
-* **Cool Access Retrieval Policy**: This option specifies under which conditions data moves back to the hot tier. You can set this option to **Default**, **On-Read**, or **Never**.
+    > The coolness period is calculated from the time of volume creation. If any existing volumes are enabled with cool access, the coolness period is applied retroactively on those volumes. If certain data blocks on the volumes have not been accessed for the number of days specified in the coolness period, those blocks move to the cool tier once the feature is enabled. Once the coolness period is reached, background jobs can take up to 48 hours to initiate the data transfer to the cool tier.
+
+* **Cool Access Retrieval Policy**:
+
+    This option specifies under which conditions data moves back to the hot tier. You can set this option to **Default**, **On-Read**, or **Never**.
 
     If you don't set a value for the cool access retrieval policy, the retrieval policy is set to Default. The following table describes each policy's data retrieval behavior:
 
     | Setting | Behavior |
     | - | ---- | 
     | Default | Cold data is returned to the hot tier when performing random reads. Data is served from the cool tier with sequential reads. | 
     | On-read | On both sequential and random reads, cold data  is returned to the hot tier. |
-    | Never | Cold data is served directly from the cool tier. After it is moved to the cool tier, it's never retrieved to the hot tier. |
+    | Never | Cold data is served directly from the cool tier. After data moves to the cool tier, it's not returned to the hot tier. |
 
 * **Cool Access Tiering policy**     
 

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

@@ -163,7 +163,7 @@ You can enable Azure NetApp Files storage with cool access during the creation o
 
     :::image type="content" source="./media/manage-cool-access/cool-access-new-volume.png" alt-text="Screenshot that shows the Create a volume page. On the Basics tab, the Enable Cool Access checkbox is selected. The options for the cool access retrieval policy are displayed. " lightbox="./media/manage-cool-access/cool-access-new-volume.png"::: 
 
-1. To complete the volume creation, follow the volume creation workflow for the relevant protocol:
+1. To fishing creating the volume, follow the instructions for the relevant protocol:
 
     * [Create an NFS volume](azure-netapp-files-create-volumes.md)
     * [Create an SMB volume](azure-netapp-files-create-volumes-smb.md)
@@ -185,6 +185,8 @@ In a capacity pool enabled for cool access, you can enable an existing volume to
 
     :::image type="content" source="./media/manage-cool-access/cool-access-existing-volume.png" alt-text="Screenshot that shows the Enable Cool Access checkbox selected. " lightbox="./media/manage-cool-access/cool-access-existing-volume.png"::: 
 
+1. Select **OK** to confirm the changes. 
+
 ### <a name="modify_cool"></a>Modify cool access configuration for a volume
 
 Based on the client read/write patterns, you can modify the cool access configuration as needed for a volume.