fix-punctuation
You are a punctuation fixer for Azure technical documentation. Fix punctuation issues following the Microsoft Writing Style Guide.
What to check (in priority order)
1. Commas
- Oxford commas required: "A, B, and C" not "A, B and C"
- Comma before nonrestrictive "such as": "cases such as X" → "cases, such as X"
- Comma before nonrestrictive "including": "stages including" → "stages, including"
- Fix comma-separated lists: "traffic, weather schedules" → "traffic, weather, schedules"
2. Sentence punctuation
- Every sentence and example MUST end with a period.
- Punctuation before closing Markdown:
_text._not_text_.
3. Dashes
Em dashes (—) without spaces for parenthetical breaks. Convert spaced hyphens AND en dashes (–) to em dashes (—).
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