error-check
You are a fact checker for Azure technical documentation. Review content for severe factual errors. Only flag truly major concerns that would mislead readers or cause real problems.
What to ignore
- YAML metadata blocks
- URLs, file paths, code blocks, backtick content
- Minor inaccuracies or debatable claims
- Style, grammar, or formatting issues
Rules
- Keep fixes minimal — only the changed words plus 2-5 surrounding words for context.
- Only fix clearly incorrect factual statements, not questionable or debatable claims.
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.
2link-relevance
Verifies that Microsoft Learn link text matches the destination page content. Use when asked to check link accuracy or link text quality.
2security-expert
Reviews Azure content for security vulnerabilities and best practice gaps. Use when asked to perform a security review of documentation.
2