diff --git a/ReadMe.txt b/ReadMe.txt
index 25f74c40ba..e8f85e7bf3 100644
--- a/ReadMe.txt
+++ b/ReadMe.txt
@@ -12,10 +12,10 @@ Initial Setup
 
  - Checkout Records Management code from https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD
    Note:  the RM branch structure reflects the main repository branch structure, so HEAD is the current development branch and BRACHES contains the release branches.
- - Run "gradlew fetchWarFile".  This will use Maven to download the dependant Alfresco War's, currently version 4.0.1
+ - Run "gradlew fetchWarFile".  This will use Maven to download the dependant Alfresco War's, currently version 4.0.1 (from the code directory)
  - Run "gradlew amp" in root directory.  This will unpack the dependancies, build the RM source and finally assemble the RM amps.
    Note:  the first execution of this task may take serveral minutes, because it will unpack the required build dependancies from the alfresco and share WAR.  It will also pull any external dependancies from Maven or 
- - You will not find rm-server\build\dist\alfresco-rm-2.0.amp and rm-share\build\dist\alfresco-rm-share-2.0.amp ahve been built.  
+ - You will now find rm-server\build\dist\alfresco-rm-2.0.amp and rm-share\build\dist\alfresco-rm-share-2.0.amp have been built.  
  
 Using Eclipse
 
@@ -24,22 +24,23 @@ Using Eclipse
     Note: make sure the WAR dependancies have been exploded before opening Eclispe.
   - Import projects found in rm-server and rm-share directories.
   
-Deploying the RM AMPs
-
-  - Set the envoronment variables TOMCAT_HOME and APP_TOMCAT_HOME to the home directory of the repository and share Tomcat instances respectively.
-    NOTE: these can be the same tomcat instance, but it is recommended that two are used.
-  - Configure your repository Tomcat so that your repository.properties settings will be successfully picked up when Alfresco is started.
-  - Run "gradlew deployAmp" in the root directory.  This will use the MMT to apply the RM AMPs to the Alfresco and Share WARs respectively.  The modified WARs will then be copied to the set Tomcat instances, cleaning any exisiting exploded WARs.
-  - Start Tomcat(s). 
- 
 For users of the Alfresco DevEnv
 
  - Create a normal project using "create-project".
  - Check out RM code into the "code" directory (checkout https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/HEAD)
  - The devEnv will automatically set the TOMCAT_HOME and APP_TOMCAT_HOME environment variables to point to the Tomcat instances created by the use-tomcat6 and use-app-tomcat6 scipts.  Magic!
  - Copy the JDBC driver to <TOMCAT_HOME>/lib/
- - You can use the dev-context.xml generated for you to configure the repository. Place it in <TOMCAT_HOME>/shared/classes/alfresco/extension and <PROJECT_NAME>/code/rm-server/config/alfresco/extension.
+ - You can use the dev-context.xml (found in <PROJECT_HOME>/code/root/projects/repository/config/alfresco/extension) generated for you to configure the repository. Place it in <TOMCAT_HOME>/shared/classes/alfresco/extension and <PROJECT_NAME>/code/rm-server/config/alfresco/extension.
+    
+Deploying the RM AMPs
+
+  - Set the envoronment variables TOMCAT_HOME and APP_TOMCAT_HOME to the home directory of the repository and share Tomcat instances respectively.
+    NOTE: these can be the same tomcat instance, but it is recommended that two are used.
+  - Configure your repository Tomcat so that your repository.properties settings will be successfully picked up when Alfresco is started.
+  - Run "gradlew deployAmp" in the root directory.  This will use the MMT to apply the RM AMPs to the Alfresco and Share WARs respectively.  The modified WARs will then be copied to the set Tomcat instances, cleaning any exisiting exploded WARs.
+  - Start Tomcat(s). (with start_tomcat and start_app-tomcat)
  
+
 Summary Of Available Gradle Tasks
 
   Note:  All these tasks can be executed in the root directory or in either of the sub-project directories.