/docs/k8s/crds

website/content/docs/k8s/crds/index.mdx

@@ -1,13 +1,11 @@
 ---
 layout: docs
-page_title: Consul Custom Resource Definitions
+page_title: Custom Resource Definitions for Consul on Kubernetes
 description: >-
-  Consul supports managing configuration entries via Kubernetes Custom Resources.
+Consul on Kubernetes supports Consul's configuration entry kind through Custom Resource Definitions (CRDs). Learn how to configure Helm charts to enable CRDs and use kubectl to create, manage, and delete mesh components like gateways and intentions on k8s.
-  These custom resource can be used to manage the configuration for workloads
-  deployed within the cluster.
 ---
 
-# Custom Resource Definitions
+# Custom Resource Definitions (CRDs) for Consul on Kubernetes
 
 This topic describes how to manage Consul [configuration entries](/docs/agent/config-entries)
 via Kubernetes Custom Resources. Configuration entries provide cluster-wide defaults for the service mesh.

website/content/docs/k8s/crds/upgrade-to-crds.mdx

@@ -1,11 +1,11 @@
 ---
 layout: docs
-page_title: Upgrade An Existing Cluster to CRDs
+page_title: Upgrade Existing Clusters to Use Custom Resource Definitions
 description: >-
-  Upgrade an existing cluster to use custom resources.
+Kubernetes clusters configured with a Consul Helm chart version older than 0.30.0 require updates in order to use CRDs. Learn about the changes you need to make, as well as how to migrate a Consul config entry to a k8s CRD.
 ---
 
-# Upgrade An Existing Cluster to CRDs
+# Upgrade Existing Clusters to Use Custom Resource Definitions
 
 Upgrading to consul-helm versions >= `0.30.0` will require some changes if
 you utilize the following: