Intermediate
Grammar
#pronouns
#clarity
#technical-writing
Pronoun Clarity in Technical Writing
5 exercises — identifying and fixing ambiguous pronouns (it, this, they, that) in documentation, incident reports, and code comments.
0 / 29 completed
1 / 29
A PR description reads: "The service calls the database and then it returns a response. It logs the result." What is the problem with this sentence?
Option B is correct. When a sentence contains multiple possible referents (the service, the database), the pronoun "it" creates ambiguity. Readers must guess — and in technical writing, guessing is a defect. Fix: restate the noun. "The service calls the database and then returns a response. The service also logs the result." In technical documents, every pronoun must have one unambiguous antecedent within the same sentence or the immediately preceding sentence. When in doubt, repeat the noun.
2 / 29
An incident report states: "The load balancer forwards requests to the backend. This caused the outage." What does "This" refer to?
Option C is correct. "This" used as a standalone subject — sometimes called a "naked this" — is one of the most common errors in incident writing. It nominally refers to "the previous statement as a whole", but in technical writing the reader needs precision. Fix: "This misconfiguration caused the outage." or "This forwarding behaviour caused the outage." Always complete "this" with a descriptive noun: "this issue", "this pattern", "this delay", "this condition". The noun you choose also demonstrates your understanding of the root cause.
3 / 29
An architecture doc says: "The API gateway and the auth service communicate over mTLS. They handle all external requests." Which rewrite improves pronoun clarity?
Option C is the clearest. When "they" could refer to either one of two named components, or to both together, the correct fix is to restate each noun with its specific responsibility. This forces the writer to clarify the architecture and makes the document unambiguous. Option A replaces "they" with "it", which is still ambiguous. Option B compresses information but loses the distinction between the two components. Option D introduces a new pronoun ("them") without improving clarity. Technical writing rule: when a plural pronoun follows two distinct nouns with different roles, expand — do not compress.
4 / 29
A code comment says: "// The validator calls the parser, which validates the input. If it fails, retry." Which "it" is ambiguous here?
Option B is correct. "If it fails" is ambiguous because there are multiple candidates: the validator (calling fails), the parser (parsing fails), or the validation step (validation result fails). The rule "it refers to the most recently mentioned noun" is a guideline, not a guarantee, and in technical contexts it fails whenever the closest noun is not the actual referent. Fix: "// If validation fails, retry." or "// If the parser call fails, retry." In code comments, precision matters as much as in documentation — ambiguous retry conditions can cause unexpected loops or silent failures.
5 / 29
A README says: "Install the CLI and configure the environment. Once you do this, the build will succeed." How should "this" be improved?
Option C is the clearest because it explicitly restates both actions — install and configure — removing all ambiguity. "This", "it", and "that" used to refer to a sequence of actions are all weak in technical writing. Option A replaces "this" with "it", which is equally vague. Option B ("that") is marginally more formal but still vague. Option D ("once done") is concise but loses specificity. In READMEs and setup guides, step references should be explicit: readers may skip steps, read out of order, or be unclear which steps count as "done". Explicit summary sentences also serve as natural checklists.
6 / 29
Sarah from the DevOps team sent this Slack message: "The container crashed. The pod restarted itself. It's back online now." What's the issue with Sarah's phrasing?The primary problem is the ambiguous use of 'it.' While technically correct that the pod restarted itself, it doesn't explain *why* the container crashed. Using 'it' obscures the underlying issue and hinders troubleshooting. The options highlight common misinterpretations – a failure to identify root cause, an overly vague pronoun reference, or simply unnecessary repetition.
7 / 29
You're reviewing a PR description for a new feature. It reads: "The service now uses the new authentication library. This improves security and performance." What's the most effective way to rewrite this sentence for improved clarity?
The original sentence suffers from a dangling pronoun. 'This' is vague and doesn't clearly connect to the action of using the library. Option 2 directly links the improvement to *using* the library, creating a more logical flow. It avoids passive voice and clarifies the relationship between the library and its effects.
8 / 29
In an API response, you receive this data: `{"status": "success", "data": {"user_id": 123}}`. A developer writes the following comment to explain it: 'The service returns a success status and the user ID.' What's wrong with this explanation?
The core issue here is pronoun ambiguity. 'It' in this context refers back to the *entire* API response, which isn't helpful for understanding the specific data element (the user ID). The goal of a good explanation is to pinpoint exactly what the 'user_id' represents within the broader response structure.
9 / 29
During a standup meeting,
Ben says: 'The microservice failed. The queue processed the message successfully.' What could be improved about this statement to enhance clarity?The primary problem is the lack of context. While technically accurate, Ben doesn't provide any information about *why* the microservice failed. This makes it difficult for others to understand the issue and potentially contribute to a solution. A more detailed explanation would offer valuable insights.
10 / 29
Sarah from the DevOps team sent this Slack message: "The container crashed. The pod restarted itself. It's back online now." What's the issue with Sarah's phrasing?The primary problem is the ambiguous use of 'it.' While technically correct that the pod restarted itself, it doesn't explain *why* the container crashed. Using 'it' obscures the underlying issue and hinders troubleshooting. The options highlight common misinterpretations – a failure to identify root cause, an overly vague pronoun reference, or simply unnecessary repetition.
11 / 29
You're reviewing a PR description for a new feature. It reads: "The service now uses the new authentication library. This improves security and performance." What's the most effective way to rewrite this sentence for improved clarity?
The original sentence suffers from a dangling pronoun. 'This' is vague and doesn't clearly connect to the action of using the library. Option 2 directly links the improvement to *using* the library, creating a more logical flow. It avoids passive voice and clarifies the relationship between the library and its effects.
12 / 29
In an API response, you receive this data: `{"status": "success", "data": {"user_id": 123}}`. A developer writes the following comment to explain it: 'The service returns a success status and the user ID.' What's wrong with this explanation?
The core issue here is pronoun ambiguity. 'It' in this context refers back to the *entire* API response, which isn't helpful for understanding the specific data element (the user ID). The goal of a good explanation is to pinpoint exactly what the 'user_id' represents within the broader response structure.
13 / 29
During a standup meeting,
Ben says: 'The microservice failed. The queue processed the message successfully.' What could be improved about this statement to enhance clarity?The primary problem is the lack of context. While technically accurate, Ben doesn't provide any information about *why* the microservice failed. This makes it difficult for others to understand the issue and potentially contribute to a solution. A more detailed explanation would offer valuable insights.
14 / 29
Sarah from the DevOps team sent this Slack message: "The container crashed. The pod restarted itself. It's back online now." What's the issue with Sarah's phrasing?The primary problem is the ambiguous use of 'it.' While technically correct that the pod restarted itself, it doesn't explain *why* the container crashed. Using 'it' obscures the underlying issue and hinders troubleshooting. The options highlight common misinterpretations – a failure to identify root cause, an overly vague pronoun reference, or simply unnecessary repetition.
15 / 29
You're reviewing a PR description for a new feature. It reads: "The service now uses the new authentication library. This improves security and performance." What's the most effective way to rewrite this sentence for improved clarity?
The original sentence suffers from a dangling pronoun. 'This' is vague and doesn't clearly connect to the action of using the library. Option 2 directly links the improvement to *using* the library, creating a more logical flow. It avoids passive voice and clarifies the relationship between the library and its effects.
16 / 29
In an API response, you receive this data: `{"status": "success", "data": {"user_id": 123}}`. A developer writes the following comment to explain it: 'The service returns a success status and the user ID.' What's wrong with this explanation?
The core issue here is pronoun ambiguity. 'It' in this context refers back to the *entire* API response, which isn't helpful for understanding the specific data element (the user ID). The goal of a good explanation is to pinpoint exactly what the 'user_id' represents within the broader response structure.
17 / 29
During a standup meeting,
Ben says: 'The microservice failed. The queue processed the message successfully.' What could be improved about this statement to enhance clarity?The primary problem is the lack of context. While technically accurate, Ben doesn't provide any information about *why* the microservice failed. This makes it difficult for others to understand the issue and potentially contribute to a solution. A more detailed explanation would offer valuable insights.
18 / 29
Mark, a senior engineer, left this comment on a code review:
"The service calls the database. It retrieves the user's data and returns it to the client. The query is optimized for performance."
The issue lies with the pronoun 'it'. While technically correct that the service retrieves data, it's ambiguous. The explanation clarifies why specifying 'the service' would be better – to avoid vagueness and directly link the action to the relevant component. The other options misinterpret the comment's purpose or introduce irrelevant technical details.
19 / 29
During a Slack discussion about a failing deployment, Alex writes: "The build failed because of an error in the frontend. The CI pipeline restarted it."
What's the primary issue with this message regarding pronoun clarity?
The repeated use of 'it' creates ambiguity. While a CI pipeline *did* restart the build, the pronoun obscures which specific entity performed that action. Rewriting to explicitly state 'the CI pipeline restarted the build' significantly improves clarity and avoids unnecessary repetition. The other options highlight issues with less critical aspects of the message.
20 / 29
In a PR description for a new API endpoint, David writes: "The server now handles requests to /users/{user_id}. This improves data retrieval speed."
Which revision best clarifies the pronoun 'this'?
The pronoun 'this' in the original sentence refers to the entire API endpoint. While technically correct that it improves data retrieval speed, it lacks specificity. Replacing 'this' with 'the new API endpoint' provides context and directly links the improvement to the feature being described – a crucial element of clear technical writing. The other options address tangential concerns.
21 / 29
A developer writes in a PR description: "The new service uses the updated logging library. This reduces log volume and improves debugging."
Which revision best clarifies the pronoun 'this'?
The pronoun 'this' refers to the *updated* logging library. Clarifying this by explicitly stating 'the updated logging library' provides context and directly links the benefits – reduced log volume and improved debugging – to the specific change being implemented. This makes the PR description more informative and impactful.
22 / 29
During a code review discussion, Liam says: 'The function now returns the user's details. This makes the API more efficient.' What's the most precise way to rephrase this sentence to avoid ambiguity and improve clarity for another developer?
The original sentence suffers from unclear pronoun reference. 'This' refers back to the entire function change, not the specific action of returning details. Option A clearly connects 'this' to the result – the improved API efficiency. Options B and C are also better than the original because they explicitly state the relationship between the return value and the efficiency.
23 / 29
In a Slack channel for troubleshooting an application outage, Emily writes: 'The database server is down. The application automatically failed over to the backup.' What adjustment would most effectively improve this message's clarity regarding responsibility and action?
Emily's phrasing implies that the *application* made a decision without context. Option A provides a more formal and precise description of the event, attributing it to an 'unplanned outage' and clarifying the action taken by the system. Options B and C are less specific, while option D is too simplistic.
24 / 29
A developer submits a PR with the following description: 'The service now uses version 2.5 of the library. This improves scalability.' What's the primary issue with this statement that needs addressing regarding pronoun clarity?
'This' is ambiguous and doesn't clearly link the improvement to the library version. The reader needs to understand *why* version 2.5 improves scalability. The question aims at identifying this lack of specific connection – a common issue in technical writing where vague improvements are described without explanation.
25 / 29
Sarah from the DevOps team posted this message to a monitoring dashboard: 'The service experienced high latency. The load balancer adjusted the traffic distribution.' What is the most effective way to revise this statement for improved clarity and understanding of the system's response?
Option A provides a more sophisticated and precise description of the event sequence. It clearly articulates that 'high latency' triggered the action taken by the load balancer. This demonstrates a deeper understanding of how these components interact within the system – crucial for effective monitoring and troubleshooting.
26 / 29
During a Slack discussion about a recent deployment rollback, John writes: 'The service was unstable. The team reverted to the previous version.' What's the most effective way to revise this message to clarify who performed the reversion and reduce potential confusion?
This revision addresses pronoun ambiguity and clarifies action responsibility.The original phrasing leaves it unclear *who* initiated the reversion. Option A is better because it explicitly states 'the team' performed the action. Options B and C are too vague, while option D removes agency entirely. This clarifies responsibility and avoids potential blame or confusion.
27 / 29
A developer leaves this comment in a PR description: 'The new function now returns the data from the API call. This improves response times.' What's the key issue with this statement regarding pronoun clarity and how could it be improved?
This highlights the potential for ambiguity about what 'this' refers to—the function or the API call.The original statement uses 'this' without a clear antecedent. Option A directly clarifies that 'this' refers to the API call. Options B and C are equally ambiguous and unnecessarily complex. Option D is overly verbose and shifts the focus away from the function's role.
28 / 29
In a standup meeting, Maria says: 'The server experienced high CPU usage. The application automatically scaled up.' What's the most precise revision of this statement to improve clarity and avoid potential misunderstanding about the scaling process?
This focuses on the action taken by the system rather than attributing it solely to the application.Option 2 is the most precise. It clearly states that 'the system' performed the scaling action. Options A and B include unnecessary repetition ('so'/'because'), while option D shifts the focus to the application instead of the server.
29 / 29
During a code review discussion, David says: 'The new component renders the data from the API. This reduces page load times.' What's the most effective way to revise this statement for improved clarity and precision?
This tests the ability to replace vague pronouns with more specific phrasing.Option 0 is the clearest and most concise. It directly states that the reduction in page load times *results from* the component rendering the data. Options B and C introduce unnecessary clauses, while Option D uses overly formal language.
Frequently Asked Questions
What will I practise in "Pronoun Clarity in Technical Writing — Grammar Exercise"?
Practice identifying and fixing ambiguous pronouns in technical writing: it, this, they, and that with unclear referents in documentation, code comments
How many exercises are in this module?
This module has 29 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.