Fix some typos

content/v3/git/blobs.md

@@ -5,7 +5,7 @@ title: Git Blobs | GitHub API
 # Blobs API
 
 Since blobs can be any arbitrary binary data, the input and responses
-for the blob api takes an encoding parameter that can be either `utf-8`
+for the blob API takes an encoding parameter that can be either `utf-8`
 or `base64`.  If your data cannot be losslessly sent as a UTF-8 string,
 you can base64 encode it.
 

content/v3/git/refs.md

@@ -41,7 +41,7 @@ For a full refs listing, you'll get something that looks like:
 
     POST /repos/:user/:repo/git/refs
 
-### Paramaters
+### Parameters
 
 ref
 : _String_ of the name of the fully qualified reference (ie: `refs/heads/master`).
@@ -59,7 +59,7 @@ sha
 
     PATCH /repos/:user/:repo/git/refs/:ref
 
-### Paramaters
+### Parameters
 
 sha
 : _String_ of the SHA1 value to set this reference to

content/v3/git/tags.md

@@ -4,7 +4,7 @@ title: Git Tags | GitHub API
 
 # Tags API
 
-This tags api only deals with tag objects - so only annotated tags, not
+This tags API only deals with tag objects - so only annotated tags, not
 lightweight tags.
 
 ## Get a Tag

content/v3/oauth.md

@@ -179,14 +179,14 @@ scopes
 ### Input
 
 scopes
-: _Optional_ **array** - Replaces the authorization' scopes with these.
+: _Optional_ **array** - Replaces the authorization scopes with these.
 
 add_scopes
 : _Optional_ **array** - A list of scopes to add to this authorization.
 
 remove_scopes
 : _Optional_ **array** - A list of scopes to remove from this
-authorizatin.
+authorization.
 
 You can only send one of these scope keys at a time.
 

content/v3/orgs.md

@@ -42,7 +42,7 @@ company
 : _Optional_ **string**
 
 email
-: _Optional_ **string** - Publically visible email address.
+: _Optional_ **string** - Publicly visible email address.
 
 location
 : _Optional_ **string**

content/v3/orgs/teams.md

@@ -5,7 +5,7 @@ title: Organization Teams | GitHub API
 # Org Teams API
 
 All actions against teams require at a minimum an authenticated user who
-is a member of the owner's team in the `:org` being managed. Api calls
+is a member of the owner's team in the `:org` being managed. API calls
 that require explicit permissions are noted.
 
 ## List teams
@@ -44,13 +44,13 @@ repo\_names
 permission
 : _Optional_ **string**
 
-  `pull` - team members can pull, but not push or administor this
+  `pull` - team members can pull, but not push or administer this
   repositories. **Default**
 
-  `push` - team members can pull and push, but not administor this
+  `push` - team members can pull and push, but not administer this
   repositores.
 
-  `admin` - team members can pull, push and administor these
+  `admin` - team members can pull, push and administer these
   repositories.
 
 <%= json \

content/v3/repos/collaborators.md

@@ -17,11 +17,11 @@ title: Repo Collaborators | GitHub API
 
     GET /repos/:user/:repo/collaborators/:user
 
-### Reponse if user is a collaborator
+### Response if user is a collaborator
 
 <%= headers 204 %>
 
-### Reponse if user is not a collaborator
+### Response if user is not a collaborator
 
 <%= headers 404 %>
 

content/v3/repos/hooks.md

@@ -15,7 +15,7 @@ The default event is `push`.  The available events are:
 * `issues` - Any time an Issue is opened or closed.
 * `issue_comment` - Any time an Issue is commented on.
 * `commit_comment` - Any time a Commit is commented on.
-* `pull_request` - Any time a Pull Request is opend, closed, or
+* `pull_request` - Any time a Pull Request is opened, closed, or
   synchronized (updated due to a new push in the branch that the pull
 request is tracking).
 * `gollum` - Any time a Wiki page is updated.
@@ -30,7 +30,7 @@ request is tracking).
 
 For a Hook to go through, the Hook needs to be configured to trigger for
 an event, and the Service has to listen to it.  The Services are all
-part of the open source [github-services](https://github.com/github/github-services) project.Most of the Services only listen for `push` events.  However, the generic [Web Service](https://github.com/github/github-services/blob/master/services/web.rb) listens for all events.  Other services like the [IRC Service](https://github.com/github/github-services/blob/master/services/irc.rb) may only listen for `push`, `issues`, and `pull_request` events.  
+part of the open source [github-services](https://github.com/github/github-services) project. Most of the Services only listen for `push` events.  However, the generic [Web Service](https://github.com/github/github-services/blob/master/services/web.rb) listens for all events.  Other services like the [IRC Service](https://github.com/github/github-services/blob/master/services/irc.rb) may only listen for `push`, `issues`, and `pull_request` events.  
 
 ## List
 

content/v3/users.md

@@ -38,7 +38,7 @@ name
 : _Optional_ **string**
 
 email
-: _Optional_ **string** - Publically visible email address.
+: _Optional_ **string** - Publicly visible email address.
 
 blog
 : _Optional_ **string**

content/v3/users/emails.md

@@ -4,7 +4,7 @@ title: User Emails | GitHub API
 
 # User Emails API
 
-Mangement of email addresses via the API requires that you are
+Management of email addresses via the API requires that you are
 authenticated.
 
 ## List email addresses for a user

content/v3/users/followers.md

@@ -25,7 +25,7 @@ List who a user is following:
 
     GET /users/:user/following
 
-List who the authenicated user is following:
+List who the authenticated user is following:
 
     GET /user/following