5 exercises — placing negation correctly relative to quantifiers and frequency adverbs to avoid ambiguity in specs and reports.
Key patterns:
not all / not every — partial negation, some succeed and some fail
no / none — total negation, unambiguous zero cases
does not always — negates frequency, not the verb itself
does not X unlimited Y — narrows negation scope to a modifier, not the whole clause
0 / 5 completed
1 / 5
A status report says: "Not all requests failed during the outage." Which statement correctly interprets the scope of this negation?
"Not all X" negates the universal quantifier all, not the verb itself — it means "some, but not all." This is a classic partial-negation pattern: "not all requests failed" logically entails that at least some requests succeeded. Contrast this with "all requests did not fail", which is ambiguous in casual speech but formally parses the same way; in careful technical writing, "not all" is preferred precisely because it avoids that ambiguity.
2 / 5
Which sentence removes the negation-scope ambiguity present in "All services did not restart after the patch"?
The original sentence, "All services did not restart," is ambiguous between "none of the services restarted" and "not every service restarted." Moving the negation to directly precede the quantifier — "Not all services restarted" — unambiguously expresses the partial-failure meaning (some restarted, some did not), which is the intended meaning in most incident-reporting contexts. This reordering is a standard technique for resolving scope ambiguity in technical English.
3 / 5
An API doc states: "The endpoint does not always return a cached response." What does this sentence mean, given the scope of "always"?
"Does not always" negates the frequency adverb always, yielding "sometimes yes, sometimes no" — not a blanket denial. This differs sharply from "never returns a cached response," which would negate the verb entirely. Placing not before a frequency adverb like always, necessarily, or automatically is a common and precise way to express partial rather than total negation in specifications.
4 / 5
A security policy reads: "Every user is not required to enable two-factor authentication." Rewrite this to unambiguously mean that 2FA is optional for everyone (no one is required):
The original sentence is ambiguous because "every... not" word order could mean either "no one is required" or "not everyone is required" (i.e., some are). To state unambiguously that 2FA is optional for all users, the quantifier itself must change to no: "No user is required to..." This avoids placing negation after a universal quantifier, which is the primary source of scope ambiguity in policy and specification language.
5 / 5
Which sentence most precisely expresses that the system tolerates some, but not unlimited, packet loss?
"Does not tolerate unlimited packet loss" correctly narrows the scope of negation to the word unlimited, implying the system tolerates loss up to some threshold. Options A and B negate tolerance of packet loss entirely, which contradicts the intended partial-tolerance meaning. Option D is ungrammatical, since not cannot directly negate a bare noun phrase like "packet loss" without an auxiliary verb or quantifier to attach to.