docs-standards

To enforce documentation consistency, apply Microsoft Style Guide rules for sentence-case headings, active voice, and present tense, while adopting squad-specific formatting patterns to ensure scannability and uniform tone across project pages.

Technical documentation formatting should enforce Microsoft Style Guide rules, including sentence-case heading capitalization, second-person voice, present tense, and avoiding ampersands in prose to maximize scannability and reader trust.

Structure documentation pages using scannability-first layouts with cross-references at the bottom, experimental warnings, and "Try this" prompts to guide readers through the content efficiently.

Yes, you can apply squad-specific conventions alongside standard documentation guidelines by integrating custom structural patterns and templates with Microsoft Style Guide rules to match your team's project requirements.

To standardize tone and voice across reference pages, enforce active voice, second-person perspective, and present tense consistently, rejecting passive constructions and non-standard typography like ampersands in prose.