clarify

Explain what went wrong in plain language, suggest how to fix it, and avoid blaming the user. For example, replace "Invalid input" with "Email addresses need an @ symbol. Try: [email protected]" and link to help resources when applicable.

Assess copy for jargon, ambiguity, passive voice, and missing context, then rewrite each element by type: error messages, form labels, buttons, tooltips, empty states, and confirmations. Apply principles like being specific, concise, active, and consistent in terminology.

Good button labels describe the specific action using active voice, like "Create account" or "Save changes" instead of generic text like "Submit" or "OK". Match the user's mental model and be specific about what happens next.

Use confirmation dialogs only for risky or destructive actions, not routine tasks. State the specific action and consequences clearly, such as "Delete 'Project Alpha'? This can't be undone," with a button labeled "Delete project" rather than "Yes".

Avoid unexplained jargon, blaming users for errors, vague messages like "Something went wrong," unnecessary passive voice, humor in error states, inconsistent terminology, and using placeholders as the only field labels since they disappear when users type.