5 exercises — practise correct placement of floating quantifiers relative to auxiliaries and main verbs.
0 / 20 completed
1 / 20
Which sentence correctly uses a floating quantifier to describe the state of multiple servers?
"All" can "float" away from its noun and attach instead to the auxiliary verb, appearing directly after the first auxiliary ("have") rather than before the noun. Option B is correct: "The servers have all restarted successfully" — "all" floats to a position right after "have" and before the main verb "restarted". Option A places "all" in its standard pre-noun position ("All the servers"), which is also grammatical but is not the floating-quantifier pattern being tested. Options C and D place "all" after the main verb or at the sentence end, which is not a valid floating position in standard English — floating quantifiers must sit immediately after an auxiliary (or before a lone main verb in simple tenses), not after the full verb phrase.
2 / 20
Which sentence correctly floats the quantifier "both" in a sentence with no auxiliary verb (simple present)?
In simple tenses without an auxiliary, a floating quantifier is placed immediately before the main verb. Option B is correct: "The primary and replica databases both sync every second" — "both" floats to just before "sync". Option A places "both" in its standard pre-noun position, which is grammatical but not the floating pattern. Options C and D place "both" after the verb or at the end of the sentence, which are not valid floating positions — the quantifier must sit directly before the main verb (in simple tenses) or directly after the first auxiliary (in compound tenses), never after the verb phrase or clause-finally.
3 / 20
Which sentence correctly floats "each" to add emphasis on individual, separate action in a code review context?
"Each" floats to a position right after the modal auxiliary "must" and before the main verb "approve". Option B is correct: "The reviewers must each approve..." Option A places "each" in its standard pre-noun distributive position ("Each reviewer"), which is grammatical but changes the subject from plural to singular-distributive rather than demonstrating floating. Option C places "each" after the main verb and before its object, which is not a valid floating position — this creates an ungrammatical, confusing string ("approve each the pull request"). Option D places "each" before the modal "must" rather than after it — floating quantifiers attach after the first auxiliary/modal, not before it.
4 / 20
Which sentence demonstrates the correct floating position of "all" in a sentence with a modal + perfect construction ("must have")?
When there are two auxiliaries ("must have"), the floating quantifier attaches after the first auxiliary that carries the main grammatical weight closest to the verb — in practice, native-speaker usage places "all" after the full auxiliary chain and directly before the main verb: "must have all passed". Option B is correct. Option A places "all" between "must" and "have", which is grammatical in some dialects but far less natural for most speakers, who prefer the quantifier closest to the main verb it modifies. Option C places "all" before the modal "must", which is not a valid floating position. Option D places "all" after the main verb "passed", which is also invalid — floating quantifiers never follow the main verb.
5 / 20
Which sentence contains an incorrect floating-quantifier placement that a careful editor should flag in a status report?
Option C is incorrect: "have been all resolved" places "all" after both auxiliaries ("have been"), but the standard floating position is immediately after the first auxiliary, not after the full auxiliary chain when there are only two elements — the natural, correct order is "have all been resolved". This kind of misplacement is a common non-native error. Option A ("have both been redeployed") is correct — "both" floats immediately after the single relevant auxiliary "have". Option B ("all return") correctly floats "all" before the simple-present main verb. Option D ("were both assigned") correctly floats "both" right after the auxiliary "were". The general rule: the floating quantifier goes right after the first auxiliary verb, before any remaining auxiliaries or the main verb.
6 / 20
Reviewer: 'The API response shows some errors, but I'm not sure if we need to investigate all of them.' Is this phrasing appropriate for a code review comment?
Floating 'all' correctly emphasizes the scope of the investigation. The reviewer is expressing a degree of uncertainty and doesn't want to commit to fully addressing every single error reported by the API. Using 'some' alongside it acknowledges partial findings while avoiding an overly forceful demand for complete resolution.
7 / 20
PR Description: 'This commit addresses vulnerability issues in two components. It's important to ensure each component is fully tested.' What's the best way to phrase this for clarity?
Floating 'all' correctly highlights the need for complete testing across *both* components. The PR description needs to underscore that the changes impact multiple areas and therefore require comprehensive validation. Using 'two' is sufficient to describe the number of components affected.
8 / 20
Code Review Comment (from Senior Dev): 'The logging module uses three different formats. I'm not sure if we need to handle each format individually.' Is this a helpful comment?
Floating 'all' prompts a discussion about whether *every* logging format requires unique handling. This directs attention towards potential complexity and encourages a more thorough assessment of the requirements, preventing overlooking any particular format.
9 / 20
Reviewer: 'The API response shows some errors, but I'm not sure if we need to investigate all of them.' Is this phrasing appropriate for a code review comment?
Floating 'all' correctly emphasizes the scope of the investigation. The reviewer is expressing a degree of uncertainty and doesn't want to commit to fully addressing every single error reported by the API. Using 'some' alongside it acknowledges partial findings while avoiding an overly forceful demand for complete resolution.
10 / 20
PR Description: 'This commit addresses vulnerability issues in two components. It's important to ensure each component is fully tested.' What's the best way to phrase this for clarity?
Floating 'all' correctly highlights the need for complete testing across *both* components. The PR description needs to underscore that the changes impact multiple areas and therefore require comprehensive validation. Using 'two' is sufficient to describe the number of components affected.
11 / 20
Code Review Comment (from Senior Dev): 'The logging module uses three different formats. I'm not sure if we need to handle each format individually.' Is this a helpful comment?
Floating 'all' prompts a discussion about whether *every* logging format requires unique handling. This directs attention towards potential complexity and encourages a more thorough assessment of the requirements, preventing overlooking any particular format.
12 / 20
Reviewer: 'The API response shows some errors, but I'm not sure if we need to investigate all of them.' Is this phrasing appropriate for a code review comment?
Floating 'all' correctly emphasizes the scope of the investigation. The reviewer is expressing a degree of uncertainty and doesn't want to commit to fully addressing every single error reported by the API. Using 'some' alongside it acknowledges partial findings while avoiding an overly forceful demand for complete resolution.
13 / 20
PR Description: 'This commit addresses vulnerability issues in two components. It's important to ensure each component is fully tested.' What's the best way to phrase this for clarity?
Floating 'all' correctly highlights the need for complete testing across *both* components. The PR description needs to underscore that the changes impact multiple areas and therefore require comprehensive validation. Using 'two' is sufficient to describe the number of components affected.
14 / 20
Code Review Comment (from Senior Dev): 'The logging module uses three different formats. I'm not sure if we need to handle each format individually.' Is this a helpful comment?
Floating 'all' prompts a discussion about whether *every* logging format requires unique handling. This directs attention towards potential complexity and encourages a more thorough assessment of the requirements, preventing overlooking any particular format.
15 / 20
DevOps reports: 'We've deployed the new feature to all our staging servers. It needs to be thoroughly tested before going live.' Is this a correct use of a floating quantifier?
The phrase 'all' is correctly floating here to emphasize the complete scope of the deployment. A common mistake is to force it into a complex auxiliary verb structure when the simple, direct meaning is sufficient. The key takeaway is that 'all' indicates comprehensive coverage for testing. Option A incorrectly suggests incomplete coverage; option C highlights an unnecessary grammatical addition.
16 / 20
QA writes in a Slack message: 'I've investigated each of the reported bugs in the UI. Some are duplicates.' Is this a suitable phrasing for communicating test findings?
Here, 'each' correctly floats before the subject ('bugs') to emphasize that every reported bug was individually investigated. This is common in less formal settings like Slack. Option A creates unnecessary alarm; option C misinterprets the function of a floating quantifier; option D acknowledges the lack of formality but doesn't explain *why* it's unsuitable.
17 / 20
Project Manager writes in a PR description: 'This commit addresses vulnerabilities in both the authentication and authorization modules. It's crucial that each module undergoes rigorous testing.' Is this phrasing effective?
'Both' is correctly floating here to indicate that two separate modules were affected. It's important to note that while 'both' can sometimes sound imprecise, in this context it conveys the intended meaning effectively. Option A suggests a lack of clarity; option C misinterprets the quantifier's function; and option D points out the lack of detail.
18 / 20
A senior developer comments: 'The build process uses multiple tools. We need to ensure each tool is configured correctly before deployment.' Which sentence best demonstrates the correct floating quantifier usage in this context?
The correct answer uses 'each' to emphasize the individual tools. The sentence highlights the specific action required for each tool, demonstrating a precise and targeted instruction. Options A and B are grammatically correct but lack the emphasis provided by 'each' in this scenario. Option C is too vague, and option D doesn't use the floating quantifier effectively.
19 / 20
Standup Update: 'We've implemented the new caching layer. We need to test all of its functionalities before deploying it to production.' Does this statement effectively utilize a floating quantifier?
Using 'all' correctly emphasizes that *every* functionality of the new caching layer must be tested before deployment. This prevents potential issues arising from untested features. The incorrect options suggest a narrower or less comprehensive approach to testing.
20 / 20
Code Review Comment: 'The deployment script uses multiple stages. We need to ensure that each stage is executed correctly.' Is this a suitable use of a floating quantifier in a code review?
Here, 'each' correctly directs attention to verifying the execution of *every* stage in the deployment script. This is crucial because an error at any stage could halt the entire process. The other options don't address the critical need for individual step validation.
What will I practise in "Floating Quantifiers in Technical English — IT Grammar Exercise"?
Practise placing all, both, and each after auxiliaries and before main verbs — 'The servers have all restarted', 'The reviewers must each approve' — in status
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.