When writing logic, I shy away from mixed "and/or", never remembering, or liking reliance on, precedence, so I would have used some sort of parentheses to tie the first two together and indented them as not peers of the OR operand (the parentheses are the OR peer). Easy to read is esay to get right the first time, debug, read, maintain and extend. You, too, deserve readable code! The career you save/enhance might be your own.

When writing procedure, the gay spiderweb of tree logic and one return/exit at the very end or piling 5 steps in one line is not productive. If you can return or exit from anywhere, why would you not use the power of that?

It is always nicer to use a series of simple if statements of the form: if this step fails then report the error, undo any damage you have not dealt with by good design that gracefully anticipates the possibility of this failure (rollback transaction, for instance), and exit or return from this list of steps. The one step check error form keeps all aspects of one step together and away from unrelated steps, and encourages good error checking and reporting, so it is easy to develop (quick debug), read, maintain and extend. You, too, deserve readable code! The career you save/enhance might be your own.