[mq] working branch - merge 34592a9 on top of master at 01afe25

{"baseBranch":"master","baseCommit":"01afe259e8efe99f6a7e43c11d1ac916bea7dd99","createdAt":"2025-05-16T19:09:17.862588Z","headSha":"34592a9317e8d595362615f2f2a35b5c919e9afd","id":"457e00d4-d12b-4d81-8025-f442d04a1816","priority":"200","pullRequestNumber":"29372","queuedAt":"2025-05-16T19:09:17.861998Z","status":"STATUS_QUEUED"}

Author: dd-mergequeue[bot]

layouts/shortcodes/pci-logs.en.md

@@ -14,10 +14,10 @@ To begin **onboarding**:
 - `pci.browser-intake-datadoghq.com:443` for browser logs
 
 3. For example, add the following lines to the Agent configuration file:
-```
-logs_config:
-  logs_dd_url: <agent-http-intake-pci.logs.datadoghq.com:443>
-```
+   ```
+   logs_config:
+     logs_dd_url: agent-http-intake-pci.logs.datadoghq.com:443
+   ```
 4. All logs that are sent to the PCI compliant endpoint(s) automatically have a set of [Sensitive Data Scanner][106] PCI rules that are applied to scrub any cardholder data. These dedicated PCI rules must be enabled for PCI DSS compliance and are included with no additional charge. Note that Sensitive Data Scanner for PCI customers does not include the Summary page or estimated usage metric capabilities.
 
 To finish onboarding and be moved to **compliant**: