5 exercises — Practice choosing precise action verbs and button labels for checkout flows, trial signups, confirmation dialogs, and email campaigns.
0 / 10 completed
1 / 10
A checkout page has a button to complete a purchase. Which label performs best?
Purchase CTAs should use the precise, specific verb that describes the action being taken.
• "Submit" — generic; appropriate for form submissions, not purchases; creates cognitive uncertainty
• "Proceed" — directional but vague; doesn't tell users what comes next
• "Click Here to Complete Order" — "Click Here" is a well-known anti-pattern; redundant in a button context
• "Place Order" ✓ — specific, commercial vocabulary; a merchant term that accurately describes the action
Other high-performing checkout CTA patterns:
• "Buy Now" — urgency, directness
• "Complete Purchase" — formal, transactional clarity
• "Pay $49.99" — specificity about what happens next
Key vocabulary:
• CTA (call to action) — a button or link prompting the user to take a specific action
• Action verb — the verb that precisely describes the action (Place, Buy, Start, Create)
• "Click Here" anti-pattern — generic instruction that adds no information and fails accessibility
• Transaction CTA — a CTA that initiates a commercial action and implies money changing hands
2 / 10
A SaaS pricing page has a primary CTA for starting a free trial. Which label is most effective?
Pricing page CTAs should reflect the offer, not just the account creation step.
• "Sign Up" — describes the backend action (creating an account), not the value the user is getting
• "Register" — formal, legacy terminology; feels like a government form
• "Start Free Trial" ✓ — communicates what the user is beginning (trial) + key modifier (free)
• "Get Access" — slightly better than "Sign Up" but misses the "free" differentiator
When "free" is the main selling point, the CTA MUST include "free" or "No credit card required" nearby.
CTA formula: [Action verb] + [Offer descriptor]
• "Start Free Trial" — Start (verb) + Free Trial (offer)
• "Try [Product] Free" — alternative with brand name
• "Get [Plan Name] Plan" — appropriate for paid plans
Key vocabulary:
• Pricing CTA — the primary action button on a pricing or landing page
• Offer descriptor — the part of a CTA that names what the user is getting (trial, plan, access)
• "Free" modifier — including the word "free" in a CTA when cost is the main barrier to conversion
• Conversion friction — anything in copy that makes users hesitate before clicking
3 / 10
A delete confirmation modal asks: "Are you sure you want to delete this project? This action cannot be undone." The primary button says "OK". What should it say instead?
Destructive action confirmation buttons must use the specific action verb — never "OK", "Yes", or "Confirm".
"OK" and "Yes" are generic affirmatives — they fail when a user is in a hurry and doesn't fully read the dialog. They also fail accessibility: screen readers announce "OK" without context.
Best practice for destructive confirmations:
1. Primary (destructive) button: specific verb + object → "Delete Project"
2. Secondary (safe) button: "Cancel" (never "No" — "No" implies they disagree, not that they changed their mind)
Bonus: Make destructive buttons visually distinct (red/danger color) so users register the severity before clicking.
Key vocabulary:
• Destructive action — an action that permanently removes or irrevocably changes data
• Confirmation dialog — a modal that asks users to confirm before completing a destructive action
• Specific verb rule — using the exact action verb in confirmation buttons ("Delete", "Remove", "Archive")
• Irreversibility notice — copy that warns users the action cannot be undone
4 / 10
A marketing email has a button CTA. The email promotes a webinar on Python performance. Which CTA label is most effective?
Email CTAs perform better when they are outcome-oriented and use first-person perspective.
• "Click Here" — describes the gesture, not the outcome; always an anti-pattern
• "Learn More" — vague; no specificity about what they're signing up for
• "Register" — accurate but transactional and cold
• "Save My Spot" ✓ — first-person perspective creates ownership; "spot" implies scarcity and urgency
First-person CTAs consistently outperform in A/B tests:
• "Start My Free Trial" vs "Start Your Free Trial"
• "Save My Seat" vs "Register Now"
• "Get My Report" vs "Download Report"
The first-person framing shifts from "this is what the button does" to "this is what I get".
Key vocabulary:
• First-person CTA — a button label written from the user's perspective ("My", "I")
• Scarcity signal — copy that implies limited availability ("spot", "seat", "slot")
• Outcome-oriented CTA — label that describes what the user achieves, not the action
• A/B testing CTAs — testing two versions of a button label to optimize conversion
5 / 10
A SaaS dashboard has two buttons at the end of a settings form: one saves changes, one discards. Which pair is correct?
Button pairs should use parallel, specific verbs — and the cancellation button should name what's being discarded, not just cancel the dialog.
• "Submit / Cancel" — "Submit" is generic; "Cancel" is acceptable but could confuse (cancel the form? Cancel my account?)
• "OK / Cancel" — "OK" provides zero information about what's being confirmed
• "Save Changes / Discard" ✓ — "Save Changes" is specific; "Discard" communicates exactly what will happen (changes lost)
• "Confirm / Go Back" — "Confirm" is vague; "Go Back" is navigation, not a discard action
Button pair guidelines:
• Primary (positive) button: specific action verb + object
• Secondary (negative) button: names the cost ("Discard", "Cancel", "Leave Without Saving")
• Destructive secondary: "Discard Changes" if changes would be lost permanently
Key vocabulary:
• Button pair — two buttons offering opposing actions (primary vs. dismissal)
• Parallel structure — both buttons in a pair using the same grammatical form (verb + object)
• Dismissal action — the secondary button that cancels, discards, or abandons a flow
• Destructive secondary — a dismissal button that results in data loss, requiring stronger language
6 / 10
During a code review of a new authentication endpoint, you notice the API response includes a 'refresh_token' field. The developer has labeled the button that returns this token 'Get Token'. Which label would be more intuitive for another developer to understand the action's purpose?
'Get Token' is too generic. While technically correct, it doesn't clearly communicate the *purpose* of the token – that it's for refreshing an existing session. 'Retrieve Refresh Token' accurately describes what the button does and aligns with best practices for API documentation. It also avoids ambiguity about the action.
7 / 10
You're drafting a Slack message to announce a critical bug fix in the payment processing module. A teammate asks for a button label on a link you're sending that directs them to view the release notes. Which CTA is most effective in this scenario?
'Check Notes' provides a clear and direct instruction about what the user will find when they click the link. The other options are too vague – 'View Release', 'See Updates,' and 'Release Details' don't immediately convey that the notes contain specific information about the bug fix.
8 / 10
You're writing a PR description for a new feature: an automated deployment pipeline. The button within the pull request to trigger this pipeline is labeled 'Start Deployment'. Which of the following options provides the most clarity and encourages immediate action?
'Start Deployment' is slightly ambiguous as it doesn't explicitly state that this button triggers the entire pipeline. 'Deploy Now' is more direct and action-oriented, clearly communicating the desired outcome – immediate deployment of changes. It aligns with a sense of urgency commonly found in CI/CD workflows.
9 / 10
During a daily standup meeting, Sarah mentions she's working on improving the error handling for the user profile service. She asks another developer to click a button in her Jira task to view the updated code. The button label is 'View Error Handling'. What would be a better CTA that directly reflects the purpose of the button?
'View Error Handling' is too broad. 'See Error Fixes' explicitly tells the user what they will find – a specific focus on error resolution. This is more helpful than simply viewing 'Changes,' 'Code Updates,' or 'Improvements.'
10 / 10
A developer is creating a new form in the admin panel to manage user roles. One button saves changes made to the role definition and another discards them. The label on the 'Discard' button currently reads 'Cancel'. Which of the following options provides the most effective and clear instruction for this action?
'Cancel' is ambiguous and doesn't clearly communicate that the button will revert to the previous state. 'Return to Draft' or 'Undo Updates' are more descriptive options, accurately reflecting the action of discarding changes and returning to an earlier version of the form.
This exercise, "CTA & Button Language", tests your understanding of ux writing vocabulary and phrasing through 10 multiple-choice questions drawn from real workplace scenarios.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 10 questions. Each one presents a realistic sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Who is this UX Writing exercise for?
It's designed for IT professionals and learners who want to sound natural discussing ux writing topics in English — useful for meetings, documentation, interviews, and day-to-day communication with English-speaking teams.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more UX Writing exercises?
Browse the full UX Writing exercises hub for more practice, or explore other exercise categories covering vocabulary, grammar, interviews, and workplace communication.