Source: https://developers.google.com/style/highlights\n\n# Highlights
Stay organized with collections
Save and categorize content based on your preferences.\n\n- Home\n- Products\n- Style\n\n\n## Page Summary\n\n- This style guide outlines important standards for tone, content, language, grammar, formatting, punctuation, organization, and image use in documentation.\n- Key recommendations include using conversational language, writing for accessibility and a global audience, employing active voice and second person, and following specific formatting rules for lists, code, and UI elements.\n- For clarity, the guide promotes descriptive link text, unambiguous date formats, the use of alt text for images, and the preference for high-resolution images whenever possible.\n- This guide aims to ensure consistent, clear, and user-friendly documentation.\n\nThis style guide outlines important standards for tone, content, language, grammar, formatting, punctuation, organization, and image use in documentation.\n\nKey recommendations include using conversational language, writing for accessibility and a global audience, employing active voice and second person, and following specific formatting rules for lists, code, and UI elements.\n\nFor clarity, the guide promotes descriptive link text, unambiguous date formats, the use of alt text for images, and the preference for high-resolution images whenever possible.\n\nThis guide aims to ensure consistent, clear, and user-friendly documentation.\n\nThe style guide covers a lot of material, so the following page provides an overview of its most
important points. For more information about topics on the page, follow the links.\n\n\n## Tone and content\n\n- Be conversational and friendly without being
frivolous.\n- Don't pre-announce anything in
documentation.\n- Use descriptive link text.\n- Write accessibly.\n- Write for a global audience.\n\n\n## Language and grammar\n\n- Use second person: "you" rather than
"we."\n- Use active voice: make clear who's performing
the action.\n- Use standard American spelling and
punctuation.\n- Put conditions before instructions,
not after.\n- For usage and spelling of specific words, see
the word list.\n\n\n## Formatting, punctuation, and organization\n\n- Use sentence case for document
titles and section headings.\n- Use numbered lists for sequences.\n- Use bulleted lists for most other lists.\n- Use description lists for pairs of related
pieces of data.\n- Use serial commas.\n- Put code-related text in code font.\n- Put UI elements in bold.\n- Use unambiguous date formatting.\n\n\n## Images\n\n- Provide alt
text.\n- Provide high-resolution or vector
images when practical.\n