Copy Edit

[Loquacity]

ALL Pull-Requests require an associated Issue as documented in How to contribute.

Fixes: #96

Purpose / why

End-to-end copyedit of all templates and their companion docs.

What changes were made?

Style and wording updates to meet GDSG standards

Verification

Please check for any typos or style issues that might have been introduced or missed.

Notes for reviewers

• I have not edited logging/template-logging.adoc, reference/template-reference.adoc, or tutorial/template-tutorial.adoc as they need to be changed into markdown, and a lot of the content needs to be moved out of the template and into the companion doc. TODO: Create issues for this.
• We have lots of different terms for the people reading the docs created with the templates, I have standardised on "reader" where it's obvious it's the person reading the document created with the template, but have left it as "user" if it's specific to someone using a product (as opposed to reading a doc). TODO: As a group, do we agree with this? Document this choice.
• I have standardised across the various documents a fair bit (eg: "the overview section" in the companion docs), but please point out any internal inconsistencies you notice. TODO: Should we consider using snippets/content reuse for stuff that is repeated frequently?

---

Checklist

Pull-request reviewer should ensure the following

• Are issues linked correctly?
• Is this PR labeled correctly?
• If template updates: do they align with developers.google.com/style/?
• Did the PR receive at least one 👍 and no 👎 from core-maintainers?
• On merging, did you complete the merge using keywords?
• On merging, did you add any applicable notes to a draft release and link to this PR?

[jaredmorgs]

From a US dialect edit this is definitely approved.

There are some wider questions about title casing that may need to be started up as a mailing list discussion.

I don't feel that the title casing issues should block this PR from being merged, in the spirit of iterative releases.

[Loquacity]

Suggested change

	### Step 1: Optional: Title for step - image or screenshot
	### Step 1 (Optional): Title for step - image or screenshot

What about this?

[camerons]

A few minor typos, and a number of minor suggestions which I suggest addressing.

[camerons]

While I think it was me who originally suggested putting writing instructions inside comments, we've since realized that many people look at these templates from the github website interface, were the comments are not rendered.
So we should move all these comments into some {text inside brackets} or similar. See what Alyssa has done with the style guide: https://github.com/thegooddocsproject/incubator/blob/master/style-guide/template-style-guide.md

This comment applies to other instances in this pull request.