A few spelling fixes

alexwlchan · berkerpeksag · commit 513a391eb871 · 2016-12-10T10:31:22.000+03:00
diff --git a/clang.rst b/clang.rst
@@ -126,7 +126,7 @@ On Mac OS X, the libraries are installed in
 
 The installer does not install all the components needed on occasion. For
 example, you might want to run a ``scan-build`` or examine the results with
-``scan-veiw``. You can copy the components by hand with: ::
+``scan-view``. You can copy the components by hand with: ::
 
     sudo mkdir /usr/local/bin/scan-build
     sudo cp -r llvm-3.4/tools/clang/tools/scan-build /usr/local/bin
diff --git a/committing.rst b/committing.rst
@@ -327,7 +327,7 @@ pointing to the official repository. To do so, here are the steps needed to have
 that setup::
 
    git remote set-url origin https://github.com/<your-username>/cpython
-   git remote add upstrem https://github.com/python/cpython
+   git remote add upstream https://github.com/python/cpython
 
 After that, your remotes configuration should look like this::
 
diff --git a/communication.rst b/communication.rst
@@ -77,7 +77,7 @@ IRC
 Some core developers enjoy spending time on IRC discussing various issues
 regarding Python's development in the ``#python-dev`` channel on
 ``irc.freenode.net``. This is not a place to ask for help with Python, but to
-discuss issues related to Python's own development.  You can use freenode's
+discuss issues related to Python's own development.  You can use Freenode's
 `Web interface <http://webchat.freenode.net/>`_ if you don't have an IRC
 client.
 
diff --git a/coverage.rst b/coverage.rst
@@ -236,7 +236,7 @@ order to create a HTML report you can install `lcov`_. The command::
 
     make coverage-lcov
 
-assembles coverage data, removes 3rd party and system libaries and finally
+assembles coverage data, removes 3rd party and system libraries and finally
 creates a report. You can skip both steps and just run::
 
     make coverage-report
diff --git a/gitdevs.rst b/gitdevs.rst
@@ -268,7 +268,7 @@ that changeset 93654 now also has the bookmark "issueA". Bookmarks are advanced
 automatically with each subsequent commit.
 
 Once work has been completed on issueA, commit and prepare a patch for
-submission to the issue tracker. Note that Mercurial doesn't have git's concept
+submission to the issue tracker. Note that Mercurial doesn't have Git's concept
 of staging, so all changes will be committed::
 
     hg commit -m 'fix for issueA'
