5 exercises — practise omitting recoverable words for conciseness in commit messages, PR titles, changelogs, README files, and code review comments.
0 / 20 completed
1 / 20
A developer writes two commit messages: "Fix login bug" and "Fix logout bug". They want to combine them in a PR title using ellipsis (omitting the repeated word). Which PR title is the most concise and natural?
"Fix login bug and logout bug" uses verb ellipsis — the repeated verb Fix is omitted in the second clause because it is recoverable from context. This is the most concise form. In technical writing, especially commit messages and PR titles, ellipsis of repeated elements is both natural and encouraged: "Refactor auth module and payment module" (omitting Refactor in the second phrase). Option C is grammatically possible but shifts the noun to plural, which changes the register. Option A is verbose. Option D is awkward. The golden rule: omit what is fully recoverable; keep what disambiguates.
2 / 20
A tech writer reviews this sentence from a changelog: "Version 2.0 adds dark mode support and version 2.0 removes the legacy XML parser." Which revision best applies subject ellipsis?
"Version 2.0 adds dark mode support and removes the legacy XML parser." applies subject ellipsis: the repeated subject "Version 2.0" and auxiliary are omitted in the second coordinated verb phrase. This is the most natural and concise revision. In changelog entries and release notes this structure is standard: "This release fixes three edge cases and updates the dependency manifest." Option B introduces a passive and a semicolon unnecessarily. Option C adds also but keeps the full repeated subject — more verbose. Option D reshuffles to passive voice, losing the tight active structure.
3 / 20
A tech lead writes in a code review: "You can use a list or you can use a dictionary." Which rewrite best uses auxiliary ellipsis to tighten the sentence?
"You can use a list or a dictionary." is the tightest form — both the subject you and the auxiliary can use are elided after or, leaving only the contrasting noun phrase a dictionary. This is called gapping: the repeated predicate is omitted, retaining only the differing element. This pattern is ubiquitous in concise technical documentation: "Pass a string or an integer", "Set the flag to true or false". Option D retains can use in the second clause — grammatically acceptable but less elegant. Options A and C restructure unnecessarily.
4 / 20
A README instruction reads: "The setup script will install dependencies, the setup script will configure environment variables, and the setup script will start the server." Which revision applies ellipsis correctly?
"The setup script will install dependencies, configure environment variables, and start the server." is the canonical form using VP (verb phrase) ellipsis in lists. The subject "The setup script" and auxiliary "will" are stated once; the three infinitive base verbs share them across all list items. This is the standard pattern in README setup instructions: "This command will download the image, create a container, and expose port 8080." Option B repeats will redundantly. Option C uses semicolons unnecessarily and still repeats will. Option D converts to passive, which loses the active agent and is less direct for instructions.
5 / 20
In a pull request description a developer writes: "The old implementation was slow. The new implementation is fast." Which revision uses a demonstrative or comparative ellipsis to tighten the pair of sentences?
"The old implementation was slow; the new one is fast." uses the pro-form one to replace the repeated head noun implementation. This is a specific form of lexical ellipsis / substitution common in technical comparisons: "The synchronous approach blocks the thread; the asynchronous one does not", "The v1 API requires polling; the v2 one uses webhooks". The semicolon is appropriate for two closely related independent clauses in formal writing. Option B omits the auxiliary incorrectly ("the new is fast" is ungrammatical without one). Options C and D restructure awkwardly or lose the parallel contrast.
6 / 20
Sarah, a senior engineer, is drafting a Slack message to her team about a recent deployment. She wants to acknowledge the successful rollback of a problematic feature. Which of the following uses ellipsis most effectively?
Option 1 is best because it concisely summarizes the actions taken without unnecessary repetition. The other options include redundant phrases like 'everything's running smoothly' or 'which was causing issues,' which are better avoided when conveying information efficiently. Using ellipsis avoids stating the obvious and streamlines communication.
7 / 20
During a code review, David writes: 'The API returns a 404 error if the user ID isn't provided. The API then returns a 500 error.' Which revision best utilizes subject ellipsis to improve clarity?
Option 1 uses subject ellipsis to combine the two related events into a single, more concise statement. The other options either repeat information or introduce unnecessary detail. Subject ellipsis is most effective when referring back to a previously mentioned topic – in this case, the API's behavior.
8 / 20
As part of a pull request description for a new feature, Michael writes: 'We implemented authentication using OAuth 2.0. We also integrated with the payment gateway.' Which revision demonstrates the most effective use of demonstrative ellipsis?
Option 2 correctly uses an 'and' to link the two related actions, employing demonstrative ellipsis effectively. The other options either introduce unnecessary commas or rephrase the sentence in a less direct way. Demonstrative ellipsis is appropriate when joining closely related ideas.
9 / 20
During a standup meeting, Alex summarizes his progress: 'I finished the database schema design. I'm now working on implementing the API endpoints.' Which revision best demonstrates auxiliary ellipsis to streamline the update?
Option 2 utilizes auxiliary ellipsis effectively by combining 'and' with a shorter phrasing of the subsequent action. The other options either add unnecessary words or employ overly formal language that doesn't fit a standup update. Auxiliary ellipsis is useful for linking related activities concisely.
10 / 20
A developer writes in a PR description: 'The previous version had performance issues with large datasets. The current version handles larger datasets efficiently.' Which revision best uses comparative ellipsis to highlight the improvement?
Option 2 employs comparative ellipsis by using ';' to directly contrast the two versions and emphasizes the positive change. This approach is more concise than simply restating the information. Comparative ellipsis is ideal when highlighting a difference in performance or behavior.
11 / 20
Sarah, a senior engineer, is drafting a Slack message to her team about a recent deployment. She wants to acknowledge the successful rollback of a problematic feature. Which of the following uses ellipsis most effectively?
Option 1 is best because it concisely summarizes the actions taken without unnecessary repetition. The other options include redundant phrases like 'everything's running smoothly' or 'which was causing issues,' which are better avoided when conveying information efficiently. Using ellipsis avoids stating the obvious and streamlines communication.
12 / 20
During a code review, David writes: 'The API returns a 404 error if the user ID isn't provided. The API then returns a 500 error.' Which revision best utilizes subject ellipsis to improve clarity?
Option 1 uses subject ellipsis to combine the two related events into a single, more concise statement. The other options either repeat information or introduce unnecessary detail. Subject ellipsis is most effective when referring back to a previously mentioned topic – in this case, the API's behavior.
13 / 20
As part of a pull request description for a new feature, Michael writes: 'We implemented authentication using OAuth 2.0. We also integrated with the payment gateway.' Which revision demonstrates the most effective use of demonstrative ellipsis?
Option 2 correctly uses an 'and' to link the two related actions, employing demonstrative ellipsis effectively. The other options either introduce unnecessary commas or rephrase the sentence in a less direct way. Demonstrative ellipsis is appropriate when joining closely related ideas.
14 / 20
During a standup meeting, Alex summarizes his progress: 'I finished the database schema design. I'm now working on implementing the API endpoints.' Which revision best demonstrates auxiliary ellipsis to streamline the update?
Option 2 utilizes auxiliary ellipsis effectively by combining 'and' with a shorter phrasing of the subsequent action. The other options either add unnecessary words or employ overly formal language that doesn't fit a standup update. Auxiliary ellipsis is useful for linking related activities concisely.
15 / 20
A developer writes in a PR description: 'The previous version had performance issues with large datasets. The current version handles larger datasets efficiently.' Which revision best uses comparative ellipsis to highlight the improvement?
Option 2 employs comparative ellipsis by using ';' to directly contrast the two versions and emphasizes the positive change. This approach is more concise than simply restating the information. Comparative ellipsis is ideal when highlighting a difference in performance or behavior.
16 / 20
Sarah, a senior engineer, is drafting a Slack message to her team about a recent deployment. She wants to acknowledge the successful rollback of a problematic feature. Which of the following uses ellipsis most effectively?
Option 1 is best because it concisely summarizes the actions taken without unnecessary repetition. The other options include redundant phrases like 'everything's running smoothly' or 'which was causing issues,' which are better avoided when conveying information efficiently. Using ellipsis avoids stating the obvious and streamlines communication.
17 / 20
During a code review, David writes: 'The API returns a 404 error if the user ID isn't provided. The API then returns a 500 error.' Which revision best utilizes subject ellipsis to improve clarity?
Option 1 uses subject ellipsis to combine the two related events into a single, more concise statement. The other options either repeat information or introduce unnecessary detail. Subject ellipsis is most effective when referring back to a previously mentioned topic – in this case, the API's behavior.
18 / 20
As part of a pull request description for a new feature, Michael writes: 'We implemented authentication using OAuth 2.0. We also integrated with the payment gateway.' Which revision demonstrates the most effective use of demonstrative ellipsis?
Option 2 correctly uses an 'and' to link the two related actions, employing demonstrative ellipsis effectively. The other options either introduce unnecessary commas or rephrase the sentence in a less direct way. Demonstrative ellipsis is appropriate when joining closely related ideas.
19 / 20
During a standup meeting, Alex summarizes his progress: 'I finished the database schema design. I'm now working on implementing the API endpoints.' Which revision best demonstrates auxiliary ellipsis to streamline the update?
Option 2 utilizes auxiliary ellipsis effectively by combining 'and' with a shorter phrasing of the subsequent action. The other options either add unnecessary words or employ overly formal language that doesn't fit a standup update. Auxiliary ellipsis is useful for linking related activities concisely.
20 / 20
A developer writes in a PR description: 'The previous version had performance issues with large datasets. The current version handles larger datasets efficiently.' Which revision best uses comparative ellipsis to highlight the improvement?
Option 2 employs comparative ellipsis by using ';' to directly contrast the two versions and emphasizes the positive change. This approach is more concise than simply restating the information. Comparative ellipsis is ideal when highlighting a difference in performance or behavior.
What will I practise in "Ellipsis in Technical Communication"?
Practise omitting repeated words for conciseness in commit messages, PR titles, changelogs, and technical documentation. 5 advanced exercises on ellipsis.
How many exercises are in this module?
This module has 20 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.