Clarifications, more active voice, American spellings

[Technicalleigh]

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

Purpose / why

Replace this text - Restate the purpose/justification of this work and include links to the Issue inside of the purpose/why.

What changes were made?

Replace this text - State clearly the direct additions or modifications made in this change-request.

Verification

Replace this text - Document the details that help a reviewer understand what steps or actions should be taken in-order to verify the work is completed and satisfies the initial scope of work.

---

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?

[Loquacity]

This has picked up a bunch of conflicts with my PR #162 Would you like to me go through and fix the conflicts, or should we close this PR without merging?

[aidanatwork]

This has picked up a bunch of conflicts with my PR #162 Would you like to me go through and fix the conflicts, or should we close this PR without merging?

@Loquacity Please go ahead and try to resolve the conflicts. If you are getting stuck, feel free to reach out to me or Morgan Craft to help further.

[Loquacity]

Merge conflicts resolved. Ready to merge once others are happy.