Fix spelling mistakes in //docs.

docs/linux_profiling.md

 # Linux Profiling
 
-How to profile chromium on Linux.
+How to profile Chromium on Linux.
 
 See
 [Profiling Chromium and WebKit](https://sites.google.com/a/chromium.org/dev/developers/profiling-chromium-and-webkit)
 for alternative discussion.
 
 ## CPU Profiling
 
 gprof: reported not to work (taking an hour to load on our large binary).
 
 oprofile: Dean uses it, says it's good. (As of 9/16/9 oprofile only supports
@@ skipping 151 matching lines @@
 
 [Massif](http://valgrind.org/docs/manual/mc-manual.html) is a
 [Valgrind](http://www.chromium.org/developers/how-tos/using-valgrind)-based heap
 profiler. It is much slower than the heap profiler from google-perftools, but it
 may have some advantages. (In particular, it handles the multi-process
 executables well).
 
 First, you will need to build massif from valgrind-variant project yourself,
 it's [easy](http://code.google.com/p/valgrind-variant/wiki/HowTo).
 
-Then, make sure your chromium is built using the
+Then, make sure your Chromium is built using the
 [valgrind instructions](http://www.chromium.org/developers/how-tos/using-valgrind).
 Now, you can run massif like this:
 
 ```
 path-to-valgrind-variant/valgrind/inst/bin/valgrind \
    --fullpath-after=/chromium/src/ \
    --trace-children-skip=*npviewer*,/bin/uname,/bin/sh,/usr/bin/which,/bin/ps,/bin/grep,/usr/bin/linux32 \
    --trace-children=yes \
    --tool=massif \
    out/Release/chrome --noerrdialogs --disable-hang-monitor --other-chrome-flags
@@ skipping 16 matching lines @@
     Xephyr :1 -ac -screen 800x600 &
     DISPLAY=:1 out/Debug/chrome
 
 When ready to start debugging issue the following command, which will tell
 Xephyr to start drawing red rectangles:
 
     kill -USR1 `pidof Xephyr`
 
 For further information, please refer to
 http://cgit.freedesktop.org/xorg/xserver/tree/hw/kdrive/ephyr/README.