Fix spelling mistakes in //docs.

docs/linux_debugging.md

 # Tips for debugging on Linux
 
 This page is for Chromium-specific debugging tips; learning how to run gdb is
 out of scope.
 
 [TOC]
 
 ## Symbolized stack trace
 
 The sandbox can interfere with the internal symbolizer. Use `--no-sandbox` (but
@@ skipping 357 matching lines @@
         --gtest_filter="MyBrowserTest.MyActivateWindowTest"
 
 ### BROWSER_WRAPPER
 
 You can also get the browser under a debugger by setting the `BROWSER_WRAPPER`
 environment variable.  (You can use this for `browser_tests` too, but see above
 for discussion of a simpler way.)
 
     BROWSER_WRAPPER='xterm -e gdb --args' out/Debug/browser_tests
 
-### Replicating Trybot Slowness
+### Replicating try bot Slowness
 
-Trybots are pretty stressed, and can sometimes expose timing issues you can't
+Try bots are pretty stressed, and can sometimes expose timing issues you can't
 normally reproduce locally.
 
 You can simulate this by shutting down all but one of the CPUs
 (http://www.cyberciti.biz/faq/debian-rhel-centos-redhat-suse-hotplug-cpu/) and
 running a CPU loading tool (e.g., http://www.devin.com/lookbusy/). Now run your
-test. It will run slowly, but any flakiness found by the trybot should replicate
+test. It will run slowly, but any flakiness found by the try bot should replicate
 locally now - and often nearly 100% of the time.
 
 ## Logging
 
 ### Seeing all LOG(foo) messages
 
 Default log level hides `LOG(INFO)`. Run with `--log-level=0` and
 `--enable-logging=stderr` flags.
 
-Newer versions of chromium with VLOG may need --v=1 too. For more VLOG tips, see
+Newer versions of Chromium with VLOG may need --v=1 too. For more VLOG tips, see
 [the chromium-dev thread](http://groups.google.com/a/chromium.org/group/chromium-dev/browse_thread/thread/dcd0cd7752b35de6?pli=1).
 
 ### Seeing IPC debug messages
 
 Run with `CHROME_IPC_LOGGING=1` eg.
 
     CHROME_IPC_LOGGING=1 out/Debug/chrome
 
 or within gdb:
 
@@ skipping 130 matching lines @@
 [Running layout tests on Linux](layout_tests_linux.md) page.
 
 If you need to test something with hardware accelerated compositing
 (e.g., compiz), you can use `Xgl` (`sudo apt-get install xserver-xgl`). E.g.:
 
     Xgl :1 -ac -accel glx:pbuffer -accel xv:pbuffer -screen 1024x768
 
 ## Mozilla Tips
 
 https://developer.mozilla.org/en/Debugging_Mozilla_on_Linux_FAQ