From aa42fea074e270c2a51446586aa3a82bee8aecdf Mon Sep 17 00:00:00 2001 From: Ryan Breen Date: Sun, 1 Mar 2015 19:15:49 -0500 Subject: [PATCH] Website: remove confusing language from docs/guides/outage.html --- website/source/docs/guides/outage.html.markdown | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/source/docs/guides/outage.html.markdown b/website/source/docs/guides/outage.html.markdown index f1a5708eb6..31622b4578 100644 --- a/website/source/docs/guides/outage.html.markdown +++ b/website/source/docs/guides/outage.html.markdown @@ -45,9 +45,9 @@ the rebuilt server needs to have the same IP as the failed server. Again, once this server is online, the cluster will return to a fully healthy state. Both of these strategies involve a potentially lengthy time to reboot or rebuild -a failed server. If this is impractical, if building a new server with the same -IP isn't an option, or if your failed server is unrecoverable, you need to remove -the failed server from the `raft/peers.json` file on all remaining servers. +a failed server. If this is impractical or if building a new server with the same +IP isn't an option, you need to remove the failed server from the `raft/peers.json` +file on all remaining servers. To begin, stop all remaining servers. You can attempt a graceful leave, but it will not work in most cases. Do not worry if the leave exits with an