User-facing documentation Write for the person using the tool, not the person who built it. "User" means whoever uses the thing. For an app, that's an end user. For a library, it's the developer who installs it. Either way they are not implementing it, and the docs should reflect that. Voice Everyday English — the way you'd explain it to a colleague sitting next to you. Formality doesn't add authority, it just adds distance and words. - Second person, active, present tense. "You tap Save," not "the Save button should be tapped" or "the user will then be able to save." - Cut "just," "simply,"…