Apply @hamogu minor suggestions from code review

Co-authored-by: Hans Moritz Günther <[email protected]>

Author: eteq

messages/maintainer_access.md

@@ -2,7 +2,7 @@ Hello {NAME},
 
 You have been nominated as {role} and the Coordinating Committee has enthusiastically accepted this nomination! We would be thrilled if you are able to accept this nomination. {More context might be necessary for some people - fill it in here}
 
-In case you are not familiar with the role, maintainers are the people who keep a package or sub-package working. In particular, they review and merge PRs, keep track of what's going on and organize ideas for future development (see https://www.astropy.org/team.html#Subpackage_maintainer for details). In practice this means a fair amount of community interaction when reviewing PRs and related discussion.  As a general guideline, if you have any uncertainty or if there is extended debate about merging a PR, seek consensus from other maintainers in the Project.  If necessary, you should also real free to reach out to the Coordination Committee (by @-mention on github or via [email protected]), as the Coordination Committee has the authority to make decisions when consensus cannot be acheived.
+In case you are not familiar with the role, maintainers are the people who keep a package or sub-package working. In particular, they review and merge PRs, keep track of what's going on and organize ideas for future development (see https://www.astropy.org/team.html#Subpackage_maintainer for details). In practice this means a fair amount of community interaction when reviewing PRs and related discussion.  As a general guideline, if you have any uncertainty or if there is extended debate about merging a PR, seek consensus from other maintainers in the Project.  If necessary, you should also free to reach out to the Coordination Committee (by @-mention on github or via [email protected]), as the Coordination Committee has the authority to make decisions when consensus cannot be achieved.
 
 If you would like to accept this nomination, we ask that you familiarize yourself with the following Project guidelines:
 

policies/adding-new-role-members.md

@@ -1,5 +1,5 @@
 This document describes the process for adding new people to named roles. This
-document is *not* about how people are nominated for a rolein the first place,
+document is *not* about how people are nominated for a role in the first place,
 but rather the process by which they are added once nominated. The
 process itself is in the hands of the Coordination Committee according to
 [APE0](https://github.com/astropy/astropy-APEs/blob/main/APE0.rst).
@@ -30,7 +30,6 @@ The process is:
    final decision based on any feedback.
 6. If the appointment is confirmed, the nominee is added to the roles page
    (i.e., the PR created in step 4 can be merged).
-7. If a maintainer, the nominee receives the necessary Github or other
-   permissions.
+7.  The nominee receives the necessary Github or other permissions for the new role.
 8. The Coordination Committee member sends a confirmation message to the nominee
    to complete the process.