From 7e8e11aea38f765891d1e1a46d8d2b7061d63576 Mon Sep 17 00:00:00 2001 From: Kim Toms Date: Sun, 14 Feb 2016 09:32:23 -0500 Subject: [PATCH] Update leader-election.html.markdown Remove duplicate 'leader' --- website/source/docs/guides/leader-election.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/guides/leader-election.html.markdown b/website/source/docs/guides/leader-election.html.markdown index 1a2f1fab80..48adf97926 100644 --- a/website/source/docs/guides/leader-election.html.markdown +++ b/website/source/docs/guides/leader-election.html.markdown @@ -94,7 +94,7 @@ curl -X PUT http://localhost:8500/v1/kv/?release= Another common practice regarding leader election is for nodes to wish to identify the leader for a given service. -As with leader leader election, all nodes that are participating should agree on the key +As with leader election, all nodes that are participating should agree on the key being used to coordinate. This key will be referred to as just `key`. Clients have a very simple role, they simply read `` to discover who the current