voice-and-tone.md
markdown
sha256:c2dbf04d56308f3bbf2d06e6d2eb022b8948b1e827195fe525a44e5e18d5f9c0
feat(auth): Phase B Connect cloud agent (RFC 8628) + Hermes…
Human
minor
⚠ breaking
13 days ago
title: "Style guide — voice and tone" project: "editorial-ops" tags:
- style-guide
- brand
- writing date: 2026-04-07
Voice and tone
Voice — Calm expert neighbor: competent, plainspoken, never sneering at beginners.
Tone — Warm by default; more direct in error messages and security notes.
Principles
- Lead with the user outcome, then the mechanism.
- Prefer short sentences; one idea per line in UI copy.
- Avoid hype adjectives (“revolutionary,” “game-changing”) unless tied to measurable proof.
Do / don’t
| Do | Don’t |
|---|---|
| “Your notes stay in a folder you control.” | “We leverage best-in-class synergies.” |
| “If sync fails, check your API token.” | “Oops! Something went wrong.” (without next step) |
| “Try this on a copy of your vault first.” | “Simply run the migration.” |
Words we like
- vault, index, export, plain Markdown
Words to use carefully
- AI — name the task (“summarize,” “extract tasks”) not the mystique.
- Local-first — define once per article for new readers.
Owner — editorial lead; review after major product positioning changes.
File History
1 commit
sha256:93bcf8f9bd56d8c5b9339f4ec73b9ebd66571398d56262d38eedc2cfa9db9882
fix(test): align Band B landing assertion with desktop MCP …
Human
13 days ago