From b628815dbeea3e2e7bdbd7ffabe500678d2edbd5 Mon Sep 17 00:00:00 2001
From: lcawley <lcawley@elastic.co>
Date: Thu, 12 Oct 2017 13:40:30 +0100
Subject: [PATCH] [DOCS] Fixed link to X-Pack transport client

Original commit: elastic/x-pack-elasticsearch@0870334e4b8bf5d23ed26dd755073c42fcb486da
---
 docs/en/security/tribe-clients-integrations/java.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/security/tribe-clients-integrations/java.asciidoc b/docs/en/security/tribe-clients-integrations/java.asciidoc
index e5c622aef91..150a4c38638 100644
--- a/docs/en/security/tribe-clients-integrations/java.asciidoc
+++ b/docs/en/security/tribe-clients-integrations/java.asciidoc
@@ -16,7 +16,7 @@ NOTE: Using the Java Node Client with secured clusters is not recommended or
 To use the transport client with a secured cluster, you need to:
 
 [[java-transport-client-role]]
-. <<xpack-javaclient, Set up the client for use with {xpack}>>.
+. {ref}/setup-xpack-client.html[Configure the {xpack} transport client].
 
 . Configure a user with the privileges required to start the transport client.
 A default `transport_client` role is built-in to {xpack} that grants the