Update datadog.mdx

[natemollica-nm]

Description

Reword the end user note to be in an English-understandable format.

Original

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 tls.crt, tls.key, and ca.crt secret volumes at the /etc/datadog-agent/conf.d/consul.d/certs path on the Datadog Agent, agent container.

Update

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 tls.crt, tls.key, and ca.crt secret volumes at the /etc/datadog-agent/conf.d/consul.d/certs path within the Datadog Agent pod's agent container.

Testing & Reproduction steps

• N/A

Links

• N/A

PR Checklist

• external facing docs updated
• appropriate backport labels added
• not a security concern

[boruszak]

Thank you for addressing this confusing note!

I left some additional suggestions to help clarify these sentences and align with our style guide! Please implement the suggestions and then I will approve you to merge!

[github-actions]

This pull request has been automatically flagged for inactivity because it has not been acted upon in the last 60 days. It will be closed if no new activity occurs in the next 30 days. Please feel free to re-open to resurrect the change if you feel this has happened by mistake. Thank you for your contributions.

[github-actions]

Closing due to inactivity. If you feel this was a mistake or you wish to re-open at any time in the future, please leave a comment and it will be re-surfaced for the maintainers to review.