Which is a professional way to write about the possible errors or exceptions that a program can trigger?

I have not worked in software professionally, only at a hobby/studient level and I would like to know how professionals handle in their documentation about a program's possible errors and exceptions that might be triggered during execution.

I would like to know if there are any set of rules so any programmer who has the duty to fix an error or exception reads this text and knows were it happened and why.

I'm looking for an universal way to do it. No matter what computer language you are working with.