home.md

 # [wslph/mule](https://hub.docker.com/r/wslph/mule)
 
 - [Introduction](#introduction)
-    - [Changelog](Changelog.md)
+    - [Changelog](https://git.whiteskylabs.com/mulesoft/docker-mule/wikis/changelog)
 - [Contributing](#contributing)
 - [Issues](#issues)
 - [Announcements](https://git.whiteskylabs.com/mulesoft/docker-mule/issues)
@@ -41,7 +41,7 @@ wget -qO- https://get.docker.com/ | sh
 
 Fedora and RHEL/CentOS users should try disabling selinux with `setenforce 0` and check if resolves the issue. If it does than there is not much that I can help you with. You can either stick with selinux disabled (not recommended by redhat) or switch to using ubuntu.
 
-If you want to try this on your local development machine, you can try [Docker for Mac](https://docs.docker.com/docker-for-mac/), and for [Docker for Windows](https://docs.docker.com/docker-for-windows/).
+If you want to try this on your local development machine, you can try [Docker for Mac](https://docs.docker.com/docker-for-mac/), and [Docker for Windows](https://docs.docker.com/docker-for-windows/).
 
 If you find any issues with this release, please file an issue request on the [issues](https://git.whiteskylabs.com/mulesoft/docker-mule/issues) page.
 
@@ -62,12 +62,25 @@ Your docker host needs to have at least 2GB (or more) of available RAM to run Mu
 
 Automated builds of the image are available on [Dockerhub](https://hub.docker.com/r/wslph/mule) and is the recommended method of installation.
 
+`------------------------------------------------------------------------------`
+
+__To pull the latest build for 3.9.0-ee__
 
 ```bash
 docker pull wslph/mule:3.9.0-ee
 ```
 
-Example 1 : Launching  Mule ESB Server runtime container for Community Edition
+`------------------------------------------------------------------------------`
+
+__To pull the container tagged 3.9.0-ee built on 2018-02-02 (YYYY-MM-DD).__
+
+```bash
+docker pull wslph/mule:3.9.0-ee-2018-02-02
+```
+
+`------------------------------------------------------------------------------`
+
+__Example 1 : Launching  Mule ESB Server runtime container for Community Edition__
 
 ```bash
 docker run --restart=always --name mule-ce -d \
@@ -76,7 +89,9 @@ docker run --restart=always --name mule-ce -d \
     wslph/mule:3.9.0-ce && docker logs -f mule-ce
 ```
 
-Example 2 : Launching  Mule ESB Server runtime container for Enterprise Edition
+`------------------------------------------------------------------------------`
+
+__Example 2 : Launching  Mule ESB Server runtime container for Enterprise Edition__
 
 ```bash
 docker run --restart=always --name mule-ee -d \
@@ -85,7 +100,9 @@ docker run --restart=always --name mule-ee -d \
     wslph/mule:3.9.0-ee && docker logs -f mule-ee
 ```
 
-Example 3 : Attaching container to host network
+`------------------------------------------------------------------------------`
+
+__Example 3 : Attaching container to host network__
 
 ```bash
 docker run --restart=always --name mule-ee -d \
@@ -94,6 +111,8 @@ docker run --restart=always --name mule-ee -d \
     wslph/mule:3.9.0-ee && docker logs -f mule-ee
 ```
 
+`------------------------------------------------------------------------------`
+
 *Please refer to [Available Configuration Parameters](#available-configuration-parameters) to understand `MULE_ENV` and other configuration options*
 
 __NOTE__: Please allow a couple of minutes for the Mule ESB Server runtime to start.