@roadriverrail Right? I mean, you're the embedded pro, but I've seen some of it even with my toy projects.
My compsci brain wants to take a data sheet for a hypothetical xyz456 chip and write a xyz456.datasheet text file that's a line-by-line copy of the relevant parts, but with syntax to annotate it with those errata and other experience-driven hints. As complex as that would be, it just floors me that sometimes the real right answer is really:
delay *= 163; /* not 162 as per p163 */