status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

website: Fixing small typos in guides section

This commit is contained in:
Phillip Markert 2014-06-17 08:19:45 -04:00
parent 441d613e1b
commit 339edd722b
4 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/source/docs/guides/dns-cache.html.markdown
View File

@ -35,14 +35,14 @@ and `dns_config.max_stale` which limits how stale results are allowed to
be.
By default, `allow_stale` is disabled meaning no stale results may be served.
The default for `max_stale` is 5 seconds. This means that is `allow_stale` is
The default for `max_stale` is 5 seconds. This means that if `allow_stale` is
enabled, we will use data from any Consul server that is within 5 seconds
of the leader.
## TTL Values
TTL values can be set to allow DNS results to be cached upstream
of Consul which can be reduce the number of lookups and to amortize
of Consul which can be used to reduce the number of lookups and to amortize
the latency of doing a DNS lookup. By default, all TTLs are zero,
preventing any caching.

2
website/source/docs/guides/forwarding.html.markdown
View File

@ -6,7 +6,7 @@ sidebar_current: "docs-guides-forwarding"
# Forwarding DNS
By default DNS is served from port 53 which requires root privileges.
By default, DNS is served from port 53 which requires root privileges.
Instead of running Consul as root, it is possible to instead run Bind
and forward queries to Consul as appropriate.

2
website/source/docs/guides/index.html.markdown
View File

@ -8,7 +8,7 @@ sidebar_current: "docs-guides"
This section provides various guides for common actions. Due to the nature
of Consul, some of these procedures can be complex, so our goal is to provide
guidance do doing them safely.
guidance to do them safely.
The following guides are available:

2
website/source/docs/guides/servers.html.markdown
View File

@ -72,7 +72,7 @@ the new servers up-to-date.
Removing servers must be done carefully to avoid causing an availability outage.
For a cluster of N servers, at least (N/2)+1 must be available for the cluster
to functions. See this [deployment table](/docs/internals/consensus.html#toc_3).
to function. See this [deployment table](/docs/internals/consensus.html#toc_3).
If you have 3 servers, and 1 of them is currently failed, removing any servers
will cause the cluster to become unavailable.