Clarifying these are placeholders for Community SIG work to-be-done

- discussion operate-first/community#107 (comment)

Signed-off-by: Karsten Wade <kwade@redhat.com>

governance.md

@@ -31,7 +31,7 @@ The subprojects are where the work happens, and the SIGs organize and guide thei
 A healthy open source project is one that demonstrates open practices, uses open infrastructure, and cultivates an open culture with the goal of becoming more sustainable.
 
 ### Principles
-As a new community with a vision to grow, we are following in the footsteps of many massively scaled and successful projects. We want to take care to learn from those who came before us, while forging our own path into the challenges we've chosen to undertake.
+As a new cloud-native community growing up at the footsteps of massively scaled and successful projects such as Kubernetes and OpenInfra, we want to be careful to learn from those who came before us, while forging our own path into the challenges we've chosen to undertake.
 
 To stand up this Governance for a 1.0 good-enough minimal-viable-governance (MVG), we are looking to our key predecessors for some of our starting points.
 As an initial set of principles we are combining elements of the [Kubernetes community principles](https://github.com/kubernetes/community/blob/master/governance.md#principles) and the [OpenInfra Foundations Four Opens](https://openinfra.dev/four-opens/).
@@ -45,8 +45,8 @@ These are the Op1st community principles we adhere to:
   - This is crucial to fulfilling our mission around open sourcing operations
 2. **Welcoming and respectful** : We intend to be an open, welcoming, and inclusive community.
 Diversity is our strength.
-We have and follow a [Code of Conduct](https://operate-first.cloud/community/code_of_conduct/).
-  - We currently follow the [OpenInfra Foundation Code of Conduct](https://www.openstack.org/legal/community-code-of-conduct/) as a member of the OpenInfra Labs.
+We have and follow a Code of Conduct.
+  - We currently follow the OpenInfra Foundation Code of Conduct as a member of the OpenInfra Labs.
 3. **Open Design** : We follow a transparent and open process for planning and designing any content, services, and features of Op1st.
 Ideas and contributions are accepted according to their technical merit and alignment with project objectives, scope, and design principles.
 4. **Open Work** : Two of our core tools for successful community building are transparency and accessibility.
@@ -69,7 +69,6 @@ We are opening the Governance 1.0 directly borrowing from the [Kubernetes commun
 This section outlines the various responsibilities of contributor roles in Op1st.
 The Op1st project is subdivided into subprojects under SIGs.
 Responsibilities for most roles are scoped to these subprojects.
-"[Ownership, roles and responsibilities](https://stumblingabout.com/2011/01/27/ownership-roles-and-responsibilities/)" is a good external reference for understanding how the project roles interact.
 
 A contribution can take many, many forms, such as: documentation, code, best-practices content, marketing materials, running a meeting, helping a user in chat, operating a cluster, responding to a `help wanted` flag, reviewing and commenting on contributions of all these types when in a proposed-state (a _pull request_ or _PR_), giving a talk at a conference, staffing a booth at a conference, and so forth.
 For a longer list, refer to this chapter, "[What Is A Contribution?](https://www.theopensourceway.org/the_open_source_way-guidebook-2.0.html#_what_is_a_contribution)", which includes these definitions: