Exercise 3: Query-String Order vs. Grouping — Why One Matters and One Doesn't — Possible Solution
====================================================================

WHAT "ORDER IN THE QUERY STRING" MEANS
------------------------------
This refers to which position an operator is typed in relative to the
others - whether site:a.com comes before or after "rate limit" in the
raw text of the query. Per this chapter, "most operators combine
independently of the order they're typed in" - site:a.com "rate
limit" and "rate limit" site:a.com are treated as logically
equivalent, since each operator still applies the same restriction to
the overall result set regardless of where it physically sits in the
string.

WHAT "GROUPING WITH PARENTHESES" MEANS
------------------------------
This refers to which operators an OR (or similar combining logic)
actually applies to - not their position, but their logical scope.
Per this chapter, without parentheses a query like "rate limit"
site:a.com OR site:b.com is ambiguous about whether the OR applies
narrowly (just the two site: terms) or broadly (a larger portion of
the query) - a structural, logical ambiguity, not a matter of where
things are typed.

WHY ORDER USUALLY DOESN'T MATTER
------------------------------
Most operators (site:, filetype:, intitle:, a plain keyword) are each
independent, standalone restrictions applied to the whole query - AND
is commutative, so it genuinely doesn't matter which order independent
AND-style restrictions are listed in, the same way "python AND
flask AND site:a.com" means the same thing regardless of which
restriction is written first.

WHY GROUPING GENUINELY DOES MATTER
------------------------------
OR is not simply another independent restriction stacked onto the
others - it changes the logical relationship between whichever terms
it's scoped to. Without an explicit boundary (parentheses), it's
ambiguous exactly which terms are inside that OR relationship and
which remain outside it as ordinary ANDed restrictions. This is a
genuine difference in meaning, not merely a stylistic or readability
concern the way plain reordering is.

WHY THIS WORKS AS AN ANSWER
------------------------------
It defines both concepts precisely before contrasting them, explains
the underlying logical reason order doesn't matter for independent
AND-style restrictions (commutativity), and explains why OR's scoping
is a genuine logical-ambiguity problem rather than a mere stylistic
one - the real distinction the question is asking for.