Fix clang tool refactoring docs formatting.

docs/clang_tool_refactoring.md

 # Clang Tool Refactoring
 
 [TOC]
 
 ## Introduction
 
 Clang tools can help with global refactorings of Chromium code. Clang tools can
 take advantage of clang's AST to perform refactorings that would be impossible
 with a traditional find-and-replace regexp:
 
@@ skipping 100 matching lines @@
 
 ## Running
 First, build all chromium targets to avoid failures due to missing dependecies
 that are generated as part of the build:
 
 ```shell
 ninja -C out/Debug
 ```
 
 Then run the actual tool:
-```
+
+```shell
 tools/clang/scripts/run_tool.py <toolname> \
   --generate-compdb
   out/Debug <path 1> <path 2> ...
 ```
 
 `--generate-compdb` can be omitted if the compile DB was already generated and
 the list of build flags and source files has not changed since generation.
 
 `<path 1>`, `<path 2>`, etc are optional arguments to filter the files to run
 the tool across. This is helpful when sharding global refactorings into smaller
 chunks. For example, the following command will run the `empty_string` tool
 across just the files in `//base`:
 
 ```shell
 tools/clang/scripts/run_tool.py empty_string  \
   --generated-compdb \
   out/Debug base
 ```
 
 ## Debugging
 Dumping the AST for a file:
+
 ```shell
 clang++ -cc1 -ast-dump foo.cc
 ```
 
 Using `clang-query` to dynamically test matchers (requires checking out
 and building [clang-tools-extras](https://github.com/llvm-mirror/clang-tools-extra)):
+
 ```shell
 clang-query -p path/to/compdb base/memory/ref_counted.cc
 ```
 
 `printf` debugging:
+
 ```c++
   clang::Decl* decl = result.Nodes.getNodeAs<clang::Decl>("decl");
   decl->dumpColor();
   clang::Stmt* stmt = result.Nodes.getNodeAs<clang::Stmt>("stmt");
   stmt->dumpColor();
 ```
+
 By default, the script hides the output of the tool. The easiest way to change
 that is to `return 1` from the `main()` function of the clang tool.
 
 ## Testing
 Synposis:
+
 ```shell
 test_tool.py <tool name>
 ```
 
 The name of the tool binary and the subdirectory for the tool in
 `//tools/clang` must match. The test runner finds all files that match the
 pattern `//tools/clang/<tool name>/tests/*-original.cc`, runs the tool across
 those files, and compared it to the `*-expected.cc` version. If there is a
 mismatch, the result is saved in `*-actual.cc`.