as stated above.
just try to imagine, or even toggle offline in any program that does updates, and becomes the logic yourself. Scan top to bottom, left to right.
Input A is false -> Coil A = Low
Input B is False -> Coil A= Low
Send data to keep coil A low
next scan
Input A is true -> Coil A = high
Input B is false -> Coil A = Low
Send data to keep Coil A low as the last received information was Coil A = Low
Next scan
Input A is false -> Coil A = low
Input B is True -> Coil A = High
Send data to put Coil A High as the last received information was Coil A = High
when read top to bottom, left to right the last read state of the logic for that coil will be what is done. There are instances where a (L) can be in multiple places, and that's where you can fall into some intermittent output issues, but an OTE is a one time use, any instance of the coil before the last one scanned mean nothing in the final decision.