Index: trunk/doc/manual/en_US/dita/topics/additions-linux-graphics-mouse.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/additions-linux-graphics-mouse.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/additions-linux-graphics-mouse.dita	(revision 105388)
@@ -5,96 +5,50 @@
   
   <body>
-    <p>
-          In Linux and Oracle Solaris guests, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphics
-          and mouse integration goes through the X Window System.
-          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can use the X.Org variant of the system, or
-          XFree86 version 4.3 which is identical to the first X.Org
-          release. During the installation process, the X.Org display
-          server will be set up to use the graphics and mouse drivers
-          which come with the Guest Additions.
-        </p>
-    <p>
-          After installing the Guest Additions into a fresh installation
-          of a supported Linux distribution or Oracle Solaris system,
-          many unsupported systems will work correctly too, the guest's
-          graphics mode will change to fit the size of the
-          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> window on the host when it is resized. You can
-          also ask the guest system to switch to a particular resolution
-          by sending a video mode hint using the
-          <userinput>VBoxManage</userinput> tool.
-        </p>
-    <p>
-          Multiple guest monitors are supported in guests using the
-          X.Org server version 1.3, which is part of release 7.3 of the
-          X Window System version 11, or a later version. The layout of
-          the guest screens can be adjusted as needed using the tools
-          which come with the guest operating system.
-        </p>
-    <p> If you want to understand more about the details of how the X.Org drivers are set up, in
-      particular if you want to use them in a setting which our installer does not handle correctly,
-      see <xref href="guestxorgsetup.dita">Guest Graphics and Mouse Driver Setup in Depth</xref>. </p>
-    <p>
-          Starting from <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7, Linux guest screen resize
-          functionality for guests running VMSVGA graphics configuration
-          has been changed. Since then, this functionality consists of a
-          standalone daemon called VBoxDRMClient and its Desktop
-          Environment helper counterpart.
-        </p>
-    <p>
-          VBoxDRMClient runs as a root process and is a bridge between
-          the host and the guest's vmwgfx driver. This means that
-          VBoxDRMClient listens to screen resize hints from the host and
-          forwards them to the vmwgfx driver. This enables guest screen
-          resize functionality to be available before the user has
-          performed a graphical login.
-        </p>
-    <p>
-          In order to perform Desktop Environment specific actions, such
-          as setting the primary screen in a multimonitor setup, a
-          Desktop Environment helper is used. Once the user has
-          performed a graphical login operation, the helper daemon
-          starts with user session scope and attempts to connect to
-          VBoxDRMClient using an IPC connection. When VBoxDRMClient has
-          received a corresponding command from the host, it is
-          forwarded to the helper daemon over IPC and the action is then
-          performed.
-        </p>
-    <p>
-          By default, VBoxDRMClient allows any process to connect to its
-          IPC socket. This can be restricted by using the following
-          steps:
-        </p>
+    <p>In Linux and Oracle Solaris guests, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphics and mouse
+      integration goes through the X Window System. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can use the
+      X.Org variant of the system, or XFree86 version 4.3 which is identical to the first X.Org release. During the
+      installation process, the X.Org display server will be set up to use the graphics and mouse drivers which come
+      with the Guest Additions. </p>
+    <p>After installing the Guest Additions into a fresh installation of a supported Linux distribution or Oracle
+      Solaris system, many unsupported systems will work correctly too, the guest's graphics mode will change to fit the
+      size of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> window on the host when it is resized. You can
+      also ask the guest system to switch to a particular resolution by sending a video mode hint using the
+        <userinput>VBoxManage</userinput> tool. </p>
+    <p>Multiple guest monitors are supported in guests using the X.Org server version 1.3, which is part of release 7.3
+      of the X Window System version 11, or a later version. The layout of the guest screens can be adjusted as needed
+      using the tools which come with the guest operating system. </p>
+    <p>If you want to understand more about the details of how the X.Org drivers are set up, in particular if you want
+      to use them in a setting which our installer does not handle correctly, see <xref href="guestxorgsetup.dita">Guest
+        Graphics and Mouse Driver Setup in Depth</xref>. </p>
+    <p>Starting from <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 7, Linux guest screen resize functionality
+      for guests running VMSVGA graphics configuration has been changed. Since then, this functionality consists of a
+      standalone daemon called VBoxDRMClient and its Desktop Environment helper counterpart. </p>
+    <p>VBoxDRMClient runs as a root process and is a bridge between the host and the guest's vmwgfx driver. This means
+      that VBoxDRMClient listens to screen resize hints from the host and forwards them to the vmwgfx driver. This
+      enables guest screen resize functionality to be available before the user has performed a graphical login. </p>
+    <p>In order to perform Desktop Environment specific actions, such as setting the primary screen in a multimonitor
+      setup, a Desktop Environment helper is used. Once the user has performed a graphical login operation, the helper
+      daemon starts with user session scope and attempts to connect to VBoxDRMClient using an IPC connection. When
+      VBoxDRMClient has received a corresponding command from the host, it is forwarded to the helper daemon over IPC
+      and the action is then performed. </p>
+    <p>By default, VBoxDRMClient allows any process to connect to its IPC socket. This can be restricted by using the
+      following steps: </p>
     <ol>
       <li>
-        <p>
-              The Guest Additions Linux installer creates a
-              <codeph>vboxdrmipc</codeph> user group. A corresponding
-              user needs to be added to this group.
-            </p>
+        <p>The Guest Additions Linux installer creates a <codeph>vboxdrmipc</codeph> user group. A corresponding user
+          needs to be added to this group. </p>
       </li>
       <li>
-        <p>
-              You must set the <codeph>DRMIpcRestricted</codeph> guest
-              property, as follows:
-            </p>
+        <p>You must set the <codeph>DRMIpcRestricted</codeph> guest property, as follows: </p>
         <pre xml:space="preserve">VBoxManage guestproperty set "VM name" /VirtualBox/GuestAdd/DRMIpcRestricted 1 \
 --flags RDONLYGUEST</pre>
-        <p>
-              It is important to set only the RDONLYGUEST flag for the
-              property, so that it cannot be changed from inside the
-              guest.
-            </p>
+        <p>It is important to set only the RDONLYGUEST flag for the property, so that it cannot be changed from inside
+          the guest. </p>
       </li>
     </ol>
     <note>
-      <p>
-            Both steps are required. If one of them is missing, all
-            processes will have access to the IPC socket.
-          </p>
+      <p>Both steps are required. If one of them is missing, all processes will have access to the IPC socket. </p>
     </note>
-    <p>
-          Restricted mode can be disabled by unsetting the guest
-          property, as follows:
-        </p>
+    <p>Restricted mode can be disabled by unsetting the guest property, as follows: </p>
     <pre xml:space="preserve">VBoxManage guestproperty unset "VM name" /VirtualBox/GuestAdd/DRMIpcRestricted</pre>
   </body>
Index: trunk/doc/manual/en_US/dita/topics/additions-linux-uninstall.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/additions-linux-uninstall.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/additions-linux-uninstall.dita	(revision 105388)
@@ -5,27 +5,17 @@
   
   <body>
-    <p> If you have a version of the Guest Additions installed on your virtual machine and want to
-      remove it without installing new ones, you can do so by inserting the Guest Additions CD image
-      into the virtual CD-ROM drive as described above. Then run the installer for the current Guest
-      Additions with the <codeph>uninstall</codeph> parameter from the path that the CD image is
-      mounted on in the guest, as follows: </p>
+    <p>If you have a version of the Guest Additions installed on your virtual machine and want to remove it without
+      installing new ones, you can do so by inserting the Guest Additions CD image into the virtual CD-ROM drive as
+      described above. Then run the installer for the current Guest Additions with the <codeph>uninstall</codeph>
+      parameter from the path that the CD image is mounted on in the guest, as follows: </p>
     <pre xml:space="preserve">sh ./VBoxLinuxAdditions.run uninstall</pre>
-    <p>
-          While this will normally work without issues, you may need to
-          do some manual cleanup of the guest in some cases, especially
-          of the XFree86Config or xorg.conf file. In particular, if the
-          Additions version installed or the guest operating system were
-          very old, or if you made your own changes to the Guest
-          Additions setup after you installed them.
-        </p>
-    <p>
-          You can uninstall the Additions as follows:
-        </p>
+    <p>While this will normally work without issues, you may need to do some manual cleanup of the guest in some cases,
+      especially of the XFree86Config or xorg.conf file. In particular, if the Additions version installed or the guest
+      operating system were very old, or if you made your own changes to the Guest Additions setup after you installed
+      them. </p>
+    <p>You can uninstall the Additions as follows: </p>
     <pre xml:space="preserve">/opt/VBoxGuestAdditions-<varname>version</varname>/uninstall.sh</pre>
-    <p>
-          Replace
-          <filepath>/opt/VBoxGuestAdditions-<varname>version</varname></filepath>
-          with the correct Guest Additions installation directory.
-        </p>
+    <p>Replace <filepath>/opt/VBoxGuestAdditions-<varname>version</varname></filepath> with the correct Guest Additions
+      installation directory. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/additions-linux-updating.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/additions-linux-updating.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/additions-linux-updating.dita	(revision 105388)
@@ -5,10 +5,7 @@
   
   <body>
-    <p>
-          The Guest Additions can simply be updated by going through the
-          installation procedure again with an updated CD-ROM image.
-          This will replace the drivers with updated versions. You
-          should reboot after updating the Guest Additions.
-        </p>
+    <p>The Guest Additions can simply be updated by going through the installation procedure again with an updated
+      CD-ROM image. This will replace the drivers with updated versions. You should reboot after updating the Guest
+      Additions. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/additions-windows-install-unattended-certs.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/additions-windows-install-unattended-certs.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/additions-windows-install-unattended-certs.dita	(revision 105388)
@@ -5,31 +5,17 @@
   
   <body>
-    <p>
-            To avoid popups when performing an unattended installation
-            of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions, the code signing
-            certificates used to sign the drivers needs to be installed
-            in the correct certificate stores on the guest operating
-            system. Failure to do this will cause a typical Windows
-            installation to display multiple dialogs asking whether you
-            want to install a particular driver.
-          </p>
+    <p>To avoid popups when performing an unattended installation of the <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions, the code signing certificates used to sign
+      the drivers needs to be installed in the correct certificate stores on the guest operating system. Failure to do
+      this will cause a typical Windows installation to display multiple dialogs asking whether you want to install a
+      particular driver. </p>
     <note>
-      <p>
-              On some legacy Windows versions, such as Windows 2000 and
-              Windows XP, the user intervention popups mentioned above
-              are always displayed, even after importing the Oracle
-              certificates.
-            </p>
+      <p>On some legacy Windows versions, such as Windows 2000 and Windows XP, the user intervention popups mentioned
+        above are always displayed, even after importing the Oracle certificates. </p>
     </note>
-    <p>
-            Installing the code signing certificates on a Windows guest
-            can be done automatically. Use the
-            <filepath>VBoxCertUtil.exe</filepath> utility from the
-            <filepath>cert</filepath> folder on the Guest Additions
-            installation CD.
-          </p>
-    <p>
-            Use the following steps:
-          </p>
+    <p>Installing the code signing certificates on a Windows guest can be done automatically. Use the
+        <filepath>VBoxCertUtil.exe</filepath> utility from the <filepath>cert</filepath> folder on the Guest Additions
+      installation CD. </p>
+    <p>Use the following steps: </p>
     <ol>
       <li>
@@ -62,37 +48,19 @@
       </li>
     </ol>
-    <p>
-            To allow for completely unattended guest installations, you
-            can specify a command line parameter to the install
-            launcher:
-          </p>
+    <p>To allow for completely unattended guest installations, you can specify a command line parameter to the install
+      launcher: </p>
     <pre xml:space="preserve">VBoxWindowsAdditions.exe /S</pre>
-    <p>
-            This automatically installs the right files and drivers for
-            the corresponding platform, either 32-bit or 64-bit.
-          </p>
+    <p>This automatically installs the right files and drivers for the corresponding platform, either 32-bit or 64-bit. </p>
     <note>
-      <p>
-              By default on an unattended installation on a Vista or
-              Windows 7 guest, there will be the XPDM graphics driver
-              installed. This graphics driver does not support Windows
-              Aero / Direct3D on the guest. Instead, the WDDM graphics
-              driver needs to be installed. To select this driver by
-              default, add the command line parameter
-              <codeph>/with_wddm</codeph> when invoking the Windows
-              Guest Additions installer. This is only required for Vista
-              and Windows 7.
-            </p>
+      <p>By default on an unattended installation on a Vista or Windows 7 guest, there will be the XPDM graphics driver
+        installed. This graphics driver does not support Windows Aero / Direct3D on the guest. Instead, the WDDM
+        graphics driver needs to be installed. To select this driver by default, add the command line parameter
+          <codeph>/with_wddm</codeph> when invoking the Windows Guest Additions installer. This is only required for
+        Vista and Windows 7. </p>
     </note>
     <note>
-      <p>
-              For Windows Aero to run correctly on a guest, the guest's
-              VRAM size needs to be configured to at least 128 MB.
-            </p>
+      <p>For Windows Aero to run correctly on a guest, the guest's VRAM size needs to be configured to at least 128 MB. </p>
     </note>
-    <p>
-            For more options regarding unattended guest installations,
-            consult the command line help by using the command:
-          </p>
+    <p>For more options regarding unattended guest installations, consult the command line help by using the command: </p>
     <pre xml:space="preserve">VBoxWindowsAdditions.exe /?</pre>
   </body>
Index: trunk/doc/manual/en_US/dita/topics/additions-windows-install-unattended.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/additions-windows-install-unattended.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/additions-windows-install-unattended.dita	(revision 105388)
@@ -5,17 +5,9 @@
   
   <body>
-    <p>
-          You can configure unattended installation of the
-          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions when you create a new VM using
-          the <b outputclass="bold">Create Virtual Machine</b>
-          wizard. Select the <b outputclass="bold">Guest
-          Additions</b> check box on the
-          <b outputclass="bold">Unattended Guest OS Install</b>
-          page of the wizard.
-        </p>
-    <p>
-          Guest Additions are installed automatically, following
-          completion of the guest OS installation.
-        </p>
+    <p>You can configure unattended installation of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest
+      Additions when you create a new VM using the <b outputclass="bold">Create Virtual Machine</b> wizard. Select the
+        <b outputclass="bold">Guest Additions</b> check box on the <b outputclass="bold">Unattended Guest OS Install</b>
+      page of the wizard. </p>
+    <p>Guest Additions are installed automatically, following completion of the guest OS installation. </p>
   </body>
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/additions-windows.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/additions-windows.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/additions-windows.dita	(revision 105388)
@@ -5,9 +5,6 @@
   
   <body>
-    <p>
-        The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Windows Guest Additions are designed to be
-        installed in a virtual machine running a Windows operating
-        system. The following versions of Windows guests are supported:
-      </p>
+    <p>The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Windows Guest Additions are designed to be installed in
+      a virtual machine running a Windows operating system. The following versions of Windows guests are supported: </p>
     <ul>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/clone.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/clone.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/clone.dita	(revision 105388)
@@ -2,138 +2,46 @@
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
 <topic xml:lang="en-us" id="clone">
-  <title>Cloning Virtual Machines</title>
+  <title>Cloning a Virtual Machine</title>
   
   <body>
     <p>You can create a full copy or a linked copy of an existing VM. This copy is called a <i>clone</i>. You might use
       a cloned VM to experiment with a VM configuration, to test different guest OS levels, or to back up a VM. </p>
-    <p>The <b outputclass="bold">Clone Virtual Machine</b> wizard guides you through the cloning process. </p>
-    <p>You can start the Clone Virtual Machine wizard in one of the following ways: </p>
-    <ul>
+    <p>To clone a VM: </p>
+    <ol id="ol_ulp_zct_bcc">
+      <li>Ensure the VM you want to clone is not running.</li>
       <li>
-        <p>Click the VM name in the machine list and then select <b outputclass="bold">Clone</b> from the <b
+        <p>Click the VM name in the machine list, and then select <b outputclass="bold">Clone</b> from the <b
             outputclass="bold">Machine</b> menu. </p>
       </li>
-      <li>
-        <p>Click <b outputclass="bold">Clone</b> in the <b outputclass="bold">Snapshots</b> window for the selected VM. </p>
-      </li>
-    </ul>
-    <note>
-      <p>The <b outputclass="bold">Clone</b> menu item is disabled while a virtual machine is running. </p>
-    </note>
-    <p>The <b outputclass="bold">New Machine Name and Path</b> page is displayed. </p>
-    <fig id="fig-clone-wizard-name-path">
-      <title>Clone Virtual Machine Wizard: New Machine Name and Path</title>
-      <xref href="images/clone-vm-1.png" format="png" platform="htmlhelp">
-        <image href="images/clone-vm-1.png" width="10cm" placement="break">
-          <alt>Clone Virtual Machine Wizard: New Machine Name and Path</alt>
-        </image>
-      </xref>
-        <image href="images/clone-vm-1.png" width="10cm" placement="break" platform="ohc">
-          <alt>Clone Virtual Machine Wizard: New Machine Name and Path</alt>
-        </image>
-    </fig>
-    <p>The following clone options are available: </p>
-    <ul>
-      <li>
-        <p><b outputclass="bold">Name:</b> A name for the cloned
-          machine.
-        </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Path:</b> Choose a location for
-          the cloned virtual machine, otherwise <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses the
-          default machines folder.
-        </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">MAC Address Policy:</b> Specifies
-          whether to retain network card MAC addresses when cloning the
-          VM.
-        </p>
-        <p>
-          For example, the <b outputclass="bold">Generate New MAC
-          Addresses For All Network Adapters</b> value assigns a
-          new MAC address to each network card during cloning. This is
-          the default setting. This is the best option when both the
-          source VM and the cloned VM must operate on the same network.
-          Other values enable you to retain the existing MAC addresses
-          in the cloned VM.
-        </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Keep Disk Names:</b> Retains the
-          disk image names when cloning the VM.
-        </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Keep Hardware UUIDs:</b> Retains
-          the hardware universally unique identifiers (UUIDs) when
-          cloning the VM.
-        </p>
-      </li>
-    </ul>
-    <p>Click <b outputclass="bold">Next</b>. The <b outputclass="bold">Clone Type</b> page is displayed. </p>
-    <fig id="fig-clone-type">
-      <title>Clone Virtual Machine Wizard: Clone Type</title>
-      <xref href="images/clone-vm-2.png" format="png" platform="htmlhelp">
-        <image href="images/clone-vm-2.png" width="10cm" placement="break">
-          <alt>Clone Virtual Machine Wizard: Clone Type</alt>
-        </image>
-      </xref>
-      <image href="images/clone-vm-2.png" width="10cm" placement="break" platform="ohc">
-        <alt>Clone Virtual Machine Wizard: Clone Type</alt>
-      </image>
-    </fig>
-    <p>The <b outputclass="bold">Clone Type</b> option specifies whether to create a clone that is linked to the source
-      VM or to create a fully independent clone: </p>
-    <ul>
-      <li>
-        <p><b outputclass="bold">Full Clone:</b> Copies all
-          dependent disk images to the new VM folder. A full clone can
-          operate fully without the source VM.
-        </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Linked Clone:</b> Creates new
-          differencing disk images based on the source VM disk images.
-          If you select the current state of the source VM as the clone
-          point, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates a new snapshot.
-        </p>
-      </li>
-    </ul>
-    <p>
-      (Optional) Click <b outputclass="bold">Next</b>. The
-      <b outputclass="bold">Snapshots</b> page is displayed.
-    </p>
-    <note>
-      <p>The Snapshots page is only displayed for machines that have snapshots and the selected clone type is <b
-          outputclass="bold">Full Clone</b>. </p>
-    </note>
-    <fig id="fig-clone-wizard-snapshots">
-      <title>Clone Virtual Machine Wizard: Snapshots</title>
-      <xref href="images/clone-vm-3.png" format="png" platform="htmlhelp">
-        <image href="images/clone-vm-3.png" width="10cm" placement="break">
-          <alt>Clone Virtual Machine Wizard: Snapshots</alt>
-        </image>
-      </xref>
-      <image href="images/clone-vm-3.png" width="10cm" placement="break" platform="ohc">
-        <alt>Clone Virtual Machine Wizard: Snapshots</alt>
-      </image>
-    </fig>
-    <p>You use this page to select which parts of the snapshot tree to include in the clone. The available options are
-      as follows: </p>
-    <ul>
-      <li>
-        <p><b outputclass="bold">Current Machine State:</b> Clones
-          the current state of the VM. Snapshots are not included.
-        </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Everything:</b> Clones the
-          current machine state and all its snapshots.
-        </p>
-      </li>
-    </ul>
-    <p>Click <b outputclass="bold">Finish</b> to start the clone operation. </p>
+      <li>Enter the following details for the clone.<ul id="ul_rkb_nct_bcc">
+          <li><b outputclass="bold">Name:</b> A name for the cloned machine. </li>
+          <li><b outputclass="bold">Path:</b> Choose a location for the cloned virtual machine, otherwise <ph
+              conkeyref="vbox-conkeyref-phrases/product-name"/> uses the default machines folder. </li>
+          <li><b outputclass="bold">MAC Address Policy:</b> Specifies whether to retain network card MAC addresses when
+            cloning the VM.<p>The <b outputclass="bold">Generate New MAC Addresses For All Network Adapters</b> value
+              assigns a new MAC address to each network card during cloning. This is the default setting. This is the
+              best option when both the source VM and the cloned VM must operate on the same network. Other values
+              enable you to retain the existing MAC addresses in the cloned VM.</p></li>
+          <li><b outputclass="bold">Keep Disk Names:</b> Retains the disk image names when cloning the VM.</li>
+          <li><b outputclass="bold">Keep Hardware UUIDs:</b> Retains the hardware universally unique identifiers (UUIDs)
+            when cloning the VM. </li></ul></li>
+      <li>Click <b outputclass="bold">Next</b>. The <b outputclass="bold">Clone Type</b> page is displayed.</li>
+      <li>The <b outputclass="bold">Clone Type</b> option specifies whether to create a clone that is linked to the
+        source VM or to create a fully independent clone:<ul id="ul_i1y_qn5_bcc">
+          <li><b outputclass="bold">Full Clone:</b> Copies all dependent disk images to the new VM folder. A full clone
+            can operate fully without the source VM. </li>
+          <li><b outputclass="bold">Linked Clone:</b> Creates new differencing disk images based on the source VM disk
+            images. If you select the current state of the source VM as the clone point, <ph
+              conkeyref="vbox-conkeyref-phrases/product-name"/> creates a new snapshot. </li>
+        </ul></li>
+    <li>Click <b outputclass="bold">Next</b>. If your VM has snapshots and you chose Full Clone, use the <b
+          outputclass="bold">Snapshots</b> page to select the parts of the snapshot tree to clone with the VM.<ul
+          id="ul_igj_t45_bcc">
+          <li><b outputclass="bold">Current Machine State:</b> Clones the current state of the VM. Snapshots are not
+            included. </li>
+          <li><b outputclass="bold">Everything:</b> Clones the current machine state and all its snapshots.</li>
+        </ul></li>
+
+    <li><p>Click <b outputclass="bold">Finish</b> to start the clone operation. </p></li></ol>
     <p>The duration of the clone operation depends on the size and number of attached disk images. In addition, the
       clone operation saves all the differencing disk images of a snapshot. </p>
Index: trunk/doc/manual/en_US/dita/topics/create-vm-wizard.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/create-vm-wizard.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/create-vm-wizard.dita	(revision 105388)
@@ -2,5 +2,5 @@
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
 <topic xml:lang="en-us" id="create-vm-wizard">
-  <title>Creating Your First Virtual Machine</title>
+  <title>Creating a Virtual Machine</title>
   
   <body>
Index: trunk/doc/manual/en_US/dita/topics/gui-vmgroups.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/gui-vmgroups.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/gui-vmgroups.dita	(revision 105388)
@@ -5,21 +5,8 @@
   
   <body>
-    <p>VM groups are groups of VMs that you can create as and when required. You can manage and perform functions on
-      them collectively, as well as individually. </p>
-    <p>The following figure shows VM groups displayed in VirtualBox Manager. </p>
-    <fig id="fig-vm-groups">
-      <title>Groups of Virtual Machines</title>
-      <xref href="images/vm-groups.png" format="png" platform="htmlhelp">
-        <image href="images/vm-groups.png" width="10cm" placement="break">
-          <alt>Groups of Virtual Machines</alt>
-        </image>
-      </xref>
-      <image platform="ohc" href="images/vm-groups.png" width="10cm" placement="break">
-        <alt>Groups of Virtual Machines</alt>
-      </image>
-    </fig>
-    <p>
-      The following features are available for groups:
-    </p>
+      <!-- 7.1: pic removed-->
+    <p>Create VM groups if you want to manage several VMs together, and perform functions on them collectively, as well
+      as individually. </p>
+    <p>The following features are available for groups: </p>
     <ul>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/intro-running.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/intro-running.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/intro-running.dita	(revision 105388)
@@ -2,5 +2,5 @@
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
 <topic xml:lang="en-us" id="intro-running">
-  <title>Running Your Virtual Machine</title>
+  <title>Running a Virtual Machine</title>
   
   <body>
Index: trunk/doc/manual/en_US/dita/topics/mountingadditionsiso.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/mountingadditionsiso.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/mountingadditionsiso.dita	(revision 105388)
@@ -5,24 +5,13 @@
   
   <body>
-    <p>
-          In the <b outputclass="bold">Devices</b> menu in the
-          virtual machine's menu bar, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has a menu item
-          <b outputclass="bold">Insert Guest Additions CD
-          Image</b>, which mounts the Guest Additions ISO file
-          inside your virtual machine. A Windows guest should then
-          automatically start the Guest Additions installer, which
-          installs the Guest Additions on your Windows guest.
-        </p>
-    <p>
-          For other guest operating systems, or if automatic start of
-          software on a CD is disabled, you need to do a manual start of
-          the installer.
-        </p>
+    <p>In the <b outputclass="bold">Devices</b> menu in the virtual machine's menu bar, <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> has a menu item <b outputclass="bold">Insert Guest Additions
+        CD Image</b>, which mounts the Guest Additions ISO file inside your virtual machine. A Windows guest should then
+      automatically start the Guest Additions installer, which installs the Guest Additions on your Windows guest. </p>
+    <p>For other guest operating systems, or if automatic start of software on a CD is disabled, you need to do a manual
+      start of the installer. </p>
     <note>
-      <p>
-            For the basic Direct3D acceleration to work in a Windows
-            guest, you have to install the WDDM video driver available
-            for Windows Vista or later.
-          </p>
+      <p>For the basic Direct3D acceleration to work in a Windows guest, you have to install the WDDM video driver
+        available for Windows Vista or later. </p>
       <p>
             For Windows 8 and later, only the WDDM Direct3D video driver
@@ -33,97 +22,50 @@
           </p>
     </note>
-    <p>
-          If you prefer to mount the Guest Additions manually, you can
-          perform the following steps:
-        </p>
+    <p>If you prefer to mount the Guest Additions manually, you can perform the following steps: </p>
     <ol>
       <li>
-        <p>
-              Start the virtual machine in which you have installed
-              Windows.
-            </p>
+        <p>Start the virtual machine in which you have installed Windows. </p>
       </li>
       <li>
-        <p>
-              Select <b outputclass="bold">Optical Drives</b>
-              from the <b outputclass="bold">Devices</b> menu in
-              the virtual machine's menu bar and then
-              <b outputclass="bold">Choose/Create a Disk
-              Image</b>. This displays the Virtual Media Manager,
-              described in <xref href="virtual-media-manager.dita#virtual-media-manager"/>.
-            </p>
+        <p>Select <b outputclass="bold">Optical Drives</b> from the <b outputclass="bold">Devices</b> menu in the
+          virtual machine's menu bar and then <b outputclass="bold">Choose/Create a Disk Image</b>. This displays the
+          Virtual Media Manager, described in <xref href="virtual-media-manager.dita#virtual-media-manager"/>. </p>
       </li>
       <li>
-        <p>
-              In the Virtual Media Manager, click
-              <b outputclass="bold">Add</b> and browse your host
-              file system for the
-              <filepath>VBoxGuestAdditions.iso</filepath> file.
-            </p>
+        <p>In the Virtual Media Manager, click <b outputclass="bold">Add</b> and browse your host file system for the
+            <filepath>VBoxGuestAdditions.iso</filepath> file. </p>
         <ul>
-          <li>
-            <p>
-                  On a Windows host, this file is in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
-                  installation directory, usually in
-                  <filepath>C:\Program
-                  files\Oracle\VirtualBox</filepath>.
-                </p>
-          </li>
+          <li>On a Windows host, this file is in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installation
+            directory, usually in <filepath>C:\Program files\Oracle\VirtualBox</filepath>. </li>
           <li>
             <p> On macOS hosts, this file is in the application bundle of <ph
                 conkeyref="vbox-conkeyref-phrases/product-name"/>. Right-click the <ph
-                conkeyref="vbox-conkeyref-phrases/product-name"/> icon in Finder and choose <b
-                outputclass="bold">Show Package Contents</b>. The file is located in the
-                <filepath>Contents/MacOS</filepath> folder. </p>
+                conkeyref="vbox-conkeyref-phrases/product-name"/> icon in Finder and choose <b outputclass="bold">Show
+                Package Contents</b>. The file is located in the <filepath>Contents/MacOS</filepath> folder. </p>
           </li>
           <li>
-            <p>
-                  On a Linux host, this file is in the
-                  <filepath>additions</filepath> folder where you
-                  installed <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, usually
-                  <filepath>/opt/VirtualBox/</filepath>.
-                </p>
+            <p>On a Linux host, this file is in the <filepath>additions</filepath> folder where you installed <ph
+                conkeyref="vbox-conkeyref-phrases/product-name"/>, usually <filepath>/opt/VirtualBox/</filepath>. </p>
           </li>
           <li>
-            <p>
-                  On Oracle Solaris hosts, this file is in the
-                  <filepath>additions</filepath> folder where you
-                  installed <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, usually
-                  <filepath>/opt/VirtualBox</filepath>.
-                </p>
+            <p>On Oracle Solaris hosts, this file is in the <filepath>additions</filepath> folder where you installed
+                <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, usually <filepath>/opt/VirtualBox</filepath>. </p>
           </li>
         </ul>
       </li>
       <li>
-        <p>
-              In the Virtual Media Manager, select the ISO file and
-              click the <b outputclass="bold">Add</b> button.
-              This mounts the ISO file and presents it to your Windows
-              guest as a CD-ROM.
-            </p>
+        <p>In the Virtual Media Manager, select the ISO file and click the <b outputclass="bold">Add</b> button. This
+          mounts the ISO file and presents it to your Windows guest as a CD-ROM. </p>
       </li>
     </ol>
-    <p>
-          Unless you have the Autostart feature disabled in your Windows
-          guest, Windows will now autostart the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest
-          Additions installation program from the Additions ISO. If the
-          Autostart feature has been turned off, choose
-          <filepath>VBoxWindowsAdditions.exe</filepath> from the CD/DVD
-          drive inside the guest to start the installer.
-        </p>
-    <p>
-          The installer will add several device drivers to the Windows
-          driver database and then invoke the hardware detection wizard.
-        </p>
-    <p>
-          Depending on your configuration, it might display warnings
-          that the drivers are not digitally signed. You must confirm
-          these in order to continue the installation and properly
-          install the Additions.
-        </p>
-    <p>
-          After installation, reboot your guest operating system to
-          activate the Additions.
-        </p>
+    <p>Unless you have the Autostart feature disabled in your Windows guest, Windows will now autostart the <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions installation program from the Additions ISO.
+      If the Autostart feature has been turned off, choose <filepath>VBoxWindowsAdditions.exe</filepath> from the CD/DVD
+      drive inside the guest to start the installer. </p>
+    <p>The installer will add several device drivers to the Windows driver database and then invoke the hardware
+      detection wizard. </p>
+    <p>Depending on your configuration, it might display warnings that the drivers are not digitally signed. You must
+      confirm these in order to continue the installation and properly install the Additions. </p>
+    <p>After installation, reboot your guest operating system to activate the Additions. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/sharedfolders.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/sharedfolders.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/sharedfolders.dita	(revision 105388)
@@ -6,126 +6,75 @@
             
             <body>
-               <p>
-      With the <i>shared folders</i> feature of
-      <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you can access files of your host system from
-      within the guest system. This is similar to how you would use
-      network shares in Windows networks, except that shared folders do
-      not require networking, only the Guest Additions. Shared folders
-      are supported with Windows 2000 or later, Linux, and Oracle
-      Solaris guests. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> includes experimental support for
-      Mac OS X and OS/2 guests.
-    </p>
-               <p>
-      Shared folders physically reside on the <i>host</i>
-      and are then shared with the guest, which uses a special file
-      system driver in the Guest Additions to talk to the host. For
-      Windows guests, shared folders are implemented as a pseudo-network
-      redirector. For Linux and Oracle Solaris guests, the Guest
-      Additions provide a virtual file system.
-    </p>
-               <p>
-      To share a host folder with a virtual machine in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>,
-      you must specify the path of the folder and choose a
-      <i>share name</i> that the guest can use to access
-      the shared folder. This happens on the host. In the guest you can
-      then use the share name to connect to it and access files.
-    </p>
-               <p>
-      There are several ways in which shared folders can be set up for a
-      virtual machine:
-    </p>
+               <p>With the <i>shared folders</i> feature of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you
+      can access files of your host system from within the guest system. This is similar to how you would use network
+      shares in Windows networks, except that shared folders do not require networking, only the Guest Additions. Shared
+      folders are supported with Windows 2000 or later, Linux, and Oracle Solaris guests. <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> includes experimental support for Mac OS X and OS/2 guests. </p>
+               <p>Shared folders physically reside on the <i>host</i> and are then shared with the guest, which uses a
+      special file system driver in the Guest Additions to talk to the host. For Windows guests, shared folders are
+      implemented as a pseudo-network redirector. For Linux and Oracle Solaris guests, the Guest Additions provide a
+      virtual file system. </p>
+               <p>To share a host folder with a virtual machine in <ph conkeyref="vbox-conkeyref-phrases/product-name"
+      />, you must specify the path of the folder and choose a <i>share name</i> that the guest can use to access the
+      shared folder. This happens on the host. In the guest you can then use the share name to connect to it and access
+      files. </p>
+               <p>There are several ways in which shared folders can be set up for a virtual machine: </p>
                <ul>
                   <li>
-                     <p> In the window of a running VM, you select <b outputclass="bold">Shared
-            Folders</b> from the <b outputclass="bold">Devices</b> menu, or click the folder icon on
-          the status bar in the bottom right corner. </p>
+                     <p>In the window of a running VM, you select <b outputclass="bold">Shared Folders</b> from the <b
+            outputclass="bold">Devices</b> menu, or click the folder icon on the status bar in the bottom right corner. </p>
                   </li>
                   <li>
-                     <p>
-          If a VM is not currently running, you can configure shared
-          folders in the virtual machine's
-          <b outputclass="bold">Settings</b> window.
-        </p>
+                     <p>If a VM is not currently running, you can configure shared folders in the virtual machine's <b
+            outputclass="bold">Settings</b> window. </p>
                   </li>
                   <li>
-                     <p>
-          From the command line, you can create shared folders using
-          <userinput>VBoxManage</userinput>, as follows:
-        </p>
+                     <p>From the command line, you can create shared folders using <userinput>VBoxManage</userinput>, as
+          follows: </p>
                      <pre xml:space="preserve">VBoxManage sharedfolder add "VM name" --name "sharename" --hostpath "C:\test"</pre>
                      <p> See <xref href="vboxmanage-sharedfolder.dita"/>. </p>
                   </li>
                </ul>
-               <p>
-      There are two types of shares:
-    </p>
+               <p>There are two types of shares: </p>
                <ul>
                   <li>
-                     <p>
-          Permanent shares, that are saved with the VM settings.
-        </p>
+                     <p>Permanent shares, that are saved with the VM settings. </p>
                   </li>
                   <li>
-                     <p>
-          Transient shares, that are added at runtime and disappear when
-          the VM is powered off. These can be created using a check box
-          in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, or by using the <codeph>--transient</codeph>
-          option of the <userinput>VBoxManage sharedfolder add</userinput>
-          command.
-        </p>
+                     <p>Transient shares, that are added at runtime and disappear when the VM is powered off. These can
+          be created using a check box in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, or by using the
+            <codeph>--transient</codeph> option of the <userinput>VBoxManage sharedfolder add</userinput> command. </p>
                   </li>
                </ul>
-               <p>
-      Shared folders can either be read-write or read-only. This means
-      that the guest is either allowed to both read and write, or just
-      read files on the host. By default, shared folders are read-write.
-      Read-only folders can be created using a check box in the
-      <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, or with the <codeph>--readonly option</codeph> of the
-      <userinput>VBoxManage sharedfolder add</userinput> command.
-    </p>
-               <p>
-      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> shared folders also support symbolic links, also
-      called <i>symlinks</i>, under the following
-      conditions:
-    </p>
+               <p>Shared folders can either be read-write or read-only. This means that the guest is either allowed to
+      both read and write, or just read files on the host. By default, shared folders are read-write. Read-only folders
+      can be created using a check box in the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, or with the
+        <codeph>--readonly option</codeph> of the <userinput>VBoxManage sharedfolder add</userinput> command. </p>
+               <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> shared folders also support symbolic links, also
+      called <i>symlinks</i>, under the following conditions: </p>
                <ul>
                   <li>
-                     <p>
-          The host operating system must support symlinks. For example,
-          a macOS, Linux, or Oracle Solaris host is required.
-        </p>
+                     <p>The host operating system must support symlinks. For example, a macOS, Linux, or Oracle Solaris
+          host is required. </p>
                   </li>
                   <li>
-                     <p>
-          The guest VM must have a version of the Guest Additions
-          installed which supports symlinks. Currently only the Linux and
-          Oracle Solaris Guest Additions support symlinks.
-        </p>
+                     <p>The guest VM must have a version of the Guest Additions installed which supports symlinks.
+          Currently only the Linux and Oracle Solaris Guest Additions support symlinks. </p>
                   </li>
                   <li>
-                     <p>
-          For security reasons the guest OS is not allowed to create
-          symlinks by default. If you trust the guest OS to not abuse
-          this functionality, you can enable the creation of symlinks for
-          a shared folder as follows:
-        </p>
+                     <p>For security reasons the guest OS is not allowed to create symlinks by default. If you trust the
+          guest OS to not abuse this functionality, you can enable the creation of symlinks for a shared folder as
+          follows: </p>
                      <pre xml:space="preserve">VBoxManage setextradata <varname>VM-name</varname> VBoxInternal2/SharedFoldersEnableSymlinksCreate/<varname>sharename</varname> 1</pre>
                   </li>
                </ul>
+            <p>If a symbolic link is created inside a shared folder on the host and the installed Guest Additions do not
+      support symbolic links then the guest will see the target of the symlink as a file inside the shared folder. For
+      example, if a symlink is created to a file on a Linux host: </p>
             <p>
-          If a symbolic link is created inside a shared folder on the host
-          and the installed Guest Additions do not support symbolic links
-          then the guest will see the target of the symlink as a file
-          inside the shared folder. For example, if a symlink is created
-          to a file on a Linux host:
-        </p>
-               <p>
                      <pre xml:space="preserve">$ cd /SharedFolder &amp;&amp; ln -s filename symlink-to-filename</pre>
         </p>
-               <p>
-          When the shared folder is viewed on a Windows guest there
-          will be two identical files listed, <userinput>filename</userinput>
-          and <userinput>symlink-to-filename</userinput>.
-        </p>
+               <p>When the shared folder is viewed on a Windows guest there will be two identical files listed,
+        <userinput>filename</userinput> and <userinput>symlink-to-filename</userinput>. </p>
             </body>
             
Index: trunk/doc/manual/en_US/dita/topics/soft-keyb.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/soft-keyb.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/soft-keyb.dita	(revision 105388)
@@ -4,5 +4,5 @@
 
 <topic xml:lang="en-us" id="soft-keyb">
-  <!-- 7.1: Updated pic added -->
+  <!-- 7.1: pic removed-->
   <title>Soft Keyboard</title>
   <body>
@@ -15,15 +15,4 @@
         by the soft keyboard. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> does not do this automatically. </p>
     </note>
-    <fig id="fig-soft-keyb">
-      <title>Soft Keyboard in a Guest Virtual Machine</title>
-      <xref href="images/softkeybd.png" format="png" platform="htmlhelp">
-        <image href="images/softkeybd.png" width="14cm" placement="break">
-          <alt>Soft Keyboard in a Guest Virtual Machine</alt>
-        </image>
-      </xref>
-      <image platform="ohc" href="images/softkeybd.png" width="14cm" placement="break">
-        <alt>Soft Keyboard in a Guest Virtual Machine</alt>
-      </image>
-    </fig>
     <p>The soft keyboard can be used in the following scenarios: </p>
     <ul>
Index: trunk/doc/manual/en_US/dita/topics/windows-guest-file-extraction.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/windows-guest-file-extraction.dita	(revision 105361)
+++ trunk/doc/manual/en_US/dita/topics/windows-guest-file-extraction.dita	(revision 105388)
@@ -6,19 +6,11 @@
                   
                   <body>
-                     <p>
-          If you would like to install the files and drivers manually,
-          you can extract the files from the Windows Guest Additions
-          setup as follows:
-        </p>
+                     <p>If you would like to install the files and drivers manually, you can extract the files from the
+      Windows Guest Additions setup as follows: </p>
                      <pre xml:space="preserve">VBoxWindowsAdditions.exe /extract</pre>
-                     <p>
-          To explicitly extract the Windows Guest Additions for another
-          platform than the current running one, such as 64-bit files on
-          a 32-bit system, you must use the appropriate platform
-          installer. Use
-          <filepath>VBoxWindowsAdditions-x86.exe</filepath> or
-          <filepath>VBoxWindowsAdditions-amd64.exe</filepath> with the
-          <codeph>/extract</codeph> parameter.
-        </p>
+                     <p>To explicitly extract the Windows Guest Additions for another platform than the current running
+      one, such as 64-bit files on a 32-bit system, you must use the appropriate platform installer. Use
+        <filepath>VBoxWindowsAdditions-x86.exe</filepath> or <filepath>VBoxWindowsAdditions-amd64.exe</filepath> with
+      the <codeph>/extract</codeph> parameter. </p>
                   </body>
                   
