Adding guidance for minor changes to the standard

[kathrynmohror]

Proposal to add guidance to the governance document to describe the reduced process for minor ("typo", formatting) changes to the standard document. The idea is that these changes could be reviewed by the ASC chairs and release managers and simply included in the next release without requiring readings and voting.

[kathrynmohror]

Please use emoji reactions ON THIS COMMENT to indicate your position on this proposal.

• You do not need to vote on every proposal
• If you have no opinion, don't vote - that is also useful data
• If you've already commented on this issue, please still vote so
  we know your current thoughts
• Not all proposals solve exactly the same problem, so we may end
  up accepting proposals that appear to have some overlap
  This is not a binding majority-rule vote, but it will be a very
  significant input into the corresponding ASC decision.

Here are the meanings for the emojis:

• Hooray or Rocket: I support this so strongly that I
  want to be an advocate for it
• Heart: I think this is an ideal solution
• Thumbs up: I'd be happy with this solution
• Confused: I'd rather we not do this, but I can tolerate it
• Thumbs down: I'd be actively unhappy, and may even consider
  other technologies instead
  If you want to explain in more detail, feel free to add another
  comment, but please also vote on this comment.

[jjhursey]

Note to Reviewer: This PR builds off of PR #7. Until PR #7 is merged the diff will include the changes from that PR (they are separate commits to this branch). Once PR #7 is merged then we will rebase this PR.

[jjhursey]

PMIx ASC Q1'2020 Meeting:

• The first vote passed: 10 yes / 0 no / 1 abstain

[jjhursey]

PMIx ASC 2Q 2020 Meeting:

• Passed second vote: 11 Yes / 0 No / 0 Abstain / 3 not present for vote