Fix spelling mistakes in //docs.

docs/git_cookbook.md

 # Git Cookbook
 
 A collection of git recipes to do common git tasks.
 
 See also [Git Tips](git_tips.md).
 
 [TOC]
 
 ## Introduction
 
 This is designed to be a cookbook for common command sequences/tasks relating to
-git, git-cl, and how they work with chromium development. It might be a little
+git, git-cl, and how they work with Chromium development. It might be a little
 light on explanations.
 
 If you are new to git, or do not have much experience with a distributed version
 control system, you should also check out
 [The Git Community Book](http://book.git-scm.com/) for an overview of basic git
 concepts and general git usage. Knowing what git means by branches, commits,
 reverts, and resets (as opposed to what SVN means by them) will help make the
 following much more understandable.
 
 ## Excluding file(s) from git-cl, while preserving them for later use
@@ skipping 122 matching lines @@
 git checkout mybranch
 git reset --hard origin
 
 
 git cherry-pick abcdef  # re-apply your bad change
 git show                # grab the rietveld issue number out of the old commit
 git cl issue 12345      # restore the rietveld issue that was cleared on commit
 ```
 
 And now you can continue hacking where you left off, and since you're reusing
-the Reitveld issue you don't have to rewrite the commit message. (You may want
+the Rietveld issue you don't have to rewrite the commit message. (You may want
 to go manually reopen the issue on the Rietveld site -- `git cl status` will
 give you the URL.)
 
 ## Retrieving, or diffing against an old file revision
 
 Git works in terms of commits, not files. Thus, working with the history of a
 single file requires modified version of the show and diff commands.
 
 ```shell
 # Find the commit you want in the file's commit log.
 git log path/to/file
 # This prints out the file contents at commit 123abc.
 git show 123abc:path/to/file
 # Diff the current version against path/to/file against the version at
 # path/to/file
 git diff 123abc -- path/to/file
 ```
 
 When invoking `git show` or `git diff`, the `path/to/file` is **not relative the
 the current directory**. It must be the full path from the directory where the
 .git directory lives. This is different from invoking `git log` which
 understands relative paths.
 
 ## Checking out pristine branch from git-svn
 
-In the backend, git-svn keeps a remote tracking branch that points to the the
+In the backend, git-svn keeps a remote tracking branch that points to the
 commit tree representing the svn repository. The name of this branch is
 configured during `git svn init`. The git-svn remote branch is often named
 `origin/trunk` for Chromium, and `origin/master` for WebKit.
 
 If you want to checkout a "fresh" branch, you can base it directly off the
 remote branch for svn.
 
     git checkout -b fresh origin/trunk  # Replace with origin/master for webkit.
 
 
@@ skipping 73 matching lines @@
 
 If you have a nearby copy of a Git repo, you can quickly bootstrap your copy
 from that one then adjust it to point it at the real upstream one.
 
 1.  Clone a nearby copy of the code you want: `git clone coworker-machine:/path/to/repo`
 1.  Change the URL your copy fetches from to point at the real git repo:
     `git set-url origin http://src.chromium.org/git/chromium.git`
 1.  Update your copy: `git fetch`
 1.  Delete any extra branches that you picked up in the initial clone:
     `git prune origin`