docs-standards

To standardize squad documentation, apply the Microsoft Style Guide rules for sentence-case headings, active voice, and present tense, while enforcing squad-specific formatting patterns to ensure uniform readability.

The Microsoft Style Guide rules for technical writing mandate sentence-case headings, active voice, second person, present tense, and no ampersands in prose to ensure clear and consistent documentation.

Structure product documentation pages using scannability-first writing, placing "Try this" prompts at the top, experimental warnings prominently, and cross-references at the bottom for maintainability.

The recommended page structure for API docs and feature guides includes a Title, warning, quick start, overview, and detailed sections, ensuring a uniform and readable experience across squads.

Yes, you can apply these documentation standards to onboarding material, as the rules for headings, voice, tense, and cross-references are designed for maintaining product documentation across all squad outputs.

Squad documentation lacks consistency and discoverability when it does not enforce a common set of formatting, voice, and structural patterns like those defined in the Microsoft Style Guide.