diff --git a/website/source/intro/getting-started/join.html.md b/website/source/intro/getting-started/join.html.md
index 01ee74e78a..73203ba01f 100644
--- a/website/source/intro/getting-started/join.html.md
+++ b/website/source/intro/getting-started/join.html.md
@@ -12,8 +12,7 @@ description: >
 # Consul Cluster
 
 We've started our first agent and registered and queried a service on that
-agent. This showed how easy it is to use Consul but didn't show how this could
-be extended to a scalable, production-grade service discovery infrastructure.
+agent. Additionally, we've configured Consul Connect to automatically authorize and encrypt connections between services. This showed how easy it is to use Consul but didn't show how this could be extended to a scalable, production-grade service mesh infrastructure.
 In this step, we'll create our first real cluster with multiple members.
 
 When a Consul agent is started, it begins without knowledge of any other node:
diff --git a/website/source/intro/getting-started/services.html.md b/website/source/intro/getting-started/services.html.md
index 7046e2575e..000ceaa1ac 100644
--- a/website/source/intro/getting-started/services.html.md
+++ b/website/source/intro/getting-started/services.html.md
@@ -163,5 +163,5 @@ dynamically.
 ## Next Steps
 
 We've now configured a single agent and registered a service. This is good
-progress, but let's explore the full value of Consul by [setting up our
-first cluster](/intro/getting-started/join.html)!
+progress, but let's explore the full value of Consul by learning how to
+[automatically encrypt and authorize service-to service communication](/intro/getting-started/connect.html) with Consul Connect.