Merge pull request #6 from elharo/typo

Author: tdcmeehan

CONTRIBUTING.md

@@ -20,9 +20,9 @@ To create one:
 
 1. Fork the https://github.com/prestodb/rfcs repository
 2. Copy the template file `RFC-0000-template.md` to `RFC-00xx-your-feature.md` and fill it out with your proposal.
-   The template is a guideline, feel free to add sections as appropriate
-3. You may also have the template simply link to another editor, like a Google Docs file, but please ensure that the
-   document is publicly visible.  This can make the template easier to add edit, but commenting doesn’t scale very well, so
+   The template is a guideline. Feel free to add sections as appropriate.
+3. The RFC may simply link to another editor, like a Google Docs file, but please ensure that the
+   document is publicly visible.  This can make the RFC easier to edit, but commenting doesn’t scale very well, so
    please use this option with caution.
 
 ## Step 2: Get Feedback on the RFC
@@ -34,14 +34,14 @@ To create one:
 4. A committer will review your proposal.
 5. Build consensus. Those committers will review your PR and offer feedback. Revise your proposal as needed until
    everyone agrees on a path forward. Additional forums you can share the proposal on include the
-   [the mailing list](https://lists.prestodb.io/g/presto-dev), and the
+   [the mailing list](https://lists.prestodb.io/g/presto-dev) and the
    [Slack channel in #dev](https://communityinviter.com/apps/prestodb/prestodb). Tagging interested stakeholders
    (identifiable via [CODEOWNERS](https://github.com/prestodb/presto/blob/master/CODEOWNERS)) can help with consensus building.
 
 _(Note: A proposal may get rejected if it comes with unresolvable drawbacks or if it’s against the long term plans of the Presto committers)_
 
 ## Step 3: Implement your Feature
-1. If your RFC PR is accepted then the PR will be merged.
+1. If your RFC PR is accepted, then the PR will be merged.
 2. As soon as possible, create an issue in Github in the relevant repository (most likely
    [prestodb/presto](https://github.com/prestodb/presto)) summarizing the RFC and linking to it.
 3. When you submit PRs to implement your proposal, remember to link to your issue that has a link to the RFC

README.md

@@ -13,7 +13,7 @@ an opportunity to suggest refinements before you start code.  For example, they
 your work would otherwise collide with, or they may suggest implementation changes that make your feature more broadly
 usable.
 
-Smaller changes, including bug fixes and documentation improvements can be implemented and reviewed via the normal
+Smaller changes, including bug fixes and documentation improvements, can be implemented and reviewed via the normal
 GitHub pull request workflow on the main Presto repo.
 
 RFCs are more suitable for design proposals that are too large to discuss on a feature-request issue, like adding new