There aren't "Actions for True" and "Actions for False" anymore because you don't have a "rule" defined by conditions in Rule 4.0 anymore, either, so there is no concept of "true" or "false" evaluation that would cause the appropriate set of actions to run. Instead, the (only) "Actions" section will run whenever the trigger fires, and there--in the actions section--is where you can fork your actions, generally with conditionals (IF statements), to do what you want. In many cases this also means you'll want your trigger to be something like "motion changes" so you can test for "IF motion active..." and "ELSE" (i.e., motion inactive) in the actions section itself.
If you just want to cut to the chase, Bruce had a very similar rule in the new docs for Rule 4.0. The screenshot is here: https://community.hubitat.com/uploads/default/original/3X/2/8/28ec357b8c94548fbfd57f38ee73620815d4edff.png. But for a better understanding, I'd recommend reading the whole thread, [Released] Rule 4.0. The way "cancel" works changed, too, since with just a trigger and no rule, there is no such thing as "truth change." This is demonstrated in the screenshot of the rule I linked to, but it's explained more generally in the documentation thread I also linked to.
Hope this helps!
(PS - While learning RM is great, if all you want is motion-based lighting, the stock Motion Lighting app can handle this--and a bit more--quite easily with less work and thinking on the user's part.)
