Formatting Markup-Language Elements in Technical Documentation
Formatting Markup-Language Elements in Technical Documentation records a distinct source-supported procedure or technical-formatting task while keeping adjacent UI behavior, accessibility concerns, and implementation mechanics outside the page.
ReviewedEvidence1 sourceSectionWriting & Style
Quick answer
Use code style for markup-language elements such as tags, and preserve the capitalization required by the language or example.
Key details
Core Issueformatting markup-language elements in technical documentation
Registertechnical and professional writing
Important caveats
Scope Boundary
The guidance concerns markup-language elements in documentation; it does not define the syntax or capitalization rules of a particular markup language.
Further guidance
Content
Use code style for markup-language elements such as tags, and preserve the capitalization required by the language or example.
Purpose
This separates literal markup syntax from surrounding explanatory prose.
Sources and evidence
Sources are shown with the role they play in this guide. Historical or style-sensitive claims are kept within the evidence boundary described above.
Formatting XML Schema Elements in Technical Documentation records a distinct source-supported procedure or technical-formatting task while keeping adjacent UI behavior, accessibility concerns, and implementation mechanics outside the page.
Formatting AI Prompts in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Attributes in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Classes in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Code Keywords in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Code Samples in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it scoped to technical instructions rather than presenting it as a universal grammar rule.
Formatting Constants in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
Formatting Control Classes in Technical Documentation records a distinct Microsoft Style Guide authoring convention and keeps it explicitly scoped to technical documentation rather than presenting it as a universal grammar rule.
