Docs: Update multiple typo fixes

docs/api.rst

@@ -110,7 +110,7 @@ With an HTTP 200, you'll get back a set of results in JSON.
                "num_answers": ...         # total number of answers
                "locale": ...              # the locale for the question
                "metadata": ...            # metadata collected for the question
-               "tags": ...                # tags for the qeustion
+               "tags": ...                # tags for the question
                "num_votes_past_week": ... # the number of votes in the last week
                "num_votes": ...           # the total number of votes
                "product": ...             # the product

docs/deployments.rst

@@ -44,7 +44,7 @@ Dev
 ===
 
 Dev is a small environment that is updated manually. We use it primarily to
-develop infrastructure changes, like uprading to Python 2.7.
+develop infrastructure changes, like upgrading to Python 2.7.
 
 
 Stage

docs/hacking_howto.rst

@@ -150,7 +150,7 @@ Setting up an Environment
 =========================
 
 It is strongly recommended to run Kitsune in a virtual environment, which is a
-tool to isolate Python environments from eachother and the system. It makes
+tool to isolate Python environments from each other and the system. It makes
 local development much easier, especially when working on multiple projects.
 
 To create a virtual environment::

docs/patching.rst

@@ -69,7 +69,7 @@ You should only need to do that once. Here's the bit to do every time::
 
 Eventually you'll get an r+. If you have commit access, now you can go ahead
 and merge your branch. You may, if you want, rebase your branch to clean up
-any embarassing mistakes, but it isn't required. If you don't have commit
+any embarrassing mistakes, but it isn't required. If you don't have commit
 access the next part will be done by someone who does.
 
 There are two options. The first is to press the Big Green Button in GitHub PRs
@@ -131,7 +131,7 @@ The correct way to keep your local master up to date is::
     git reset --hard mozilla/master
 
 This will forcibly move your local master branch to whatever is on the Mozilla
-master branch, destroying anything you have commited that wasn't pushed.
+master branch, destroying anything you have committed that wasn't pushed.
 Remember to always work on a branch that is not master!