Clarify changelog description formatting

[lcawl]

Summary

Relates to elastic/elastic-docs-skills#122
Updates the changelog style guide with respect to the format of the description field.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

2. If you answered "Yes" to the previous question, please specify the tool(s) and model(s) used (e.g., Google Gemini, OpenAI ChatGPT-4, etc.).

Tool(s) and model(s) used: Cursor Grok 4.6

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• contribute-docs/content-types/changelogs.md
• contribute-docs/style-guide/formatting.md

[github-actions]

Elastic Docs Style Checker (Vale)

Summary: 1 warning, 1 suggestion found

⚠️ Warnings (1): Fix when the suggestion improves clarity or correctness.

File	Line	Rule	Message
contribute-docs/style-guide/formatting.md	596	Elastic.Spelling	'monospace' is a possible misspelling.

💡 Suggestions (1): Optional style improvements. Apply when helpful.

File	Line	Rule	Message
contribute-docs/style-guide/formatting.md	609	Elastic.WordChoice	Consider using 'can, might' instead of 'may', unless the term is in the UI.

---

The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.