From c3deebee32ed017bad0b9ed4fd5e1cad31d52db8 Mon Sep 17 00:00:00 2001 From: eduartua Date: Thu, 25 Oct 2018 20:06:31 -0500 Subject: [PATCH] Conformance of the names of the conferences file: community/committee-steering/governance/README.md --- committee-steering/governance/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/committee-steering/governance/README.md b/committee-steering/governance/README.md index b61ac493c..b99d0d6cf 100644 --- a/committee-steering/governance/README.md +++ b/committee-steering/governance/README.md @@ -18,7 +18,7 @@ All Kubernetes SIGs must define a charter defining the scope and governance of t 6. 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 or holidays. Make any necessary changes. + event such as KubeCon/CloudNativeCon or holidays. Make any necessary changes. 8. Once accepted, the steering committee will ratify the PR by merging it. ## Steps to update an existing SIG charter