Revert of Add Android fonts to blimp engine

blimp/docs/container.md

 # Running the engine in a Docker container
 
 For local development and testing, you can run the engine in a Docker
 container.
 
 The steps are:
 
 1. Bundle the engine and its dependencies.
 
 1. Build a Docker image.
@@ skipping 25 matching lines @@
 This target is always built as part of the top-level `blimp/blimp` meta-target.
 
 ### Update Engine Dependencies
 
 `blimp/engine/engine-manifest.txt` is a list of the engine's runtime
 dependencies. From time to time, this list may need to be updated. Use
 `blimp/tools/generate-engine-manifest.py` to (re)generate the manifest:
 
 ```bash
 ./blimp/tools/generate-engine-manifest.py \
-    --build-dir out-chromeos/Debug \
+    --build-dir out-linux/Debug \
     --target //blimp/engine:blimp_engine \
     --output blimp/engine/engine-manifest.txt
 ```
 
 Be sure to review the generated manifest and remove any false runtime
 dependencies.
 
 ## Build Docker Image
 
 Using the tarfile you can create a Docker image:
 
 ```bash
-docker build -t blimp_engine - < ./out-chromeos/Debug/blimp_engine_bundle.tar.gz
+docker build -t blimp_engine - < ./out-linux/Debug/blimp_engine_bundle.tar
 ```
 
 ## Running the Engine in a Docker Container
 
 After building the Docker image you can launch the engine inside the Docker
 container.
 
 ### Setting up an Environment
 
 A little prep work is necessary to enable the engine to start as it requires a
 few files that are not provided by the container. You need:
 
 *   A directory (`$CONFIG_DIR`) with permissions of 0755 (ie. world accessable)
 *   `$CONFIG_DIR/stunnel.pem`: A PEM encoded file with a private key and a
     public certificate. Permissions should be set to 644.
 *   `$CONFIG_DIR/client_token`: A file with a non-empty string used as the
     client token (the shared secret between the client and the engine).
-    Permissions should also be set to 644. See [running](running.md) for how
-    to get the default token from the source code.
+    Persmissions should also be set to 644.
 
 This setup step is only required once and can be reused for all the rest of the
 runs of the engine.
 
 ### Running the Engine
 
 Once the `$CONFIG_DIR` is set up, you can launch the engine in the Docker
 container:
 
 ```bash
 docker run -v $CONFIG_DIR:/engine/data -p 443:25466 blimp_engine
 ```
 You can also pass additional flags:
 
 ```bash
 docker run ... blimp_engine --with-my-flags
 ```
 See the [blimp engine `Dockerfile`](../engine/Dockerfile) to find out what flags
 are passed by default.
+