5 exercises — choosing the right connector in API docs, changelogs, postmortems, and ADRs.
0 / 5 completed
1 / 5
Choose the correct word to complete this API documentation sentence:
"_____ the latency was higher than expected, overall throughput improved by 18%."
Although is a subordinating conjunction that introduces a dependent clause with a full subject + verb structure (the latency was higher). Despite is a preposition and must be followed by a noun phrase or gerund, not a clause — e.g., despite the higher latency or despite latency being higher. However and Nevertheless are adverbs, not conjunctions; they cannot join clauses and require a semicolon or new sentence. IT examples: "Although the patch reduced memory usage, response times increased." / "Although the API is deprecated, it remains in use by legacy clients."
2 / 5
A changelog entry reads:
"The new caching layer reduced database load by 40%. _____, peak-hour query times remain above the SLA threshold."
Which connector is correct?
However signals contrast — the second sentence contradicts or qualifies the first. Therefore, Consequently, and Furthermore all imply a logical consequence or addition, which is the opposite of what is needed here. In technical writing, "however" is the standard adverbial connector for contrast between two related but opposing facts. Placement note: as a sentence adverb, "however" is followed by a comma. It can also appear mid-sentence with commas: "Peak-hour times, however, remain above the SLA threshold." Do not confuse with "although", which joins clauses within one sentence.
3 / 5
An Architecture Decision Record compares two deployment strategies:
"A monolithic deploy requires a full-service restart, _____ a blue-green strategy allows zero-downtime switchover."
Which word is most appropriate in formal technical documentation?
Whereas is the preferred choice in formal technical documents such as ADRs, RFCs, and design specs because it is explicitly contrastive and carries no temporal ambiguity. While is grammatically acceptable but can be read as temporal ("at the same time"), which may introduce ambiguity in architectural prose. But and yet are coordinating conjunctions suitable for informal writing but considered too colloquial for ADRs and formal specs. Rule of thumb: in technical comparisons, prefer whereas when the contrast is the primary message. Example: "The REST endpoint returns XML, whereas the GraphQL endpoint returns JSON."
4 / 5
Complete this postmortem summary sentence with the correct conjunction and punctuation:
"The failover completed successfully _____ data loss was minimal."
", and" is correct here because it joins two independent clauses that are both positive outcomes and logically related — the second clause adds information rather than contrasting it. "The failover completed successfully, and data loss was minimal." ", however" placed after the subject of the second clause would require the structure: "The failover completed successfully; data loss, however, was minimal." — but that changes the meaning to imply contrast. ", therefore" would imply the second event caused the first, which is reversed logic. Postmortem writing tip: use and for parallel positive findings; use however for unexpected negatives after a positive.
5 / 5
A risk section in an RFC states:
"The proposed migration path has been tested in staging environments. _____, production traffic patterns may expose edge cases not seen during testing."
Which connector best fits formal RFC prose?
Nevertheless is the most formal option and the standard choice in RFCs, technical proposals, and engineering specs. It concedes the preceding point while introducing a counterpoint. Even so and Nonetheless (not listed) are near-synonyms but slightly less formal. Still is grammatically valid but more common in spoken English and informal writing. Anyway is informal and dismissive — never appropriate in risk analysis. Formal register ladder (most → least formal): Nevertheless > Nonetheless > Even so > Still. In IETF-style RFCs and Google Design Docs, "nevertheless" or "nonetheless" are the accepted conventions for acknowledging risks after mitigation.
What will I practise in "Conjunctions in Technical Writing | Grammar Exercises"?
Practice using although, despite, however, therefore, and whereas correctly in API docs, changelogs, postmortems, and ADRs.
How many exercises are in this module?
This module has 5 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.