5 exercises — using do/does/did for emphasis to affirm facts and correct false assumptions in reviews and reports.
Key patterns:
does/do/did + base verb — emphasis or correction, not a question or negative
The main verb after emphatic do stays in its base form (does handle, not does handles)
Match the auxiliary to tense and subject: does (3rd sg. present), do (other present), did (any past)
Commonly used to contradict a doubted or false claim in reviews
0 / 13 completed
1 / 13
A reviewer questions whether error handling exists. The engineer replies in the pull request. Which response correctly uses emphatic "do" to affirm and correct the assumption?
Emphatic "do" (here, does handle) is used to stress and affirm a fact that has been doubted or contradicted, adding rhetorical emphasis that a plain present-tense verb lacks. This is distinct from the auxiliary "do" used in questions and negatives — here it functions purely for emphasis, common in code review replies that push back on an incorrect assumption. A plain statement (option A) is grammatically correct but lacks the corrective force needed to directly counter the reviewer's doubt.
2 / 13
A postmortem draft is being reviewed, and a colleague claims the on-call engineer never received the page. Which sentence uses emphatic "do" to assert the opposite, based on evidence?
"Did receive" uses the emphatic auxiliary did before the base form of the verb specifically to contradict a false claim ("never received"). This structure — did + base verb — is reserved for emphasis or contrast in past tense, whereas the plain past tense (option B) merely states the fact without emphasizing the correction. Emphatic "do/does/did" is one of the few grammatical tools in English dedicated purely to stress rather than tense or aspect.
3 / 13
Which sentence is grammatically correct as an example of emphatic "do" used for contrast in a technical discussion?
After emphatic "does", the main verb must appear in its base form (invalidate), not the third-person singular (invalidates), past tense (invalidated), or -ing form (invalidating). This mirrors the rule for all auxiliary "do" constructions: the auxiliary carries the tense and agreement information, so the following verb stays uninflected. Getting this verb form wrong is a common error even among advanced learners when adding emphasis.
4 / 13
A team lead writes in a design review: "I know the diagram looks like the service is stateless, but it _____ maintain in-memory session state, which is exactly the issue we need to address." Which phrase fits, using emphatic "do" for contrast with an implied assumption?
Since the subject is it (third person singular) and the context is present tense ("looks like... is"), the correct emphatic auxiliary is "does", followed by the base form maintain. Do would be used with plural or first/second-person subjects; did would shift the sentence into past tense, contradicting the present-tense framing; doing is not a valid auxiliary form at all.
5 / 13
In a stand-up, a developer says: "I _____ push the fix yesterday, even though the ticket still shows it as open — someone probably forgot to close it." Which emphatic form correctly fits the past-tense context?
"Did" is the correct emphatic auxiliary for past tense with any subject, including I, and it forces the following verb into its base form (push), which matches the sentence. Do and does would incorrectly shift the sentence to present tense, and done is a past participle that cannot function as an emphatic auxiliary at all — it would require a form of "have" (e.g., "I have done...").
6 / 13
During a code review of the user authentication module, Sarah noticed that the server-side validation was missing. Mark responded: 'But it *should* be validating against the database before returning a JWT!' What best demonstrates emphatic 'do' in this scenario?
Mark's response isn't simply stating a fact; he's using 'do' to strongly suggest what the code *should* be doing. This highlights an expected behavior that wasn't implemented, correcting a perceived omission. The incorrect options either accept the assumption or don't use 'do' effectively for this corrective purpose.
7 / 13
During a code review of the user authentication module, Sarah noticed that the server-side validation was missing. Mark responded: 'But it *should* be validating against the database before returning a JWT!' What best demonstrates emphatic 'do' in this scenario?
Mark's response isn't simply stating a fact; he's using 'do' to strongly suggest what the code *should* be doing. This highlights an expected behavior that wasn't implemented, correcting a perceived omission. The incorrect options either accept the assumption or don't use 'do' effectively for this corrective purpose.
8 / 13
During a code review of the user authentication module, Sarah noticed that the server-side validation was missing. Mark responded: 'But it *should* be validating against the database before returning a JWT!' What best demonstrates emphatic 'do' in this scenario?
Mark's response isn't simply stating a fact; he's using 'do' to strongly suggest what the code *should* be doing. This highlights an expected behavior that wasn't implemented, correcting a perceived omission. The incorrect options either accept the assumption or don't use 'do' effectively for this corrective purpose.
9 / 13
David: 'The API response indicates a 404 error for this endpoint. It's clearly not working.'
Mark needs to respond emphatically to correct the assumption. Which of the following options best reflects that?
Emphatic 'do' here corrects an assumption about the API's behavior. The core issue is that Mark believes the endpoint *should* return a successful response (200 OK). The incorrect options either shift blame or introduce irrelevant details – outdated documentation or routing problems – obscuring the immediate point that the endpoint isn't behaving as expected based on its intended design. This highlights the importance of specifying what *should* happen in technical discussions.
10 / 13
Lena (Slack message): 'I've deployed the new version, but I'm still seeing high latency. It really shouldn't be taking this long to process a simple request.'
Which response from Ben best uses emphatic 'do' to address Lena's concern?
Lena's statement expresses an expectation – that the request *should* have low latency. Ben uses emphatic 'do' to directly challenge this assumption by stating what *should* be true based on the system design and expected performance metrics. The other options offer troubleshooting steps or acknowledge the problem without addressing the underlying expectation, making them less effective for a corrective statement.
11 / 13
Project Lead (PR description): 'The database schema has been updated. The system *should* now handle concurrent transactions more efficiently.'
Which of the following options best completes this sentence using emphatic 'do'?
Here, the Project Lead is stating a desirable outcome – improved concurrency handling. Using 'do' emphasizes what *should* happen as a result of the schema update. The other options introduce supplementary information or caveats that don't directly address the core assertion about the expected behavior. Focusing on what *should* be true is key to this particular use case.
12 / 13
Alex (Standup update): 'I've implemented the new retry logic for failed API calls. I *did* push it yesterday, but the ticket still shows as open.'
Which response from Chloe best utilizes emphatic 'do' to clarify the situation?
Alex is highlighting a discrepancy between his action (pushing the code) and the ticket's status. Using emphatic 'do' corrects the assumption that he completed all necessary steps after pushing – specifically updating the ticket. This is a common scenario where someone forgets a procedural step, and emphasizing what *should* have happened clarifies responsibility and streamlines communication.
13 / 13
Sarah: 'The microservice needs to handle approximately 10,000 requests per second. It *should* be able to manage this load without degradation.'
Which response from Tom best utilizes emphatic 'do' in this context?
Sarah asserts a key requirement – the microservice *should* handle 10,000 requests per second. Tom uses emphatic 'do' to reinforce this expectation by stating what the architecture *should* enable, acknowledging that there might be caveats but maintaining the core functional capability. The other options introduce monitoring or SLAs, which are important considerations, but don't directly address Sarah's initial assertion about performance.
What will I practise in "Emphatic Do in Technical English — IT English Grammar Exercise"?
Practice emphatic do/does/did for asserting and correcting claims in code reviews, postmortems, and design reviews. 5 exercises, Advanced level.
How many exercises are in this module?
This module has 13 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.