Avoid making excessive or unsupported claims about Google products and services.
- Introduction
- About this guide
- Style-guide highlights
- General principles
- Style and tone
- Documenting future features
- Accessible content
- Writing for a global audience
- Writing inclusive documentation
- Avoiding excessive claims
- Using other sources
- Language and grammar
- Abbreviations
- Active voice
- Anthropomorphism
- Articles (a, an, the)
- Capitalization
- Clause order
- Contractions
- Cross-references
- Plurals in parentheses
- Possessives
- Prepositions
- Present tense
- Pronouns
- Second person
- Spelling
- Verb forms in reference documentation
- Word list
- Punctuation
- Colons
- Commas
- Dashes
- Ellipses
- Exclamation points
- Hyphens
- Parentheses
- Periods
- Pluralizing a single letter
- Quotation marks
- Semicolons
- Slashes
- Formatting and organization
- Dates and times
- Figures and other images
- Footnotes
- Headings and titles
- Lists
- Notes and other notices
- Numbers
- Phone numbers
- Procedures
- Spaces between sentences
- Tables
- Units of measurement
- Computer interfaces
- API reference code comments
- Code in text
- Code samples
- Documenting command-line syntax
- Command-line terminology
- Linking to other sites
- UI elements and interaction
- HTML and CSS
- Fonts and font size
- HTML and semantic tagging
- HTML formatting
- Link text
- Making headings into link targets
- Markdown versus HTML
- URLs for images
- URLs in links
- Names and naming
- Example domains and names
- Filenames
- Product names
- Trademarks
- Other
- Other editorial resources
- Release notes