From a1560b69d4fe4a7b4a19cffc8b34f4b08b88730f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?=
 <istvan.szabo@elastic.co>
Date: Tue, 16 Feb 2021 16:33:33 +0100
Subject: [PATCH 1/3] [DOCS] Adds machine learning to the security section of
 alerting.

---
 docs/user/alerting/alerting-getting-started.asciidoc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/user/alerting/alerting-getting-started.asciidoc b/docs/user/alerting/alerting-getting-started.asciidoc
index 06370c64aedf8..0b0cccf1b5ccf 100644
--- a/docs/user/alerting/alerting-getting-started.asciidoc
+++ b/docs/user/alerting/alerting-getting-started.asciidoc
@@ -172,6 +172,7 @@ To access alerting in a space, a user must have access to one of the following f
 * Alerting
 * <<xpack-apm,*APM*>>
 * <<logs-app,*Logs*>>
+* <<xpack-ml, *{ml-cap}*>>
 * <<metrics-app,*Metrics*>>
 * <<xpack-siem,*Security*>>
 * <<uptime-app,*Uptime*>>

From 7a65978b016994a3510fc1105072f28770635348 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?=
 <szabosteve@gmail.com>
Date: Tue, 16 Feb 2021 16:37:56 +0100
Subject: [PATCH 2/3] Apply suggestions from code review

---
 docs/user/alerting/alerting-getting-started.asciidoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/user/alerting/alerting-getting-started.asciidoc b/docs/user/alerting/alerting-getting-started.asciidoc
index 0b0cccf1b5ccf..6186fce8a51c4 100644
--- a/docs/user/alerting/alerting-getting-started.asciidoc
+++ b/docs/user/alerting/alerting-getting-started.asciidoc
@@ -172,7 +172,7 @@ To access alerting in a space, a user must have access to one of the following f
 * Alerting
 * <<xpack-apm,*APM*>>
 * <<logs-app,*Logs*>>
-* <<xpack-ml, *{ml-cap}*>>
+* <<xpack-ml,*{ml-cap}*>>
 * <<metrics-app,*Metrics*>>
 * <<xpack-siem,*Security*>>
 * <<uptime-app,*Uptime*>>
@@ -203,4 +203,4 @@ If an alert requires certain privileges to run such as index privileges, keep in
 
 For security reasons you may wish to limit the extent to which {kib} can connect to external services. <<action-settings>> allows you to disable certain <<action-types>> and whitelist the hostnames that {kib} can connect with. 
 
---
\ No newline at end of file
+--

From 708a4453632d1fabf2d47b48b1782d456c473dd2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Istv=C3=A1n=20Zolt=C3=A1n=20Szab=C3=B3?=
 <istvan.szabo@elastic.co>
Date: Tue, 16 Feb 2021 17:52:55 +0100
Subject: [PATCH 3/3] [DOCS] Adds ML link to alert type page.

---
 docs/user/alerting/alert-types.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/user/alerting/alert-types.asciidoc b/docs/user/alerting/alert-types.asciidoc
index 016ecc3167298..0877f067eee21 100644
--- a/docs/user/alerting/alert-types.asciidoc
+++ b/docs/user/alerting/alert-types.asciidoc
@@ -2,7 +2,7 @@
 [[alert-types]]
 == Standard stack alert types
 
-{kib} supplies alert types in two ways: some are built into {kib} (these are known as stack alerts), while domain-specific alert types are registered by {kib} apps such as <<xpack-apm,*APM*>>, <<metrics-app,*Metrics*>>, and <<uptime-app,*Uptime*>>.
+{kib} supplies alert types in two ways: some are built into {kib} (these are known as stack alerts), while domain-specific alert types are registered by {kib} apps such as <<xpack-apm,*APM*>>, <<xpack-ml,*{ml-cap}*>>, <<metrics-app,*Metrics*>>, and <<uptime-app,*Uptime*>>.
 
 This section covers stack alerts. For domain-specific alert types, refer to the documentation for that app.
 Users will need `all` access to the *Stack Alerts* feature to be able to create and edit any of the alerts listed below.