Promise only what you can check. List every inexact swap in the change note.
documentation/contracts
One document states two requirements that cannot both be satisfied at once, so any reading obeys one clause and breaks the other. The reader relies on the text being internally consistent, and treats compliance with the sentence in front of them as compliance with the whole rule.
A review standard requires a failing test for every new guard, while an earlier paragraph lets the author skip it by citing where the behaviour is defined; both sentences are in force.
Not a documented guarantee the code fails to keep: the conflict here is inside the text itself, so no implementation could satisfy every clause, rather than a document asserting a state the code contradicts.
Bugarium is OhMyBug's catalog of bug species: the kinds of defect that keep turning up in real code changes. Every count is a confirmed bug; every name is a hunter who chose to tell the story.