Update committee-steering/governance/project-naming.md

Co-authored-by: Patrick Ohly <patrick.ohly@intel.com>

Author: BenTheElder

committee-steering/governance/project-naming.md

@@ -6,6 +6,6 @@ The Kubernetes project has historically named most of our components/projects wi
 
 We recommend *but do not require* Kubernetes SIGS consider leveraging these when naming new subprojects, to further identify as an official project.
 
-We ask that third-party projects refrain from confusing names that sound like an official Kubernetes subproject, IE "kube", "k8s", "kubernetes" substrings and pick some alternate creative name, with a notable exception for [Conformant Distros](https://www.cncf.io/training/certification/software-conformance/). Many existing projects have not done this, and we are not seeking to alter them, but do remember that "k8s" and "kubernetes" are protected trademarks.
+We ask that third-party projects refrain from using confusing names that sound like an official Kubernetes subproject, i.e. "kube", "k8s", "kubernetes" substrings and pick some alternate creative name, with a notable exception for [Conformant Distros](https://www.cncf.io/training/certification/software-conformance/). Many existing projects have not done this, and we are not seeking to alter them, but do remember that "k8s" and "kubernetes" are protected trademarks.
 
 If you'd like to start a new sub-project within the Kubernetes project, see our [repository donation / creation guidelines](https://git.k8s.io/community/github-management/kubernetes-repositories.md)