Exercise 1: Why "react hooks - useEffect" Doesn't Exclude useEffect — Possible Solution
====================================================================

WHAT THE QUERY ACTUALLY CONTAINS
------------------------------
The query as written is "react hooks - useEffect" — note the spaces
surrounding the dash: a space before it AND a space after it. Per this
chapter, the minus operator only works as an exclusion signal when it
is placed directly against the word it's excluding, with no space in
between.

WHAT THE SEARCH ENGINE ACTUALLY PARSES THIS AS
------------------------------
With a space on both sides, the dash is not attached to "useEffect" at
all — it's just a free-floating punctuation character sitting between
two words. The engine has no reason to treat it as an operator rather
than stray punctuation, so it's effectively ignored. What's left is
three ordinary keywords ANDed together by the default behavior this
chapter opened with: react AND hooks AND useEffect — the exact
opposite of what was intended.

THE FIX
------------------------------
Removing the space after the dash — "react hooks -useEffect" — attaches
the minus sign directly to the word it should exclude, which is what
actually triggers the exclusion behavior.

WHY THIS WORKS AS AN ANSWER
------------------------------
It identifies the exact mechanical cause (a space breaking the
minus-to-word attachment) rather than a vague "it just doesn't work,"
cites the chapter's own stated rule directly, and shows precisely what
the mis-typed query is parsed as instead — three ANDed keywords, one of
which is the very term the user was trying to remove.