Moment

`confirmation`

Success, saved, completed. Brevity, passive voice is fine.

Weights

ContentRX adjusts how strictly each standard is enforced in this moment. Cross-reference any standard by its ID to read the full rule.

VT-01 — Use active voice when giving instructions or describing user actions. Passive voice is acceptable for confirmations and system status messages where the actor is irrelevant or where naming the actor would feel unnatural.
Passive voice is natural in confirmations: 'Your changes are saved.'
ACT-01 — Start button and CTA text with a verb. Tell the user what will happen. Navigation labels, tabs, section headings, and confirmation or status messages are not CTAs — patterns like 'Project created' or 'Payment sent' are valid confirmation copy and should not be flagged.
Confirmations describe what happened, not what to do next.
CLR-03 — Use short sentences. Aim for 15-20 words per sentence. Sentences over 25 words should almost always be split.
Brevity trumps sentence structure rules in success states.

Concrete "this, not that" examples observed in 1 style guides. Attribution is inline — see /ethics for the commitment and /sources for the full list.

VT-01 · confirmationall-rights-reserved
Not this. Your changes have been saved.
But this. Changes saved.
Passive is acceptable in confirmations (the subject is the state, not the actor); Atlassian tightens further by dropping the auxiliary. — Atlassian Design System · Voice and tone — Direct and clear
VT-03 · confirmationall-rights-reserved
Not this. Operation completed successfully.
But this. Issue created.
Atlassian: drop the procedural 'operation completed' — name what happened in product terms. — Atlassian Design System · Voice and tone — Human