diff --git a/website/content/docs/k8s/deployment-configurations/clients-outside-kubernetes.mdx b/website/content/docs/k8s/deployment-configurations/clients-outside-kubernetes.mdx
index d35b818a82..1e879e2d0f 100644
--- a/website/content/docs/k8s/deployment-configurations/clients-outside-kubernetes.mdx
+++ b/website/content/docs/k8s/deployment-configurations/clients-outside-kubernetes.mdx
@@ -1,12 +1,11 @@
 ---
 layout: docs
-page_title: Consul Clients Outside of Kubernetes - Kubernetes
+page_title: Join External Clients to Consul on Kubernetes
 description: >-
-  Consul clients running on non-Kubernetes nodes can join a Consul cluster
-  running within Kubernetes.
+  Client agents running on VMs that are not part of a Kubernetes cluster can join a service mesh that has agents running on k8s pods. Configure client agents to accept gRPC communication to join VMs to Kubernetes pods.
 ---
 
-# Consul Clients Outside Kubernetes
+# Join External Clients to Consul on Kubernetes
 
 Consul clients running on non-Kubernetes nodes can join a Consul cluster running within Kubernetes.
 
diff --git a/website/content/docs/k8s/deployment-configurations/consul-enterprise.mdx b/website/content/docs/k8s/deployment-configurations/consul-enterprise.mdx
index 251e724716..9843a00bfd 100644
--- a/website/content/docs/k8s/deployment-configurations/consul-enterprise.mdx
+++ b/website/content/docs/k8s/deployment-configurations/consul-enterprise.mdx
@@ -1,10 +1,11 @@
 ---
 layout: docs
-page_title: Consul Enterprise
-description: Configuration for running Consul Enterprise
+page_title: Deploy Consul Enterprise on Kubernetes
+description: >-
+  Consul Enterprise features are available when running Consul on Kubernetes. Learn how to apply your license in the Helm chart and return the license information with the `consul license get` command.
 ---
 
-# Consul Enterprise
+# Deploy Consul Enterprise on Kubernetes
 
 You can use this Helm chart to deploy Consul Enterprise by following a few extra steps.
 
diff --git a/website/content/docs/k8s/deployment-configurations/servers-outside-kubernetes.mdx b/website/content/docs/k8s/deployment-configurations/servers-outside-kubernetes.mdx
index 6d0f3bcf09..b82d9b563e 100644
--- a/website/content/docs/k8s/deployment-configurations/servers-outside-kubernetes.mdx
+++ b/website/content/docs/k8s/deployment-configurations/servers-outside-kubernetes.mdx
@@ -1,10 +1,11 @@
 ---
 layout: docs
-page_title: Consul Servers Outside of Kubernetes - Kubernetes
-description: Running Consul servers outside of Kubernetes
+page_title: Join External Servers to Consul on Kubernetes
+description: >-
+  Client agents that run on Kubernetes pods can join existing clusters whose server agents run outside of k8s. Learn how to expose gossip ports and bootstrap ACLs by configuring the Helm chart.
 ---
 
-# Consul Servers Outside of Kubernetes
+# Join External Servers to Consul on Kubernetes
 
 If you have a Consul cluster already running, you can configure your
 Consul clients inside Kubernetes to join this existing cluster.
diff --git a/website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx b/website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx
index 5408d3e987..67bc4f15b3 100644
--- a/website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx
+++ b/website/content/docs/k8s/deployment-configurations/single-dc-multi-k8s.mdx
@@ -1,10 +1,11 @@
 ---
 layout: docs
-page_title: Single Consul Datacenter in Multiple Kubernetes Clusters - Kubernetes
-description: Single Consul Datacenter deployed in multiple Kubernetes clusters
+page_title: Deploy Single Consul Datacenter Across Multiple K8s Clusters
+description: >-
+  A single Consul datacenter can run across multiple Kubernetes pods in a flat network as long as only one pod has server agents. Learn how to configure the Helm chart, deploy pods in sequence, and verify your service mesh.
 ---
 
-# Single Consul Datacenter in Multiple Kubernetes Clusters
+# Deploy Single Consul Datacenter Across Multiple Kubernetes Clusters
 
 ~> **Note:** When running Consul across multiple Kubernetes clusters, we recommend using [admin partitions](/docs/enterprise/admin-partitions) for production environments. This Consul Enterprise feature allows you to accommodate multiple tenants without resource collisions when administering a cluster at scale. Admin partitions also enable you to run Consul on Kubernetes clusters across a non-flat network.