Content
Grammar & Style
Consistency in punctuation, capitalisation, and word choice makes the product feel polished and trustworthy. Follow these rules across every UI surface.
Quick-reference rules
Sentence case for UI
Save changes · Add new member · Are you sure?
Save Changes · Add New Member · Are You Sure?
Title case for headings
Getting Started · Team Settings · Billing & Plans
Getting started · Team settings · Billing & plans
Button copy starts with a verb
Save · Delete · Cancel · Export CSV
OK · Confirm · Yes · Proceed
No trailing punctuation on labels
Full name · Email address · Due date
Full name: · Email address. · Due date —
Oxford comma
Read, write, and delete permissions
Read, write and delete permissions
Contractions are fine
You're all set · It's saved · We'll send you a link
You are all set · It is saved · We will send you a link
Numbers: spell out 1–9, use digits 10+
Three items · 10 members · 42 results
3 items · Ten members · Forty-two results
Use the % symbol, not "percent"
95% confidence · 0% tax
95 percent confidence · 0 percent tax
Error messages
Error messages should do three things: tell users what happened, why it happened (if helpful), and what to do next.
Required field
“Enter your email address”
“This field is required”
Invalid format
“Email must include an @ sign”
“Invalid email”
Server error
“Something went wrong. Try again or contact support.”
“Error 500”
Permission denied
“You don’t have access to this page. Ask your admin.”
“403 Forbidden”
Placeholder text
Placeholder copy in inputs should give a concrete example, not repeat the label. It never replaces the label.
| Label | Placeholder |
|---|---|
| [email protected] | |
| Search | Search components… |
| Amount | 0.00 |