docs: clean up markdown

docs/mac_breakpad_starter_guide.md

 # How To Add Breakpad To Your Mac Client Application
 
 This document is a step-by-step recipe to get your Mac client app to build with
 Breakpad.
 
 ## Preparing a binary build of Breakpad for use in your tree
 
 You can either check in a binary build of the Breakpad framework & tools or
 build it as a dependency of your project. The former is recommended, and
 detailed here, since building dependencies through other projects is
 problematic(matching up configuration names), and the Breakpad code doesn't
 change nearly often enough as your application's will.
 
 ## Building the requisite targets
 
 All directories are relative to the `src` directory of the Breakpad checkout.
 
-*   Build the 'All' target of `client/mac/Breakpad.xcodeproj` in Release mode.
-*   Execute `cp -R client/mac/build/Release/Breakpad.framework <location in your
-    source tree>`
-*   Inside `tools/mac/dump_syms` directory, build dump\_syms.xcodeproj, and copy
-    tools/mac/dump\_syms/build/Release/dump\_syms to a safe location where it
-    can be run during the build process.
+* Build the `All` target of
+  [client/mac/Breakpad.xcodeproj](/src/client/mac/Breakpad.xcodeproj/)
+  in Release mode.
+* Execute `cp -R client/mac/build/Release/Breakpad.framework <location in your
+  source tree>`
+* Inside [tools/mac/dump_syms](/src/tools/mac/dump_syms/) directory, build
+  `dump_syms.xcodeproj`, and copy
+  `tools/mac/dump_syms/build/Release/dump_syms` to a safe location where it
+  can be run during the build process.
 
 ## Adding Breakpad.framework
 
 Inside your application's framework, add the Breakpad.Framework to your
 project's framework settings. When you select it from the file chooser, it will
 let you pick a target to add it to; go ahead and check the one that's relevant
 to your application.
 
 ## Copy Breakpad into your Application Package
 
@@ skipping 27 matching lines @@
 
 *   Turn on Separate Strip,
 *   Set the Strip Style to Non-Global Symbols.
 
 ## Write Code!
 
 You'll need to have an object that acts as the delegate for NSApplication.
 Inside this object's header, you'll need to add
 
 1.  add an ivar for Breakpad and
-2.  a declaration for the applicationShouldTerminate:(NSApplication`*` sender)
+2.  a declaration for the `applicationShouldTerminate:(NSApplication* sender)`
     message.
 
 ```
 #import <Breakpad/Breakpad.h>
 
 @interface BreakpadTest : NSObject {
    .
    .
    .
    BreakpadRef breakpad;
@@ skipping 36 matching lines @@
 - (NSApplicationTerminateReply)applicationShouldTerminate:(NSApplication *)sender {
   BreakpadRelease(breakpad);
   return NSTerminateNow;
 }
 ```
 
 ## Configure Breakpad
 
 Configure Breakpad for your application.
 
-1.  Take a look inside the Breakpad.framework at the Breakpad.h file for the
-    keys, default values, and descriptions to be passed to BreakpadCreate().
+1.  Take a look inside the `Breakpad.framework` at the `Breakpad.h` file for the
+    keys, default values, and descriptions to be passed to `BreakpadCreate()`.
 2.  Add/Edit the Breakpad specific entries in the dictionary passed to
-    BreakpadCreate() -- typically your application's info plist.
+    `BreakpadCreate()` -- typically your application's info plist.
 
 Example from the Notifier Info.plist:
 `<key>BreakpadProduct</key><string>Google_Notifier_Mac</string>
 <key>BreakpadProductDisplay</key><string>${PRODUCT_NAME}</string>
 `
 
 ## Build Your Application
 
 Almost done!
 
@@ skipping 26 matching lines @@
 <key>BreakpadURL</key>
 <string>upload URL</string>
 <key>BreakpadReportInterval</key>
 <string>30</string>
 ```
 
 ## Final Notes
 
 Breakpad checks whether it is being run under a debugger, and if so, normally
 does nothing. But, you can force Breakpad to function under a debugger by
-setting the Unix shell variable BREAKPAD\_IGNORE\_DEBUGGER to a non-zero value.
-You can bracket the source code in the above Write The Code step with #if DEBUG
+setting the Unix shell variable `BREAKPAD_IGNORE_DEBUGGER` to a non-zero value.
+You can bracket the source code in the above Write The Code step with `#if DEBUG`
 to completely eliminate it from Debug builds. See
-//depot/googlemac/GoogleNotifier/main.m for an example. FYI, when your process
+`//depot/googlemac/GoogleNotifier/main.m` for an example. FYI, when your process
 forks(), exception handlers are reset to the default for child processes. So
 they must reinitialize Breakpad, otherwise exceptions will be handled by Apple's
 Crash Reporter.