That's different. You're describing an attempt to get a particular answer to a completely subjective question via hinting, whereas in the GP comment the recommendation is to ask questions about matters which have objective answers (e.g., "does this loop terminate?").

Don't volunteer for that! Of course they will say yes, just as if someone asked if you wanted them to document something, or just as customers always say yes if you ask if they want a feature!

Just tell them, "... You should document this in team wiki before we merge this."

One approach I took in a recent project was keeping the documentation in documentation folders under each project, using markdown.

It was good because documentation was tied to the source control and easy to locate and read when you were working on the project.

It's easy that wiki's become neglected and forgotten if there's not someone that "cracks the whip" so to speak so I think any way to lessen the friction and bring it into the coding environment is a good one

What's the engineer doing at the time? What are you doing? Why shouldn't you be the one writing the docs?