* docs: adding documentation writing guidelines * update * Apply suggestions from code review Co-authored-by: Marie Gauthier <marie.gauthier63@gmail.com> Co-authored-by: Ryan Christoffersen <12519942+ryanchristo@users.noreply.github.com> Co-authored-by: likhita-809 <78951027+likhita-809@users.noreply.github.com> Co-authored-by: Marie Gauthier <marie.gauthier63@gmail.com> Co-authored-by: Ryan Christoffersen <12519942+ryanchristo@users.noreply.github.com>
822 B
822 B
Documentation Writing Guidelines
Best Practices
- Check the spelling and grammar, even if you have to copy and paste from an external source.
- Use simple sentences. Easy-to-read sentences mean the reader can quickly use the guidance you share.
- Try to express your thoughts in a concise and clean way.
- Don't abuse
codeformat when writing in plain English. - Follow Google developer documentation style guide.
- Check the meaning of words in Microsoft's A-Z word list and term collections (use the search input!).
Technical Writing Course
Google provides a free course for technical writing.