Operators & Comparisons: Why an Odd-or-Even Check Gives the Wrong Answer
The remainder is right. The comparison built around it is backwards, and it's an easy way to get it backwards.
The Operators & Comparisons set leans on one fact: dividing by 2 and checking the remainder tells you whether a number is even (remainder 0) or odd (remainder 1). The arithmetic is rarely the mistake -- getting the two remainder values backwards is. It reads fine at a glance, runs without complaint, and quietly reports every even number as odd and vice versa.
Press Run to see what your code does.
8 is even, and that prints FALSE -- correct by accident, because it correctly says 8 is not odd. Swap in an odd number like 7 and it prints FALSE too, which is wrong: the condition never fires true for the case it was written to catch. The fix is one character of intent, not of syntax -- decide whether you're testing "is this odd" (remainder IS 1) or "is this even" (remainder IS 0), and write the branch that actually matches the question the challenge brief is asking. Reading the brief's exact wording back against your condition catches this faster than staring at the arithmetic.
Everything above runs in this page, on your own machine. There is more of it on the practice pages.