A product copy editing guide that improves interface writing in a project: buttons, errors, settings, empty states, placeholders, and links, governed by one voice with tone flexing to the stakes.
Tasks
Audit button labels across a flow so every button starts with a verb and the flow uses one consistent vocabulary (e.g. 'Continue' vs 'Next') end to end
Review error messages to ensure each states how to fix the problem, sits beside the failing field, and avoids blame, 'oops', or exclamation marks
Check capitalization consistency per element type (buttons, headings, labels), preferring sentence case as the default
Verify toggle settings describe the ON state and that every field has a visible label rather than relying on a placeholder
Rewrite empty states so they orient the user and offer one clear next action, and search empty states name the query and offer an exit
Inputs
Existing product copy in the project (labels, buttons, errors, settings, empty states, placeholders, links)
The product's terminology, localization conventions, and any voice or content style guide found in nearby copy
Outputs
A findings table with columns Severity, Location (path/to/file:line), Before, After, Why
A final verdict of Block (any HIGH remains) or Approve, or 'No actionable writing findings' with a verification statement
Limitations and checks
How copy renders (capitalization via text-transform, truncation, smart punctuation) belongs to better-typography
Error markup and announcements (aria-invalid, live regions) belong to better-accessibility
Room for translated strings belongs to better-layout
An established deliberate brand voice is not a defect; departures from plain language are raised only when they cause inconsistency, ambiguity, translation risk, or mismatched tone
Every button label begins with a verb, confirmation buttons repeat the consequence, and no consequential action uses a bare 'Yes'/'No' or 'OK!'
Every error message includes a stated fix, sits next to the field that failed, and uses positive phrasing with hints shown before the mistake
Link text makes sense out of context (no 'Click here'; suffixed 'Learn more about X' when multiple appear) and no sentence is assembled by concatenating fragments around a variable
Tone matches the stakes per the tone table (warm for onboarding, neutral for routine, calm and plain for errors, serious and explicit for data loss/security)
AI Search
Find projects, verify facts, compare options, or turn a complex need into an actionable plan
Try a searchA click only fills the search box; you stay in control