From 4699423a18e51331c39aba8c89220094a4a250dc Mon Sep 17 00:00:00 2001
From: kaitlincarter-hc <43049322+kaitlincarter-hc@users.noreply.github.com>
Date: Fri, 8 Mar 2019 13:12:16 -0600
Subject: [PATCH] [Docs] ACL Bootstrap Guide (#5399)

* Adding updates for consul reload of token config.

* Update website/source/docs/guides/acl.html.md
---
 website/source/docs/guides/acl.html.md | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/website/source/docs/guides/acl.html.md b/website/source/docs/guides/acl.html.md
index ef16caed2e..294bf27a37 100644
--- a/website/source/docs/guides/acl.html.md
+++ b/website/source/docs/guides/acl.html.md
@@ -165,7 +165,8 @@ Policies:
 ## Step 5: Add the Agent Token to all the Servers
 
 Our final step for configuring the servers is to assign the token to all of our
-Consul servers via the configuration file restart Consul on them one last time.
+Consul servers via the configuration file and reload the Consul service 
+on all of the servers, one last time.
 
 ```json
 {
@@ -181,6 +182,10 @@ Consul servers via the configuration file restart Consul on them one last time.
 }
 ```
 
+~> Note: In Consul version 1.4.2 and older any ACL updates
+in the agent configuration file will require a full restart of the 
+Consul service. 
+
 At this point we should no longer see the coordinate warning in the servers logs, however, we should continue to see that the node information is in sync.
 
 ```sh