5 exercises — practise placing adverbs correctly around infinitives in specs, docs, and blog posts.
0 / 18 completed
1 / 18
Which sentence uses a split infinitive that most style guides consider natural and idiomatic in technical writing?
A split infinitive places an adverb between "to" and the base verb: "to quickly refactor". Option B is natural and idiomatic — modern style guides (including Microsoft's and Google's developer documentation guides) accept split infinitives when the alternative sounds stilted or changes emphasis. "To quickly refactor the module" reads naturally and keeps the adverb close to the verb it modifies. Option C moves "quickly" to the end, which is also grammatical but slightly weaker in emphasis. Option D ("to refactor quickly the module") is ungrammatical — the adverb cannot separate the verb from its direct object. Option A misplaces "quickly" entirely, making it modify "decided" rather than "refactor".
2 / 18
In API documentation, which sentence avoids a split infinitive while preserving the intended meaning?
Option C avoids splitting "to generate" by placing "programmatically" after the object ("access tokens"), which is the standard way to un-split an infinitive without sounding awkward. Option A splits the infinitive ("to programmatically generate") — acceptable in most contexts, but the question asks for the version that avoids the split. Option B is awkward because the adverb interrupts the verb-object pairing without any grammatical justification. Option D ("you programmatically to generate") is ungrammatical — an adverb cannot precede a bare "to" infinitive marker like that in standard English.
3 / 18
Which sentence demonstrates a split infinitive that changes meaning if "un-split", making the split preferable?
In option A, "to actually solve" places emphatic "actually" directly before the verb it intensifies, giving the strongest contrastive emphasis against "just patch the symptom". Moving "actually" elsewhere (options B and C) weakens or garbles that emphasis — option C is outright ungrammatical, and option B sounds archaic and stilted. Option D moves "actually" to a sentence-initial position, which changes its scope from modifying "solve" to modifying the whole clause, softening the contrast. This is a case where keeping the split infinitive is the clearest and most natural choice — a useful counterexample to the outdated "never split an infinitive" rule.
4 / 18
A style guide for a documentation team recommends avoiding split infinitives in formal specs. Which rewrite of "The API is designed to seamlessly integrate with existing pipelines" follows that recommendation?
Option A correctly un-splits the infinitive by moving "seamlessly" after the verb phrase it modifies ("integrate with existing pipelines"), producing a clean, formal sentence with no ambiguity. Option B moves the adverb to before "to", which sounds unnatural and could be misread as modifying "designed". Option C introduces an incorrect comma that breaks the prepositional phrase. Option D fronts the adverb, shifting emphasis to the whole sentence rather than to how the integration happens. In formal RFCs and specs where some style guides still discourage split infinitives, moving the adverb after the full verb phrase (as in A) is the standard fix.
5 / 18
Which sentence contains an awkward, unnecessary split infinitive that should be revised for a polished engineering blog post?
Option B is awkward because it splits the infinitive with a long, multi-clause adverbial phrase ("carefully and, after extensive testing over several sprints, thoroughly") — the sheer distance between "to" and "roll out" makes the sentence hard to parse. Style guides generally tolerate splitting an infinitive with a single short adverb (as in options A, C, and D — "gradually", "fully", "soon"), because those keep the sentence readable. The rule of thumb for technical writing is not "never split an infinitive" but "do not let the split create distance or ambiguity between the verb and its subject/object". Option B should be revised, e.g., "After extensive testing over several sprints, we plan to roll out the feature carefully and thoroughly."
6 / 18
Sarah (Lead DevOps Engineer) posted this comment on a code review for a new Kubernetes deployment script:
'The service needs to be configured to automatically scale based on CPU utilization and memory usage.'
Which sentence below best reflects Sarah's intended meaning, considering the use of split infinitives in technical communication?
A. The service needs to be configured to scale automatically based on CPU utilization and memory usage.
B. The service needs to be configured based on automatic scaling for CPU utilization and memory usage.
C. The service needs to be configured to automatically scale based on both CPU utilization and memory usage simultaneously.
D. The service needs to be configured to scale automatically, considering CPU utilization and memory usage.
This question tests the understanding of when a split infinitive is acceptable. 'To' + verb is a common and natural construction in technical English when describing actions or processes. Option A correctly uses this structure to convey that the service should *automatically scale* – the most idiomatic way to express the desired behavior. Options B, C, and D are less clear and introduce unnecessary complexity by restructuring the sentence.
7 / 18
David (Backend Developer) is drafting a PR description for a new API endpoint. He writes:
'Clients should submit data through the endpoint to process asynchronously.'
Which of the following revisions avoids a split infinitive while maintaining clarity and precision?
A. Clients should submit data through the endpoint to process it asynchronously.
B. Clients should submit data through the endpoint for processing asynchronously.
C. Clients should submit data through the endpoint in order to process asynchronously.
D. Clients should submit data via the endpoint to process asynchronously.
The original sentence uses a split infinitive ('to process') which can sound awkward. Option A correctly avoids this by adding 'it' after 'process,' clarifying that the processing is done *by* the endpoint. Options B, C and D rephrase the intent but don't directly address the issue of the split infinitive, making them less precise in this context.
8 / 18
Maria (Technical Writer) is writing a section on a new logging service. She wants to emphasize that the system automatically records events when they occur.
Which sentence best demonstrates a split infinitive that subtly alters the meaning and could be improved?
A. The service automatically logs events as they happen.
B. The service automatically logs events, happening as they do.
C. The system automatically logs events when they occur.
D. The system automatically records events as they are occurring.
Option B introduces an unnecessary and slightly confusing element – 'happening as they do.' This creates a less direct relationship between the logging and the event. Although technically correct, it's more impactful than necessary. A cleaner phrasing like 'as they happen' (Option A) or 'when they occur' (Option C) is preferable for technical writing.
9 / 18
Ben (Software Engineer) is writing a blog post about optimizing database queries. He writes:
'Developers should carefully optimize their code to reduce latency and improve performance.'
Which revision of this sentence best avoids an awkward, unnecessary split infinitive suitable for a polished engineering blog post?
A. Developers should carefully optimize their code to reduce latency and improve performance.
B. Developers should carefully optimize their code for reducing latency and improving performance.
C. Developers should carefully optimize their code in order to reduce latency and improve performance.
D. Developers should carefully optimize their code, reducing latency and improving performance.
The original sentence contains a split infinitive ('to reduce'). While not grammatically incorrect, it's stylistically less elegant. Option A removes the split, providing a more concise and professional tone suitable for a technical blog post. Options B, C and D introduce additional phrases that are unnecessary and weaken the sentence.
10 / 18
Sarah (Lead DevOps Engineer) posted this comment on a code review for a new Kubernetes deployment script:
'The service needs to be configured to automatically scale based on CPU utilization and memory usage.'
Which sentence below best reflects Sarah's intended meaning, considering the use of split infinitives in technical communication?
A. The service needs to be configured to scale automatically based on CPU utilization and memory usage.
B. The service needs to be configured based on automatic scaling for CPU utilization and memory usage.
C. The service needs to be configured to automatically scale based on both CPU utilization and memory usage simultaneously.
D. The service needs to be configured to scale automatically, considering CPU utilization and memory usage.
This question tests the understanding of when a split infinitive is acceptable. 'To' + verb is a common and natural construction in technical English when describing actions or processes. Option A correctly uses this structure to convey that the service should *automatically scale* – the most idiomatic way to express the desired behavior. Options B, C, and D are less clear and introduce unnecessary complexity by restructuring the sentence.
11 / 18
David (Backend Developer) is drafting a PR description for a new API endpoint. He writes:
'Clients should submit data through the endpoint to process asynchronously.'
Which of the following revisions avoids a split infinitive while maintaining clarity and precision?
A. Clients should submit data through the endpoint to process it asynchronously.
B. Clients should submit data through the endpoint for processing asynchronously.
C. Clients should submit data through the endpoint in order to process asynchronously.
D. Clients should submit data via the endpoint to process asynchronously.
The original sentence uses a split infinitive ('to process') which can sound awkward. Option A correctly avoids this by adding 'it' after 'process,' clarifying that the processing is done *by* the endpoint. Options B, C and D rephrase the intent but don't directly address the issue of the split infinitive, making them less precise in this context.
12 / 18
Maria (Technical Writer) is writing a section on a new logging service. She wants to emphasize that the system automatically records events when they occur.
Which sentence best demonstrates a split infinitive that subtly alters the meaning and could be improved?
A. The service automatically logs events as they happen.
B. The service automatically logs events, happening as they do.
C. The system automatically logs events when they occur.
D. The system automatically records events as they are occurring.
Option B introduces an unnecessary and slightly confusing element – 'happening as they do.' This creates a less direct relationship between the logging and the event. Although technically correct, it's more impactful than necessary. A cleaner phrasing like 'as they happen' (Option A) or 'when they occur' (Option C) is preferable for technical writing.
13 / 18
Ben (Software Engineer) is writing a blog post about optimizing database queries. He writes:
'Developers should carefully optimize their code to reduce latency and improve performance.'
Which revision of this sentence best avoids an awkward, unnecessary split infinitive suitable for a polished engineering blog post?
A. Developers should carefully optimize their code to reduce latency and improve performance.
B. Developers should carefully optimize their code for reducing latency and improving performance.
C. Developers should carefully optimize their code in order to reduce latency and improve performance.
D. Developers should carefully optimize their code, reducing latency and improving performance.
The original sentence contains a split infinitive ('to reduce'). While not grammatically incorrect, it's stylistically less elegant. Option A removes the split, providing a more concise and professional tone suitable for a technical blog post. Options B, C and D introduce additional phrases that are unnecessary and weaken the sentence.
14 / 18
John needs to quickly debug the application. He writes: 'The developer must immediately investigate the error and fix it.' Which sentence best illustrates a split infinitive in this context?
Split infinitives occur when an adverb is placed between 'to' and the base form of a verb. While not always incorrect, using 'needs to' here provides a smoother, more natural phrasing for technical communication. Option A creates an unnecessary split, while option B adds extra words that don't improve clarity.
15 / 18
Alice, a Senior Software Engineer, is drafting a Slack message to her team regarding a critical production issue. She types: 'We need to roll back the deployment immediately.' Which sentence demonstrates a split infinitive that is appropriate for this urgent communication?
In urgent situations like this, brevity and directness are crucial. A split infinitive here – 'to roll' – is perfectly acceptable and even preferable because it conveys urgency without adding extra words. Option B adds unnecessary repetition. Option C is too verbose.
16 / 18
Mark wrote the following API response snippet:
```json
{"status": "error", "message": "Insufficient funds. The account balance is too low."}"
```
Which sentence avoids a split infinitive while accurately describing this error?
Split infinitives can sound overly formal and less direct in technical documentation. Rephrasing 'is too low' as 'indicates an insufficient account balance' maintains a clear and concise message. Option A is also acceptable, but option B adds extra words for no benefit.
17 / 18
Emily, a technical writer, is explaining the new monitoring service to her team. She writes: 'The system automatically records events when they occur.' Which sentence demonstrates a split infinitive that sub…
While a split infinitive isn't *wrong* here, using 'when they occur' provides a more common and easily understood phrasing for describing an automated process. The split is technically correct but less idiomatic in this context. Option B adds unnecessary repetition.
18 / 18
David is writing a standup update about his progress on a new feature. He says: 'Developers should carefully optimize their code to reduce latency and improve performance.' Which revision of this sentence best avoids a split infinitive while maintaining the intended meaning?
Split infinitives can feel clunky in spoken communication. While grammatically correct, rephrasing the sentence by adding a comma allows for a more natural flow of thought. Option A incorrectly adds another split infinitive.
What will I practise in "Split Infinitives in Technical English — IT Grammar Exercise"?
Practise when placing an adverb between 'to' and the verb is natural in technical writing, and when to move it for clarity or formality.
How many exercises are in this module?
This module has 18 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.