When given a visual example to evaluate, we are expected to do it in our head, using what we understand about operator precedence and order of operations, and about OR. We are NOT to use the interface to solve those two expressions.
Look, and evaluate, then write only the outcome as you have determined it. If you get it wrong, then find out why.
It is imperative that we get this concept straight in our thinking, and the only way to do that is to think, not tap keys.
Which makes no sense whatever. The lesson is clearly about OR and does not reference type in any way, nor does it even mention bool.
Personally, @mtf I see what you are trying to communicate, however, being able to distinguish the difference between true/false/or in our heads with elementary math is a paltry exercise. We are here to practice coding, not play algebra games in our head. It would be beneficial if these first check boxes also required us to manipulate the code/print results rather than a simple copy/pasting experience.
gpa and credits are the parameters of the function. (Maybe think of them as empty placeholders). When you call the function, you pass through arguments that will execute the function and return either True or False depending on whether or not one of those conditions (gpa is >= 2.0 or credits >= 120) is met.