impeccable-clarifylisted

Rewrite unclear interface text so users understand what happened, what matters, and what to do next. Preserve factual meaning, product terminology, and brand voice. ## Audit the language Read the entire interaction path, not isolated strings. Identify: - ambiguous nouns, verbs, and actions; - internal jargon or assumed knowledge; - vague labels, outcomes, and system states; - missing consequences, recovery, or timing; - inconsistent terminology and capitalization; - redundant headings, intros, helper text, and confirmations; - text that breaks at realistic widths or in translation; - tone that ignores stress, risk, success, or urgency. Infer audience and task from product context and surrounding UI. Ask before changing factual claims, legal meaning, or a term that may be domain-specific. ## Set the message hierarchy For each state, decide: 1. the one fact the user needs now; 2. the action available next; 3. supporting context that changes the decision; 4. the appropriate tone for this moment. Say each idea once. If the heading already explains the state, the introduction should add new information or disappear. ## Rewrite by function ### Actions and navigation Use a specific verb and object when the outcome is not already obvious. Labels should describe what will happen, not the gesture used to trigger it. Keep the same noun and verb for the same concept throughout the product. For destructive actions, name the object and consequence. Prefer undo over confirmation