The useful split is the one between a changelog, release notes, and a migration guide: the first records what changed, the second announces what is new, and the guide answers what the reader needs to change in their code. A changelog line like "pagination now uses cursors" is the example that shows why the third document is needed. The advice to treat an uncertain change as breaking, and not to rely on the docs alone — checking the changelog, pull requests, and the engineers who built the new version — keeps the Inventory API table honest. Listing, for each difference, where it happens, whether it is breaking, and who it affects is a practical way to write that list before the before-and-after examples.