diff --git a/website/content/docs/dynamic-app-config/kv.mdx b/website/content/docs/dynamic-app-config/kv.mdx
index b6f7631b72..00a1193ef9 100644
--- a/website/content/docs/dynamic-app-config/kv.mdx
+++ b/website/content/docs/dynamic-app-config/kv.mdx
@@ -1,10 +1,11 @@
 ---
 layout: docs
-page_title: Consul KV
-description: Consul KV is a core feature of Consul and is installed with the Consul agent.
+page_title: Key/Value (KV) Store Overview
+description: >-
+  Consul includes a KV store for indexed objects, configuration parameters, and metadata that you can use to dynamically configure apps. Learn about accessing and using the KV store to extend Consul's functionality through watches, sessions, and Consul Template.
 ---
 
-# Consul KV
+# Key/Value (KV) Store Overview
 
 Consul KV is a core feature of Consul and is installed with the Consul agent.
 Once installed with the agent, it will have reasonable defaults. Consul KV allows
diff --git a/website/content/docs/dynamic-app-config/sessions.mdx b/website/content/docs/dynamic-app-config/sessions.mdx
index 05251d3886..729c1b312b 100644
--- a/website/content/docs/dynamic-app-config/sessions.mdx
+++ b/website/content/docs/dynamic-app-config/sessions.mdx
@@ -1,14 +1,11 @@
 ---
 layout: docs
-page_title: Sessions
+page_title: Sessions and Distributed Locks Overview
 description: >-
-  Consul provides a session mechanism which can be used to build distributed
-  locks. Sessions act as a binding layer between nodes, health checks, and
-  key/value data. They are designed to provide granular locking and are heavily
-  inspired by The Chubby Lock Service for Loosely-Coupled Distributed Systems.
+  Consul supports sessions that you can use to build distributed locks with granular locking. Learn about sessions, how they can prevent ""split-brain"" systems by ensuring consistency in deployments, and how they can integrate with the key/value (KV) store.
 ---
 
-# Sessions
+# Sessions and Distributed Locks Overview
 
 Consul provides a session mechanism which can be used to build distributed locks.
 Sessions act as a binding layer between nodes, health checks, and key/value data.
diff --git a/website/content/docs/dynamic-app-config/watches.mdx b/website/content/docs/dynamic-app-config/watches.mdx
index 2c6ac883b9..2a90beef64 100644
--- a/website/content/docs/dynamic-app-config/watches.mdx
+++ b/website/content/docs/dynamic-app-config/watches.mdx
@@ -1,15 +1,11 @@
 ---
 layout: docs
-page_title: Watches
+page_title: Watches Overview and Reference
 description: >-
-  Watches are a way of specifying a view of data (e.g. list of nodes, KV pairs,
-  health checks) which is monitored for updates. When an update is detected, an
-  external handler is invoked. A handler can be any executable. As an example,
-  you could watch the status of health checks and notify an external system when
-  a check is critical.
+  Watches monitor the key/value (KV) store, services, nodes, health checks, and events for updates. When it detects a change, it invokes a handler that can call an HTTP endpoint or run an executable. Learn how to configure watches to dynamically respond to changes in Consul.
 ---
 
-# Watches
+# Watches Overview and Reference
 
 Watches are a way of specifying a view of data (e.g. list of nodes, KV pairs, health
 checks) which is monitored for updates. When an update is detected, an external handler