> ## Documentation Index > Fetch the complete documentation index at: https://content-designer-ux-writing-skill-26.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Examples > Real-world UX writing improvements with before/after analysis and scoring These real transformations show UX text scored against the four quality standards: Purposeful, Concise, Conversational, and Clear. ## Scoring guide **9-10**: Excellent — Best practice example\ **7-8**: Good — Minor improvements possible\ **5-6**: Adequate — Notable issues to address\ **3-4**: Needs work — Significant problems\ **0-2**: Poor — Major revision required *** ## E-commerce checkout error "An error has occurred while processing your payment. Please try again later or contact customer support if the problem persists." ### Analysis Doesn't help user recover or understand next steps 18 words, vague timeframe ("later") Robotic system-speak ("an error has occurred") What error? When is "later"? Why did it fail? **Overall**: 3/10 — Poor user experience "We couldn't process your payment. Check your card details and try again." ### Analysis Provides specific next action 11 words, direct instruction Natural language ("we couldn't") Specific problem and solution **Overall**: 9/10 — Excellent **Why it works**: Users know exactly what failed (payment), likely cause (card details), and what to do (check and retry). *** ## SaaS dashboard empty state "No data available." ### Analysis Doesn't explain why or guide next steps Very brief, but too brief Cold and unhelpful Technically accurate but not helpful **Overall**: 4/10 — Needs significant work "No data yet. Connect your account to see insights." ### Analysis Explains state and provides clear CTA 9 words, includes action Friendly "yet" implies this is temporary Tells you exactly what to do **Overall**: 9/10 — Excellent **Why it works**: "Yet" creates expectation of future value, CTA is specific and actionable. *** ## Mobile app permission request "'AppName' Would Like to Access Your Location"\ \[Allow] \[Don't Allow] ### Analysis Doesn't explain benefit to user Adequate length but no context Standard iOS pattern, not particularly engaging Action is clear but reason isn't **Overall**: 5/10 — Adequate but could be better "Enable location to find coffee shops near you"\ \[Allow] \[Not now] ### Analysis Clear user benefit (find shops) 7 words with value proposition Direct, benefit-focused Exact benefit stated upfront **Overall**: 9/10 — Excellent **Why it works**: Leads with user benefit, not system need. "Not now" is less final than "Don't Allow." *** ## Account deletion confirmation "Are you sure you want to delete your account? This action cannot be undone. All your data will be permanently deleted." ### Analysis Warns of consequences but feels heavy-handed 19 words, some redundancy ("permanently deleted") Somewhat robotic multiple sentences Consequences are clear **Overall**: 6/10 — Adequate but could be improved "Delete your account? You'll lose all your data and this can't be undone." ### Analysis Clear warning without being preachy 13 words, no redundancy Natural phrasing, contraction Consequences clearly stated **Overall**: 9/10 — Excellent **Why it works**: Question format engages user, contractions feel human, consequences clear without repetition. *** ## Password requirements "Password must contain at least 8 characters including uppercase letters, lowercase letters, numbers and special characters." ### Analysis Provides requirements but hard to scan 17 words in one dense sentence List reads like technical documentation Complete info but overwhelming format **Overall**: 5/10 — Adequate but not optimal "Create a strong password (8+ characters)\ Use a mix of letters, numbers, and symbols" ### Analysis Explains why (strong) and what 14 words, broken into scannable lines "Create" vs "must contain" Easy to scan and understand **Overall**: 9/10 — Excellent **Why it works**: Two short lines easier to scan, "strong password" explains purpose, active voice. *** ## Newsletter unsubscribe confirmation "You have been successfully unsubscribed from our mailing list. You will no longer receive emails from us. Thank you for your participation." ### Analysis Overly formal for someone leaving 23 words, lots of redundancy Corporate, stiff Message is clear but verbose **Overall**: 4/10 — Needs work "You're unsubscribed. You can resubscribe anytime in your settings." ### Analysis Confirms action, offers easy reversal 9 words, direct Casual, respectful Simple and actionable **Overall**: 9/10 — Excellent **Why it works**: Respects user's decision, provides exit ramp without guilt, uses contraction. *** ## File upload progress "File uploading... Please wait." ### Analysis Shows status but no time estimate Very brief Somewhat robotic Basic info only **Overall**: 6/10 — Adequate "Uploading report.pdf... Almost done" ### Analysis Shows filename and reassuring progress 4 words plus filename Encouraging "almost done" Specific file being uploaded **Overall**: 8/10 — Good **Why it works**: Filename confirms right file is uploading, "almost done" reduces anxiety. *** ## Common patterns across these improvements "We couldn't process your payment" vs "An error occurred" "Find coffee shops" before "access location" "You're" feels human, "You are" feels robotic Two short lines beat one long sentence "Permanently deleted" → "can't be undone" "Create a password" vs "Password must contain" Always tell users what to do next Don't guilt-trip people who opt out *** ## Quick self-audit questions Use these to improve any UX text: Every word should have a job. Cut filler words like "basically," "actually," "just." Focus on immediate, actionable information. Save details for help docs. If it sounds robotic or corporate when spoken, rewrite it. "Delete" is clearer than "remove" for permanent actions. "Save" is clearer than "OK." Lead with user benefit: "Find nearby stores" before "Allow location access."