diff --git a/docs/runbook/en-US/Book_Info.xml b/docs/runbook/en-US/Book_Info.xml
index 5d2014beb9a..8e38bbde8ee 100644
--- a/docs/runbook/en-US/Book_Info.xml
+++ b/docs/runbook/en-US/Book_Info.xml
@@ -27,7 +27,7 @@
     <title>Runbook</title>
     <subtitle>Prescriptive instructions for deploying Apache CloudStack</subtitle>
     <productname>Apache CloudStack</productname>
-    <productnumber>4.0.1</productnumber>
+    <productnumber>4.0.0-incubating</productnumber>
     <edition>0</edition>
     <pubsnumber>0</pubsnumber>
     <abstract>
diff --git a/docs/runbook/en-US/Management.xml b/docs/runbook/en-US/Management.xml
index 1b1880aa436..b52eebf6dd0 100644
--- a/docs/runbook/en-US/Management.xml
+++ b/docs/runbook/en-US/Management.xml
@@ -83,19 +83,12 @@ binlog-format = 'ROW'
       acquire those system images ready for deployment when we bootstrap
       your cloud.
     </para>
-    <para> 
-      The place we are going to download these images to is the secondary 
-      storage share that we setup earlier, so we'll need to mount that share
-      with the <command>mount</command> command run on the management server:
-    </para>
-    <screen><prompt># </prompt><userinput><command>mount</command> -t nfs <replaceable>172.16.10.</replaceable>2:/secondary /mnt/secondary</userinput>
-    </screen>
     <para>
       Now we need to download the system VM template and deploy that to the
       share we just mounted. The management server includes a script to properly
       manipulate the system VMs images. 
     </para>
-    <screen><prompt># </prompt><userinput><command>/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt</command> -m  /mnt/secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -F</userinput>
+    <screen><prompt># </prompt><userinput><command>/usr/lib64/cloud/common/scripts/storage/secondary/cloud-install-sys-tmplt</command> -m  /secondary -u http://download.cloud.com/templates/acton/acton-systemvm-02062012.qcow2.bz2 -h kvm -F</userinput>
     </screen>
     <para>
       That concludes our setup of the management server. We still need to