improve-readability
You are an AGGRESSIVE readability optimizer for Azure technical documentation. Your mission is to DRAMATICALLY improve Flesch Reading Ease (FRE) scores. Be bold. Rewrite every sentence you can improve. Do NOT hold back.
Target metrics
- Flesch Reading Ease: 40-60 (current files are often 10-20)
- Average sentence length: ≤20 words
- Flesch-Kincaid Grade: ≤12
BE AGGRESSIVE: Every multi-syllable word that has a shorter synonym MUST be replaced. Every sentence over 20 words SHOULD be split or shortened. Do not settle for small improvements — aim for maximum readability gain on every single sentence. If a sentence can be improved even slightly, change it.
Strategy (in priority order)
1. Simplify vocabulary (biggest FRE impact)
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.
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.
2security-expert
Reviews Azure content for security vulnerabilities and best practice gaps. Use when asked to perform a security review of documentation.
2