[E&A] Fixes more links.

Author: szabosteve

explore-analyze/alerts-cases/alerts/alerting-getting-started.md

@@ -112,7 +112,7 @@ This section will clarify some of the important differences in the function and
 Functionally, the {{alert-features}} differ in that:
 
 * Scheduled checks are run on {{kib}} instead of {es}
-* {{kib}} [rules hide the details of detecting conditions](../../../explore-analyze/alerts-cases.md#alerting-concepts-conditions) through rule types, whereas watches provide low-level control over inputs, conditions, and transformations.
+* {{kib}} [rules hide the details of detecting conditions](../../../explore-analyze/alerts-cases/alerts/alerting-getting-started.md#alerting-concepts-conditions) through rule types, whereas watches provide low-level control over inputs, conditions, and transformations.
 * {{kib}} rules track and persist the state of each detected condition through alerts. This makes it possible to mute and throttle individual alerts, and detect changes in state such as resolution.
 * Actions are linked to alerts. Actions are fired for each occurrence of a detected condition, rather than for the entire rule.
 

explore-analyze/alerts-cases/alerts/rule-types.md

@@ -5,7 +5,7 @@ mapped_pages:
 
 # Rule types [rule-types]
 
-A rule is a set of [conditions](../alerts.md#alerting-concepts-conditions), [schedules](../alerts.md#alerting-concepts-scheduling), and [actions](../alerts.md#alerting-concepts-actions) that enable notifications. {{kib}} provides rules built into the {{stack}} and rules registered by one of the {{kib}} apps. You can create most rules types in [{{stack-manage-app}} > {{rules-ui}}](create-manage-rules.md). Security rules must be defined in the Security app. For more information, refer to the documentation about [creating a detection rule](../../../solutions/security/detect-and-alert/create-detection-rule.md).
+A rule is a set of [conditions](../alerts.md#rules-conditions), [schedules](../alerts.md#rules-schedule), and [actions](../alerts.md#rules-actions ) that enable notifications. {{kib}} provides rules built into the {{stack}} and rules registered by one of the {{kib}} apps. You can create most rules types in [{{stack-manage-app}} > {{rules-ui}}](create-manage-rules.md). Security rules must be defined in the Security app. For more information, refer to the documentation about [creating a detection rule](../../../solutions/security/detect-and-alert/create-detection-rule.md).
 
 ::::{note}
 Some rule types are subscription features, while others are free features. For a comparison of the Elastic subscription levels, see [the subscription page](https://www.elastic.co/subscriptions).

explore-analyze/machine-learning/anomaly-detection/ml-configuring-alerts.md

@@ -5,7 +5,7 @@ mapped_pages:
 
 # Generating alerts for anomaly detection jobs [ml-configuring-alerts]
 
-{{kib}} {{alert-features}} include support for {{ml}} rules, which run scheduled checks for anomalies in one or more {{anomaly-jobs}} or check the health of the job with certain conditions. If the conditions of the rule are met, an alert is created and the associated action is triggered. For example, you can create a rule to check an {{anomaly-job}} every fifteen minutes for critical anomalies and to notify you in an email. To learn more about {{kib}} {{alert-features}}, refer to [Alerting](../../alerts-cases/alerts.md#alerting-getting-started).
+{{kib}} {{alert-features}} include support for {{ml}} rules, which run scheduled checks for anomalies in one or more {{anomaly-jobs}} or check the health of the job with certain conditions. If the conditions of the rule are met, an alert is created and the associated action is triggered. For example, you can create a rule to check an {{anomaly-job}} every fifteen minutes for critical anomalies and to notify you in an email. To learn more about {{kib}} {{alert-features}}, refer to [Alerting](../../alerts-cases/alerts/alerting-getting-started.md).
 
 The following {{ml}} rules are available:
 

raw-migrated-files/docs-content/serverless/detections-logsdb-index-mode-impact.md

@@ -32,7 +32,7 @@ Alerts that are generated by threshold, {{ml}}, and event correlation sequence r
 
 While we do not recommend using `_source` for actions, in cases where the action relies on the `_source`, the same limitations and changes apply.
 
-If you send alert notifications by enabling [actions](../../../explore-analyze/alerts-cases.md#alerting-concepts-actions) to the external systems that have workflows or automations based on fields formatted from the original source, they may be affected. In particular, this can happen when the fields used are arrays of objects.
+If you send alert notifications by enabling [actions](../../../explore-analyze/alerts-cases/alerts.md#rules-actions) to the external systems that have workflows or automations based on fields formatted from the original source, they may be affected. In particular, this can happen when the fields used are arrays of objects.
 
 We recommend checking and adjusting the rule actions using `_source` before switching to logsdb index mode.
 

raw-migrated-files/security-docs/security/detections-logsdb-index-mode-impact.md

@@ -42,7 +42,7 @@ Alerts that are generated by threshold, {{ml}}, and event correlation sequence r
 
 While we do not recommend using `_source` for actions, in cases where the action relies on the `_source`, the same limitations and changes apply.
 
-If you send alert notifications by enabling [actions](../../../explore-analyze/alerts-cases.md#alerting-concepts-actions) to the external systems that have workflows or automations based on fields formatted from the original source, they may be affected. In particular, this can happen when the fields used are arrays of objects.
+If you send alert notifications by enabling [actions](../../../explore-analyze/alerts-cases/alerts.md#rules-actions) to the external systems that have workflows or automations based on fields formatted from the original source, they may be affected. In particular, this can happen when the fields used are arrays of objects.
 
 We recommend checking and adjusting the rule actions using `_source` before switching to logsdb index mode.