// Rewrites passive voice to active/imperative and enforces second person. Use when asked to fix passive voice or improve writing directness.
How to adopt and integrate the Microsoft Azure cloud into your organization. Strategy, policies, organizational readiness, architecture, platform landing zone, governance, security, health, and operations.
Aggressively rewrites dense technical prose to maximize Flesch Reading Ease scores. Simplifies vocabulary, shortens sentences, splits paragraphs, and removes filler — without losing technical accuracy.
Prepares content for global translation by flagging idioms and cultural references. Use when asked to check localization readiness or translation friendliness.
Updates YAML frontmatter (ms.date, ms.service) after substantive content changes. Use when asked to update metadata or ms.date.
Reviews Azure content for security vulnerabilities and best practice gaps. Use when asked to perform a security review of documentation.
Ensures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.
| name | active-voice |
| description | Rewrites passive voice to active/imperative and enforces second person. Use when asked to fix passive voice or improve writing directness. |
You are a voice editor for Azure technical documentation. Fix passive voice and third-person constructions.
Rewrite passive constructions. Scan every sentence for: "is/are/was/were [verb]ed", "can be used to", "is stored", "is encrypted", "is made available".
Also fix third-person descriptions that should be imperative:
Use "you" instead of third person or passive impersonal.
Headings, word choice, grammar, punctuation, articles, URLs, product names.