copyediting

Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>

inactivity.md

@@ -7,30 +7,30 @@ nav_order: 6
 
 # Inactivity Policies
 
-As part of the normal lifecycle of a project codebases and maintainers come and go.  This document formalizes a Hyperledger wide polciy for archiving projects and moving maintainers to emereitus status when a proejct does not have an explicit policy of their own.
+As part of the normal lifecycle of a project codebases and maintainers come and go. This document formalizes a Hyperledger wide policy for archiving projects and moving maintainers to emeritus status when a project does not have an explicit policy of their own.
 
 ## Maintainer Inactivity
 
-Hyperledger very much appreciates the contributions of all maintainers but removing write privledges is in the interest of an orderly and secure project.
+Hyperledger very much appreciates the contributions of all maintainers but removing write privileges is in the interest of an orderly and secure project.
 
-Maintainers who have not contributed to a Hyperledger project for (`exact timeframe to be decided`) 3 / 4 / 6 months will be removed from the relevant Github Organizations.
+Maintainers who have not contributed to a Hyperledger project for (`exact timeframe to be decided`) 3 / 4 / 6 months will be removed from the relevant GitHub teams.
 
-Activity can be code contributions, code reviews, issue reporting, or any other such activity trackable by github attriubuted to a Hyperledger repository.
+Activity can be code contributions, code reviews, issue reporting, or any other such activity trackable by GitHub attributed to a Hyperledger repository.
 
-Maintainers will notified of this via an "at" @ mention in a pull request moving their name from a projects active contributors to the emeritus contributors.
+Maintainers will be notified of this via an "at" @ mention in a pull request moving their name from a projects active contributors to the emeritus contributors.
 
-Maintainers who express a desire to continue contributing will, at the maintainers request, be given a 3 month extension to contribute to the project.
+Maintainers who express a desire to continue contributing will, at the maintainers request, be given a 3-month extension to contribute to the project.
 
 Maintainers who have been moved to emeritus status may be re-added by the projects when their contributions resume and the existing maintainers approve their reactivation.
 
-These policies apply to projects that do not have an expicity maintainer inactivity policy. Where a project has an established and functioning policy the projects policies shall prevail.
+This policy applies to projects that do not have an explicit maintainer inactivity policy. Where a project has an established and functioning policy, the project's policy shall prevail.
 
 ## Repository Inactivity
 
 Any repository that has not had a release for (`exact timeframe to be decided`) 12 months or that has had no commits for 6 months may be archived by the TSC or Hyperledger staff.
 
-Projects will be notified via a PR in the appropriate repository, as well as a notice in the project appropriate Discord channel and mailing list, if they exist.
+Projects will be notified via a PR in the appropriate repository and a notice in the project corresponding Discord channel and mailing list if they exist.
 
-Generally speaking a projects expressed request to keep the repositor active will be honored.  However if a project has a lot of out of date dependencies, particulaly ones relating to security vulnerabilites, this request may not be honored.
+Generally speaking, projects that expressed a request to keep the repository active will be honoured. However, this request may not be honoured if a project has many out of date dependencies, particularly ones relating to security vulnerabilities.
 
-A request by a project to un-archive a repository for the purposes of active contirbution will be honored, unless the project is in a dormant or end-of-life state.  In those cases the project lifecycle issues will need to be resolved first.
+A request by a project to un-archive a repository for the purposes of active contribution will be honored, unless the project is in a dormant or end-of-life state. In those cases the project lifecycle issues will need to be resolved first.