Merge pull request #635 from ceh/spell

website: fix minor typos in docs
This commit is contained in:
Ryan Uber 2015-01-23 13:15:12 -08:00
commit 1b3225cb9d
3 changed files with 3 additions and 3 deletions

View File

@ -250,7 +250,7 @@ field is not used by Consul, and is meant to be human readable.
If a `Script` is provided, the check type is a script, and Consul will If a `Script` is provided, the check type is a script, and Consul will
evaluate the script every `Interval` to update the status. evaluate the script every `Interval` to update the status.
An `HTTP` check will preform an HTTP GET request to the value of `HTTP` (expected to be a URL) every `Interval`. If the response is any `2xx` code the check is passing, if the response is `429 Too Many Requests` the check is warning, otherwise the check is critical. An `HTTP` check will perform an HTTP GET request to the value of `HTTP` (expected to be a URL) every `Interval`. If the response is any `2xx` code the check is passing, if the response is `429 Too Many Requests` the check is warning, otherwise the check is critical.
If a `TTL` type is used, then the TTL update APIs must be used to periodically update If a `TTL` type is used, then the TTL update APIs must be used to periodically update
the state of the check. the state of the check.

View File

@ -23,7 +23,7 @@ If the lock holder count is more than one, then a semaphore is used instead.
A semaphore allows more than a single holder, but the is less efficient than A semaphore allows more than a single holder, but the is less efficient than
a simple lock. This follows the [semaphore algorithm](/docs/guides/semaphore.html). a simple lock. This follows the [semaphore algorithm](/docs/guides/semaphore.html).
All locks using the same prefix must agree on the value of `-n`. If conflictling All locks using the same prefix must agree on the value of `-n`. If conflicting
values of `-n` are provided, an error will be returned. values of `-n` are provided, an error will be returned.
An example use case is for highly-available N+1 deployments. In these An example use case is for highly-available N+1 deployments. In these

View File

@ -113,7 +113,7 @@ This is done by:
curl -X PUT -d <Updated Lock> http://localhost:8500/v1/kv/<lock>?cas=<lock-modify-index> curl -X PUT -d <Updated Lock> http://localhost:8500/v1/kv/<lock>?cas=<lock-modify-index>
``` ```
If this suceeds with `true` the condenter now holds a slot in the semaphore. If this fails If this suceeds with `true` the contender now holds a slot in the semaphore. If this fails
with `false`, then likely there was a race with another contender to acquire the slot. with `false`, then likely there was a race with another contender to acquire the slot.
Both code paths now go into an idle waiting state. In this state, we watch for changes Both code paths now go into an idle waiting state. In this state, we watch for changes
on `<prefix>`. This is because a slot may be released, a node may fail, etc. on `<prefix>`. This is because a slot may be released, a node may fail, etc.