5 exercises — choosing the right connectors (however, therefore, consequently, given that, provided that, unless) in API docs and architecture decision records.
0 / 17 completed
1 / 17
An ADR reads: "We considered Redis for session storage. _____, its operational complexity outweighed the performance gains for our current scale." Which connector signals contrast?
"However" is an adversative connector — it introduces a contrasting or opposing point. The sentence moves from a positive consideration (Redis was considered) to a negative finding (operational complexity), which is a classic contrast. "Therefore" and "Consequently" introduce results or conclusions, not contrasts. "Given that" introduces a reason or premise. In technical documentation, "however" is the standard connector for pivot sentences that introduce a complication or caveat after an initial statement.
2 / 17
API documentation states: "The rate limit resets every 60 seconds. _____, if your application exceeds 100 requests per minute, subsequent requests will return HTTP 429." Which connector introduces a logical consequence?
"Therefore" is a causal connector that introduces a logical conclusion or result derived from the preceding statement. The rate limit rule is the cause; the 429 response is the consequence. "Consequently" would also be correct here. "However" signals contrast, not causation. "Unless" introduces a conditional exception. "Provided that" introduces a condition for something to be true. In API documentation, "therefore" and "consequently" are preferred for stating the technical implications of a rule.
3 / 17
A README states: "The webhook will retry delivery up to five times _____ the endpoint returns a 2xx status code." Which connector introduces the condition that stops retries?
"Unless" means "except if" or "if not" — it introduces a negative condition: retries continue in all circumstances except when a 2xx is returned. This is essential in technical documentation for describing exception conditions and stop criteria. "However" signals contrast. "Therefore" and "consequently" signal results. Note that "unless" clauses do not use "not": say "unless the endpoint returns" (NOT "unless the endpoint does not return"). This is a common error in technical writing.
4 / 17
An architecture decision record states: "_____ we are deploying to multiple regions, we must implement a distributed tracing solution." Which connector correctly introduces the premise?
"Given that" introduces a known premise or accepted fact that logically necessitates the following action. It is equivalent to "because" or "since" but more formal — ideal for ADRs and design documents where you state the context before the decision. The multi-region deployment is the established fact; the tracing requirement is the conclusion. "Consequently" introduces a result but does not introduce a premise. "However" introduces contrast. In formal technical writing, "given that" is preferred over "because" when the reason is a shared, established context.
5 / 17
API documentation reads: "The endpoint will accept the request _____ the Authorization header contains a valid bearer token." Which connector introduces a positive requirement?
"Provided that" (also: "providing that") introduces a positive condition that must be satisfied for the main clause to hold true. It means "on the condition that" or "as long as". This makes it perfect for documenting API requirements and access conditions. "Unless" introduces a negative condition (if not). "Given that" introduces a known fact, not a requirement. "However" introduces contrast. In API documentation, "provided that" is the precise choice when specifying the condition under which the system will perform an action.
6 / 17
You are writing a Slack message to inform your team about a new feature: 'We've deployed the updated payment processing service. As long as the API key is valid, transactions will be processed smoothly.' Which connector best conveys this condition?
'As long as' is a standard discourse connector that introduces a necessary condition for the feature to function correctly. It clearly states what must be true for the system to operate as intended. The other options introduce contrasting information or additional points, which aren't relevant to this conditional statement.
7 / 17
You are writing a Slack message to inform your team about a new feature: 'We've deployed the updated payment processing service. As long as the API key is valid, transactions will be processed smoothly.' Which connector best conveys this condition?
'As long as' is a standard discourse connector that introduces a necessary condition for the feature to function correctly. It clearly states what must be true for the system to operate as intended. The other options introduce contrasting information or additional points, which aren't relevant to this conditional statement.
8 / 17
David from QA just left this comment on your PR: 'The response time is significantly slower after the database migration. _____ , we need to investigate further and potentially rollback.' Which discourse connector best reflects David's concern?
'However' signals a contrast or contradiction – David is pointing out an unexpected negative outcome (slow response time) compared to the expected result after the migration. 'Consequently' and 'Therefore' would imply a direct cause-and-effect relationship that isn't explicitly stated; 'Subsequently' simply denotes order, not opposition.
9 / 17
In a Slack message to your team regarding a recent deployment, you write: 'We've upgraded the authentication service. _____ , users will now be required to use multi-factor authentication for all logins.' What discourse connector effectively highlights the new requirement?
'Consequently' clearly establishes a direct result of the upgrade – requiring MFA. 'Moreover' and 'Furthermore' would add additional points without establishing a causal link; 'Nevertheless' presents a contradictory statement that isn't appropriate here.
10 / 17
Sarah from the dev team sent this PR description: 'We've implemented a new caching layer. However, we're still seeing occasional inconsistencies with the backend data. We need to investigate further before deploying to production.' Which discourse connector best highlights the contrasting information here?
The word 'however' directly contrasts Sarah's positive statement about the caching layer with her observation of data inconsistencies. It signals a shift in focus and introduces a problem that requires attention. The other options – 'therefore,' 'consequently,' and 'furthermore' – don't represent this direct opposition of ideas.
11 / 17
You are drafting a Slack message to announce a change in the deployment pipeline: 'We've upgraded the monitoring system. As a result, all deployments will now be automatically rolled back if any critical metrics exceed predefined thresholds.' Which discourse connector best indicates this outcome?
'As a result' explicitly demonstrates that the upgrade to the monitoring system *caused* the automatic rollbacks. This signifies a direct impact and is a common pattern in technical communication when describing changes and their effects. The other options – 'in addition,' 'for instance,' and 'despite' – do not establish this causal relationship.
12 / 17
Ben, a junior developer, left this comment in a code review: 'The function handles null values. To avoid unexpected errors, we should add explicit checks for null before performing calculations.' Which discourse connector best expresses the reason or justification for adding the null checks?
'To avoid' clearly states the purpose of the null checks – preventing potential errors. This is a standard way to justify technical decisions and highlight the desired outcome. Options like 'in contrast,' 'for instance,' and 'instead' would not accurately convey this preventative reasoning.
13 / 17
John from the infrastructure team sent this update: 'We've migrated the database to PostgreSQL. Consequently, query performance has improved significantly.' Which discourse connector best indicates a result?
The word 'Consequently' directly signals that the improved query performance is *because of* the migration. The other options introduce contrasting ideas or unrelated issues. Understanding this causal relationship is key to correctly using discourse connectors.
14 / 17
Maria, a senior developer, wrote this comment in a code review: 'The API endpoint returns data in JSON format. Furthermore, the response includes pagination information to handle large datasets.' Which discourse connector best indicates an additional piece of information?
'Furthermore' explicitly adds related information to the existing statement about JSON and pagination. The other options present conflicting suggestions or alternative approaches, not adding to the original point.
15 / 17
David, a junior developer, posted this message in a Slack channel: 'We've implemented a new feature flag. Given that it's currently disabled for all users, we need to thoroughly test its functionality before enabling it.' Which discourse connector best introduces a condition?
'Because' clearly establishes a conditional relationship – the need to test stems from the fact that the feature flag is disabled. The other options present alternative motivations or actions without introducing a condition.
16 / 17
Emily sent this PR description: 'We've updated the logging service. Considering that it now captures detailed metrics, we'll need to adjust our alerting thresholds.' Which discourse connector best introduces a recommendation based on new information?
'As a result' indicates that the recommendation (monitoring) is driven by the increased detail in the logging service. The other options suggest alternative actions or consequences unrelated to the new feature.
17 / 17
Michael left this comment on a code review: 'The authentication module uses OAuth 2.0. To ensure security, we should implement strict access controls.' Which discourse connector best indicates a necessary step?
'Since' establishes a causal link – the risk of unauthorized access *necessitates* implementing strict access controls. The other options suggest alternative approaches or potential drawbacks that don't address the core security concern.
What will I practise in "Discourse Connectors in Technical Documentation | CoderSlingo"?
Practise however, therefore, consequently, given that, provided that, and unless in API docs and ADRs. 5 exercises.
How many exercises are in this module?
This module has 17 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.