[Docs]: Update to match style guide.

docs/android_test_instructions.md

 # Android Test Instructions
 
 Device Setup Tests are runnable on physical devices or emulators. See the
 instructions below for setting up either a physical device or an emulator.
 
 [TOC]
 
 ## Physical Device Setup **ADB Debugging**
 
 In order to allow the ADB to connect to the device, you must enable USB
 debugging:
-  * Before Android 4.1 (Jelly Bean):
-      * Go to "System Settings"
-      * Go to "Developer options"
-      * Check "USB debugging".
-      * Un-check "Verify apps over USB".
-  * On Jelly Bean, developer options are hidden by default. To unhide them:
-      * Go to "About phone"
-      * Tap 10 times on "Build number"
-      * The "Developer options" menu will now be available.
-      * Check "USB debugging".
-      * Un-check "Verify apps over USB".
+
+*   Before Android 4.1 (Jelly Bean):
+    *   Go to "System Settings"
+    *   Go to "Developer options"
+    *   Check "USB debugging".
+    *   Un-check "Verify apps over USB".
+*   On Jelly Bean, developer options are hidden by default. To unhide them:
+    *   Go to "About phone"
+    *   Tap 10 times on "Build number"
+    *   The "Developer options" menu will now be available.
+    *   Check "USB debugging".
+    *   Un-check "Verify apps over USB".
 
 ### Screen
 
 You MUST ensure that the screen stays on while testing: `adb shell svc power
 stayon usb` Or do this manually on the device: Settings -> Developer options
 -> Stay Awake.
 
 If this option is greyed out, stay awake is probably disabled by policy. In that
 case, get another device or log in with a normal, unmanaged account (because the
 tests will break in exciting ways if stay awake is off).
 
 ### Enable Asserts!
 
-`adb shell setprop debug.assert 1`
+    adb shell setprop debug.assert 1
 
 ### Disable Verify Apps
 
 You may see a dialog like
 [this one](http://www.samsungmobileusa.com/simulators/ATT_GalaxyMega/mobile/screens/06-02_12.jpg),
 which states, _Google may regularly check installed apps for potentially harmful
 behavior._ This can interfere with the test runner. To disable this dialog, run:
 `adb shell settings put global package_verifier_enable 0`
 
 ## Emulator Setup
@@ skipping 40 matching lines @@
 Alternatively, you can create an run your own emulator using the tools provided
 by the Android SDK. When doing so, be sure to enable GPU emulation in hardware
 settings, since Chromium requires it to render.
 
 ## Building Tests
 
 It may not be immediately obvious where your test code gets compiled to, so here
 are some general rules:
 
 *  If your test code lives under /content, it will probably be built as part of
-   the content\_shell\_test\_apk * If your test code lives under /chrome (or
-   higher), it will probably be built as part of the chrome\_public\_test\_apk *
-   (Please fill in more details here if you know them).
+   the content_shell_test_apk
+*  If your test code lives under /chrome (or higher), it will probably be built
+   as part of the chrome_public_test_apk
+*  (Please fill in more details here if you know them).
 
-   NB: We used to call the chrome\_public\_test\_apk the
-   chromium\_shell\_test\_apk. There may still be references to this kicking
-   around, but wherever you see chromium\_shell\_test you should replace with
-   chrome\_public\_test.
+   NB: We used to call the chrome_public_test_apk the
+   chromium_shell_test_apk. There may still be references to this kicking
+   around, but wherever you see chromium_shell_test you should replace with
+   chrome_public_test.
 
 Once you know what to build, just do it like you normally would build anything
 else, e.g.: `ninja -C out/Release chrome_public_test_apk`
 
 ## Running Tests
 
 All functional tests are run using `build/android/test_runner.py`.
 Tests are sharded across all attached devices. In order to run tests, call:
 `build/android/test_runner.py <test_type> [options]`
 For a list of valid test types, see `test_runner.py --help`. For
@@ skipping 138 matching lines @@
 See
 https://sites.google.com/a/chromium.org/dev/developers/testing/webkit-layout-tests
 
 ## Running GPU tests
 
 (e.g. the "Android Debug (Nexus 7)" bot on the chromium.gpu waterfall)
 
 See http://www.chromium.org/developers/testing/gpu-testing for details. Use
 --browser=android-content-shell. Examine the stdio from the test invocation on
 the bots to see arguments to pass to src/content/test/gpu/run\_gpu\_test.py.