From 7a722907e827d0b8e5efedbe59603e6a1779694e Mon Sep 17 00:00:00 2001
From: awelsh93 <32643586+awelsh93@users.noreply.github.com>
Date: Thu, 14 Feb 2019 14:38:09 +0000
Subject: [PATCH] Update api-reference.md doc (#7065)

- moving description of coordinator isLeader endpoint
---
 docs/content/operations/api-reference.md | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/docs/content/operations/api-reference.md b/docs/content/operations/api-reference.md
index 7a0b43421fc9..23d118864a9d 100644
--- a/docs/content/operations/api-reference.md
+++ b/docs/content/operations/api-reference.md
@@ -74,17 +74,15 @@ Returns the current leader Coordinator of the cluster.
 
 * `/druid/coordinator/v1/isLeader`
 
-Returns true if the Coordinator receiving the request is the current leader.
-
-#### Segment Loading
-
-##### GET
-
 Returns a JSON object with field "leader", either true or false, indicating if this server is the current leader
 Coordinator of the cluster. In addition, returns HTTP 200 if the server is the current leader and HTTP 404 if not.
 This is suitable for use as a load balancer status check if you only want the active leader to be considered in-service
 at the load balancer.
 
+#### Segment Loading
+
+##### GET
+
 * `/druid/coordinator/v1/loadstatus`
 
 Returns the percentage of segments actually loaded in the cluster versus segments that should be loaded in the cluster.