@@ -40,7 +40,7 @@ work of the contributor above and beyond single contributions.
40
40
## Defining the Trusted Committer Role for a Project
41
41
42
42
What a Trusted Committer handles is up to each project and its maintainers.
43
- Whatever shape your Trusted Committer role takes make sure it's clearly
43
+ Whatever shape your Trusted Committer role takes, make sure it's clearly
44
44
documented somewhere in your project. This sets expectations for new community
45
45
members and outlines the role for future candidates.
46
46
@@ -53,7 +53,7 @@ in community support.
53
53
54
54
* A good candidate for a Trusted Committer, is someone who frequently submits
55
55
code, documentation, or other repository changes. Start by including this
56
- person on pull requests. If they are actively engaing in pull requests,
56
+ person on pull requests. If they are actively engaging in pull requests,
57
57
consider approaching them about opportunities for further collaboration on the
58
58
project.
59
59
@@ -114,7 +114,7 @@ example:
114
114
* No longer employed by the company
115
115
116
116
In each of the above cases a plan for removing access to project resources
117
- should agreed upon by both parties. This includes transitioning their entry in
117
+ should be agreed upon by both parties. This includes transitioning their entry in
118
118
a project's ** Trusted Committer** section to a list of past contributors.
119
119
120
120
After access is removed it is courteous to [ thank the Trusted Committer for
0 commit comments