From 852fe86ea2b361a97d1fe0770bc2457a4809d86e Mon Sep 17 00:00:00 2001
From: jorbay-au <40071830+jorbay-au@users.noreply.github.com>
Date: Fri, 1 Feb 2019 13:38:22 -0800
Subject: [PATCH] Remove repeated word in indexing-service.md (#6983)

---
 docs/content/design/indexing-service.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/content/design/indexing-service.md b/docs/content/design/indexing-service.md
index 0d583b7fb6c..8a3d5a6ea43 100644
--- a/docs/content/design/indexing-service.md
+++ b/docs/content/design/indexing-service.md
@@ -26,7 +26,7 @@ title: "Indexing Service"
 
 The indexing service is a highly-available, distributed service that runs indexing related tasks. 
 
-Indexing tasks [tasks](../ingestion/tasks.html) create (and sometimes destroy) Druid [segments](../design/segments.html). The indexing service has a master/slave like architecture.
+Indexing [tasks](../ingestion/tasks.html) create (and sometimes destroy) Druid [segments](../design/segments.html). The indexing service has a master/slave like architecture.
 
 The indexing service is composed of three main components: a [Peon](../design/peons.html) component that can run a single task, a [Middle Manager](../design/middlemanager.html) component that manages Peons, and an [Overlord](../design/overlord.html) component that manages task distribution to MiddleManagers.
 Overlords and MiddleManagers may run on the same node or across multiple nodes while MiddleManagers and Peons always run on the same node.