diff --git a/website/pages/docs/security/encryption.mdx b/website/pages/docs/security/encryption.mdx
index 03fb135962..2a98d1171a 100644
--- a/website/pages/docs/security/encryption.mdx
+++ b/website/pages/docs/security/encryption.mdx
@@ -109,6 +109,6 @@ and is secured using a symmetric key. See above for enabling gossip encryption.
 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 the
-[Securing RPC Communication with TLS Encryption tutorial](ps://learn.hashicorp.com/tutorials/consul/tls-encryption-secure)
+[Securing RPC Communication with TLS Encryption tutorial](https://learn.hashicorp.com/tutorials/consul/tls-encryption-secure)
 for the step-by-step process to configure TLS on a new or existing cluster. Note the call outs there
 for existing cluster configuration.