Wrapping

In the current draft, the plain-text documentation specifies: "Wrap paragraphs at 80 characters."

I would advocate for all code, not just documentation, being wrapped at 80 characters, for two reasons:

• You can easily view code on standard terminals with less or vim without confusing wrapping. (Even if I'm the only person on the team that codes in vim, others may want to look something up using less or cat or similar.)
• It is one way to discourage lots of nested indents.

Start with the current plain-text documentation draft referenced in the issue and review how its 80-character paragraph rule is expressed. Decide how the rule should apply to code, then update the guide so the 80-character expectation is explicit and consistent for both documentation and code.