Final fixes

Author: normesta

articles/storage/blobs/archive-blob.md

@@ -7,7 +7,7 @@ author: normesta
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 07/21/2022
+ms.date: 08/24/2022
 ms.author: normesta
 ms.reviewer: fryu
 ms.subservice: blobs
@@ -320,6 +320,8 @@ To create a lifecycle management policy to archive blobs in the Azure portal, fo
 
 10. If you chose to limit the blobs affected by the rule with filters, you can specify a filter, either with a blob prefix or blob index match.
 
+    If you selected the **Last modified** rule condition, you can optionally exclude rehydrated blobs from being impacted by this rule. See the next step. Otherwise select the **Add** button to add the rule to the policy.
+
 #### Step 3: Ensure that the rule excludes rehydrated blobs
 
 If you rehydrate a blob by changing it's tier, this rule will move the blob back to the archive tier if the last modified time, creation time, or last access time is beyond the threshold set for the policy. 
@@ -329,6 +331,9 @@ To prevent this from happening, select **Skip blobs that have been rehydrated in
 > [!div class="mx-imgBorder"]
 > ![Screenshot showing the skip blobs that have been rehydrated in the last setting](./media/archive-blob/lifecycle-policy-base-blobs-tab-portal-exclude-rehydrated-blobs.png)
 
+> [!NOTE]
+> This option appears only if you selected the **Last modified** rule condition.
+
 Select the **Add** button to add the rule to the policy.
 
 

articles/storage/blobs/archive-rehydrate-overview.md

@@ -5,7 +5,7 @@ services: storage
 author: normesta
 
 ms.author: normesta
-ms.date: 07/26/2022
+ms.date: 08/24/2022
 ms.service: storage
 ms.subservice: blobs
 ms.topic: conceptual

articles/storage/blobs/archive-rehydrate-to-online-tier.md

@@ -7,7 +7,7 @@ author: normesta
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 07/26/2022
+ms.date: 08/24/2022
 ms.author: normesta
 ms.reviewer: fryu
 ms.custom: devx-track-azurepowershell

articles/storage/blobs/lifecycle-management-overview.md

@@ -5,7 +5,7 @@ description: Use Azure Storage lifecycle management policies to create automated
 author: normesta
 
 ms.author: normesta
-ms.date: 05/09/2022
+ms.date: 08/24/2022
 ms.service: storage
 ms.subservice: common
 ms.topic: conceptual
@@ -395,7 +395,7 @@ The updated policy takes up to 24 hours to go into effect. Once the policy is in
 
 If there's a lifecycle management policy in effect for the storage account, then rehydrating a blob by changing it's tier can result in a scenario where the lifecycle policy moves the blob back to the archive tier. This can happen if the last modified time, creation time, or last access time is beyond the threshold set for the policy. There's three ways to prevent this from happening:
 
-- Add the `daysAfterLastTierChangeGreaterThan` condition to the tierToArchive action of the policy. See [Use lifecycle management policies to archive blobs](archive-blob.md#use-lifecycle-management-policies-to-archive-blobs).
+- Add the `daysAfterLastTierChangeGreaterThan` condition to the tierToArchive action of the policy. This condition applies only to the last modified time. See [Use lifecycle management policies to archive blobs](archive-blob.md#use-lifecycle-management-policies-to-archive-blobs).
 
 - Disable the rule that affects this blob temporarily to prevent it from being archived again. Re-enable the rule when the blob can be safely moved back to archive tier.