diff --git a/website/source/docs/agent/services.html.markdown b/website/source/docs/agent/services.html.markdown
index c64cb68ee6..1575c7d293 100644
--- a/website/source/docs/agent/services.html.markdown
+++ b/website/source/docs/agent/services.html.markdown
@@ -74,10 +74,10 @@ from `1`.
 
 Note: there is more information about [checks here](/docs/agent/checks.html). 
 
-The `enableTagOverride` can optionally specified to disable the antientropy feature for 
-this service. If `enableTagOverride` is set to TRUE then external agents can
-reregister this service and modify the tags. Subsequent local sync operations
-by this agent will ignore the updated tags. For instance: If an external agent
+The `enableTagOverride` can optionally be specified to disable the anti-entropy 
+feature for this service. If enableTagOverride is set to TRUE then external 
+agents can update this service in the [catalog](/docs/agent/http/catalog.html) and modify the tags. Subsequent
+local sync operations by this agent will ignore the updated tags. For instance: If an external agent
 modified both the tags and the port for this service and `enableTagOverride` 
 was set to TRUE then after the next sync cycle the service's port would revert 
 to the original value but the tags would maintain the updated value. As a 
diff --git a/website/source/docs/internals/anti-entropy.html.markdown b/website/source/docs/internals/anti-entropy.html.markdown
index 69a78bbe94..6643038353 100644
--- a/website/source/docs/internals/anti-entropy.html.markdown
+++ b/website/source/docs/internals/anti-entropy.html.markdown
@@ -138,8 +138,8 @@ automatically recover from these types of transient failures.
 
 ### EnableTagOverride
 
-Synchronization of service registration can be partially modified to allow
-external agents change the tag value of a service.  This can be useful in
+Synchronization of service registration can be partially modified to allow 
+external agents to change the tags for a service.  This can be useful in
 situations where an external monitoring service needs to be the source of
 truth for tag information.  For instance: Redis DB and its monitoring service
 Redis Sentinel have this kind of relationship.  Redis instances are responsible