Update CONTRIBUTING.md

Author: sushant-varanasi

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # Contributing Guidelines
 
-For anyone looking to get involved to this project, we are glad to hear from you. Here are a few types of contributions
+For anyone looking to get involved in this project, we are glad to hear from you. Here are a few types of contributions
 that we would be interested in hearing about.
 
 *  Bug fixes
@@ -12,14 +12,12 @@ that we would be interested in hearing about.
     -  If you'd like to accomplish something in the library that it doesn't already do, describe the problem in a new
        Github Issue.
     -  Issues that have been identified as a feature request will be labelled `enhancement`.
-    -  If you'd like to implement the new feature, please wait for feedback from the project maintainers before spending
-       too much time writing the code. In some cases, `enhancement`s may not align well with the project objectives at
-       the time.
+    -  If you'd like to implement the new feature, please wait for feedback from the project maintainers before spending too much time writing the code. In some cases, `enhancement's may not align well with the project objectives at the time.
 *  Tests, Documentation, Miscellaneous
     -  If you think the test coverage could be improved, the documentation could be clearer, you've got an alternative
-       implementation of something that may have more advantages, or any other change we would still be glad hear about
+       implementation of something that may have more advantages or any other change we would still be glad to hear about
        it.
-       -  If its a trivial change, go ahead and send a Pull Request with the changes you have in mind
+       -  If it's a trivial change, go ahead and send a Pull Request with the changes you have in mind
        -  If not, open a Github Issue to discuss the idea first.
 
 ## Requirements
@@ -37,7 +35,7 @@ continue to add more commits to the branch you have sent the Pull Request from.
 
 1. Fork this repository on GitHub.
 1. Clone/fetch your fork to your local development machine.
-1. Create a new branch (e.g. `issue-12`, `feat.add_foo`, etc) and check it out.
+1. Create a new branch (e.g. `issue-12`, `feat.add_foo`, etc.) and check it out.
 1. Make your changes and commit them. (Did the tests pass?)
 1. Push your new branch to your fork. (e.g. `git push myname issue-12`)
 1. Open a Pull Request from your new branch to the original fork's `master` branch.