Formatting errors

Author: mhopkins-msft

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

@@ -10,6 +10,7 @@ ms.subservice: common
 ms.topic: conceptual
 ms.reviewer: yzheng 
 ms.custom: devx-track-azurepowershell
+ms.custom: references_regions
 ---
 
 # Manage the Azure Blob storage lifecycle
@@ -545,13 +546,13 @@ For data that is modified and accessed regularly throughout its lifetime, snapsh
 
 ## FAQ
 
-**I created a new policy, why do the actions not run immediately?*.
+**I created a new policy, why do the actions not run immediately?**
 The platform runs the lifecycle policy once a day. Once you configure a policy, it can take up to 24 hours for some actions to run for the first time.
 
-**If I update an existing policy, how long does it take for the actions to run?*.
+**If I update an existing policy, how long does it take for the actions to run?**
 The updated policy takes up to 24 hours to go into effect. Once the policy is in effect, it could take up to 24 hours for the actions to run. Therefore, the policy actions may take up to 48 hours to complete.
 
-**I manually rehydrated an archived blob, how do I prevent it from being moved back to the Archive tier temporarily?*.
+**I manually rehydrated an archived blob, how do I prevent it from being moved back to the Archive tier temporarily?**
 When a blob is moved from one access tier to another, its last modification time doesn't change. If you manually rehydrate an archived blob to hot tier, it would be moved back to archive tier by the lifecycle management engine. 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. You may also copy the blob to another location if it needs to stay in hot or cool tier permanently.
 
 ## Next steps