Update docs remove Container Linux references

config_app/docs/initial_setup.md

@@ -8,17 +8,15 @@ Quay Enterprise requires three components to be running to begin the setup proce
 
 **NOTE**: Please have the host and port of the database and the Redis instance ready.
 
-## Downloading your license
-
-A valid license is required to run Quay Enterprise. Your license can be found on [Tectonic Accounts](https://account.tectonic.com). Please download or copy this license in **Raw Format** as a file named `license`.
-
 ## Preparing the database
 
-A MySQL RDBMS or Postgres installation with an empty database is required, and a login with full access to said database. The schema will be created the first time the registry image is run. The database install can either be pre-existing or run on Container Linux via a [Docker container](mysql-container.md).
+A MySQL RDBMS or Postgres installation with an empty database is required, and a login with full access to said database. The schema will be created during the creation of the configuration. The database install can either be pre-existing or run via a [Docker container](mysql-container.md).
+
+**Note**: Running your database on as a Docker container is not recommended for production workloads.
 
 ## Setting up redis
 
-Redis stores data which must be accessed quickly but doesn’t necessarily require durability guarantees. If you have an existing Redis instance, make sure to accept incoming connections on port 6379 (or change the port in the setup process) and then feel free to skip this step.
+Redis stores data which must be accessed quickly but doesn’t require durability guarantees. If you have an existing Redis instance, make sure to accept incoming connections on port 6379 (or change the port in the setup process) and then feel free to skip this step.
 
 To run redis, simply pull and run the Quay.io Redis image:
 
@@ -46,7 +44,7 @@ The `config.json` file will look like this:
 }
 ```
 
-`config.json` contains your credentials for the `quay.io/coreos/quay` repository. Save this file to your Container Linux machine in `/home/core/.docker/config.json` and `/root/.docker/config.json`. You should now be able to execute `docker pull quay.io/coreos/quay:v2.9.2` to download the container.
+`config.json` contains your credentials for the `quay.io/coreos/quay` repository. Save this file to your machine in `/home/$USER/.docker/config.json` and `/root/.docker/config.json`. You should now be able to execute `docker pull quay.io/coreos/quay:v2.9.2` to download the container.
 
 ## Booting up the configuration tool
 
@@ -91,7 +89,7 @@ mkdir storage
 
 
 
-## Setting up and running the registry
+## Running the registry
 
 If you are running with local storage, you'll have to add it as a volume to the docker command, replacing `/local/path/to/the/config/directory` and `/local/path/to/the/storage/directory` with the absolute paths to the directories created in the previous step:
 
@@ -136,5 +134,14 @@ sudo docker run -p 443:443 -d quay.io/coreos/quay:v3.0.0 config
 
 Click on "Modify an existing configuration", and upload the tarball provided when initially creating the configuration. 
 
-You will be taken to the setup page, with your previous configuration values pre-populated. After you have made your changes,
+You will be taken to the setup page, with your previous configuration values pre-populated. After you have made your changes, save the configuration and download the tarball.
+
+<img src="img/load-tarball-config.png" class="img-center" alt="Quay Enterprise Load Configuration"/>
+
+Extract the tarball into the config directory where your Quay Enterprise will run:
+```
+mkdir config && tar xzf quay-config.tar.gz -C config
+```
+
+Now run Quay Enterprise as stated in the **Running the registry** step, and your new instance will reflect the changes made in the new configuration.