5 exercises — choose the correct participle clause construction in technical contexts including deployment descriptions, incident reports, and architecture documentation.
0 / 13 completed
1 / 13
Choose the sentence that correctly uses a present participle clause in a technical context.
A participle clause must have the same implied subject as the main clause. In "Running on Kubernetes, the service can be scaled horizontally," the subject of both clauses is "the service" (the service runs on Kubernetes; the service can be scaled). Option A is a dangling participle: "Running on Kubernetes" implies the engineers are running on Kubernetes, not the service. Option C is a comma splice (two independent clauses joined only by a comma). Option D is a sentence fragment.
2 / 13
___ the configuration file, the script automatically restarts all dependent services.
"Having updated" (perfect participle) shows that the configuration update happens BEFORE the restarting. It is the correct choice when the participle action precedes the main clause action. "To update" (infinitive) would indicate purpose. "Updated" (past participle) creates a passive reading: "Updated [by someone], the script..." — grammatically possible but changes the meaning. "Being updated" is present passive participle — implies simultaneous, ongoing updating, which does not fit the sequential logic here.
3 / 13
The pipeline failed, ___ in a three-hour production outage.
A present participle clause after a comma can express a consequence or result: "The pipeline failed, resulting in a three-hour production outage." The participle "resulting" describes the consequence that flows from the main clause. This construction is common in incident reports and technical narratives: "The memory leak went undetected, eventually causing the container to crash," "The migration ran without a rollback plan, leading to four hours of downtime." The past participle "resulted" cannot function here without "which" (relative clause).
4 / 13
___ in Go for performance reasons, the new version of the service reduced P99 latency by 40%.
"Having been rewritten" is the perfect passive participle — it correctly expresses that the rewriting was completed BEFORE the latency reduction was observed. The passive is required because the service was rewritten (by the team), not rewriting itself. "Rewriting" (active present) would make the service the one doing the rewriting. "Being rewritten" implies concurrent ongoing action. "Rewritten" (bare past participle) is also possible and common: "Rewritten in Go for performance, the service reduced..." — slightly less explicit about the completeness of the action.
5 / 13
Which sentence correctly uses a participle clause to combine two ideas about a technical process?
"The team merged the pull request, deploying the new build immediately afterwards" — correct. The participle clause "deploying the new build" has the same subject as the main clause (the team) and describes a subsequent action. Option A is ungrammatical (progressive tense used incorrectly). Option B has a dangling modifier — "Merging the pull request" implies the new build merged it, but the subject of the main clause is "the new build." Option D uses a dangling construction in the participial phrase "After merging" — unclear who merged.
6 / 13
Reviewer: 'After running the tests, we observed intermittent failures.' Is this sentence correctly employing a participle clause to describe a technical observation?
The key here is understanding that present participles function as adjectives describing nouns. 'Running the tests' directly modifies 'tests,' indicating the action happening *while* the tests were being executed. Option A misinterprets this and suggests a more complex sentence structure isn't needed. Options C and D are both incorrect because they imply a subordinate clause is appropriate, which isn't typical for concise technical updates.
7 / 13
Reviewer: 'After running the tests, we observed intermittent failures.' Is this sentence correctly employing a participle clause to describe a technical observation?
The key here is understanding that present participles function as adjectives describing nouns. 'Running the tests' directly modifies 'tests,' indicating the action happening *while* the tests were being executed. Option A misinterprets this and suggests a more complex sentence structure isn't needed. Options C and D are both incorrect because they imply a subordinate clause is appropriate, which isn't typical for concise technical updates.
8 / 13
Reviewer: 'After running the tests, we observed intermittent failures.' Is this sentence correctly employing a participle clause to describe a technical observation?
The key here is understanding that present participles function as adjectives describing nouns. 'Running the tests' directly modifies 'tests,' indicating the action happening *while* the tests were being executed. Option A misinterprets this and suggests a more complex sentence structure isn't needed. Options C and D are both incorrect because they imply a subordinate clause is appropriate, which isn't typical for concise technical updates.
9 / 13
Code Review Comment: 'While processing the payment webhook, we detected a high error rate.' Is this sentence effectively using a present participle clause to describe a technical issue?
This sentence correctly uses a present participle clause 'while processing the payment webhook' to connect the action (processing) with its observed effect (high error rate). The key point is that the participle describes an ongoing process directly related to the technical issue. Option A misinterprets the purpose of the clause, while options C and D suggest incorrect phrasing or unnecessary words.
10 / 13
Slack Message: 'The database replication lag increased significantly after deploying the new schema. db_replication_lag is currently at 30 minutes.'
This uses the present participle clause correctly to describe the ongoing state of the database. 'After deploying the new schema' explains *why* the replication lag increased. The phrase establishes a clear cause-and-effect relationship crucial for technical communication. Options A and C are incomplete or incorrect phrasing, while option D suggests an unnecessary addition.
11 / 13
PR Description: 'The service now implements rate limiting based on IP address. rate_limiting_config is stored in Redis and updated after each request.'
Here, the present participle clause 'based on IP address' concisely explains the core functionality. It clearly indicates *how* rate limiting is applied. Options A and C provide insufficient detail or incorrect phrasing, while option D suggests a less precise alternative.
12 / 13
Standup Update: 'I'm currently investigating the performance bottleneck in the image processing pipeline. image_processing_latency has increased by 20% since the last deployment.'
This example uses the present participle clause effectively to describe the technical problem being addressed. 'After the last deployment' explains the context for the increased latency. This is crucial information for a standup update and demonstrates understanding of key metrics. Options A and C are redundant or incorrect, while option D suggests an alternative phrasing that isn't as direct.
13 / 13
Code Review Comment: 'Following the successful completion of the integration tests, we observed a significant reduction in reported bugs.'
This sentence correctly utilizes a present participle clause – 'following the successful completion of the integration tests' – to clearly connect the testing process with its observed outcome (reduced bugs). It's a standard way to express cause and effect in technical documentation. Options A and C contain inaccuracies, while option D proposes an unsuitable phrasing for this context.
What will I practise in "Participle Clauses in Technical Documentation — Grammar Exercises"?
Practise present and past participle clauses in technical English: avoiding dangling participles, using perfect participles for sequence, and expressing
How many exercises are in this module?
This module has 13 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.