diff --git a/website/source/docs/agent/encryption.html.md b/website/source/docs/agent/encryption.html.md
index 6758889ff..3ddb801b6 100644
--- a/website/source/docs/agent/encryption.html.md
+++ b/website/source/docs/agent/encryption.html.md
@@ -101,7 +101,9 @@ and is secured using a symmetric key. See above for enabling gossip encryption.
 ## Configuring TLS on an existing cluster
 
 As of version 0.8.4, Consul supports migrating to TLS-encrypted traffic on a running cluster
-without downtime. This process assumes a starting point with no TLS settings configured, and involves
-an intermediate step in order to get to full TLS encryption. Review this step-by-step
-[guide](https://learn.hashicorp.com/consul/security-networking/certificates) to learn how. 
+without downtime. This process assumes a starting point with no TLS settings configured and involves
+an intermediate step in order to get to full TLS encryption. Review the
+[Securing RPC Communication with TLS Encryption guide](https://learn.hashicorp.com/consul/security-networking/certificates)
+for the step-by-step process to configure TLS on a new or existing cluster. Note the call outs there
+for existing cluster configuration.