diff --git a/Docker-image.md b/Docker-image.md
deleted file mode 100644
index 7acd60c..0000000
--- a/Docker-image.md
+++ /dev/null
@@ -1,66 +0,0 @@
-Docker is the easiest way to run Tracks, as the various library requirements have already been taken care of for you.
-
-## Official Docker image
-
-You can run Tracks by installing Docker and launching a MySQL instance for example using
-
-$ docker run --name mariadb -t mariadb
-
-Create a database and a user for Tracks. Then build the Tracks image by running the following command in the Tracks repository root:
-
-$ docker build -t="tracks" .
-
-And then run an instance of the image using the following command (but replacing the database connection information appropriately)
-
-$ docker run -p 3000:3000 --name tracks --link mariadb:db -t tracks
-
-If all went to plan, you should now be able to reach Tracks in http://localhost:3000 .
-
-### Environmental variables
-
-You can override database connection details by defining the environment variables in the run command, for example ”-e DATABASE_USERNAME=tracks_dev”.
-
-|Name              |Default    |For PostgreSQL |
-|------------------|-----------|---------------|
-|DATABASE_NAME     |tracks     |               |
-|DATABASE_HOST     |db         |               |
-|DATABASE_PORT     |3306       |5432           |
-|DATABASE_USERNAME |tracks     |               |
-|DATABASE_PASSWORD |password   |               |
-|DATABASE_TYPE     |mysql2     |postgresql     |
-|DATABASE_ENCODING |utf8       |unicode        |
-|RAILS_ENV         |production |
-
-### Override files
-
-You can override files in the Docker image by using the --volume argument.
-
-|File               |Argument                                                 |Replace for production?|
-|-------------------|---------------------------------------------------------|-----------------------|
-|config/site.yml    |--volume /app/config/site.yml:/home/user/site.yml        |Yes                    |
-
-## Staannoe's Dockerimage
-
-### Prerequisites
-Docker installed on the host machine
-
-Tracks is a web-based application to help you implement David Allens Getting Things Done™ methodology. It was built using Ruby on Rails.
-
-This is the easy way getting up and running with Tracks, which is one of the greatest software implementations of the GTD™ methodology.
-
-This builds main parts are:
-
-* Tracks 2.3.0 (stable)
-* Ubuntu 14.04 
-* Tracks 2.2.3
-* Apache 2 (Passenger)
-* Sqlite3
-* Dockerize (Utility to simplify running applications in docker containers)
-
-It utilizes mostly native Ubuntu 14.04 packages, thus rebuilding it will provide the latest updates.
-
-For production use it is highly recommended to update the `site.yml.template` within the build repo, rename it to `site.yml` then rebuild the container.
-
-Example on how to run the Tracks container:
-
-     docker run -d --name=tracks -p 80:80 staannoe/tracks
\ No newline at end of file
diff --git a/Staannoe's-Docker-image.md b/Staannoe's-Docker-image.md
new file mode 100644
index 0000000..51cc587
--- /dev/null
+++ b/Staannoe's-Docker-image.md
@@ -0,0 +1,23 @@
+## Prerequisites
+Docker installed on the host machine
+
+Tracks is a web-based application to help you implement David Allens Getting Things Done™ methodology. It was built using Ruby on Rails.
+
+This is the easy way getting up and running with Tracks, which is one of the greatest software implementations of the GTD™ methodology.
+
+This builds main parts are:
+
+* Tracks 2.3.0 (stable)
+* Ubuntu 14.04 
+* Tracks 2.2.3
+* Apache 2 (Passenger)
+* Sqlite3
+* Dockerize (Utility to simplify running applications in docker containers)
+
+It utilizes mostly native Ubuntu 14.04 packages, thus rebuilding it will provide the latest updates.
+
+For production use it is highly recommended to update the `site.yml.template` within the build repo, rename it to `site.yml` then rebuild the container.
+
+Example on how to run the Tracks container:
+
+     docker run -d --name=tracks -p 80:80 staannoe/tracks
\ No newline at end of file