Copyedit comments

Publishing Tasks: Phase 6 Sustainability Accessibility

Copyedit comments

---

Contents of this page:

• Issue comment
• Pull Request comment

---

Issue comment

This comment can be use as a template to post in the Issue comment thread when the copyedits are ready to be reviewed by the author and editor:

Hello @author and @editor, I've prepared a [PR with the copyedits for your review](https://github.com/programminghistorian/ph-submissions/pull/XXX).

There, you'll be able to [review the 'rich-diff'](https://github.com/programminghistorian/ph-submissions/pull/XXX/files) to see my edits in detail. You'll also find brief instructions for how to reply to any questions or comments which came up during the copyedit.

When you're both happy, we can merge in the PR.

Pull Request comment

This comment can be use as a template to post in the Pull Request comment thread when the copyedits are ready to be reviewed by the author and editor:

Hello @author and @editor. I've now prepared the copyedits for this lesson. I'd be grateful if you could review the adjustments and confirm that you are happy for me to merge these. You can see the details of my edits under the [files changed](https://github.com/programminghistorian/ph-submissions/pull/XXX/files) tab!

You can respond to any of my suggestions via the comments if there are any, or click to _Resolve conversation_ if you're happy with them like this:

![image](https://github.com/programminghistorian/jekyll/assets/143802849/6a73acb9-215d-4fe1-8ab7-247921a3e6a4)

If you want to make edits, please work [here](https://github.com/programminghistorian/ph-submissions/pull/XXX/files) by clicking the three dots at the upper right of the file, then _Edit file_:

#Take screenshot of relevant lesson