Add note on why we're using Docker

Author: InnovativeInventor

README.md

@@ -1,4 +1,10 @@
-# Running districtr-process
+# Running districtr-process (with Docker)
+## Why Docker?
+Docker is a tool to standardize and automate the setup of a virtual enviroment. 
+It allows every developer to test and work with the same enviroment, regardless of operating system, as long as they have Docker installed.
+The districtr-process scripts only work on older versions of Python and require building custom libraries with `make`, which can be finnicky.
+Using Docker allows us to skip the normal convoluted setup process and simply fetch a pre-built virtual enviroment to work in.
+
 ## Installing Docker
 First, install Docker.
 On macOS, you can install Docker like so:
@@ -20,17 +26,17 @@ docker pull innovativeinventor/districtr-process:latest
 Alternatively, you can build the dockerfile in `docker/Dockerfile` yourself.
 
 ## Running
-Finally, to run `districtr-process`, you can either run:
+Finally, to run `districtr-process`, you can run in the root of this git repo:
 ```bash
 bash docker/run.sh [args] 
 ```
 where `[args]` are whatever arguments you pass to districtr_process (e.g. `python -m districtr_process data/minnesota.yml` becomes `bash docker/run.sh data/data/minnesota.yml`).
 
-Alternatively, you can run:
+This is equivalent to running:
 ```
 docker run -it --rm -v $(pwd):/districtr-process innovativeinventor/districtr-process python3 -m districtr_process [args]
 ```
-where `$(pwd)` is the path to your `districtr-process` repo.
+where `$(pwd)` is the path to your `districtr-process` repo. 
 
 If you want to pass a mapbox API token to the Docker container, simply add it to `.env.list` file. For example, the contents of `.env.list` would look like:
 ```