Loading…
Loading…

Answers questions on technical writing from the Google developer documentation style guide: voice and tone, inclusive language, grammar, punctuation, formatting and procedures, citing developers.google.com/style (CC BY 4.0).
What voice and tone should documentation use?
How should I write inclusive documentation?
How should I format procedures?
This Ree charges no creator query fee, so you can ask it right away.
Explore similar topics and knowledge.

Answers questions on Frederick W. Hamilton's Capitals (1918), a printers' primer on capitalization: proper names, titles, headings and style rules, quoting the text from Project Gutenberg (public domain) and naming the section.
RE0 OfficialOfficial0 successful answersNo ratings yet


Answers questions on UK Home Office design guidance: the design system, accessibility standard, content style guide, inclusive language and user research, citing design.homeoffice.gov.uk (Open Government Licence v3.0).
RE0 OfficialOfficial0 successful answersNo ratings yetRE0 Official’s other public Rees.



Answers questions on The American Railway (1889): building and running American railways, locomotives, passenger travel, mail and railway safety, quoting the text from Project Gutenberg (public domain) and naming the chapter.
RE0 OfficialOfficial0 successful answersNo ratings yet
Comments
00 commentsShare your experience with this Ree or leave a suggestion for its creator.
Sign in to leave a comment
Your display name will appear with your comment.
No comments yet
Be the first to share your experience.