From cba968ad4d1b4474deb45fa79a9cae839e1115b5 Mon Sep 17 00:00:00 2001 From: Laurent Raufaste Date: Thu, 23 Oct 2014 14:32:11 -0400 Subject: [PATCH] Small typo in the doc --- website/source/docs/internals/acl.html.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/source/docs/internals/acl.html.markdown b/website/source/docs/internals/acl.html.markdown index 45acaa81ed..f2f0dfe075 100644 --- a/website/source/docs/internals/acl.html.markdown +++ b/website/source/docs/internals/acl.html.markdown @@ -37,7 +37,7 @@ on legacy clients. Enforcement is always done by the server nodes. All servers must be [configured to provide](/docs/agent/options.html) an `acl_datacenter`, which enables -ACL enforcement but also specified the authoritative datacenter. Consul does not +ACL enforcement but also specifies the authoritative datacenter. Consul does not replicate data cross-WAN, and instead relies on [RPC forwarding](/docs/internal/architecture.html) to support Multi-Datacenter configurations. However, because requests can be made across datacenter boundaries, ACL tokens must be valid globally. To avoid