5 exercises — choosing the right connectors (however, therefore, consequently, given that, provided that, unless) in API docs and architecture decision records.
0 / 5 completed
1 / 5
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 / 5
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 / 5
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 / 5
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 / 5
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.