diff --git a/docs/en/watcher/example-watches/example-watch-clusterstatus.asciidoc b/docs/en/watcher/example-watches/example-watch-clusterstatus.asciidoc
index dfc3c2c6f2f..7eef62a8831 100644
--- a/docs/en/watcher/example-watches/example-watch-clusterstatus.asciidoc
+++ b/docs/en/watcher/example-watches/example-watch-clusterstatus.asciidoc
@@ -101,7 +101,7 @@ PUT _xpack/watcher/watch/cluster_health_watch
 It would be a good idea to create a user with the minimum privileges required for use with such a watch configuration.
 
 Depending on how your cluster is configured, there may be additional settings required before the watch can access your cluster such as keystores, truststores or certificates.
-See the {ref}//notification-settings.html[Notification Settings] section of the X-Pack Settings documentation.
+See the <<notification-settings,[Notification Settings>> section of the X-Pack Settings documentation.
 
 
 If you check the watch history, you'll see that the cluster status is recorded