I've seen lots of style guides, but most of them act like writing documentation and editing it are the same process. And so they will give advice on what not to do like "eliminate unnecessary words", but none on how to actually begin explaining the structure of a new codebase or an old one.