From 24272b27a3ae289b055cb36c750eeb1ce7235ff0 Mon Sep 17 00:00:00 2001 From: Tim Kersten Date: Wed, 3 Aug 2016 21:11:02 +0100 Subject: [PATCH] Update upgrading.html.markdown The change fixes a minor bug in the document that says consul supports back to version 0 when the example output says version 1, and makes the document less ambiguous by having a different "current" protocol and earliest supported protocol. --- website/source/docs/upgrading.html.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/source/docs/upgrading.html.markdown b/website/source/docs/upgrading.html.markdown index 778df3707b..0a11900260 100644 --- a/website/source/docs/upgrading.html.markdown +++ b/website/source/docs/upgrading.html.markdown @@ -73,13 +73,13 @@ running `consul -v`. You'll see output similar to that below: ``` $ consul -v -Consul v0.1.0 -Consul Protocol: 1 (Understands back to: 1) +Consul v0.6.3 +Consul Protocol: 3 (Understands back to: 1) ``` -This says the version of Consul as well as the latest protocol version (1, +This says the version of Consul as well as the latest protocol version (3, in this case). It also says the earliest protocol version that this Consul -agent can understand (0, in this case). +agent can understand (1, in this case). By specifying the `-protocol` flag on `consul agent`, you can tell the Consul agent to speak any protocol version that it can understand. This