From 4aa4a8937359b9ab90fe7dba4c38d4bf87d69daf Mon Sep 17 00:00:00 2001
From: natemollica-dev <57850649+natemollica-nm@users.noreply.github.com>
Date: Wed, 15 Jan 2025 16:09:12 -0800
Subject: [PATCH 1/2] Update datadog.mdx

Reword the end user note to be in an English-understandable format.
---
 .../content/docs/k8s/deployment-configurations/datadog.mdx | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/website/content/docs/k8s/deployment-configurations/datadog.mdx b/website/content/docs/k8s/deployment-configurations/datadog.mdx
index c3df799f4df4..80bc0ed76a7f 100644
--- a/website/content/docs/k8s/deployment-configurations/datadog.mdx
+++ b/website/content/docs/k8s/deployment-configurations/datadog.mdx
@@ -293,9 +293,10 @@ during normal operation beyond that of Consul's available metrics.
 See the below [table](#additional-integration-checks-performed) for an outline of the features added by the official integration.
 
 <Note>
-  Currently, the annotations configured by the Helm overrides with Consul RPC TLS enabled
-  assume server and ca certificate secrets are shared with the Datadog agent release namespace and mount the valid <code>tls.crt</code>, <code>tls.key</code>,
-  and <code>ca.crt</code> secret volumes at the <code>/etc/datadog-agent/conf.d/consul.d/certs</code> path on the Datadog Agent, agent container.
+  Currently, the annotations configured by the Helm overrides, when Consul RPC TLS is enabled,
+  presume the user has shared the server and ca certificate secrets with the Datadog agent's Kubernetes namespace and 
+  mount the valid <code>tls.crt</code>, <code>tls.key</code>, and <code>ca.crt</code> secret volumes at the <code>/etc/datadog-agent/conf.d/consul.d/certs</code> 
+  path within the Datadog Agent pod's <code>agent</code> container.
 </Note>
 
 ### Helm Chart Configuration

From ebec62479e4a6f1a9c62cbb32675402f618f1b37 Mon Sep 17 00:00:00 2001
From: natemollica-dev <57850649+natemollica-nm@users.noreply.github.com>
Date: Thu, 16 Jan 2025 14:44:41 -0800
Subject: [PATCH 2/2] Update
 website/content/docs/k8s/deployment-configurations/datadog.mdx

Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com>
---
 .../content/docs/k8s/deployment-configurations/datadog.mdx   | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/website/content/docs/k8s/deployment-configurations/datadog.mdx b/website/content/docs/k8s/deployment-configurations/datadog.mdx
index 80bc0ed76a7f..ce580eb7540a 100644
--- a/website/content/docs/k8s/deployment-configurations/datadog.mdx
+++ b/website/content/docs/k8s/deployment-configurations/datadog.mdx
@@ -293,10 +293,7 @@ during normal operation beyond that of Consul's available metrics.
 See the below [table](#additional-integration-checks-performed) for an outline of the features added by the official integration.
 
 <Note>
-  Currently, the annotations configured by the Helm overrides, when Consul RPC TLS is enabled,
-  presume the user has shared the server and ca certificate secrets with the Datadog agent's Kubernetes namespace and 
-  mount the valid <code>tls.crt</code>, <code>tls.key</code>, and <code>ca.crt</code> secret volumes at the <code>/etc/datadog-agent/conf.d/consul.d/certs</code> 
-  path within the Datadog Agent pod's <code>agent</code> container.
+  When Consul RPC TLS is enabled, the annotations configured by the Helm overrides assume that the user already shared the server and CA certificate secrets with the Datadog agent's Kubernetes namespace. As a result, it mounts `tls.crt`, `tls.key`, and `ca.crt` secret volumes at the `/etc/datadog-agent/conf.d/consul.d/certs` path in the `agent` container of the Datadog agent's Pod.
 </Note>
 
 ### Helm Chart Configuration