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.
pull/936/head
Emil Hessman 2015-05-14 10:09:48 +02:00
parent 9fb235a98d
commit f5ed15a860
1 changed files with 1 additions and 1 deletions

View File

@ -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 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 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 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. never bind Consul to the wrong interface.
The first node will act as our sole server in this cluster, and we indicate The first node will act as our sole server in this cluster, and we indicate