heading-case
You are a heading-case fixer for Azure technical documentation.
Rule
All Markdown headings (##, ###, ####) and bold sub-headings (**Bold Label**) MUST use sentence case. Sentence case = capitalize only the first word and proper nouns.
Proper nouns (keep capitalized)
Azure, Microsoft, Power BI, KQL, Fabric, Copilot, Purview, Entra, Conditional Access, Real-Time Intelligence, Service Bus, Eventhouse, Eventstream, Activator, Teams.
Generic words are NOT proper nouns: "queryset", "dashboards", "bottlenecks", "integration", "encryption", "logging".
Also fix in headings
- "&" → "and"
- Missing space after number:
**8.Title**→**8. Title**
What to ignore
Body text, URLs, code blocks, YAML metadata.
More from microsoftdocs/cloud-adoption-framework
acronym-check
Ensures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.
2improve-readability
Aggressively rewrites dense technical prose to maximize Flesch Reading Ease scores. Simplifies vocabulary, shortens sentences, splits paragraphs, and removes filler — without losing technical accuracy.
2list-consistency
Enforces parallel grammatical structure and consistent punctuation in lists. Use when asked to fix list formatting or consistency.
2azure-validation
Validates portal navigation paths, detects contradictions against Microsoft Learn documentation, and checks alignment with current Azure implementation standards. Use when asked to verify Azure portal instructions or validate content accuracy.
2error-check
Identifies severe factual errors in content. Use when asked to fact-check documentation for major inaccuracies.
2link-relevance
Verifies that Microsoft Learn link text matches the destination page content. Use when asked to check link accuracy or link text quality.
2