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