Update README.md

pedantic fix of typos, that were not even displayed when the markdown was rendered on GitHub

1 files changed, 5 insertions, 5 deletions

diff --git a/committee-steering/governance/README.md b/committee-steering/governance/README.md
index b99d0d6c..bd372e2c 100644
--- a/committee-steering/governance/README.md
+++ b/committee-steering/governance/README.md
@@ -13,13 +13,13 @@ All Kubernetes SIGs must define a charter defining the scope and governance of t
 3. Fill out the template for your SIG
 4. Update [sigs.yaml] with the individuals holding the roles as defined in the template.
 5. Add subprojects owned by your SIG in the [sigs.yaml]
-5. Create a pull request with a draft of your charter.md and sigs.yaml changes.  Communicate it within your SIG
+6. Create a pull request with a draft of your charter.md and sigs.yaml changes. Communicate it within your SIG
    and get feedback as needed.
-6. Send the SIG Charter out for review to steering@kubernetes.io.  Include the subject "SIG Charter Proposal: YOURSIG"
+7. Send the SIG Charter out for review to steering@kubernetes.io. Include the subject "SIG Charter Proposal: YOURSIG"
    and a link to the PR in the body.
-7. Typically expect feedback within a week of sending your draft.  Expect longer time if it falls over an
-   event such as KubeCon/CloudNativeCon or holidays.  Make any necessary changes.
-8. Once accepted, the steering committee will ratify the PR by merging it.
+8. Typically expect feedback within a week of sending your draft. Expect longer time if it falls over an
+   event such as KubeCon/CloudNativeCon or holidays. Make any necessary changes.
+9. Once accepted, the steering committee will ratify the PR by merging it.
 
 ## Steps to update an existing SIG charter