Update lifecycle-management-best-practices.md

Author: vgs-msft

articles/storage/blobs/lifecycle-management-best-practices.md

@@ -12,14 +12,14 @@ ms.custom: references_regions, engagement-fy23
 
 # Lifecycle Management Best Practices
 
-Azure Blob Storage Lifecycle Management (LCM) helps you automate the transition of objects to lower-cost access tiers, or to delete objects at the end of their lifecycle to reduce storage costs. If a policy is active, Lifecycle Management will periodically processes the objects in a storage account that match the filter set  and rules specified in the lifecycle policy. The time required for a policy to complete processing all the objects in a storage account depends on many factors such as the number of objects to be evaluated and operated on, customer workloads on the account, availability of storage resources and more. In some cases, it can take multiple days to complete processing all the objects in the storage account, and a new LCM run does not begin until the ongoing run completes. LCM is constantly optimizing for speed of execution while keeping these factors in mind.
+Azure Blob Storage Lifecycle Management (LCM) helps you automate the transition of objects to lower-cost access tiers, or to delete objects at the end of their lifecycle to reduce storage costs. If a policy is active, Lifecycle Management periodically processes the objects in a storage account that match the filter set  and rules specified in the lifecycle policy. The time required for a policy to complete processing all the objects in a storage account depends on many factors such as the number of objects to be evaluated and operated on, customer workloads on the account, availability of storage resources and more. In some cases, it can take multiple days to complete processing all the objects in the storage account, and a new LCM run does not begin until the ongoing run completes. LCM is constantly optimizing for speed of execution while keeping these factors in mind.
 
 ## Factors Influencing Lifecycle Management Performance
 There are many factors that influence the execution time that Lifecycle Management would take to process the objects in a single storage account. 
 
 Lifecycle policies enable users to create filter sets (prefix or file path) if they want to scope which subset of objects in the storage account should be processed by Lifecycle Management. If no scope is used or broad scopes are defined, then a large number of objects might need to be processed by Lifecycle Management and this might increase the time needed for the policy to complete.  Additionally, if a significant percentage of objects meet the policy conditions, especially the first time LCM is enabled on a storage account or broadly scoped policies with substantial number of objects, could also increase the processing time.  
 
-All requests made to storage account, including requests made by Lifecycle policy runs, accrue to the same limit on requests per second, and as that limit approaches, priority is given to requests made by workloads. The latency of processing objects also increases if the scalability and performance limits of the storage account are reached. This is particularly relevant for operations that need to be performed within specific time frames.  Learn more about [Scalability and performance targets for standard storage accounts](../common/scalability-targets-standard-accounts.md).
+All requests made to storage account, including requests made by Lifecycle policy runs, accrue to the same limit on requests per second, and as that limit approaches, priority is given to requests made by workloads. The latency of processing objects also increases if the scalability and performance limits of the storage account are reached. This is particularly relevant for operations that need to be performed within specific time frames.  Learn more about [Scalability and performance targets for standard storage accounts](../common/scalability-targets-standard-accounts).
 
 Lifecycle Management also prioritizes customer workloads that utilize or impact the storage account. This allows for customer workloads to run with limited to no interruptions however, it can impact the rate of objects processed by Lifecycle Management. In such cases it is possible that the rate of object creation and modification is higher than the rate at which Lifecycle Management can process the storage account.  
 
@@ -36,7 +36,7 @@ In cases where Lifecycle Management is taking a long time to complete a run, it
 
 ### Optimize for Storage and Transactions costs
 
-It may be more cost effective for the small objects to stay in their current tier, than paying transaction costs to move them to cheaper storage tiers. Avoid moving small files to lower tiers, unless required. [Learn more](./access-tiers-best-practices#pack-small-files-before-moving-data-to-cooler-tiers) about choosing the right storage tier.
+It may be more cost effective for the small objects to stay in their current tier, than paying transaction costs to move them to cheaper storage tiers. Avoid moving small files to lower tiers, unless required. [Learn more](./access-tiers-best-practices#pack-small-files-before-moving-data-to-cooler-tiers.md) about choosing the right storage tier.
   > [!TIP] 
 > [Azure Storage Actions](../../storage-actions/overview) supports size-based object targeting, and tiering/deleting operations.