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.
ReviewedEvidence1 sourceSectionWriting & Style
Quick answer
Use quotation marks when referring to AI prompts in running text in Microsoft-style developer documentation; if a list introduction already identifies the items as prompts, special formatting is not necessary.
Key details
Core IssueUse quotation marks when referring to AI prompts in running text in Microsoft-style developer documentation; if a list introduction already identifies the items as prompts, special formatting is not necessary.
RegisterMicrosoft technical and professional documentation
Important caveats
Scope Boundary
This is a Microsoft developer-content convention for referring to prompt text; it does not prescribe prompt-engineering syntax or universal quotation rules.
Further guidance
Content
Use quotation marks when referring to AI prompts in running text in Microsoft-style developer documentation; if a list introduction already identifies the items as prompts, special formatting is not necessary.
Purpose
Help readers distinguish the literal technical element 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 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.
Formatting Data Formats 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 Data Types 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.
