From 3014446e764d0dcad688ae41b819ffb1417d7d91 Mon Sep 17 00:00:00 2001
From: James Rodewig <james.rodewig@elastic.co>
Date: Tue, 17 Sep 2019 15:48:18 -0400
Subject: [PATCH] [DOCS] Update CCR links (#44012)

---
 docs/management/managing-remote-clusters.asciidoc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/management/managing-remote-clusters.asciidoc b/docs/management/managing-remote-clusters.asciidoc
index 8612a28638866..8717476ac5d2e 100644
--- a/docs/management/managing-remote-clusters.asciidoc
+++ b/docs/management/managing-remote-clusters.asciidoc
@@ -8,7 +8,7 @@ can be used to provide remote backups for disaster recovery or for geo-proximite
 
 Before using these features, you should be familiar with the following concepts:
 
-* {stack-ov}/xpack-ccr.html[{ccr-cap}]
+* {ref}/xpack-ccr.html[{ccr-cap}]
 * {ref}/modules-cross-cluster-search.html[{ccs-cap}]
 * {stack-ov}/cross-cluster-configuring.html[Cross-cluster security requirements]
 
@@ -55,8 +55,8 @@ a given remote cluster, and monitor whether the replication is active.
 
 Before you use these features, you should be familiar with the following concepts:
 
-* {stack-ov}/ccr-requirements.html[Requirements for leader indices] 
-* {stack-ov}/ccr-auto-follow.html[Automatically following indices]
+* {ref}/ccr-requirements.html[Requirements for leader indices] 
+* {ref}/ccr-auto-follow.html[Automatically following indices]
 
 To get started, go to *Management > Elasticsearch > {ccr-cap}*.