5 exercises — practise fixing dangling modifiers in technical descriptions and reports.
0 / 20 completed
1 / 20
Which sentence corrects the dangling modifier in: "After parsing the config file, the server started successfully"?
"After the server parsed the config file, it started successfully" fixes the dangling modifier by giving the introductory clause its own explicit subject ("the server"), removing any ambiguity about who performs the parsing. In the original sentence and option A, "after parsing the config file" has no stated subject, and by the rule that an introductory participial phrase should modify the subject immediately following it, it technically attaches to "the server" — which happens to work here, but the structure is fragile and becomes a genuine dangling modifier in less fortunate word orders, so making the subject explicit is the more robust, unambiguous fix in careful technical writing. Option B still leaves the implicit subject of "parsing" ambiguous, just relocated. Option D only reorders the adverb "successfully" without addressing the modifier attachment issue at all.
2 / 20
Identify the sentence with a genuine dangling modifier that creates unintended meaning.
Option B contains a genuine dangling modifier: "having reviewed the pull request" is a participial phrase implying a human agent did the reviewing, but the subject that immediately follows is "the merge" — literally suggesting the merge reviewed the pull request, which is nonsensical. Option A correctly attaches the participial phrase to "the maintainer", the logical performer of the reviewing action. Option C also correctly links the phrase to "the maintainer", just with it set off in the middle of the sentence. Option D uses a full gerund phrase with "after", which likewise correctly modifies "the maintainer" as the following subject.
3 / 20
Which sentence correctly avoids a dangling modifier when describing an automated process?
"Once triggered by the webhook, the pipeline runs the full test suite" is correct: the passive participial phrase "triggered by the webhook" logically describes "the pipeline" (the pipeline is the thing that gets triggered), and "the pipeline" is exactly the subject that immediately follows the introductory phrase, so the modifier attaches correctly with no ambiguity. Option B changes the participle to active "triggering", which would incorrectly imply the pipeline itself triggers the webhook, reversing the real relationship. Option C keeps the correct passive participle but then swaps the subject and object of the main clause, producing the illogical claim that "the full test suite runs the pipeline". Option D is needlessly awkward and adds a redundant "by it" that muddles rather than clarifies the relationship.
4 / 20
Choose the corrected version of the dangling modifier in: "To deploy the update safely, a rollback plan should be prepared."
"To deploy the update safely, the team should prepare a rollback plan" corrects the dangling modifier: the infinitive phrase "to deploy the update safely" expresses a purpose that logically belongs to an agent capable of deploying — "the team" — and this revision supplies that agent as the subject of the main clause. In the original and option A, the phrase is left dangling because the passive main clause "a rollback plan should be prepared" has no explicit agent, so the purpose clause has nothing logical to attach to (a rollback plan cannot itself deploy anything). Option C merely relocates the dangling phrase without fixing the missing-agent problem. Option D only shifts the adverb "safely" and leaves the same underlying dangling-modifier issue unresolved.
5 / 20
A code review comment reads: "_____ , the null pointer exception was easy to reproduce." Choose the option that avoids a dangling modifier.
"After the developer added logging statements" is the only option that avoids a dangling modifier, because it is a full clause with its own explicit subject ("the developer") rather than a participial or infinitive phrase relying on the following clause's subject for its meaning. The main clause's subject is "the null pointer exception", which cannot logically be the one who "added logging statements" or was "having added" them — so options A, C, and D, all of which are reduced phrases lacking their own subject, would incorrectly and illogically attach the action of adding logging to "the null pointer exception" itself once combined with the given main clause.
6 / 20
During a Slack discussion about troubleshooting a slow API response, Sarah says: 'Because the database connection pool was exhausted, we need to scale up the backend servers.' Does this sentence contain a dangling modifier?
This sentence correctly uses 'because' to indicate a cause-and-effect relationship. The modifier 'Because the database connection pool was exhausted' directly explains *why* scaling up servers is necessary. A dangling modifier would imply that the exhaustion of the pool caused the slow response without any causal link; options A, C and D all misinterpret this fundamental relationship.
7 / 20
In a pull request description for a new feature, David writes: 'The integration with the third-party service was completed successfully. After sending the initial data, we verified the functionality.' Is there a potential dangling modifier in this paragraph?
The problem lies in the ambiguous reference of 'after'. While it describes an action that *followed* integration, it doesn't explicitly state *what* was being integrated. Options A and B are incorrect because they don't address the potential ambiguity. Option D is a misinterpretation of the sentence's meaning.
8 / 20
During a code review, Mark comments: 'To ensure data integrity, we implemented checksum validation on all file transfers.' Does this sentence contain a dangling modifier?
This sentence uses 'to ensure' to clearly indicate the *purpose* of the checksum validation. The modifier logically connects to what is being validated – file transfers. Option A is incorrect because it doesn't acknowledge the potential ambiguity. Options C and D misinterpret the relationship between purpose and action.
9 / 20
In a technical blog post about deployment procedures, Emily writes: 'Once the application is deployed, monitor its performance using Prometheus.' Does this sentence contain a dangling modifier?
The word 'once' establishes a clear temporal sequence – that monitoring should occur *after* deployment. This creates an accurate and understandable relationship between the two actions. Options A and C misinterpret the meaning of 'once,' while option D incorrectly describes the process.
10 / 20
A standup update from Alex reads: 'Having successfully migrated the database, we're now focusing on testing the new API endpoints.' Does this sentence contain a dangling modifier?
The issue here is the ambiguous reference of 'having'. While it indicates a completed action, it doesn't explicitly state *what* was migrated. This creates an unclear relationship between the migration and the subsequent testing activity. Options A and B are incorrect because they don't address this ambiguity; option D misinterprets the update's purpose.
11 / 20
During a Slack discussion about troubleshooting a slow API response, Sarah says: 'Because the database connection pool was exhausted, we need to scale up the backend servers.' Does this sentence contain a dangling modifier?
This sentence correctly uses 'because' to indicate a cause-and-effect relationship. The modifier 'Because the database connection pool was exhausted' directly explains *why* scaling up servers is necessary. A dangling modifier would imply that the exhaustion of the pool caused the slow response without any causal link; options A, C and D all misinterpret this fundamental relationship.
12 / 20
In a pull request description for a new feature, David writes: 'The integration with the third-party service was completed successfully. After sending the initial data, we verified the functionality.' Is there a potential dangling modifier in this paragraph?
The problem lies in the ambiguous reference of 'after'. While it describes an action that *followed* integration, it doesn't explicitly state *what* was being integrated. Options A and B are incorrect because they don't address the potential ambiguity. Option D is a misinterpretation of the sentence's meaning.
13 / 20
During a code review, Mark comments: 'To ensure data integrity, we implemented checksum validation on all file transfers.' Does this sentence contain a dangling modifier?
This sentence uses 'to ensure' to clearly indicate the *purpose* of the checksum validation. The modifier logically connects to what is being validated – file transfers. Option A is incorrect because it doesn't acknowledge the potential ambiguity. Options C and D misinterpret the relationship between purpose and action.
14 / 20
In a technical blog post about deployment procedures, Emily writes: 'Once the application is deployed, monitor its performance using Prometheus.' Does this sentence contain a dangling modifier?
The word 'once' establishes a clear temporal sequence – that monitoring should occur *after* deployment. This creates an accurate and understandable relationship between the two actions. Options A and C misinterpret the meaning of 'once,' while option D incorrectly describes the process.
15 / 20
A standup update from Alex reads: 'Having successfully migrated the database, we're now focusing on testing the new API endpoints.' Does this sentence contain a dangling modifier?
The issue here is the ambiguous reference of 'having'. While it indicates a completed action, it doesn't explicitly state *what* was migrated. This creates an unclear relationship between the migration and the subsequent testing activity. Options A and B are incorrect because they don't address this ambiguity; option D misinterprets the update's purpose.
16 / 20
During a Slack discussion about troubleshooting a slow API response, Sarah says: 'Because the database connection pool was exhausted, we need to scale up the backend servers.' Does this sentence contain a dangling modifier?
This sentence correctly uses 'because' to indicate a cause-and-effect relationship. The modifier 'Because the database connection pool was exhausted' directly explains *why* scaling up servers is necessary. A dangling modifier would imply that the exhaustion of the pool caused the slow response without any causal link; options A, C and D all misinterpret this fundamental relationship.
17 / 20
In a pull request description for a new feature, David writes: 'The integration with the third-party service was completed successfully. After sending the initial data, we verified the functionality.' Is there a potential dangling modifier in this paragraph?
The problem lies in the ambiguous reference of 'after'. While it describes an action that *followed* integration, it doesn't explicitly state *what* was being integrated. Options A and B are incorrect because they don't address the potential ambiguity. Option D is a misinterpretation of the sentence's meaning.
18 / 20
During a code review, Mark comments: 'To ensure data integrity, we implemented checksum validation on all file transfers.' Does this sentence contain a dangling modifier?
This sentence uses 'to ensure' to clearly indicate the *purpose* of the checksum validation. The modifier logically connects to what is being validated – file transfers. Option A is incorrect because it doesn't acknowledge the potential ambiguity. Options C and D misinterpret the relationship between purpose and action.
19 / 20
In a technical blog post about deployment procedures, Emily writes: 'Once the application is deployed, monitor its performance using Prometheus.' Does this sentence contain a dangling modifier?
The word 'once' establishes a clear temporal sequence – that monitoring should occur *after* deployment. This creates an accurate and understandable relationship between the two actions. Options A and C misinterpret the meaning of 'once,' while option D incorrectly describes the process.
20 / 20
A standup update from Alex reads: 'Having successfully migrated the database, we're now focusing on testing the new API endpoints.' Does this sentence contain a dangling modifier?
The issue here is the ambiguous reference of 'having'. While it indicates a completed action, it doesn't explicitly state *what* was migrated. This creates an unclear relationship between the migration and the subsequent testing activity. Options A and B are incorrect because they don't address this ambiguity; option D misinterprets the update's purpose.
What will I practise in "Dangling Modifiers in Technical English — IT Grammar Exercise"?
Practise identifying and correcting dangling and misplaced participial phrases in bug reports, release notes, and code review comments.
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.