diff --git a/Dockerfile b/Dockerfile
index abd53f9..9487cd2 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -5,7 +5,7 @@ FROM jboss/base-jdk:7
 MAINTAINER JBoss Windup Team <jboss-migration@redhat.com>
 
 # Set the WINDUP_VERSION env variable
-ENV WINDUP_VERSION 2.3.0.Final
+ENV WINDUP_VERSION 2.4.0.Final
 
 # Add the JBoss Windup distribution to /opt, and make windup the owner of the extracted tar content
 # Make sure the distribution is available from a well-known place
diff --git a/README.md b/README.md
index fbc0fcf..d55aa9d 100644
--- a/README.md
+++ b/README.md
@@ -10,7 +10,9 @@ This is a Dockerfile with [JBoss Windup](http://windup.jboss.org/).
     docker run -it -v /path/to/your/app:/opt/jboss/application:rw jboss/windup
 ```
 
-- This will mount the host directory, `/path/to/your/app`, into the container at `/opt/jboss/application`.
+- This will mount the host directory, `/path/to/your/app`, into the container at `/opt/jboss/application`, and show the help usage print out. 
+
+- If you need to provide more Windup CLI arguments add them after Docker image name.
 
 - To run it locally, clone [this repository](https://github.com/jboss-dockerfiles/windup) and move to the `windup` directory.
 
@@ -23,13 +25,13 @@ This is a Dockerfile with [JBoss Windup](http://windup.jboss.org/).
 	docker run -it -v /path/to/your/app:/opt/jboss/application:rw --name windup_ins windup_img
 ```
 
-- Once Windup starts and the command shell is prompted, the command `windup-migrate-app` is available, also your application will be available at `/opt/jboss/application`. This path will have `read/write` permission due to the `rw` parameter used, so you can create a folder called `output-report` inside (e.g `/opt/jboss/application/output-report`) to be the `--output` parameter that Windup uses to save the generated report.
+- Once Windup starts and the command show as processing, your application will be available at `/opt/jboss/application`. This path will have `read/write` permission due to the `rw` parameter used, so Windup can create a folder called `<application_name>.report` inside (e.g `/opt/jboss`) to be the `--output` parameter that Windup uses to save the generated report.
 
-- After report have been generated, you can access it also from the host by checking the path you mounted locally. Note you will see that the `output-report` folder was created locally as well, and the report is inside it.   
+- After report have been generated, you can access it also from the host by checking the path you mounted locally. Note you will see that the `<application_name>.report` folder was created locally as well, and the report is inside it.   
 
 ## Image internals
 
-This image extends the [`jboss/base-jdk:7`](https://github.com/JBoss-Dockerfiles/base-jdk/tree/jdk7) image which adds the OpenJDK distribution on top of the [`jboss/base`](https://github.com/JBoss-Dockerfiles/base) image. Please refer to the README.md for selected images for more info.
+This image extends the [`jboss/base-jdk:7`](https://github.com/JBoss-Dockerfiles/base-jdk/tree/jdk7) image which adds the OpenJDK distribution on top of the [`jboss/base`](https://github.com/JBoss-Dockerfiles/base) image. Be aware that the `jboss/base` assume your user and group id on host system is 1000. If your user is different you can have problems with *Permission Denied Error Messages*. Please refer to the README.md for selected images for more info.
 
 JBoss Windup is installed in the `/opt/jboss/windup` directory.
 
@@ -39,4 +41,4 @@ The source is [available on GitHub](https://github.com/JBoss-Dockerfiles/windup)
 
 ## Issues
 
-Please report any issues on [JIRA](https://issues.jboss.org/browse/WINDUP).
\ No newline at end of file
+Please report any issues on [JIRA](https://issues.jboss.org/browse/WINDUP).