5 exercises — choosing the most precise word: use vs utilise, deploy vs implement vs execute, deprecated vs removed, and quantified vs vague descriptions.
0 / 12 completed
1 / 12
A technical spec says: "The system will utilise an event queue to process messages asynchronously." Which is the better word choice and why?
Option B is correct. "Utilise" has a specific meaning: to find a practical use for something that was not originally designed for that purpose ("we utilised the spare CPU cycles for background tasks"). When you mean simply "to use", write "use". "The system will use an event queue" is shorter, clearer, and more precise. "Utilise" is a common verbose upgrade that adds syllables without adding meaning. This is one of the most frequent precision errors in non-native technical writing. The Google Developer Style Guide explicitly recommends "use" over "utilise" in all standard technical contexts. Reserve "utilise" for the specific sense of repurposing or making creative use of available resources.
2 / 12
A DevOps engineer describes a deployment step. Which sentence uses the most precise word?
Option B is the most precise. In deployment contexts: deploy = move an artefact (container, binary, code) from a source to a target environment and make it live. implement = build or put in place a system or feature (not an action performed on an artefact). execute = run a process or command (the container is executed once it is running, but you deploy it first). release = make a version available (often to users or for download), not specifically about infrastructure placement. Technical precision map: "implement a feature" → "deploy a build" → "execute a binary" → "release a version". Using the wrong verb signals imprecision to technical reviewers.
3 / 12
A code review comment reads: "This function is very slow." Which rewrite demonstrates precise technical word choice?
Option C is the most precise. "Slow" is a vague evaluation; "O(n²)" is a precise characterisation. The rewrite adds three layers of precision: (1) the algorithmic complexity (O(n²)), (2) the condition under which it degrades ("at scale"), and (3) a concrete measurement ("4 seconds at 10,000 records"). This gives the author actionable information. Options A and D are still vague (extremely, poorly). Option B uses jargon ("latency profile") that sounds technical but adds no specific information. Word choice precision in code reviews: quantify (4 seconds, O(n²)) rather than qualify (slow, fast, poor). Precise language shortens the back-and-forth needed to understand an issue.
4 / 12
An API changelog uses: "The old endpoint has been deleted." Which word is more precise in an API versioning context?
Option B is more precise for a removal action. In API versioning, the terms have specific meanings: deprecated = still available but scheduled for removal; users should migrate away. removed/deleted = no longer available. "Removed" is the conventional term in API changelogs for endpoints that are gone in a new version (it is the term used by Stripe, GitHub, and AWS in their changelogs). "Deleted" is also accurate but sounds more like a database operation than an API versioning event. "Eliminated" is unusual in this context. Critical nuance: if you write "deprecated" for something that has been removed, users will not migrate urgently — they will assume it still works. Deprecation and removal are distinct events in an API lifecycle.
5 / 12
A backend engineer writes: "The job ran and did the task." Which rewrite uses the most precise vocabulary?
Option C is the most precise. It names the job type (batch job), confirms the outcome (ran successfully), and quantifies the result (12,400 records processed). This is the level of precision expected in status updates, monitoring dashboards, and operations logs. Option A replaces vague words with slightly less vague words ("performed the operation" — which operation?). Option B is more formal but still says nothing specific about what was accomplished. Option D is colloquial and provides no technical information. Precision in status reporting: always include what type of job, the outcome (completed, failed, timed out), and a measurable result (records processed, files written, tasks queued).
6 / 12
Mark, a senior backend engineer, is responding to a Slack message from a teammate asking about an error in the payment processing pipeline. Which response demonstrates the most careful word choice?
Option 2 is best because it uses precise terminology – 'transaction flow' and 'investigate'. 'Broken' is too informal and 'failing' lacks detail. The other options are vague and don't provide enough context for a targeted troubleshooting discussion. Mark's response focuses on the *cause* of the issue, crucial in technical communication.
7 / 12
An API documentation entry states: "The /users/{user_id} endpoint has been deprecated." Which word choice is most appropriate and why?
Option 1 – 'deprecated' – is the standard technical term for an API endpoint that is no longer actively supported. It signals to developers that they shouldn't rely on it in new code. The other options are less precise and may not convey the same level of urgency or information about future changes. 'Obsolete' implies a more permanent state than 'deprecated'.
8 / 12
Mark, a senior backend engineer, is responding to a Slack message from a teammate asking about an error in the payment processing pipeline. Which response demonstrates the most careful word choice?
Option 2 is best because it uses precise terminology – 'transaction flow' and 'investigate'. 'Broken' is too informal and 'failing' lacks detail. The other options are vague and don't provide enough context for a targeted troubleshooting discussion. Mark's response focuses on the *cause* of the issue, crucial in technical communication.
9 / 12
An API documentation entry states: "The /users/{user_id} endpoint has been deprecated." Which word choice is most appropriate and why?
Option 1 – 'deprecated' – is the standard technical term for an API endpoint that is no longer actively supported. It signals to developers that they shouldn't rely on it in new code. The other options are less precise and may not convey the same level of urgency or information about future changes. 'Obsolete' implies a more permanent state than 'deprecated'.
10 / 12
David, a backend engineer, is responding to a code review comment about a database query. The comment reads: 'This query is inefficient.' David replies: 'I've optimized the query using an index.' Which response demonstrates the most precise word choice?
David's response clearly identifies *how* he addressed the issue – by adding an index. This demonstrates a technical understanding and provides actionable information. 'I've made some changes to improve performance.' is too general, while the other options are subjective or non-technical.
11 / 12
A service catalog entry for a new API states: 'The endpoint returns a 404 error when no data is available.' Which word choice is most accurate and why? It clearly indicates the specific HTTP status code and the reason for its occurrence.
A '404 Not Found' HTTP status code signifies that the requested resource doesn't exist on the server. Combining this with the explanation—'when no data is available'—provides a complete and precise description of the API behavior. It's crucial for developers to understand these error codes.
12 / 12
Sarah, a junior frontend developer, is writing a PR description for a UI change. She writes: 'I've updated the button styling to match the new brand guidelines.' Which option best demonstrates precise word choice in this context?
The correct answer highlights that 'appropriate' accurately reflects Sarah's description. 'Updated' is overly general; a better phrasing focuses on the *change* itself. The other options misinterpret the core purpose of the PR description – to communicate what was modified.
What will I practise in "Word Choice Precision in Technical Writing — Grammar Exercise"?
Practice precise word choice in technical writing: use vs utilise, implement vs deploy vs execute, deprecated vs removed, and quantified descriptions.
How many exercises are in this module?
This module has 12 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the grammar rule and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Grammar exercises?
Browse the full Grammar hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain grammar rules in prose; this exercise tests and reinforces those rules through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.