5 exercises — passive for processes, error messages, API docs, changelogs, and choosing active vs passive.
0 / 20 completed
1 / 20
Which sentence is most appropriate for a process documentation step?
Passive voice ("is validated") is preferred in process documentation when the focus is on what happens to the object, not who performs the action. This is standard in technical specifications and system design docs.
2 / 20
Choose the better error message for an API response:
Passive voice in error messages ("was not found") is appropriate because it describes a system state without blaming the user. It is precise and professional.
3 / 20
Which instruction is clearest for a user-facing guide?
Active imperative voice ("Click Save") is clearest in user-facing instructions. Passive constructions add unnecessary complexity and distance in procedural guides.
4 / 20
Choose the standard changelog entry format:
Changelogs use the passive participle without an auxiliary verb: "Memory leak fixed." This is the conventional format used by GitHub, npm, and most open-source projects — concise and agent-agnostic.
5 / 20
Which sentence from an API reference is written in the preferred style?
API documentation conventionally uses passive ("is returned") to describe what the endpoint produces, since the caller is interested in the response, not the implementation agent. Both passive and "Returns a JSON object..." (active omitting subject) are acceptable.
6 / 20
John was assigned the task of debugging the authentication service. The system automatically initiated a rollback after detecting an anomaly in database writes. Which sentence best describes this event for a process documentation step?
This question focuses on clarity in process documentation. The passive voice allows us to highlight *what happened* without focusing on the actor (John). Option A is the most concise and objective, suitable for a step-by-step guide. Options B and C introduce unnecessary focus on the individual, while option D is too vague.
7 / 20
Sarah sent the following Slack message to the team: 'The API endpoint /users/{user_id} returned a 500 error when trying to retrieve user profiles. The server logs indicate a timeout issue.' Which phrase demonstrates the most effective use of passive voice in this context?
In Slack communication, it's crucial to convey information clearly and concisely. Using the passive voice ('a timeout issue was detected') shifts the emphasis from Sarah's action (reporting) to the *problem* itself – the core of the message. Options A is too brief, B implies Sarah didn't find it, C is incorrect, and D focuses on the logs rather than the error.
8 / 20
Mark wrote this PR description: 'The database schema was updated to support new user roles. The migration script was executed successfully.' Which sentence demonstrates a better use of passive voice for a PR description?
PR descriptions should primarily focus on *what changed* and its outcome. The passive voice emphasizes the action performed by the system (the schema update and script execution), which is more relevant to reviewers than who initiated it. Option A provides a clear summary of the change, while options B, C, and D are overly focused on the individual.
9 / 20
You're documenting the response from the payment gateway API. The following is a possible entry for your changelog: 'The transactionId field was added to the response payload.' Which phrasing exemplifies the most appropriate use of passive voice in this scenario?
Changelog entries should objectively describe changes. The passive voice ('the transactionId field was added') avoids assigning agency and focuses on the technical modification made to the API's output. Options A and B are too conversational, while C is less precise, and D is simply a statement of fact.
10 / 20
David reviewed code that included the following line: 'The data was validated against predefined rules.' Which sentence demonstrates the most effective use of passive voice in an API reference for a validation step?
In API references, it's crucial to describe *how* something is done. The passive voice ('predefined rules were used') clearly explains the mechanism of validation without specifying who or what performs the action. Options A is too general, B implies an active agent, and C and D are less precise descriptions of the process.
11 / 20
John was assigned the task of debugging the authentication service. The system automatically initiated a rollback after detecting an anomaly in database writes. Which sentence best describes this event for a process documentation step?
This question focuses on clarity in process documentation. The passive voice allows us to highlight *what happened* without focusing on the actor (John). Option A is the most concise and objective, suitable for a step-by-step guide. Options B and C introduce unnecessary focus on the individual, while option D is too vague.
12 / 20
Sarah sent the following Slack message to the team: 'The API endpoint /users/{user_id} returned a 500 error when trying to retrieve user profiles. The server logs indicate a timeout issue.' Which phrase demonstrates the most effective use of passive voice in this context?
In Slack communication, it's crucial to convey information clearly and concisely. Using the passive voice ('a timeout issue was detected') shifts the emphasis from Sarah's action (reporting) to the *problem* itself – the core of the message. Options A is too brief, B implies Sarah didn't find it, C is incorrect, and D focuses on the logs rather than the error.
13 / 20
Mark wrote this PR description: 'The database schema was updated to support new user roles. The migration script was executed successfully.' Which sentence demonstrates a better use of passive voice for a PR description?
PR descriptions should primarily focus on *what changed* and its outcome. The passive voice emphasizes the action performed by the system (the schema update and script execution), which is more relevant to reviewers than who initiated it. Option A provides a clear summary of the change, while options B, C, and D are overly focused on the individual.
14 / 20
You're documenting the response from the payment gateway API. The following is a possible entry for your changelog: 'The transactionId field was added to the response payload.' Which phrasing exemplifies the most appropriate use of passive voice in this scenario?
Changelog entries should objectively describe changes. The passive voice ('the transactionId field was added') avoids assigning agency and focuses on the technical modification made to the API's output. Options A and B are too conversational, while C is less precise, and D is simply a statement of fact.
15 / 20
David reviewed code that included the following line: 'The data was validated against predefined rules.' Which sentence demonstrates the most effective use of passive voice in an API reference for a validation step?
In API references, it's crucial to describe *how* something is done. The passive voice ('predefined rules were used') clearly explains the mechanism of validation without specifying who or what performs the action. Options A is too general, B implies an active agent, and C and D are less precise descriptions of the process.
16 / 20
John was assigned the task of debugging the authentication service. The system automatically initiated a rollback after detecting an anomaly in database writes. Which sentence best describes this event for a process documentation step?
This question focuses on clarity in process documentation. The passive voice allows us to highlight *what happened* without focusing on the actor (John). Option A is the most concise and objective, suitable for a step-by-step guide. Options B and C introduce unnecessary focus on the individual, while option D is too vague.
17 / 20
Sarah sent the following Slack message to the team: 'The API endpoint /users/{user_id} returned a 500 error when trying to retrieve user profiles. The server logs indicate a timeout issue.' Which phrase demonstrates the most effective use of passive voice in this context?
In Slack communication, it's crucial to convey information clearly and concisely. Using the passive voice ('a timeout issue was detected') shifts the emphasis from Sarah's action (reporting) to the *problem* itself – the core of the message. Options A is too brief, B implies Sarah didn't find it, C is incorrect, and D focuses on the logs rather than the error.
18 / 20
Mark wrote this PR description: 'The database schema was updated to support new user roles. The migration script was executed successfully.' Which sentence demonstrates a better use of passive voice for a PR description?
PR descriptions should primarily focus on *what changed* and its outcome. The passive voice emphasizes the action performed by the system (the schema update and script execution), which is more relevant to reviewers than who initiated it. Option A provides a clear summary of the change, while options B, C, and D are overly focused on the individual.
19 / 20
You're documenting the response from the payment gateway API. The following is a possible entry for your changelog: 'The transactionId field was added to the response payload.' Which phrasing exemplifies the most appropriate use of passive voice in this scenario?
Changelog entries should objectively describe changes. The passive voice ('the transactionId field was added') avoids assigning agency and focuses on the technical modification made to the API's output. Options A and B are too conversational, while C is less precise, and D is simply a statement of fact.
20 / 20
David reviewed code that included the following line: 'The data was validated against predefined rules.' Which sentence demonstrates the most effective use of passive voice in an API reference for a validation step?
In API references, it's crucial to describe *how* something is done. The passive voice ('predefined rules were used') clearly explains the mechanism of validation without specifying who or what performs the action. Options A is too general, B implies an active agent, and C and D are less precise descriptions of the process.
What will I practise in "Passive Voice in Technical Documentation — Grammar Exercise"?
Learn when to use passive voice in API docs, error messages, changelogs, and process documentation, and when active voice is clearer.
How many exercises are in this module?
This module has 20 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.