aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Gary McDonald <mcdonagj@dukes.jmu.edu> 2023-05-29 04:22:00 -0400
committerGravatar GitHub <noreply@github.com> 2023-05-29 10:22:00 +0200
commitd34b33052fe27a225afd3b79aa921c5a293d10f3 (patch)
tree6e7f99b6ee7ddec8a4ce956fa9fb06eecb56d7a8
parente4be859d48d11e053ed186e45e9598ddcb3497a8 (diff)
downloadcoredns-d34b33052fe27a225afd3b79aa921c5a293d10f3.tar.gz
coredns-d34b33052fe27a225afd3b79aa921c5a293d10f3.tar.zst
coredns-d34b33052fe27a225afd3b79aa921c5a293d10f3.zip
Fix: Correct the spelling of committee within the Governance documentation. (#6124)
* Correct the spelling of committee within the Governance documentation. Signed-off-by: Gary McDonald <mcdonagj@dukes.jmu.edu> * Correct the spelling of steering within the Governance documentation. Signed-off-by: Gary McDonald <mcdonagj@dukes.jmu.edu> --------- Signed-off-by: Gary McDonald <mcdonagj@dukes.jmu.edu>
-rw-r--r--GOVERNANCE.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/GOVERNANCE.md b/GOVERNANCE.md
index ef358a76a..69e482ebf 100644
--- a/GOVERNANCE.md
+++ b/GOVERNANCE.md
@@ -14,7 +14,7 @@ The CoreDNS community adheres to the following principles:
The CoreDNS project has a project steering committee consisting of 5 members, with a maximum of 1 member from any single organization.
The steering committee in CoreDNS has a final say in any decision concerning the CoreDNS project, with the exceptions of
-deciding steering committe membership, and changes to project governance. See `Changes in Project Steeting Committee Membership`
+deciding steering committee membership, and changes to project governance. See `Changes in Project Steering Committee Membership`
and `Changes in Project Governance`.
Any decision made must not conflict with CNCF policy.
@@ -69,7 +69,7 @@ should have more binding votes than 1/5 of the total number of maintainers defin
The PR should be opened no earlier than 6 weeks before the end of affected committee member's term.
The PR should be kept open for no less than 4 weeks. The PR can only be merged after the end of the
-replaced committe member's term, with more +1 than -1 in the binding votes.
+replaced committee member's term, with more +1 than -1 in the binding votes.
When there are conflicting PRs for changes to a project committee member, the PR with the most
binding +1 votes is merged.
@@ -84,9 +84,9 @@ A project steering committee member may volunteer to step down, ending their ter
## Changes in Project Governance
Changes in project governance (GOVERNANCE.md) can be initiated by opening a GitHub PR.
-The PR should only be opened no earlier than 6 weeks before the end of a comittee member's term.
+The PR should only be opened no earlier than 6 weeks before the end of a committee member's term.
The PR should be kept open for no less than 4 weeks. The PR can only be merged following the same
-voting process as in `Changes in Project Steeting Committee Membership`.
+voting process as in `Changes in Project Steering Committee Membership`.
## Decision-making process