lowercase

Author: nastasha-solomon

solutions/security/detect-and-alert.md

@@ -53,7 +53,7 @@ Cold data tiers store time series data that is accessed infrequently and rarely
 ### Best practices [best-practices-data-tiers]
 
 * **Retention in hot tier**: We recommend keeping data in the hot tier for at least 24 hours. {{ilm-cap}} policies that roll over data more frequently than once every 24 hours can increase the volume of frozen data queried by rules, leading to performance issues.
-* **Replicas for Mission-Critical Data**: Your data should have replicas if it must be constantly available. Since frozen tiers don't support replicas, shard unavailability can cause partial rule run failures. Shard unavailability may be also encountered during or after {stack} upgrades. If this happens, you can [manually run](/solutions/security/detect-and-alert/manage-detection-rules.md#manually-run-rules) the rule over the affected time period.
+* **Replicas for mission-critical data**: Your data should have replicas if it must be constantly available. Since frozen tiers don't support replicas, shard unavailability can cause partial rule run failures. Shard unavailability may be also encountered during or after {stack} upgrades. If this happens, you can [manually run](/solutions/security/detect-and-alert/manage-detection-rules.md#manually-run-rules) the rule over the affected time period.
 
 ### Limitations [limitations-data-tiers]