Fix spelling mistakes in //docs.

docs/vanilla_msysgit_workflow.md

 # Vanilla msysgit workflow
 
 This describes how you can use msysgit on Windows to work on the Chromium git
 repository, without setting up Cygwin or hacking the `git cl`, `git try` and
 other scripts to work under a regular Windows shell.
 
 The basic setup is to set up a regular git checkout on a Linux (or Mac) box, and
 use this exclusively to create your branches and run tools such as `git cl`, and
 have your Windows box treat this git repository as its upstream.
 
@@ skipping 80 matching lines @@
     1.  `git push`
 1.  Later, on Linux:
     1.  `make_new_lkgr_branch lk0428`
     1.  `git merge lk0428 lk0426-mytopic`
     1.  `git branch -m lk0426-mytopic lk0428-mytopic` (to rename)
     1.  `git merge lk0428-mytopic lk0426-mytopic-nextstep`
     1.  `git branch -m lk0428-mytopic-nextstep lk0428-mytopic-nextstep`
         (to rename)
 1.  Later, when you want to commit one of the earlier changes in the pipeline;
     all on Linux.  The reason you may want to create the separate tip-of-tree
-    branch is in case the trybots show your change failing on tip-of-tree and
+    branch is in case the try bots show your change failing on tip-of-tree and
     you need to do significant additional work, this avoids having to roll back
     the tip-of-tree merge:
 
 Janitorial work on Windows:
 
 *   When you rename branches on the Linux side, the Windows repo will not know
     automatically; so if you already had a branch `lk0426-mytopic` open on
     Windows and then `git fetch`, you will still have `lk0426-mytopic` even if
     that was renamed on the Linux side to `lk0428-mytopic`.
 *   Dealing with this is straight-forward; you just
     `git checkout lk0428-mytopic` to switch to the renamed (and likely updated)
     branch. Then `git branch -d lk0426-mytopic` to get rid of the tracking
     branch for the older name.  Then, occasionally, `git remotes prune origin`
     to prune remote tracking branches (you don't normally see these listed
     unless you do `git branch -a`).
 
 Gotchas:
 
 *   You should normally create your branches on Linux only, so that the Windows
     repo gets tracking branches for them.  Any branches you create in the
     Windows repo would be local to that repository, and so will be non-trivial
     to push to Linux.
 *   `git push` from Windows will fail if your Linux repo is checked out to the
     same branch. It is easy to switch back manually, but I also have a script I
     call `safepush` that switches the Linux-side branch for you before pushing;
     let me (joi@chromium.org) know if interested.