"I agree with removing this joke. A bit of humor is fine - indeed, the manual could use a bit more than it has - but this attempt at humor does not work. The manual should be high-quality, and that includes high-quality jokes."
"your technical documentation should have a consistent tone"
I appreciate light-hearted asides in documentation. But more if I expect it than when it's unexpected. Like you wouldn't want to end up confusing some ESL programmer who goes ask a lawyer whether they should be worried about this?
Or if you're really ambitious, make all your docs super funny! But if you mix the tone it's disorienting and maybe bad writing.
Here, here!
I would even go so far as to say that Why's (Poignant) Guide to Ruby directly contributed a great deal to Ruby's popularity because of the witty content alone.
This is a bad take. When wading through dry technical documentation a little humor can make it much less laborious.
As long as the humor doesn't result in ambiguity, there's no problem.
Something like "You can tune a filesystem, but you can't tune a fish." at the end of a manpage may elicit a chuckle but doesn't reduce understanding.