Skip to content

Commit 533039e

Browse files
authored
Typos
1 parent 3e9054f commit 533039e

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

project-roles/trusted-committer.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ work of the contributor above and beyond single contributions.
4040
## Defining the Trusted Committer Role for a Project
4141

4242
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
4444
documented somewhere in your project. This sets expectations for new community
4545
members and outlines the role for future candidates.
4646

@@ -53,7 +53,7 @@ in community support.
5353

5454
* A good candidate for a Trusted Committer, is someone who frequently submits
5555
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,
5757
consider approaching them about opportunities for further collaboration on the
5858
project.
5959

@@ -114,7 +114,7 @@ example:
114114
* No longer employed by the company
115115

116116
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
118118
a project's **Trusted Committer** section to a list of past contributors.
119119

120120
After access is removed it is courteous to [thank the Trusted Committer for

0 commit comments

Comments
 (0)