typo fix

Author: king6cong

README.md

@@ -57,7 +57,7 @@ Also, you can open the repository's page, using the `open` command:
 
 ### Requests for merges *(aka Pull Requests aka Merge Requests)*
 
-Once you're all set with your repository, you can check requests to merge 
+Once you're all set with your repository, you can check requests to merge
 (aka Pull Requests on github) using the `request` command:
 
     % git hub request guyzmo/git-repo list
@@ -109,7 +109,7 @@ And when you're done you just get rid of it:
     Successfully deleted gist!
 
 > *Nota Bene*: Thanks to `git` CLI flexibility, by installing `git-repo` you directly
-> have acces to the tool using `git-repo hub …` or `git repo hub …`. For the
+> have access to the tool using `git-repo hub …` or `git repo hub …`. For the
 > `git hub …` call, you have to set up aliases, see below how to configure that.
 
 And as a bonus, each time it's adding a new remote, it's updating the `all` remote,
@@ -188,7 +188,7 @@ So you can run the tool as a git subcommand:
 ### Development
 
 For development, I like to use `buildout`, and the repository is already configured
-for that. All you have to do, is install buildout, and then call it from the root of 
+for that. All you have to do, is install buildout, and then call it from the root of
 the repository:
 
     % pip install zc.buildout
@@ -214,15 +214,15 @@ and a real connection, when testing the API on minor changes. Those recordings a
 called cassettes, thanks to the [betamax](https://github.com/sigmavirus24/betamax) framework
 being in use in the test suites.
 
-When running existing tests, based on the provided cassettes, you don't need any 
+When running existing tests, based on the provided cassettes, you don't need any
 setting. Also, if you've got a configuration in `~/.gitconfig`, the tests will use
 them. Anyway, you can use environment variables for those settings (environment
 variables will have precedence over the configuration settings):
 
 To use your own credentials, you can setup the following environment variables:
 
 * `GITHUB_NAMESPACE` (which defaults to `not_configured`) is the name of the account to use on github
-* `GITLAB_NAMESPACE` (which defaults to `not_configured`) is the name of the account to use on gitlab 
+* `GITLAB_NAMESPACE` (which defaults to `not_configured`) is the name of the account to use on gitlab
 * `BITBUCKET_NAMESPACE` (which defaults to `not_configured`) is the name of the account to use on bitbucket
 * `PRIVATE_KEY_GITHUB` your private token you've setup on github for your account
 * `PRIVATE_KEY_GITLAB` your private token you've setup on gitlab for your account