diff --git a/README.md b/README.md
index 71291b3..ab45d45 100644
--- a/README.md
+++ b/README.md
@@ -8,8 +8,8 @@
 
 Download and launch the docker image:
 ```sh
-docker pull druidio/example-cluster
-docker run --rm -i -p 8888:8888 druidio/example-cluster
+docker pull fokkodriesprong/docker-druid
+docker run --rm -i -p 8888:8888 fokkodriesprong/docker-druid
 ```
 
 Once the cluster has started, you can navigate to [http://localhost:8888](http://localhost:8888). The [Druid router process](../development/router.html), which serves the Druid console, resides at this address.
@@ -19,7 +19,7 @@ Once the cluster has started, you can navigate to [http://localhost:8888](http:/
 To build the docker image yourself
 
 ```sh
-git clone https://github.com/druid-io/docker-druid.git
+git clone https://github.com/Fokko/docker-druid.git
 cd docker-druid
 docker build -t docker-druid .
 docker run --rm -i -p 8888:8888 docker-druid
@@ -61,4 +61,4 @@ The allocated resources are limited by default to 2 cpu's and 2gb of memory. Alt
 ```
 2017-01-20T15:59:58,445 INFO [forking-task-runner-0-[index_transactions_2017-01-20T15:59:50.637Z]] io.druid.indexing.overlord.ForkingTaskRunner - Process exited with status[137] for task: index_transactions_2017-01-20T15:59:50.637Z
 ```
-From the log we observe that the process receives an 137 (=128+9) SIGKILL signal. Because it hit the memory limit, the application is killed instantly. To avoid this you might want to give more resources to the Docker hypervisor under Docker > Preferences.
\ No newline at end of file
+From the log we observe that the process receives an 137 (=128+9) SIGKILL signal. Because it hit the memory limit, the application is killed instantly. To avoid this you might want to give more resources to the Docker hypervisor under Docker > Preferences.