[Process/Documentation] How do you capture exceptions and alternative flows without making the documentation unreadable?

I try to keep the main flow readable and then layer exceptions in a structured way. If every exception is buried inside the main description, the whole document becomes hard to follow. So I usually separate the standard path from the exceptions, whether that means numbered alternative flows, a decision table, or linked...