Use when writing or reviewing technical documentation to follow Google's documentation style guide — enforce active voice and present tense, apply sentence case to headings, fix list and procedure formatting, mark code/UI elements correctly, flag non-inclusive terminology, and remove time-specific phrasing. Triggers on tasks involving technical writing, doc review, style consistency, inclusive language, or formatting standards.
64
80%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Use active voice where the grammatical subject performs the action.
Recommended:
Avoid passive voice like:
Passive voice can obscure responsibility, making it unclear whether the reader, computer, server, or another entity should perform an action.
Active voice isn't always required:
Use present tense for actions and states.
Recommended:
Avoid future tense:
Address the reader directly using "you" (implied or explicit).
Recommended:
Use appropriate pronouns consistently throughout documentation.
Recommended:
Avoid:
For deeper exploration, see Google's Technical Writing One guide on active versus passive voice principles.