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: name@example.com" and link to help resources when applicable.

Assess copy for jargon, ambiguity, passive voice, and tone mismatches, then rewrite using specific, active, concise language. Apply consistent terminology across error messages, labels, buttons, tooltips, and empty states.

State the specific action and its consequences, especially for destructive actions. Use clear button labels like "Delete project" instead of "Yes", and reserve confirmations for genuinely risky actions to avoid dialog fatigue.

Button labels should describe the specific action using active voice, such as "Create account" or "Save changes" instead of generic text like "Submit" or "OK". Specific labels match the user's mental model and reduce hesitation.

Avoid humor in error messages where users may be stressed or frustrated; use empathetic, helpful language instead. Match tone to the user's mental state, celebrating successes but staying supportive during failures.