If you want do it right: 1. Update the documentation first, to describe the desired / expected behaviour. 2. Followed by the code changes that implement the d

If you want do it right: 1. Update the documentation first, to describe the desired / expected behaviour. 2. Followed by the code changes that implement the documented behaviour. PRs: for any behaviour change, feature addition etc: patch must include corresponding documentation updates. If not: reject. Iirc that was (still is?) OpenBSD's approach to keeping docs up-to-date.