From d79139760a5655b5e97cbdbb075d228c8e93c18c Mon Sep 17 00:00:00 2001 From: Jon Benson Date: Wed, 13 Jan 2016 16:56:40 -0800 Subject: [PATCH] Fix semaphore typo --- website/source/docs/guides/semaphore.html.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/guides/semaphore.html.markdown b/website/source/docs/guides/semaphore.html.markdown index e2b409ad3..938c31b2c 100644 --- a/website/source/docs/guides/semaphore.html.markdown +++ b/website/source/docs/guides/semaphore.html.markdown @@ -28,7 +28,7 @@ reading. Actual values returned from the API will not be formatted. Let's imagine we have a set of nodes who are attempting to acquire a slot in the semaphore. All nodes that are participating should agree on three decisions: the -prefix in the Key/Value store used to coordinate, a single key to use as a lock, +prefix in the Key/Value store used to coordinate, a single key to use as a lock, and a limit on the number of slot holders. For the prefix we will be using for coordination, a good pattern is simply: @@ -73,7 +73,7 @@ The `` value is the ID returned by the call to to Consul but can be useful for human operators. The call will either return `true` or `false`. If `true`, the contender entry has been -created. If `false`, the contender node was not created; it'slikely that this indicates +created. If `false`, the contender node was not created; it's likely that this indicates a session invalidation. The next step is to use a single key to coordinate which holders are currently