Fixed reference and typo to Clang SA documentation in Clang docs

docs/clang.md

 # Clang
 
 [Clang](http://clang.llvm.org/) is a compiler with many desirable features
 (outlined on their website).
 
 Chrome can be built with Clang. It is now the default compiler on Mac and Linux
 for building Chrome, and it is currently useful for its warning and error
 messages on Android and Windows.
 
 See
@@ skipping 51 matching lines @@
 *   `clang_load`: Absolute path to a dynamic library containing your plugin
 *   `clang_add_plugin`: tells clang to run a specific PluginASTAction
 
 So for example, you could use the plugin in this directory with:
 
 *   `GYP_DEFINES='clang=1 clang_load=/path/to/libFindBadConstructs.so
     clang_add_plugin=find-bad-constructs' gclient runhooks`
 
 ## Using the clang static analyzer
 
-See [clang_static_analyser.md](clang_static_analyser.md).
+See [clang_static_analyzer.md](clang_static_analyzer.md).
 
 ## Windows
 
 **Experimental!**
 
 clang can be used as compiler on Windows. Clang uses Visual Studio's linker and
 SDK, so you still need to have Visual Studio installed.
 
 Things should compile, and all tests should pass. You can check these bots for
 how things are currently looking:
@@ skipping 35 matching lines @@
 
 You can then run `head out/Release/build.ninja` and check that the first to
 lines set `cc` and `cxx` to your clang binary. If things look good, run `ninja
 -C out/Release` to build.
 
 If your clang revision is very different from the one currently used in chromium
 
 *   Check `tools/clang/scripts/update.sh` to find chromium's clang revision
 *   You might have to tweak warning flags. Or you could set `werror=` in the
     line above to disable warnings as errors (but this only works on Linux).