From f5ed15a860b32f7cd49c2cb3500232b1dd020877 Mon Sep 17 00:00:00 2001 From: Emil Hessman Date: Thu, 14 May 2015 10:09:48 +0200 Subject: [PATCH] website: fix typo Clarify that the user is assured that Consul will listen to a specific address when specifying a `bind` address, rather than providing some kind of insurance policy. --- website/source/intro/getting-started/join.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/intro/getting-started/join.html.markdown b/website/source/intro/getting-started/join.html.markdown index 81a8785fcc..e6fc2c9779 100644 --- a/website/source/intro/getting-started/join.html.markdown +++ b/website/source/intro/getting-started/join.html.markdown @@ -49,7 +49,7 @@ this is the address that Consul listens on, and it *must* be accessible by all other nodes in the cluster. While a `bind` address is not strictly necessary (Consul will by default listen on the first private IP on a system), it's always best to provide one. Production servers often have -multiple interfaces, so specifying a `bind` address insures that you will +multiple interfaces, so specifying a `bind` address assures that you will never bind Consul to the wrong interface. The first node will act as our sole server in this cluster, and we indicate