Apply uncontroversial / typographical suggestions from code review

Co-authored-by: P. L. Lim <[email protected]>
Co-authored-by: Erik Tollerud <[email protected]>

Author: 3 people

policies/permissions.md

@@ -1,22 +1,22 @@
-# Permissions across the project
+# Permissions across the Project
 
 This document describes what access permissions are granted to individuals in
 different [roles in the project](https://www.astropy.org/team.html#roles).
 
 Occasional *temporary* write (or higher) permissions may be granted for specific
 tasks (for example, a maintainer may be given admin rights to a repo to
-configure CI for the first time or similar), be such permissions must be done
-temporarily unless prescribed by this document.
+configure CI for the first time or similar). Such permissions must be done
+temporarily unless prescribed otherwise by this document.
 
-For GitHub, the permissions are enforced by adding indivuals to the GitHub team
-matching their role (For Example, "Astropy Core Maintainers" or "Astropy web
-site maintainers" for a core maintainer or the astropy.org team, respectively),
+For GitHub, the permissions are enforced by adding individuals to the GitHub team
+matching their role (for example, "Astropy Core Maintainers" or "Astropy
+website maintainers" for a core maintainer or the astropy.org team, respectively),
 a duty primarily performed at the moment by the Coordination Committee.
 Temporary permissions should instead use the "collaborator" feature on Github to
 make it clear that these permissions are temporary in nature.
 
 Additionally, the granter of permissions (usually the Coordination Committee)
-should send a message to the new recipient of write permissions the
+should send a message to the new recipient of write permissions listing the
 responsibilities and expectations that go with this - a template for this email
 is available [in this repo](../messages/core_write_access.md). That message may
 contain a prompt for a response, which should be cc-ed/forwarded to
@@ -30,7 +30,7 @@ repository via the **Astropy Core Maintainers** GitHub team.
 ## Coordinated package maintainers
 
 Coordinated package maintainers receive **admin access** to the coordinated
-package repositories via the **<package name> maintainers** GitHUb team (e.g.
+package repositories via the **<package name> maintainers** GitHUb team (e.g.,
 'astroquery maintainers').
 
 ## Core package release coordinators
@@ -43,6 +43,6 @@ release maintainers** GitHub team.
 
 ## Coordination committee
 
-The coordination committee members receive **owner access** to all repositories
-in the astropy organization. In addition, they have access to the project
-password manager.
+The coordination committee members receive **owner access** to
+the astropy organization. In addition, they have access to the project
+credentials (or the shared password manager to access the credentials).