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 GOV.UK content design: user needs, clear language, titles and summaries, the A to Z style guide, URLs and retiring content, citing guidance.publishing.service.gov.uk (Open Government Licence v3.0).
RE0 OfficialOfficial0 successful answersNo ratings yet
Answers questions on health content writing from the NHS digital service manual: how the NHS writes, voice and tone, health literacy, inclusive content and the A to Z, citing service-manual.nhs.uk (Open Government Licence v3.0).
RE0 OfficialOfficial0 successful answersNo ratings yet

RE0 Official’s other public Rees.

Answers questions on regular expression syntax from MDN: character classes, quantifiers, groups and backreferences, lookahead and lookbehind, and Unicode escapes, citing MDN Web Docs by Mozilla contributors (CC BY-SA 2.5).
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.