Minor grammar corrections and misspelled words in GOVERNANCE.adoc (#1511

)

Motivation:

To have the GOVERNANCE.adoc file with correct grammar and without misspelled words.

Modifications:

- Minor corrections on GOVERNANCE.adoc.

Result:

The GOVERNANCE.adoc file with correct grammar and without misspelled words.

GOVERNANCE.adoc

@@ -10,11 +10,11 @@ reading the xref:CONTRIBUTING.adoc[Contributor Guidelines].
 == Decision-Making and Voting
 ServiceTalk is an open source project, and GitHub serves as the source of truth for the project. Technical disagreements
 may come up, but all community members are always expected to follow the xref:CODE_OF_CONDUCT.adoc[Code of Conduct]. In
-general it is preferred that direction can be mutually agreed upon by community members. If a disagreement cannot be
+general, it is preferred that direction can be mutually agreed upon by community members. If a disagreement cannot be
 resolved independently, the <<Maintainers>> can be called in to vote on the proposal (e.g. issue/PR) in question. An
 independent link:https://github.com/apple/servicetalk/issues[GitHub issue] should be opened prefixed with "[Vote]" and
 reference the proposal in question. The voting period should remain open for at least 2 weeks. Each Maintainer gets one
-yes/no vote and the majority will decide the direction. The final decision including the rational for the majority
+yes/no vote, and the majority will decide the direction. The final decision including the rationale for the majority
 decision must be summarized by a Maintainer.
 
 == Maintainers
@@ -27,7 +27,7 @@ project, demonstrate maturity/adoption, and then be considered for contribution
 
 === Become a Maintainer
 Making contributions does not require becoming a maintainer, or obtaining commit access to the ServiceTalk
-organization. However if you are interested in taking a more formal role with decision-making power you should
+organization. However, if you are interested in taking a more formal role with decision-making power you should
 consider becoming a Maintainer. Some characteristics of a Maintainer are as follows:
 
 * Be involved in contributing code, pull request review, triage of issues and addressing user questions in one or more
@@ -36,11 +36,11 @@ forums such as GitHub, Stackoverflow, etc.
 * Show deep understanding of the areas contributed to, and good consideration of various reliability, usability,
 backward compatibility, and performance requirements.
 
-If you believe you satisfy these above criteria please open a
+If you believe you satisfy these above criteria, please open a
 link:https://github.com/apple/servicetalk/compare[GitHub pull request] modifying the
 xref:MAINTAINERS.adoc[Maintainers doc] describing at least 5 non-trivial pull requests that have
 been accepted without major modifications. Please also make your case as to why you feel you will need Maintainer status
-moving forward and intention of continued involvement. Existing Maintainers must vote on the PR and a majority
+moving forward and intention of continued involvement. Existing Maintainers must vote on the PR, and a majority
 vote is required to merge and add the new Maintainer (see <<Decision-Making and Voting>>).
 
 === Expectations of a Maintainer
@@ -66,5 +66,5 @@ Any disagreements will be resolved by a vote of the Maintainers per the voting p
 Multiple violations of the Maintainer policies or a single egregious violation may result in loss of Maintainer status.
 
 == Releases
-Releases are generated by ServiceTalk Maintainers. They are generated roughly on a montly cadence, and can be done more
+Releases are generated by ServiceTalk Maintainers. They are generated roughly on a monthly cadence, and can be done more
 frequently at the discretion of the Maintainers if more urgent issues arise.