diff --git a/docs/management/watcher-ui/index.asciidoc b/docs/management/watcher-ui/index.asciidoc
index e47360fc110a..767f9029907f 100644
--- a/docs/management/watcher-ui/index.asciidoc
+++ b/docs/management/watcher-ui/index.asciidoc
@@ -19,7 +19,7 @@ With this UI, you can:
 [role="screenshot"]
 image:management/watcher-ui/images/watches.png["Watcher list"]
 
-{stack-ov}/xpack-alerting.html[Alerting on cluster and index events]
+{ref}/xpack-alerting.html[Alerting on cluster and index events]
 is a good source for detailed 
 information on how watches work. If you are using the UI to create a 
 threshold watch, take a look at the different watcher actions. If you are 
@@ -110,9 +110,9 @@ image:management/watcher-ui/images/threshold-alert/threshold-alert-condition.png
 
 Now that the condition is set, you must add an action. The action triggers 
 when the watch condition is met. For a complete list of actions and how to configure them, see 
-{stack-ov}/action-conditions.html[Adding conditions to actions].
+{ref}/action-conditions.html[Adding conditions to actions].
 
-In this example, you’ll configure an email action. You must have an {stack-ov}/actions-email.html#configuring-email[email account configured]
+In this example, you’ll configure an email action. You must have an {ref}/actions-email.html#configuring-email[email account configured]
 in {es} for this example to work. 
 
 . Click *Add action* and select *Email*.
@@ -178,7 +178,7 @@ image:management/watcher-ui/images/execution-history.png["Execution history tab"
 The *Action statuses* tab lists all actions associated with the watch and 
 the state of each action. If the action is firing, you can acknowledge the 
 watch to prevent too many executions of the same action for the same watch. 
-See {stack-ov}/actions.html#actions-ack-throttle[Acknowledgement and Throttling] for details. 
+See {ref}/actions.html#actions-ack-throttle[Acknowledgement and throttling] for details. 
 
 [role="screenshot"]
 image:management/watcher-ui/images/alerts-status.png["Action status tab"]
@@ -209,7 +209,7 @@ For more information, see {ref}/query-dsl.html[Query DSL].
 On the Watch overview page, click *Create* and choose *Create advanced watch*.  
 An advanced watch requires a name and ID.  Name is a user-friendly way to 
 identify the watch, and ID refers to the identifier used by {es}.  Refer to 
-{stack-ov}/how-watcher-works.html#watch-definition[Watch definition] for how 
+{ref}/how-watcher-works.html#watch-definition[Watch definition] for how 
 to input the watch JSON.  
 
 [role="screenshot"]
@@ -227,7 +227,7 @@ simulation. Be aware of these implementation details on overrides:
 * Action overrides support {ref}/watcher-api-execute-watch.html#watcher-api-execute-watch-action-mode[multiple options].
 
 After starting the simulation, you’ll see a results screen. For more information 
-on the fields in the response, see the {ref}//watcher-api-execute-watch.html[Execute Watch API].
+on the fields in the response, see the {ref}/watcher-api-execute-watch.html[Execute watch API].
 
 [role="screenshot"]
 image:management/watcher-ui/images/advanced-watch/advanced-watch-simulate.png["Create advanced watch"]
@@ -237,8 +237,8 @@ image:management/watcher-ui/images/advanced-watch/advanced-watch-simulate.png["C
 
 Refer to these examples for creating an advanced watch: 
 
-* {stack-ov}/watch-cluster-status.html[Watch the status of an {es} cluster]
-* {stack-ov}/watching-meetup-data.html[Watch event data]
+* {ref}/watch-cluster-status.html[Watch the status of an {es} cluster]
+* {ref}/watching-meetup-data.html[Watch event data]
 
 
 
diff --git a/docs/user/monitoring/cluster-alerts.asciidoc b/docs/user/monitoring/cluster-alerts.asciidoc
index f36cbaf4d54f..cfdc9e203703 100644
--- a/docs/user/monitoring/cluster-alerts.asciidoc
+++ b/docs/user/monitoring/cluster-alerts.asciidoc
@@ -47,7 +47,7 @@ include::cluster-alerts-license.asciidoc[]
 To receive email notifications for the Cluster Alerts:
 
 . Configure an email account as described in
-{stack-ov}/actions-email.html#configuring-email[Configuring email accounts].
+{ref}/actions-email.html#configuring-email[Configuring email accounts].
 . Configure the
 `xpack.monitoring.cluster_alerts.email_notifications.email_address` setting in
 `kibana.yml` with your email address.
diff --git a/docs/user/reporting/watch-example.asciidoc b/docs/user/reporting/watch-example.asciidoc
index 6f68f8c64174..6e147ccdf9ee 100644
--- a/docs/user/reporting/watch-example.asciidoc
+++ b/docs/user/reporting/watch-example.asciidoc
@@ -4,7 +4,7 @@ see {kibana-ref}/secure-reporting.html[Securing Reporting].
 
 To configure a watch to email reports, you use the `reporting` attachment type
 in an `email` action. For more information, see
-{stack-ov}/actions-email.html#configuring-email[Configuring Email Accounts].
+{ref}/actions-email.html#configuring-email[Configuring email accounts].
 
 For example, the following watch generates a PDF report and emails the report every hour:
 
@@ -46,7 +46,7 @@ PUT _watcher/watch/error_report
 
 <1> You must configure at least one email account to enable Watcher to send email.
 For more information, see
-{xpack-ref}/actions-email.html#configuring-email[Configuring Email Accounts].
+{ref}/actions-email.html#configuring-email[Configuring email accounts].
 <2> This is an example POST URL. You can copy and paste the URL for any
 report from the Kibana UI.
 <3> Optional, default is 40