Make blimp work on K

blimp/docs/running.md

 # Running Blimp
 [TOC]
 
 See [build](build.md) for instructions on how to build Blimp.
 
 ## Android Client
 
 ### Installing the client
 
 Install the Blimp APK with the following:
@@ skipping 145 matching lines @@
 ### On a workstation
 The following flags are required to start an Engine instance:
 
 * `--blimp-client-token-path=$PATH`: Path to a file containing a nonempty
   token string. If this is not present, the engine will fail to boot.
 * `--use-remote-compositing`: Ensures that the renderer uses the remote
   compositor.
 * `--disable-cached-picture-raster`: Ensures that rasterized content is not
   destroyed before serialization.
 * `--android-fonts-path=$PATH`: Path to where the fonts are located.
-  Typically this would be `out-linux/Debug/gen/third_party/blimp_fonts`.
+  If the Android client is Kitkat system, this would be
+  `out-linux/Debug/gen/third_party/blimp_fonts/font_bundle/kitkat/`.
+  If the Android client is Marshmallow system, this would be
+  `out-linux/Debug/gen/third_party/blimp_fonts/font_bundle/marshmallow/`.
 * `--disable-remote-fonts`: Disables downloading of custom web fonts in the
   renderer.
 
 #### Typical invocation
 
 One can start the engine using these flags:
 
 ```bash
 out-linux/Debug/blimp_engine_app \
-  --android-fonts-path=out-linux/Debug/gen/third_party/blimp_fonts \
+  --android-fonts-path=out-linux/Debug/gen/third_party/blimp_fonts/font_bundle/marshmallow/ \
   --blimp-client-token-path=/tmp/blimpengine-token \
   --enable-logging=stderr \
   --vmodule="blimp*=1"
 ```
 
 ## Running client engine integration with script
 
 When building the target `blimp` on a Linux host, a script is created which
 automates running the Blimp client and starting the engine. Setting up the
 environment like this is much quicker than executing each of the steps
@@ skipping 50 matching lines @@
     killing engine if keyboard interrupts or client gets killed.
 
     ```bash
     out-linux/Debug/bin/client_engine_integration run
     ```
 
 2.  Same as step 2 in Option A.
 
 3.  Engine should be auto-killed by keyboard stopping the `{run}` script or the client
     gets wiped out. `{stop}` works as well.