Table of contents
×

Review the guidelines for submitting articles on support.office.com and docs.microsoft.com:

Note:  Microsoft Style Guide - this is the overall style guide reference for Microsoft.

  • headings, titles, and labels: Use sentence case, no ending punctuation.

  • Use the UI style to bold references to user interface controls.

  • Use the User Input or User Input Localizable style to format text that the user types.

  • Capitalize proper nouns (Example: View menu).

  • Use right-angle brackets to trace the path to a command (Accounts > Other accounts > Add an account).

  • Use verbs that can apply equally to keyboard, mouse, pen, or touch (select, choose, or enter; not click or type).

  • Use sentence case for keyboard shortcuts (Ctrl+A).

  • Use lowercase for URLs unless it's a friendly name (Microsoft.com). Use approved fictitious names for fictitious URLs (Contoso.com).

  • Use informal "inline links" to link to other articles rather than "see also's" to specific titles. For example, "You can also use a picture as a watermark." Never use "click here".

  • For tables, use header rows with meaningful column titles.

  • Numbered and bulleted lists should always include more than one list item. When there is only one item to list, use a paragraph.

  • If you include audio or video in the article, it must be closed captioned or have a transcript.

  • Use notes and tips rarely, and don't interrupt the flow with them.

  • Use art and screenshots only when they are necessary to make content clear and easy to grasp.

  • Always use meaningful alt text for images.

  • Images should be no more than 520 pixels wide. For Instant Answers, art should be between 345px and 435px wide.

  • Indent screenshots that go with a procedure directly following the step they apply to.

  • For conceptual art, use high-contrast color combinations, do not put patterns or images behind text, and make sure that multiple cues convey information (color and text, not just color).

  • For screenshots, use a standard theme and use approved fictitious names. Do not show any personal information.

  • Be aware of our global audience - many readers won't understand colloquial phrases or culture-specific references and they may not have access to all websites, or understand the same visual metaphors.

  • Use familiar worldwide images and a diverse set of people and places in examples.

  • Use a worldwide format for dates (Month, dd yyyy) and start calendars on Mondays.

  • Don't include trademark bugs for Microsoft products. Trademark third-party product names at first mention.

  • Don't use product names possessively (Word's) and generally don't abbreviate product names.

  • Make sure you have permission or license to use any quotation, photo, or image not owned by Microsoft. Cite copyrighted information.

  • Don't use language like: bundle, free, new, exclusive.

  • Use "helps protect" or "promotes online privacy" and "follows security guidelines" instead of "protect," "safe," "secure," and so on.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×