docs: clean up markdown

docs/getting_started_with_breakpad.md

 # Introduction
 
 Breakpad is a library and tool suite that allows you to distribute an
 application to users with compiler-provided debugging information removed,
 record crashes in compact "minidump" files, send them back to your server, and
 produce C and C++ stack traces from these minidumps. Breakpad can also write
 minidumps on request for programs that have not crashed.
 
 Breakpad is currently used by Google Chrome, Firefox, Google Picasa, Camino,
 Google Earth, and other projects.
 
-![http://google-breakpad.googlecode.com/svn/wiki/breakpad.png]
-(http://google-breakpad.googlecode.com/svn/wiki/breakpad.png)
+![Breakpad overview](./breakpad.png)
 
 Breakpad has three main components:
 
 *   The **client** is a library that you include in your application. It can
     write minidump files capturing the current threads' state and the identities
     of the currently loaded executable and shared libraries. You can configure
     the client to write a minidump when a crash occurs, or when explicitly
     requested.
 
 *   The **symbol dumper** is a program that reads the debugging information
@@ skipping 59 matching lines @@
 that writing the minidump from within the crashed process is unsafe - key
 process data structures could be corrupted, or the stack on which the exception
 handler runs could have been overwritten, etc. All 3 platforms support what's
 known as "out-of-process" exception handling.
 
 # Integration overview
 
 ## Breakpad Code Overview
 
 All the client-side code is found by visiting the Google Project at
-http://code.google.com/p/google-breakpad. The following directory structure is
-present in the `src` directory:
+https://chromium.googlesource.com/breakpad/breakpad/. The following directory
+structure is present in the [src](/src/) directory:
 
-*   `processor` Contains minidump-processing code that is used on the server
-    side and isn't of use on the client side
-*   `client` Contains client minidump-generation libraries for all platforms
-*   `tools` Contains source code & projects for building various tools on each
-    platform.
+* [processor](/src/processor/): Contains minidump-processing code that is used on the
+  server side and isn't of use on the client side
+* [client](/src/client/): Contains client minidump-generation libraries for all
+  platforms
+* [tools](/src/tools/): Contains source code & projects for building various tools on
+  each platform.
 
 (Among other directories)
 
-*   <a
-    href='http://code.google.com/p/google-breakpad/wiki/WindowsClientIntegration'>Windows
-    Integration Guide</a>
-*   <a
-    href='http://code.google.com/p/google-breakpad/wiki/MacBreakpadStarterGuide'>Mac
-    Integration Guide</a>
-*   <a href='http://code.google.com/p/google-breakpad/wiki/LinuxStarterGuide'>
-    Linux Integration Guide</a>
+* [Windows Integration Guide](./windows_client_integration.md)
+* [Mac Integration Guide](./mac_breakpad_starter_guide.md)
+* [Linux Integration Guide](./linux_starter_guide.md)
 
 ## Build process specifics(symbol generation)
 
 This applies to all platforms. Inside `src/tools/{platform}/dump_syms` is a tool
 that can read debugging information for each platform (e.g. for OS X/Linux,
 DWARF and STABS, and for Windows, PDB files) and generate a Breakpad symbol
 file. This tool should be run on your binary before it's stripped(in the case of
 OS X/Linux) and the symbol files need to be stored somewhere that the minidump
 processor can find. There is another tool, `symupload`, that can be used to
 upload symbol files if you have written a server that can accept them.