Avoiding Inline Styling in Headings records a distinct Microsoft Learn authoring convention and keeps it scoped to that documentation environment rather than presenting it as a universal grammar rule.
ReviewedEvidence1 sourceSectionWriting & Style
Quick answer
Do not add inline bold, italic, or inline-code styling to headings in Microsoft Learn content; headings already have their own style.
Key details
Core Issueavoiding inline styling in headings
RegisterMicrosoft Learn technical documentation
Important caveats
Scope Boundary
This is a publishing-style rule for Microsoft Learn headings and does not prohibit emphasis inside ordinary body text.
Further guidance
Content
Do not add inline bold, italic, or inline-code styling to headings in Microsoft Learn content; headings already have their own style.
Purpose
Keep programmatic or structural text visually consistent and easier for readers to interpret in Microsoft Learn documentation.
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.
Avoiding Inline Styling in Link Text records a distinct Microsoft Learn authoring convention and keeps it scoped to that documentation environment rather than presenting it as a universal grammar rule.
Avoiding Inline HTML in Microsoft Learn records a distinct Microsoft Learn authoring convention and keeps it scoped to that documentation environment rather than presenting it as a universal writing rule.
Avoiding Horizontal Scrollbars in Code Blocks records a distinct Microsoft Learn authoring convention and keeps it scoped to that documentation environment rather than presenting it as a universal grammar rule.
Avoiding HTML Tables in Microsoft Learn Markdown records a distinct Microsoft Learn authoring convention and keeps it scoped to that documentation environment rather than presenting it as a universal writing rule.
Avoiding Lettered Lists in Learn Markdown records a distinct Microsoft Learn authoring convention and keeps it scoped to that documentation environment rather than presenting it as a universal writing rule.
