Zero and First Conditionals in Technical Documentation
0 / 14 completed
1 / 14
Which sentence uses a zero conditional correctly to describe a system behaviour?
Option B is correct. The zero conditional uses simple present in both clauses: "if + present, present". It describes universal, always-true behaviours — laws of the system, not predictions. "If memory usage exceeds 90%, the OOM killer terminates a process" is a factual statement about Linux kernel behaviour that is always true. Option A uses "will" in the result clause, which shifts it to a first conditional (a prediction for a specific future event). Option C puts "will" in the condition clause, which is always wrong in conditionals. Option D mixes past in the condition with present in the result. In system documentation, use zero conditional for invariant behaviours.
2 / 14
A deployment guide reads: "If you push to the main branch, the CI pipeline __ a new staging deployment." Should the blank use zero or first conditional form?
Option A is correct. Use the zero conditional ("triggers") here because the CI pipeline behaviour is not a prediction — it is a configured, deterministic system rule. Every push to main always triggers the pipeline; this is not contingent on circumstances. The zero conditional is more authoritative in documentation: it states a fact. The first conditional "will trigger" introduces a hint of uncertainty or personal prediction that is inappropriate when describing a CI/CD configuration that the reader can rely on absolutely. Reserve the first conditional for warnings, recommendations, and genuinely context-dependent outcomes.
3 / 14
Which sentence correctly uses the first conditional in a security warning?
Option B is correct. The first conditional uses "if + present simple, will + infinitive". It describes a specific, realistic future scenario and its likely consequence — ideal for security warnings where the risk is real but not universal. Option A is the zero conditional ("attackers gain access") — this is also defensible if the vulnerability is a guaranteed outcome, but the first conditional is preferred in warnings because "will gain" carries stronger urgency. Option C incorrectly uses "will" in the condition clause. Option D mixes past condition with "will" result, which is a second conditional structure used for hypotheticals, not real security risks.
4 / 14
A README has both these sentences. Which conditional type has been used correctly for each?
"If the PORT variable is not set, the server uses port 8080." "If you run the tests with --coverage, a report will be generated in coverage/."
Option C is correct. The first sentence uses the zero conditional correctly: the fallback to port 8080 is an invariant default — it always happens, no exceptions. The second sentence uses the first conditional correctly: running with --coverage is a specific deliberate action with a predictable future result ("will be generated"). This distinction is common in READMEs — system defaults are described with zero conditionals (always true), while optional commands and their effects are described with first conditionals (if you do this specific thing, here is what will happen).
5 / 14
A developer writes this error message documentation: "If the API key is invalid, you will receive a 401 Unauthorized error." A reviewer suggests changing "will receive" to "receive". Who is correct?
Option B is correct. For guaranteed, deterministic API behaviours — like error codes returned for invalid inputs — the zero conditional is more authoritative and conventional. "If the key is invalid, you receive a 401" reads as a system fact. "You will receive" hedges slightly, as if the outcome depends on circumstances. Major API documentation (Stripe, Twilio, GitHub) consistently uses the zero conditional for error response tables and conditional behaviour descriptions. The first conditional "will receive" is appropriate when the outcome involves a process with some variability ("if you retry, the request will eventually succeed").
6 / 14
Code Review Comment: 'When the database connection fails, the application automatically retries.' Which conditional best describes this behavior?
This scenario describes a *result* – the automatic retry. The first option directly reflects this cause-and-effect relationship using a zero conditional. Options B and C rephrase the same idea but introduce unnecessary complexity. Option D incorrectly changes the sentence structure.
7 / 14
Slack Message: 'I'm seeing intermittent errors with the payment processing service. It seems to fail if the API key is missing.' What conditional form should be used to accurately convey this issue?
This describes a general truth – a recurring event. The first option uses the zero conditional correctly to state this habitual occurrence. Options B and C alter the sentence structure unnecessarily. Option D incorrectly suggests a causal link.
8 / 14
Code Review Comment: 'When the database connection fails, the application automatically retries.' Which conditional best describes this behavior?
This scenario describes a *result* – the automatic retry. The first option directly reflects this cause-and-effect relationship using a zero conditional. Options B and C rephrase the same idea but introduce unnecessary complexity. Option D incorrectly changes the sentence structure.
9 / 14
Slack Message: 'I'm seeing intermittent errors with the payment processing service. It seems to fail if the API key is missing.' What conditional form should be used to accurately convey this issue?
This describes a general truth – a recurring event. The first option uses the zero conditional correctly to state this habitual occurrence. Options B and C alter the sentence structure unnecessarily. Option D incorrectly suggests a causal link.
10 / 14
Code Review Comment: 'When the database connection fails, the application automatically retries.' Which conditional best describes this behavior?
This scenario describes a *result* – the automatic retry. The first option directly reflects this cause-and-effect relationship using a zero conditional. Options B and C rephrase the same idea but introduce unnecessary complexity. Option D incorrectly changes the sentence structure.
11 / 14
Slack Message: 'I'm seeing intermittent errors with the payment processing service. It seems to fail if the API key is missing.' What conditional form should be used to accurately convey this issue?
This describes a general truth – a recurring event. The first option uses the zero conditional correctly to state this habitual occurrence. Options B and C alter the sentence structure unnecessarily. Option D incorrectly suggests a causal link.
12 / 14
PR Description: 'If the build fails, the CI system will automatically roll back to the previous successful version.' Should the blank use zero or first conditional form?
This describes a standard automated rollback procedure. The first conditional is suitable here because it clearly outlines what *will* happen – the action taken *if* the build fails. Options A and D are correct but less natural phrasing; option B is overly verbose.
13 / 14
Sarah is writing a Slack message about a new feature. 'If we implement this change, the user interface will be significantly faster.' Which conditional form best expresses this potential outcome? Consider whether the relationship between the implementation and the speed improvement is guaranteed or merely predicted.
The first conditional is appropriate here because Sarah is describing a likely consequence of implementing the change. The 'if' clause describes a condition that *could* happen, and the 'then' clause describes the resulting action. Using 'will' correctly reflects this predicted outcome. Options zero, two and three are incorrect as they relate to different tenses and scenarios.
14 / 14
David is drafting a PR description for a new API endpoint: 'If the request body is missing a required field, the server will return an error code of 422.' Which conditional form correctly conveys this expected behavior? Focus on whether the error is a predictable result of a specific condition.
The first conditional is the most accurate here. The statement describes a predictable consequence – an error code will be returned *if* the request body is missing a required field. This represents a cause-and-effect relationship that's typical of API design. Zero and three conditionals are incorrect because they don't describe a specific, triggered response; second conditional suggests a hypothetical situation.
What will I practise in "Zero and First Conditionals in Technical Documentation — Grammar Exercise"?
Practice using zero and first conditionals correctly in system documentation, API references, READMEs, and security warnings.
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.