5 exercises — how to connect ideas smoothly in technical writing: cause-and-effect, contrast, sequence, clarification, and concession transitions used in post-mortems, docs, and design documents.
Transition word quick reference
Cause → Effect: as a result, consequently, therefore, thus, this led to, which caused
Contrast: however, in contrast, on the other hand, whereas, nevertheless, yet
Sequence: first, then, next, subsequently, finally, once, after that
Addition: furthermore, moreover, in addition, also, additionally
Clarification/Example: specifically, for example, in particular, that is, namely
Concession: nevertheless, nonetheless, even so, despite this
0 / 14 completed
1 / 14
A developer writes a post-mortem report: "The database ran out of disk space. ___ the API returned 500 errors to all clients." Which transition word best connects these two sentences?
As a result expresses a cause → effect relationship: the DB filling up caused the 500 errors. This is the core transition pattern in incident reports and post-mortems — the causal chain. Other cause-effect transitions: consequently, therefore, thus, hence, which caused, leading to, this led to. Why the others fail: "However" and "In contrast" signal a contrast, not a cause. "Furthermore" signals addition — it adds more information of the same type. Pattern for post-mortems: Cause → transition → Effect. "The cache was misconfigured. As a result, all requests hit the database directly." / "Disk I/O saturated. Consequently, write latency spiked to 8 seconds." / "The deployment contained a bug. This led to elevated error rates across three services."
2 / 14
An architect writes a design document comparing two approaches: "REST APIs are easy to cache and widely understood by developers. ___, GraphQL gives clients precise control over the data they fetch." Choose the right transition.
In contrast introduces a comparison that shows a meaningful difference. The two sentences describe different capabilities of different technologies — a contrast comparison. Core contrast transitions: however, in contrast, on the other hand, conversely, whereas, while, unlike, nevertheless, yet. The choice between them: "However" — contradicts or complicates the previous point (the most common contrast marker). "In contrast" — neutral, balanced comparison (common in technical writing). "On the other hand" — weighs an alternative perspective (common in trade-off discussions). "Therefore" implies cause→result — wrong. "In addition" adds more of the same — wrong here because REST and GraphQL are being contrasted, not supplemented. "Similarly" highlights a shared quality — the opposite of what's needed. Trade-off template: "Approach A has [advantage]. However, Approach B offers [different strength]. Consequently, we recommend A for [use case], and B for [other use case]."
3 / 14
A technical writer documents a deployment process: "___ sending the deployment request, the pipeline validates the config file. ___ it builds the Docker image. ___, it pushes to the registry." Which set fills the blanks in order?
First / Secondly / Finally are sequence transitions — they mark the order of steps in a process. This is the most common pattern in technical documentation, runbooks, READMEs, and onboarding guides. Full sequence toolkit: First / To begin with → Then / Next / Secondly / After that → Finally / Lastly / Once this is done. For numbered procedures, sequence words are optional but important in prose descriptions where you can't use a numbered list. Variations in technical docs: "Once the config is validated, the pipeline proceeds to…" / "After the image is built, it is pushed to…" / "The final step involves pushing the image to the registry." Why the others fail: "Before / However / Therefore" mixes a preposition, a contrast, and a cause — no coherent sequence. "In addition / Also / Moreover" are addition markers, not sequence markers.
4 / 14
A backend developer adds a clarifying sentence in documentation: "The `retry` parameter controls how many times the request is resent on failure. ___, setting it to 0 disables all automatic retries." Choose the transition that best introduces a specific clarification or example.
Specifically narrows the focus — it introduces a concrete example, edge case, or precise detail that illustrates the preceding general statement. This pattern is constant in API docs, config references, and troubleshooting guides. The general → specific transition toolkit: specifically, for example, for instance, in particular, to illustrate, that is (i.e.), namely. When to use each: Specifically / In particular — provide a precise case or clarification. For example / For instance — give an illustrative example (may one of several). That is / In other words / i.e. — rephrase or define more clearly. Example: "The function accepts multiple formats. Specifically, it supports JSON, XML, and CSV." / "The token expires quickly. In particular, access tokens are valid for only 15 minutes." "Although" would need to introduce a contrast clause — it doesn't work as a standalone transition in this position.
5 / 14
A QA engineer writes a test summary: "The unit tests all passed. The integration tests also passed. ___, the system tests revealed a critical bug in the payment flow." Which transition correctly introduces an unexpected contrast?
Nevertheless (and its close synonym nonetheless) signals that something happened despite what was just described — a contrast where the positive setup makes the following point surprising or concerning. "Unit tests passed, integration tests passed — nevertheless, system tests found a bug." This is a classic pattern in QA reports, security audits, and code review summaries where early stages are fine but a later stage reveals an issue. The concession/contrast continuum: However — neutral contrast. Nevertheless / Nonetheless — contrast despite positive preceding context. Yet — informal, shorter version of nevertheless. Even so — similar to nevertheless, slightly more emphatic. "Furthermore" is addition — wrong. "Consequently" is cause→effect — wrong. "Meanwhile" is simultaneous timeframe — wrong. Powerful in technical communication: "The feature was thoroughly tested. Nevertheless, edge cases in production exposed three race conditions."
6 / 14
Alex, a senior developer, left this comment on a code review: 'The authentication service is returning unexpected errors. Furthermore, the database connection pool seems to be exhausted.' Which transition word best connects these two observations in Alex's feedback?
'Therefore' indicates a logical consequence – the exhaustion of the connection pool *causes* the unexpected errors. 'However' suggests a contrast, which isn't present here. 'Besides' is an unnecessary addition and 'moreover' would be redundant given the flow. Using 'moreover' would imply that the database issue is in addition to something already established – it's not.
7 / 14
Maria, a product manager, drafted this Slack message: 'We're seeing high latency on the user profile API. Initially, we thought it was due to inefficient queries, but recent monitoring indicates network congestion is the primary bottleneck.' Which transition word best connects these two pieces of information in Maria's message?
'Although' signals a contrast or qualification – the initial assumption about inefficient queries was incorrect. The message is presenting an updated understanding of the root cause. 'Instead' implies replacement and doesn't fit the context of revising a hypothesis, while 'as well as' would be redundant and 'in addition' is too formal for Slack communication.
8 / 14
Alex, a senior developer, left this comment on a code review: 'The authentication service is returning unexpected errors. Furthermore, the database connection pool seems to be exhausted.' Which transition word best connects these two observations in Alex's feedback?
'Therefore' indicates a logical consequence – the exhaustion of the connection pool *causes* the unexpected errors. 'However' suggests a contrast, which isn't present here. 'Besides' is an unnecessary addition and 'moreover' would be redundant given the flow. Using 'moreover' would imply that the database issue is in addition to something already established – it's not.
9 / 14
Maria, a product manager, drafted this Slack message: 'We're seeing high latency on the user profile API. Initially, we thought it was due to inefficient queries, but recent monitoring indicates network congestion is the primary bottleneck.' Which transition word best connects these two pieces of information in Maria's message?
'Although' signals a contrast or qualification – the initial assumption about inefficient queries was incorrect. The message is presenting an updated understanding of the root cause. 'Instead' implies replacement and doesn't fit the context of revising a hypothesis, while 'as well as' would be redundant and 'in addition' is too formal for Slack communication.
10 / 14
John, a junior developer, is writing a PR description for a new feature. He writes: 'We've implemented the search functionality. It now returns results based on user queries. The API endpoint has been updated to handle these requests.' Which transition word best connects these two sentences to improve clarity and flow?
'Furthermore' logically adds more detail about the API update after introducing the search functionality. 'Therefore' implies a conclusion that isn't present, 'However' presents a contrast, and 'Initially' suggests a starting point without adding to the description. This demonstrates how transition words can build upon ideas.
11 / 14
Sarah, a QA engineer, is writing a test summary: 'The smoke tests passed successfully. The API responded with 200 OK for all requests. ___ the performance tests revealed significant latency under load.' Which transition word best connects these two sentences?
'Nevertheless' indicates a contrast between the passing smoke tests and the failing performance tests. This highlights an unexpected outcome that needs further investigation. 'Consequently' implies a direct cause-and-effect relationship which isn't necessarily true here, and 'Subsequently' suggests a chronological order, while 'Besides' introduces additional information without establishing a connection.
12 / 14
David, a backend developer, is documenting an API endpoint: 'The endpoint accepts a user ID as input. If the user ID does not exist, the server returns a 404 error.' Which transition word best completes this explanation?
'As a result' logically connects the scenario of an invalid user ID to the resulting 404 error. This demonstrates how transition words can clearly explain cause and effect relationships within technical documentation. The other options introduce irrelevant contrasts or additions.
13 / 14
Emily, a product manager, is drafting an email to the development team: 'We're investigating a spike in error rates. The initial analysis pointed towards a memory leak in the caching layer. ___ we've identified a race condition in the database access logic.' Which transition word best connects these two sentences?
'Indeed' strengthens and expands upon the previous statement about the memory leak. It suggests a confirmed finding that warrants further attention. Using 'However' would imply a contradiction or problem, which isn't the intended flow here; 'Therefore' is too conclusive at this stage, and 'Moreover' simply adds another point without connecting it to the existing information.
14 / 14
Ben, a code reviewer, writes: 'The database connection pool is consistently maxed out. This appears to be caused by inefficient queries in the user authentication service.' Which transition word best connects these two sentences?
'Therefore' indicates a logical conclusion – that the maxed-out connection pool *is caused by* the inefficient queries. This clearly establishes a cause-and-effect relationship, which is crucial for effective code reviews and debugging discussions. The other options introduce alternative explanations or irrelevant information.
What will I practise in "Transition Words & Cohesion — IT English Grammar Exercise"?
Practice transition words and cohesion in technical English: cause-effect, contrast, sequence, clarification, and concession transitions.
How many exercises are in this module?
This module has 14 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.