Fix MDX verification failures in i18n files due to Callout indentation

[Copilot]

✨ Summary

MDX verification was failing for 6 translated files due to incorrect indentation inside <Callout> tags. The MDX parser requires specific indentation patterns that differ from standard markdown formatting.

Files affected:

• src/i18n/content/{es,fr,jp,kr,pt}/docs/alerts/get-notified/notification-integrations.mdx
• src/i18n/content/pt/docs/cci/configure-cci/general-setting.mdx

Root cause:
Translated files used consistent 6-space indentation for all content inside Callout tags, but the MDX compiler expects the pattern used in English source files:

• 6 spaces before <Callout>
• 1 space before heading text
• 18 spaces before bullet lists
• 0 spaces before </Callout>

Changes:

• Matched Callout indentation patterns to English source files
• Removed blank lines between Callout headings and content where present

All files now pass yarn verify-mdx.

🖼️ Screenshots

N/A

🔮 Engineering checklist

• Code changes are self-documenting or clearly commented/documented
• No new warnings or errors where added to the browser or build console

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

Hi @Copilot 👋

Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days.

Please ensure the propsed changes look good by building it first in your local environment. Refer to this contribution guide to get the site up and running in your local.

If you really require a preview url, reach out to one of the writers and they will generate one for you.

[Copilot]

Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• unpkg.com
  • Triggering command: /usr/local/bin/node scripts/postinstall.js (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)