better-writing

Error messages should state how to fix the problem and appear next to the failing field. Replace vague text like "Invalid name" with actionable guidance such as "Use only letters for your name", phrased positively without blame or exclamation marks.

Button labels should start with a verb naming the specific action, like "Save draft" or "Delete project". Avoid "OK", "Yes", or "Let's go!", and on destructive confirmations repeat the consequence so the dialog is answerable without reading the body.

An empty state should orient the user and point forward: name the place, explain its purpose, and offer one clear next action such as "Create a project". Search empty states should name the query and offer an exit like clearing filters.

Pick one capitalization policy per element type and apply it consistently. Sentence case is the safer default because it is calmer, avoids per-word case rules, and localizes cleanly; mixing "Save Changes" beside "Discard changes" reads as sloppiness.

Placeholders should never serve as a field's only label because they vanish on input. Every field keeps a visible label, while placeholders show the expected format such as name@example.com or DD/MM/YYYY.