I'm looking for a short list of Do/Don't items that people can refer to when writing documentation. Something that people with English as a (long used and familiar) second language can understand.
In a similar vein of thinking, I've run into multiple people in operations and development who feel like documentation is something someone else does. They don't feel the need to write descriptive ticket comments. Nor do they want to learn about best practices and standards. I guess this feeds into the more general question of how do you push people to improve themselves?
The first step is to write a clear explanation to sincerely answer why what you're proposing is an improvement. How does the practice which you're proposing fulfill a need?
Remember that your being loved is less important than being effective.
Note, however, that reluctance may be embarrassment or lack of self confidence in writing. I have worked with some remarkably good tech people who would do anything to wriggle out of writing comments ... because they thought themselves bad at it. Maybe point out perfection isn't the issue, capturing the information that someone else can understand (grammar Nazis notwithstanding) is...