Address PR comments re: approvers list

contributors/devel/contributing-api-changes.md

@@ -84,11 +84,11 @@ Expected time for next slot: 4-8 weeks
 
 Schedule a time for your design to be reviewed.
 
-Design approvers:
-- @smarterclayton
-- @bgrant0607
-- @thockin
-- @erictune
+See the current list of [design approvers](https://github.com/orgs/kubernetes/teams/api-approvers)
+
+**Note**: these are the current reviewers, we are still figuring out how to
+add/remove people to this list.  For more information, see the
+[governance discussion](https://groups.google.com/forum/#!topic/kubernetes-dev/4e8WOnMvZC0)
 
 ### Implement the proposal
 
@@ -99,6 +99,8 @@ Once the proposal has been accepted an merged, you can begin implementing the so
 Escalation should be done through the owning SIG.  If you need help getting attention, reach out to your
 SIG.
 
+FOr a
+
 ## API change considerations
 
 First read the [API changes] document for background on how to make changes in the API.
@@ -115,9 +117,9 @@ existing fields are validated, defaulted, or interpreted requires an API version
 It is important to pick the correct API group for your API.  This will ensure that it is discoverable
 by users and is maintained in concert with related APIs.  Current API groups:
 
-| Group  | Description  |
-|---|---|
-| abac |   |
+| Group  | Description |
+| ------ | ----------- |
+| abac   |             |
 | apps |   |
 | authentication |   |
 | authorization |   |