From fa233675b96e64f744ab148021415a644e3241c6 Mon Sep 17 00:00:00 2001 From: Ryan Breen Date: Fri, 27 Mar 2015 13:20:32 -0400 Subject: [PATCH] Website: GH-730 for docs/guides/manual-bootstrap.html. --- website/source/docs/guides/manual-bootstrap.html.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/guides/manual-bootstrap.html.markdown b/website/source/docs/guides/manual-bootstrap.html.markdown index eec322cf5..6d4b9ecbf 100644 --- a/website/source/docs/guides/manual-bootstrap.html.markdown +++ b/website/source/docs/guides/manual-bootstrap.html.markdown @@ -21,8 +21,8 @@ storing the cluster state. The client nodes are mostly stateless and rely on the server nodes, so they can be started easily. Manual bootstrapping requires that the first server that is deployed in a new -datacenter provide the `-bootstrap` -[configuration option](/docs/agent/options.html). This option allows the server +datacenter provide the [`-bootstrap` configuration option](/docs/agent/options.html#_bootstrap). +This option allows the server to assert leadership of the cluster without agreement from any other server. This is necessary because at this point, there are no other servers running in the datacenter! Lets call this first server `Node A`. When starting `Node A`