From 21deacb5d6914f7a36fc513fd6b07a6143274471 Mon Sep 17 00:00:00 2001 From: James Phillips Date: Wed, 5 Apr 2017 10:40:30 -0700 Subject: [PATCH] Cleans up some doc typos. --- website/source/docs/guides/acl.html.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/source/docs/guides/acl.html.markdown b/website/source/docs/guides/acl.html.markdown index 812059c5d9..8fc5a131b4 100644 --- a/website/source/docs/guides/acl.html.markdown +++ b/website/source/docs/guides/acl.html.markdown @@ -26,7 +26,7 @@ The ACL system is based on tokens, which are managed by Consul operators via Con [HashiCorp's Vault](https://www.vaultproject.io/docs/secrets/consul/index.html). Every token has an ID, name, type, and rule set. The ID is a randomly generated -UUID, making it unfeasible to guess. The name is opaque to Consul and human readable. +UUID, making it infeasible to guess. The name is opaque to Consul and human readable. The type is either "client" (meaning the token cannot modify ACL rules) or "management" (meaning the token is allowed to perform all actions). @@ -50,7 +50,7 @@ policy is to "deny all" actions, then token rules can be set to whitelist specif actions. In the inverse, the "allow all" default behavior is a blacklist where rules are used to prohibit actions. By default, Consul will allow all actions. -The following table summarizes the ACL policies that are availabile for constructing +The following table summarizes the ACL policies that are available for constructing rules: | Policy | Scope |