CIO-83 Fix typos in readme and contributing guidelines

Author: MrAaronCasanova

CONTRIBUTING.md

@@ -14,7 +14,7 @@ Please note we have a code of conduct, please follow it in all your interactions
     * Commit messages should follow the PROJECT-ISSUE MESSAGE convention. e.g. `CIO-60 Add missing contributing guidelines`
 
 3. Update README and with any necessary changes such as adding hot keys, updating instructions, fixing help text, etc.
-4. Reference the issue the PR aims to resolve using the hash tag at the beggining of your PR description. e.g. `Fixes #52`
+4. Reference the issue the PR aims to resolve using the hash tag at the beginning of your PR description. e.g. `Fixes #52`
 
 ## Code of Conduct
 

README.md

@@ -2,7 +2,7 @@
 [![npm version](https://badge.fury.io/js/check-it-out.svg)](https://badge.fury.io/js/check-it-out) [![GitHub version](https://badge.fury.io/gh/jwu910%2Fcheck-it-out.svg)](https://badge.fury.io/gh/jwu910%2Fcheck-it-out)
 Check it out, before you checkout.
 
-Too many keystrokes just to checkout a branch? Tired of long branch names? Don't remember what branches are available? Don't be bothered by fix-a-bug-where-code-is-broken-becuase-bad branch names any more! Check It Out gives you the interactive power to see your branches and check them out with fewer keystrokes.
+Too many keystrokes just to checkout a branch? Tired of long branch names? Don't remember what branches are available? Don't be bothered by fix-a-bug-where-code-is-broken-because-bad branch names any more! Check It Out gives you the interactive power to see your branches and check them out with fewer keystrokes.
 
 ## Requirements
 [Node >= v7.0](https://nodejs.org/en/blog/release/v7.0.0/) - Required for async/await