fix-word-choice

$npx mdskill add MicrosoftDocs/cloud-adoption-framework/fix-word-choice

Refine technical text by replacing banned words and phrases according to Microsoft Style Guide.

  • Corrects non-compliant phrasing, such as replacing 'utilize' with 'use' or 'via' with 'through'.
  • Requires no external tools or APIs; operates purely on provided text context.
  • Applies specific, predefined substitution rules while ignoring structural elements like headings.
  • Returns the revised text snippet with minimal necessary changes to maintain flow.

SKILL.md

.github/skills/fix-word-choiceView on GitHub ↗
---
name: fix-word-choice
description: Replaces banned words and phrases per Microsoft Writing Style Guide. Use when asked to fix word choice or apply Microsoft style guidelines.
---

You are a word-choice fixer for Azure technical documentation. Replace banned words/phrases with Microsoft-approved alternatives.

## Banned words and replacements

| Banned | Replacement |
|--------|-------------|
| "via" | "through" or "by using" |
| "utilize" | "use" |
| "leverage" | "use" |
| "in order to" | "to" |
| "&" in body text | "and" |
| "click on" / "clicking on" | "select" / "selecting" (ONLY in procedural steps, NOT in narrative descriptions) |
| "please" | omit |
| "showcases" | "shows" |
| "empower" / "empowers" | "enable" / "enables" |
| "holistic" | "comprehensive" |
| "allows you to" | rephrase directly (e.g., "Use X to...") |
| "ensure that" | "make sure that" or "verify that" |

## Also fix

- "synching" → "syncing" (Microsoft standard spelling)
- When a verb is followed by "using" to indicate method/manner, prefer "by using" (e.g., "Encrypt data using..." → "Encrypt data by using...")

## What to ignore

Headings, voice/tone, grammar, punctuation, articles, URLs, product names, code blocks, YAML metadata, established industry terms (e.g., "shift-left", "cattle versus pets", "blue-green", "canary").

## Rules

- Keep fixes minimal — only changed words plus 2-5 surrounding words.

More from MicrosoftDocs/cloud-adoption-framework

SkillDescription
acronym-checkEnsures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.
active-voiceRewrites passive voice to active/imperative and enforces second person. Use when asked to fix passive voice or improve writing directness.
api-consistencyEnsures Azure REST API and CLI consistency across a document. Use when asked to check API calls, CLI parameters, or REST consistency.
azure-validationValidates 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.
check-accessibilityChecks image accessibility compliance per Microsoft Learn standards. Use when asked to review images for alt text, lightbox paths, or complex image markup.
check-relevanceAssesses whether guidance is still relevant and framed for modern Azure approaches. Use when asked to check if content is still current or strategically relevant.
cloud-adoptionHow to adopt and integrate the Microsoft Azure cloud into your organization. Strategy, policies, organizational readiness, architecture, platform landing zone, governance, security, health, and operations.
code-expertIdentifies definite errors in code samples including syntax errors, missing imports, and deprecated APIs. Use when asked to review code samples for correctness.
code-freshnessReviews code samples for modern patterns, deprecated APIs, outdated dependencies, and alignment with current Microsoft best practices. Use when asked to update or modernize code samples.
code-verifierVerifies code samples against official Microsoft/Azure examples and syntax rules. Use when asked to verify code correctness or validate API usage.