From 26916b03e67ede0201ac6aacaf6ae194c463a8e1 Mon Sep 17 00:00:00 2001 From: Laurent Raufaste Date: Thu, 30 Oct 2014 21:46:19 -0400 Subject: [PATCH] Rephrase --- website/source/docs/agent/options.html.markdown | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/source/docs/agent/options.html.markdown b/website/source/docs/agent/options.html.markdown index b34c555e9e..f2860c74ed 100644 --- a/website/source/docs/agent/options.html.markdown +++ b/website/source/docs/agent/options.html.markdown @@ -180,10 +180,10 @@ definitions support being updated during a reload. is authoritative for ACL information. It must be provided to enable ACLs. All servers and datacenters must agree on the ACL datacenter. Setting it on the servers is all you need for enforcement, but for the APIs to work on the - clients, it must be set (to forward properly). Also, if we want to enhance - the ACL support for other features like service discovery, enforcement - might move to the edges, so it's best to just set the acl_datacenter on all - the nodes. + clients, it must be set on them too (to forward properly). Also, if we want + to enhance the ACL support for other features like service discovery, + enforcement might move to the edges, so it's best to just set the + `acl_datacenter` on all the nodes. * `acl_default_policy` - Either "allow" or "deny", defaults to "allow". The default policy controls the behavior of a token when there is no matching