Moment
celebration
Achievement, milestone, streak. Enthusiasm is earned, not excessive.
Weights
ContentRX adjusts how strictly each standard is enforced in this moment. Cross-reference any standard by its ID to read the full rule.
Emphasized — flag more aggressively
VT-05— Show empathy in error and failure states, scaled to the severity of the problem. High-impact errors (payment failures, data loss) should acknowledge the frustration and reassure the user. Low-impact errors (failed upload, timeout) should be clear and helpful without over-dramatizing.
Celebration copy should feel genuinely warm.VT-02— Address the user directly with 'you' and 'your' in consumer-facing UI copy. Third-person references to 'users,' 'members,' or 'customers' are acceptable in admin interfaces, documentation, and system descriptions where the reader is not the subject.
Use 'you/your' — this is the user's achievement, not the product's.VT-03— Be conversational but not casual. Write like a knowledgeable colleague, not a robot or a buddy.
Robotic tone undermines the earned emotional beat.
Relaxed — minor deviations acceptable
GRM-03— Use exclamation points sparingly. Never use more than one at a time, and never in error messages or alerts.
Exclamation marks are earned in achievement moments.CON-02— Use sentence case for headings and UI labels, not title case.
Achievement copy uses branded/stylized casing as intentional emphasis.
Suppressed — rarely applies here
PRF-11
Enthusiasm is legitimate in celebrations, not dismissive.
Example pairs
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-03· confirmationCC-BY-NC-ND-4.0Not this. Task completed. Operation successful.
But this. Campaign sent 🎉
Mailchimp: robotic tone undermines earned celebratory moments. Specific + warm beats procedural. — Mailchimp · Voice and tone — Celebration