Moment
decision_point
Pricing, plan selection, upgrade prompts. No dark patterns.
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
CLR-01— Use plain language. Avoid jargon, technical terms, or insider language unless the audience requires it.
Users making decisions need precise, jargon-free language.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.
Active voice keeps decision copy direct and scannable.GRM-05— Use numerals for numbers in body copy. Spell out a number only when it begins a sentence.
Use numerals in pricing and comparisons for quick scanning.CON-02— Use sentence case for headings and UI labels, not title case.
Inconsistent casing undermines trust at the point of purchase.
Suppressed — rarely applies here
PRF-11
Decision pages legitimately describe features as 'easy' to influence choice.
Example pairs
Concrete "this, not that" examples observed in 2 style guides. Attribution is inline — see /ethics for the commitment and /sources for the full list.
ACT-01· button_ctaCC-BY-4.0Not this. Continue
But this. Choose plan
Material: name what comes next, not the act of proceeding. — Material Design · Buttons — Writing
GRM-05· short_ui_copyCC-BY-NC-ND-4.0Not this. Save up to thirty percent when you upgrade.
But this. Save up to 30% when you upgrade.
Mailchimp + Chicago: use numerals for data (prices, percentages) so readers can scan. Spell out non-data numbers. — Mailchimp · Grammar and mechanics — Numbers