Index: trunk/doc/manual/en_US/dita/topics/TechnicalBackground.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/TechnicalBackground.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/TechnicalBackground.dita	(revision 105134)
@@ -5,11 +5,9 @@
   
   <body>
-    <p>
-    This chapter provides additional information for readers who are
-    familiar with computer architecture and technology and wish to find
-    out more about how <ph conkeyref="vbox-conkeyref-phrases/product-name"/> works <i>under the
-    hood</i>. The contents of this chapter are not required
-    reading in order to use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> successfully.
-  </p>
+    <p> This chapter provides additional information for readers who are familiar with computer
+      architecture and technology and want to find out more about how <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> works <i>under the hood</i>. The contents
+      of this chapter are not required reading in order to use <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> successfully. </p>
   </body>
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/VirtualBoxAPI.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/VirtualBoxAPI.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/VirtualBoxAPI.dita	(revision 105134)
@@ -6,10 +6,9 @@
   <body>
     <p>
-    <ph conkeyref="vbox-conkeyref-phrases/product-name"/> comes with comprehensive support for third-party
-    developers. The so-called <i>Main API</i> of
-    <ph conkeyref="vbox-conkeyref-phrases/product-name"/> exposes the entire feature set of the virtualization
-    engine. It is completely documented and available to anyone who
-    wishes to control <ph conkeyref="vbox-conkeyref-phrases/product-name"/> programmatically.
-  </p>
+      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> comes with comprehensive support for
+      third-party developers. The so-called <i>Main API</i> of <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> exposes the entire feature set of the
+      virtualization engine. It is completely documented and available to anyone who wants to
+      control <ph conkeyref="vbox-conkeyref-phrases/product-name"/> programmatically. </p>
     <p>
     The Main API is made available to C++ clients through COM on Windows
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 105087)
+++ trunk/doc/manual/en_US/dita/topics/additions-linux-graphics-mouse.dita	(revision 105134)
@@ -31,10 +31,7 @@
           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 wish 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> 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
Index: trunk/doc/manual/en_US/dita/topics/additions-linux-uninstall.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/additions-linux-uninstall.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/additions-linux-uninstall.dita	(revision 105134)
@@ -5,13 +5,9 @@
   
   <body>
-    <p>
-          If you have a version of the Guest Additions installed on your
-          virtual machine and wish 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>
Index: trunk/doc/manual/en_US/dita/topics/additions-linux.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/additions-linux.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/additions-linux.dita	(revision 105134)
@@ -52,17 +52,14 @@
         Additions work in those distributions.
       </p>
-    <p>
-        Note that some Linux distributions already come with all or part
-        of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions. You may choose to keep
-        the distribution's version of the Guest Additions but these are
-        often not up to date and limited in functionality, so we
-        recommend replacing them with the Guest Additions that come with
-        <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Linux Guest Additions
-        installer tries to detect an existing installation and replace
-        them but depending on how the distribution integrates the Guest
-        Additions, this may require some manual interaction. It is
-        highly recommended to take a snapshot of the virtual machine
-        before replacing preinstalled Guest Additions.
-      </p>
+    <p> Note that some Linux distributions already come with all or part of the <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions. You may choose to keep
+      the distribution's version of the Guest Additions but these are often out of date and limited
+      in functionality, so we recommend replacing them with the Guest Additions that come with <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/>. The <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> Linux Guest Additions installer tries to
+      detect an existing installation and replace them but depending on how the distribution
+      integrates the Guest Additions, this may require some manual interaction. It is highly
+      recommended to take a snapshot of the virtual machine before replacing preinstalled Guest
+      Additions. </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 105087)
+++ trunk/doc/manual/en_US/dita/topics/additions-windows.dita	(revision 105134)
@@ -23,5 +23,5 @@
       <li>
         <p>
-            Microsoft Windows 10 (all feature updates)
+            Microsoft Windows 10 (all builds)
           </p>
       </li>
Index: trunk/doc/manual/en_US/dita/topics/autologon.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/autologon.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/autologon.dita	(revision 105134)
@@ -9,10 +9,7 @@
       and Oracle Solaris to enable automated logins on the guest.
     </p>
-    <p>
-      When a guest operating system is running in a virtual machine, it
-      might be desirable to perform coordinated and automated logins
-      using credentials passed from the host. Credentials are user name,
-      password, and domain name, where each value might be empty.
-    </p>
+    <p> When a guest operating system is running in a virtual machine, it might be required to
+      perform coordinated and automated logins using credentials passed from the host. Credentials
+      are user name, password, and domain name, where each value might be empty. </p>
   </body>
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/autologon_unix.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/autologon_unix.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/autologon_unix.dita	(revision 105134)
@@ -35,16 +35,10 @@
         </p>
     </note>
-    <p>
-        The <filepath>pam_vbox.so</filepath> module is shipped as part
-        of the Guest Additions but it is not installed and/or activated
-        on the guest OS by default. In order to install it, it has to be
-        copied from
-        <filepath>/opt/VBoxGuestAdditions-<varname>version</varname>/other/</filepath>
-        to the security modules directory. This is usually
-        <filepath>/lib/security/</filepath> on 32-bit Linux guests or
-        <filepath>/lib64/security/</filepath> on 64-bit Linux guests.
-        Please refer to your guest OS documentation for the correct PAM
-        module directory.
-      </p>
+    <p> The <filepath>pam_vbox.so</filepath> module is shipped as part of the Guest Additions but it
+      is not installed or activated on the guest OS by default. In order to install it, it has to be
+      copied from <filepath>/opt/VBoxGuestAdditions-<varname>version</varname>/other/</filepath> to
+      the security modules directory. This is usually <filepath>/lib/security/</filepath> on 32-bit
+      Linux guests or <filepath>/lib64/security/</filepath> on 64-bit Linux guests. Please refer to
+      your guest OS documentation for the correct PAM module directory. </p>
     <p>
         For example, to use <filepath>pam_vbox.so</filepath> with a
@@ -74,20 +68,14 @@
       </li>
       <li>
-        <p>
-            If authentication against the shadow database using
-            <filepath>pam_unix.so</filepath> or
-            <filepath>pam_unix2.so</filepath> is desired, the argument
-            <codeph>try_first_pass</codeph> for
-            <filepath>pam_unix.so</filepath> or
-            <codeph>use_first_pass</codeph> for
-            <filepath>pam_unix2.so</filepath> is needed in order to pass
-            the credentials from the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> module to the shadow
-            database authentication module. For Ubuntu, this needs to be
-            added to <filepath>/etc/pam.d/common-auth</filepath>, to the
-            end of the line referencing
-            <filepath>pam_unix.so</filepath>. This argument tells the
-            PAM module to use credentials already present in the stack,
-            such as the ones provided by the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> PAM module.
-          </p>
+        <p> If authentication against the shadow database using <filepath>pam_unix.so</filepath> or
+            <filepath>pam_unix2.so</filepath> is required, the argument
+            <codeph>try_first_pass</codeph> for <filepath>pam_unix.so</filepath> or
+            <codeph>use_first_pass</codeph> for <filepath>pam_unix2.so</filepath> is needed in order
+          to pass the credentials from the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
+          module to the shadow database authentication module. For Ubuntu, this must be added to
+            <filepath>/etc/pam.d/common-auth</filepath>, to the end of the line referencing
+            <filepath>pam_unix.so</filepath>. This argument tells the PAM module to use credentials
+          already present in the stack, such as the ones provided by the <ph
+            conkeyref="vbox-conkeyref-phrases/product-name"/> PAM module. </p>
       </li>
     </ol>
Index: trunk/doc/manual/en_US/dita/topics/autostart-windows.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/autostart-windows.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/autostart-windows.dita	(revision 105134)
@@ -74,9 +74,6 @@
         installed for users with empty passwords.
       </p>
-    <p>
-        Finally, the user should define which VMs should be started at
-        boot. The user should run the following command for every VM
-        they wish to start at boot:
-      </p>
+    <p> Finally, the user should define which VMs should be started at boot. The user should run the
+      following command for every VM they want to start at boot: </p>
     <pre xml:space="preserve">VBoxManage modifyvm <varname>VM name or UUID</varname> --autostart-enabled on</pre>
     <p>
@@ -86,10 +83,7 @@
     <pre xml:space="preserve">VBoxManage modifyvm <varname>VM name or UUID</varname> --autostart-enabled off</pre>
     <note>
-      <p>
-          On Windows hosts, starting VMs via the autostart service might
-          cause some issues, as the virtual machines are starting within
-          the same session as VBoxSVC. For more information see
-          <xref href="vboxsvc-session-0.dita#vboxsvc-session-0"/>.
-        </p>
+      <p> On Windows hosts, starting VMs by using the autostart service might cause some issues, as
+        the virtual machines are starting within the same session as VBoxSVC. For more information
+        see <xref href="vboxsvc-session-0.dita#vboxsvc-session-0"/>. </p>
     </note>
   </body>
Index: trunk/doc/manual/en_US/dita/topics/buffer-overwriting-mitigation.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/buffer-overwriting-mitigation.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/buffer-overwriting-mitigation.dita	(revision 105134)
@@ -5,12 +5,8 @@
   
   <body>
-    <p>
-          First, up to date CPU microcode is a prerequisite for the
-          buffer overwriting (clearing) mitigations. Some host OSes may
-          install these automatically, though it has traditionally been
-          a task best performed by the system firmware. Please check
-          with your system or mainboard manufacturer for the latest
-          firmware update.
-        </p>
+    <p> First, up-to-date CPU microcode is a prerequisite for the buffer overwriting (clearing)
+      mitigations. Some host OSes may install these automatically, though it has traditionally been
+      a task best performed by the system firmware. Please check with your system or mainboard
+      manufacturer for the latest firmware update. </p>
     <p>
           This mitigation aims at removing potentially sensitive data
Index: trunk/doc/manual/en_US/dita/topics/changevpd.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/changevpd.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/changevpd.dita	(revision 105134)
@@ -17,10 +17,7 @@
 $ VBoxManage setextradata <varname>VM-name</varname> \
 "VBoxInternal/Devices/ahci/0/Config/Port0/ModelNumber" "model"</pre>
-    <p>
-        The serial number is a 20 byte alphanumeric string, the firmware
-        revision an 8 byte alphanumeric string and the model number a 40
-        byte alphanumeric string. Instead of Port0, referring to the
-        first port, specify the desired SATA hard disk port.
-      </p>
+    <p> The serial number is a 20 byte alphanumeric string, the firmware revision an 8 byte
+            alphanumeric string and the model number a 40 byte alphanumeric string. Instead of
+            Port0, referring to the first port, specify the required SATA hard disk port. </p>
     <p>
         The above commands apply to virtual machines with an AHCI (SATA)
@@ -34,8 +31,6 @@
 $ VBoxManage setextradata <varname>VM-name</varname> \
 "VBoxInternal/Devices/piix3ide/0/Config/PrimaryMaster/ModelNumber" "model"</pre>
-    <p>
-        For hard disks, you can mark the drive as having a
-        non-rotational medium by using the following command:
-      </p>
+    <p> For hard disks, you can mark the drive as having a nonrotational medium by using the
+            following command: </p>
     <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> \
 "VBoxInternal/Devices/ahci/0/Config/Port0/NonRotational" "1"</pre>
@@ -50,10 +45,7 @@
 VBoxManage setextradata <varname>VM-name</varname> \
 "VBoxInternal/Devices/ahci/0/Config/Port0/ATAPIRevision" "revision"</pre>
-    <p>
-        The vendor id is an 8 byte alphanumeric string, the product id
-        an 16 byte alphanumeric string and the revision a 4 byte
-        alphanumeric string. Instead of Port0, referring to the first
-        port, specify the desired SATA hard disk port.
-      </p>
+    <p> The vendor id is an 8 byte alphanumeric string, the product id an 16 byte alphanumeric
+            string and the revision a 4 byte alphanumeric string. Instead of Port0, referring to the
+            first port, specify the required SATA hard disk port. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/cloud-using-cli.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/cloud-using-cli.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/cloud-using-cli.dita	(revision 105134)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="cloud-using-cli">
   <title>Using VBoxManage Commands With <ph conkeyref="vbox-conkeyref-phrases/oci"/></title>
-
+  
   <body>
     <p>
@@ -79,9 +79,14 @@
     <pre xml:space="preserve">VBoxManage cloud --provider="OCI" --profile="vbox-oci" instance terminate \
 --id="ocid1.instance.oc1..." </pre>
+    
+    <p><b outputclass="bold">Showing Cloud Instance Performance Metrics</b></p>
     <p>
-        For more details about the available commands for cloud operations, see <xref
-        href="vboxmanage-cloud.dita"/>.
+      To show CPU usage metrics for a cloud instance:
     </p>
+    <pre xml:space="preserve">VBoxManage cloud --provider="OCI" --profile="vbox-oci" instance metricdata \
+--id="ocid1.instance.oc1..." --metric-name="CpuUtilization"</pre>  
+    <p> For more details about the available commands for cloud operations, see <xref
+      href="vboxmanage-cloud.dita"/>. </p>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-networks.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-networks.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-networks.dita	(revision 105134)
@@ -3,5 +3,4 @@
 <topic xml:lang="en-us" id="cloud-using-cloud-networks">
   <title>Using a Cloud Network</title>
-
   <body>
     <p>
Index: trunk/doc/manual/en_US/dita/topics/cloud-vm-control.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/cloud-vm-control.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/cloud-vm-control.dita	(revision 105134)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="cloud-vm-control">
   <title>Controlling a Cloud VM</title>
-  
+  <!-- 7.1: OCI instance reset feature-->
   <body>
     <p>
@@ -16,9 +16,13 @@
       </li>
       <li>
-        <p><b outputclass="bold">Stop.</b> Right-click on the
-              cloud VM name, to display the
-              <b outputclass="bold">Close</b> menu. Options to
+        <p><b outputclass="bold">Stop.</b> Click on the
+              cloud VM name and select <b>Machine</b>, <b>Stop</b>. Menu options to
               shut down and power off the cloud VM are available.
             </p>
+      </li>
+      <li>
+        <p><b outputclass="bold">Reset.</b> Click on the
+          cloud VM name and select <b>Machine</b>, <b>Reset</b>. The cloud VM is stopped, then restarted automatically.
+        </p>
       </li>
       <li>
@@ -37,6 +41,5 @@
           When you control a cloud VM in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> the machine list is
           updated automatically with the current instance state, such as
-          <b outputclass="bold">Stopped</b> or
-          <b outputclass="bold">Running</b>.
+          <b outputclass="bold">Stopped</b> or <b outputclass="bold">Running</b>.
         </p>
     <p>
Index: trunk/doc/manual/en_US/dita/topics/cloud-vm.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/cloud-vm.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/cloud-vm.dita	(revision 105134)
@@ -3,5 +3,4 @@
 <topic xml:lang="en-us" id="cloud-vm">
   <title>Using Cloud Virtual Machines</title>
-  
   <body>
     <p>
@@ -23,12 +22,12 @@
     </note>
     <fig id="fig-cloud-vm-overview">
-      <title>Cloud VMs, Shown in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></title>
-      <xref href="images/cloudvm-overview.png" format="png" platform="htmlhelp">
-        <image href="images/cloudvm-overview.png" width="12cm" placement="break">
-          <alt>Cloud VMs, Shown in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></alt>
+      <title>Cloud VMs, Shown With Local VMs in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></title>
+      <xref href="images/cloudvm-overview-mixed.png" format="png" platform="htmlhelp">
+        <image href="images/cloudvm-overview-mixed.png" width="12cm" placement="break">
+          <alt>Cloud VMs, Shown With Local VMs in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></alt>
         </image>
       </xref>
-      <image platform="ohc" href="images/cloudvm-overview.png" width="12cm" placement="break">
-        <alt>Cloud VMs, Shown in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></alt>
+      <image platform="ohc" href="images/cloudvm-overview-mixed.png" width="12cm" placement="break">
+        <alt>Cloud VMs, Shown With Local VMs in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/></alt>
       </image>
     </fig>
@@ -46,4 +45,9 @@
             instance.</b> See <xref href="cloud-vm-add.dita#cloud-vm-add"/>.
           </p>
+      </li>
+      <li>
+        <p><b outputclass="bold">Copy an existing <ph conkeyref="vbox-conkeyref-phrases/oci"/>
+          instance.</b> See <xref href="cloud-vm-clone.dita#cloud-vm-clone"/>.
+        </p>
       </li>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/create-optical-disk-image.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/create-optical-disk-image.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/create-optical-disk-image.dita	(revision 105134)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="create-optical-disk-image">
   <title>Creating a Virtual Optical Disk Image</title>
-  
+  <!-- 7.1: Can now import VISO files-->
   <body>
     <p>
@@ -32,6 +32,6 @@
               </p>
             <p>
-                Click <b outputclass="bold">Configuration</b> and
-                enter a name in the <b outputclass="bold">Viso
+                Click <b outputclass="bold">Settings</b> and select the <b>VISO Options</b> tab.
+                Enter the name in the <b outputclass="bold">Viso
                 Name</b> field.
               </p>
@@ -77,4 +77,12 @@
                   </p>
               </li>
+              <li>
+                <p> To import <i>all</i> file content from an existing ISO into the virtual ISO,
+                  highlight the ISO file name and click <b>Import Selected ISO into the VISO
+                    Content</b>. The imported ISO is opened and content is listed in the <b
+                    outputclass="bold">VISO Content</b> pane.</p>
+                <p>To remove files from the imported ISO, select the files in the <b>Viso
+                    Content</b> pane and click <b>Remove Selected Item(s) from VISO</b>.</p>
+              </li>
             </ul>
           </li>
@@ -86,5 +94,5 @@
           </p>
         <p>
-            Click <b outputclass="bold">Create</b>.
+            Click <b outputclass="bold">Save and Close</b>.
           </p>
         <p>
Index: trunk/doc/manual/en_US/dita/topics/create-vm-wizard-hardware.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/create-vm-wizard-hardware.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/create-vm-wizard-hardware.dita	(revision 105134)
@@ -2,88 +2,30 @@
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
 <topic xml:lang="en-us" id="create-vm-wizard-hardware">
-  <title>Create Virtual Machine Wizard: Hardware</title>
+  <title>Set Up VM Hardware</title>
   
   <body>
-    <p>
-        Use this page to configure hardware settings for the virtual
-        machine.
-      </p>
-    <fig id="fig-create-vm-hardware">
-      <title>Creating a Virtual Machine: Hardware</title>
-      <xref href="images/create-vm-3.png" format="png" platform="htmlhelp">
-        <image href="images/create-vm-3.png" width="10cm" placement="break">
-          <alt>Creating a Virtual Machine: Hardware</alt>
-        </image>
-      </xref>
-      <image platform="ohc" href="images/create-vm-3.png" width="10cm" placement="break">
-        <alt>Creating a Virtual Machine: Hardware</alt>
-      </image>
-    </fig>
-    <p>
-        The following fields are available on this wizard page:
-      </p>
-    <ul>
-      <li>
-        <p><b outputclass="bold">Base Memory.</b> Select the
-            amount of RAM that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> should allocate every time
-            the virtual machine is started. The amount of memory
-            selected here will be taken away from your host machine and
-            presented to the guest OS, which will report this size as
-            the virtual machines installed RAM.
-          </p>
-        <note type="caution">
-          <p>
-              Choose this setting carefully. The memory you give to the
-              VM will not be available to your host OS while the VM is
-              running, so do not specify more than you can spare.
-            </p>
-          <p>
-              For example, if your host machine has 4 GB of RAM and you
-              enter 2048 MB as the amount of RAM for a particular
-              virtual machine, you will only have 2 GB left for all the
-              other software on your host while the VM is running. If
-              you run two VMs at the same time, even more memory will be
-              allocated for the second VM, which may not even be able to
-              start if that memory is not available.
-            </p>
-          <p>
-              On the other hand, you should specify as much as your
-              guest OS and your applications will require to run
-              properly. A guest OS may require at least 1 or 2 GB of
-              memory to install and boot up. For best performance, more
-              memory than that may be required.
-            </p>
-        </note>
-        <p>
-            Always ensure that the host OS has enough RAM remaining. If
-            insufficient RAM remains, the system might excessively swap
-            memory to the hard disk, which effectively brings the host
-            system to a standstill.
-          </p>
-        <p>
-            As with other <b outputclass="bold">Create Virtual
-            Machine</b> wizard settings, you can change this
-            setting later, after you have created the VM.
-          </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Processor(s).</b> Select the
-            number of virtual processors to assign to the VM.
-          </p>
-        <p>
-            It is not advised to assign more than half of the total
-            processor threads from the host machine.
-          </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Enable EFI.</b> Enables
-            Extensible Firware Interface (EFI) booting for the guest OS.
-          </p>
-      </li>
-    </ul>
-    <p>
-        Click <b outputclass="bold">Next</b> to go to the next
-        wizard page.
-      </p>
+    <ol id="ol_ndb_dbx_4bc">
+      <li>For <b outputclass="bold">Base Memory</b>, select the amount of RAM that <ph
+          conkeyref="vbox-conkeyref-phrases/product-name"/> should allocate to the virtual machine
+        (VM) every time it is started. The guest OS will report this size as the VM's installed RAM.
+          <note type="caution" id="note_pjs_x1x_4bc">
+          <p>Choose this setting carefully. The memory you give to the VM will not be available to
+            your host OS while the VM is running.  </p>
+        </note><p>Do not specify more than you can spare, whilst ensuring you allocate enough for
+          your guest OS and applications to run properly. For example, if your host machine has 4 GB
+          of RAM and you enter 2048 MB as the base memory for a VM, you will have 2 GB left for all
+          the other software on your host while that VM is running. </p><p>A guest OS may require at
+          least 1 or 2 GB of memory to install and boot up. If you intend to run more than one VM at
+          a time, plan accordingly. A VM will not start if it does not have enough RAM to
+          boot.</p><p>Always ensure that the host OS has enough RAM remaining. If insufficient RAM
+          remains, the system might excessively swap memory to the hard disk, which will effectively
+          bring the host system to a standstill. </p></li>
+      <li>For <b>Processor(s)</b>, select the number of virtual processors to assign to the VM. Do
+        not assign more than half of the total processor threads from the host machine. </li>
+      <li>Select <b outputclass="bold">Enable EFI</b> if you want to enable Extensible Firmware
+        Interface (EFI) booting for the guest OS.</li>
+      <li>Click <b outputclass="bold">Next</b> to <xref
+          href="create-vm-wizard-virtual-hard-disk.dita"/>. </li>
+    </ol>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/create-vm-wizard-name-os.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/create-vm-wizard-name-os.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/create-vm-wizard-name-os.dita	(revision 105134)
@@ -2,110 +2,45 @@
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
 <topic xml:lang="en-us" id="create-vm-wizard-name-os">
-  <title>Create Virtual Machine Wizard: Name and Operating System</title>
-  
+  <title>Specify Name and Operating System</title>
+ <!--7.1: Subtype field added --> 
   <body>
-    <fig id="fig-create-vm-name">
-      <title>Creating a Virtual Machine: Name and Operating System</title>
-      <xref href="images/create-vm-1.png" format="png" platform="htmlhelp">
-        <image href="images/create-vm-1.png" width="10cm" placement="break">
-          <alt>Creating a Virtual Machine: Name and Operating System</alt>
-        </image>
-      </xref>
-      <image platform="ohc" href="images/create-vm-1.png" width="10cm" placement="break">
-        <alt>Creating a Virtual Machine: Name and Operating System</alt>
-      </image>
-    </fig>
     <p>
-        Use this page to specify a name and operating system (OS) for
-        the virtual machine and to change the storage location used for
-        VMs.
-      </p>
-    <p>
-        You can also choose to disable the unattended guest operating
-        system install feature. See also
-        <xref href="create-vm-wizard-unattended-install.dita#create-vm-wizard-unattended-install"/>.
-      </p>
-    <p>
-        The following fields are available on this wizard page:
-      </p>
-    <ul>
-      <li>
-        <p><b outputclass="bold">Name.</b> A name for the new
-            VM. The name you enter is shown in the machine list of
-            <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> and is also used for the virtual machine's files
-            on disk.
-          </p>
-        <p>
-            Be sure to assign each VM an informative name that describes
-            the OS and software running on the VM. For example, a name
-            such as <codeph>Windows 10 with Visio</codeph>.
-          </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Folder.</b> The location where
-            VMs are stored on your computer, called the
-            <i>machine folder</i>. The default folder
-            location is shown.
-          </p>
-        <p>
-            Ensure that the folder location has enough free space,
-            especially if you intend to use the snapshots feature. See
-            also <xref href="vboxconfigdata-machine-folder.dita">The Machine Folder</xref>.
-          </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">ISO Image.</b> Select an ISO
-            image file. The image file can be used to install an OS on
-            the new virtual machine or it can be attached to a DVD drive
-            on the new virtual machine.
-          </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Type and Version.</b> These
-            fields are used to select the OS that you want to install on
-            the new virtual machine.
-          </p>
-        <p>
-            The supported OSes are grouped into types. If you want to
-            install something very unusual that is not listed, select
-            the <b outputclass="bold">Other</b> type. Depending
-            on your selection, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will enable or disable
-            certain VM settings that your guest OS may require. This is
-            particularly important for 64-bit guests. See
-            <xref href="intro-64bitguests.dita#intro-64bitguests"/>. It is therefore
-            recommended to always set this field to the correct value.
-          </p>
-        <p>
-            If an ISO image is selected and <ph conkeyref="vbox-conkeyref-phrases/product-name"/> detects the
-            operating system for the ISO, the
-            <b outputclass="bold">Type</b> and
-            <b outputclass="bold">Version</b> fields are
-            populated automatically and are disabled.
-          </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Skip Unattended
-            Installation.</b> Disables unattended guest OS
-            installation, even if an ISO image is selected that supports
-            unattended installation. In that case, the selected ISO
-            image is mounted automatically on the DVD drive of the new
-            virtual machine and user interaction is required to complete
-            the OS installation.
-          </p>
-        <p>
-            The unattended installation step in the wizard is skipped.
-          </p>
-        <note>
-          <p>
-              This option is disabled if you do not select an
-              installation medium in the <b outputclass="bold">ISO
-              Image</b> field.
-            </p>
-        </note>
-      </li>
-    </ul>
-    <p>
-        Click <b outputclass="bold">Next</b> to go to the next
-        wizard page.
+      <ol id="ol_s3f_d13_4bc">
+        <li>Give the virtual machine (VM) a name. The name you enter is shown in the machine list in
+            <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> and is also used for the virtual
+          machine's files on disk. Be sure to assign each VM an informative name that describes the
+          OS and software running on the VM. For example, <codeph>Windows 10 with
+          Visio</codeph>.</li>
+        <li>Select the location where VMs are stored on your computer, called the machine folder.
+          Ensure that the folder location has enough free space, especially if you intend to use the
+          snapshots feature. See also <xref href="vboxconfigdata-machine-folder.dita">The Machine
+            Folder</xref>.</li>
+        <li>Select the ISO image file for the operating system you intend to install on the new VM.
+          The image file can be used directly to install an OS on the new VM as part of an
+          unattended installation, or it can be attached to a DVD drive on the new VM.</li>
+        <li><ph conkeyref="vbox-conkeyref-phrases/product-name"/> will populate the <b>Type</b>,
+            <b>Subtype</b>, and <b>Version</b> fields if it can detect the operating system in the
+          ISO. If it cannot detect the OS, then set these according to your OS. For example, if the
+            <b>Type</b> is Linux, the <b>Subtype</b> might be Oracle Linux and the <b>Version</b>
+          might be Oracle Linux 8.x (64-bit). <p>The supported OSs are grouped into types. If you
+            want to install something very unusual that is not listed, select the <b>Other</b> type.
+            Depending on your selection, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will
+            enable or disable certain VM settings that your guest OS may require. This is
+            particularly important for 64-bit guests (see <xref
+              href="intro-64bitguests.dita#intro-64bitguests"/>) but you must always set this field
+            to the correct value.</p></li>
+        <li>By default, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will install the
+          chosen OS using the ISO image provided, if the image supports unattended installation. See
+          also <xref
+            href="create-vm-wizard-unattended-install.dita#create-vm-wizard-unattended-install"
+            />.<p>If you prefer to install the OS, you can disable the unattended guest operating
+            system install feature by selecting <b outputclass="bold">Skip Unattended
+              Installation</b>. In that case, the selected ISO image is mounted automatically on the
+            DVD drive of the new VM and you must install the OS from there.</p><p>Not all images
+            support unattended installation.</p></li>
+        <li>Click Next to <xref
+            href="create-vm-wizard-unattended-install.dita#create-vm-wizard-unattended-install"/>
+          (if using) or to <xref href="create-vm-wizard-hardware.dita"/>.</li>
+      </ol>
       </p>
   </body>
Index: trunk/doc/manual/en_US/dita/topics/create-vm-wizard-summary.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/create-vm-wizard-summary.dita	(revision 105087)
+++ 	(revision )
@@ -1,24 +1,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="create-vm-wizard-summary">
-  <title>Create Virtual Machine Wizard: Summary</title>
-  
-  <body>
-    <p>
-        This page displays a summary of the configuration for the
-        virtual machine.
-      </p>
-    <p>
-        If you are not happy with any of the settings, use the
-        <b outputclass="bold">Back</b> button to return to the
-        corresponding page and modify the setting.
-      </p>
-    <p>
-        Click <b outputclass="bold">Finish</b> to create your new
-        virtual machine. The virtual machine is displayed in the machine
-        list on the left side of the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window, with the name
-        that you entered on the first page of the wizard.
-      </p>
-  </body>
-  
-</topic>
Index: trunk/doc/manual/en_US/dita/topics/create-vm-wizard-unattended-examples.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/create-vm-wizard-unattended-examples.dita	(revision 105087)
+++ 	(revision )
@@ -1,76 +1,0 @@
-<?xml version='1.0' encoding='UTF-8'?>
-<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="create-vm-wizard-unattended-examples">
-  <title>Some Examples of Unattended Installation</title>
-  
-  <body>
-    <p>
-        To configure unattended installation, you typically just need to
-        specify an ISO image in the <b outputclass="bold">Create Virtual
-        Machine</b> wizard. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> then detects the OS
-        type and the unattended installation process is done
-        automatically when the wizard is completed. However, in some
-        situations the installation may need be completed manually.
-      </p>
-    <p>
-        The following list describes some common scenarios for
-        unattended installation:
-      </p>
-    <ul>
-      <li>
-        <p><b outputclass="bold">OS type is detected
-            automatically.</b> The following outcomes are
-            possible:
-          </p>
-        <ul>
-          <li>
-            <p>
-                If unattended installation is supported for the selected
-                ISO, the guest OS is installed automatically. No user
-                input is required.
-              </p>
-          </li>
-          <li>
-            <p>
-                If unattended installation is not supported for the
-                selected ISO, the ISO image is inserted automatically
-                into the DVD drive of the new VM. The guest OS
-                installation must then be completed manually.
-              </p>
-          </li>
-        </ul>
-      </li>
-      <li>
-        <p><b outputclass="bold">OS type is not detected
-            automatically.</b> You must configure
-            <b outputclass="bold">Type</b> and
-            <b outputclass="bold">Version</b> settings in the
-            wizard.
-          </p>
-        <p>
-            The ISO image is inserted automatically into the DVD drive
-            of the new VM. The guest OS installation must then be
-            completed manually.
-          </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Unattended Installation is
-            disabled.</b> Users can disable unattended
-            installation, by selecting the <b outputclass="bold">Skip
-            Unattended Installation</b> check box on the initial
-            wizard page.
-          </p>
-        <p>
-            The ISO image is inserted automatically into the DVD drive
-            of the new VM. The guest OS installation must then be
-            completed manually.
-          </p>
-      </li>
-    </ul>
-    <p>
-        See also <xref href="basic-unattended.dita#basic-unattended"/> for details of how
-        to perform unattended installation from the command line.
-      </p>
-  </body>
-  
-</topic>
Index: trunk/doc/manual/en_US/dita/topics/create-vm-wizard-unattended-install.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/create-vm-wizard-unattended-install.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/create-vm-wizard-unattended-install.dita	(revision 105134)
@@ -2,88 +2,38 @@
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
 <topic xml:lang="en-us" id="create-vm-wizard-unattended-install">
-  <title>(Optional) Create Virtual Machine Wizard: Unattended Guest OS Install</title>
+  <title>Configure Unattended Guest OS Install</title>
   
   <body>
-    <p>
-        Unattended guest OS installation enables you to install the OS
-        on a virtual machine automatically.
-      </p>
+    <p>If you choose Unattended guest OS Installation, <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> installs the OS on the new virtual machine
+      (VM) automatically. You must supply certain configuration options to be used in the
+      installation. </p>
+    <p>See also <xref href="unattended-guest-install-example.dita#unattended-guest-install-example"
+      /> for details of how to configure unattended installation from the command line. </p>
     <note>
-      <p>
-          This page is optional. It is not displayed if you have
-          selected the <b outputclass="bold">Skip Unattended
-          Installation</b> option on the initial wizard page.
-        </p>
-    </note>
-    <p>
-        Use this page to set up the required parameters for unattended
-        guest OS installation and to configure automatic installation of
-        the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest Additions. See also
-        <xref href="create-vm-wizard-unattended-examples.dita#create-vm-wizard-unattended-examples"/> for some
-        typical scenarios when using automated installation.
-      </p>
-    <fig id="fig-create-vm-unattended-install">
-      <title>Creating a Virtual Machine: Unattended Guest OS Installation</title>
-      <xref href="images/create-vm-2.png" format="png" platform="htmlhelp">
-        <image href="images/create-vm-2.png" width="10cm" placement="break">
-          <alt>Creating a Virtual Machine: Unattended Guest OS Installation</alt>
-        </image>
-      </xref>
-      <image platform="ohc" href="images/create-vm-2.png" width="10cm" placement="break">
-        <alt>Creating a Virtual Machine: Unattended Guest OS Installation</alt>
-      </image>
-    </fig>
-    <p>
-        The following fields are available on this wizard page:
-      </p>
-    <ul>
-      <li>
-        <p><b outputclass="bold">Username and Password.</b>
-            Enter the credentials for a default user on the guest OS.
-          </p>
+      <p>You will not see these options if you selected the <b outputclass="bold">Skip Unattended
+        Installation</b> option. </p></note><ol id="ol_ox5_xtw_4bc">
+          <li>Enter the <b outputclass="bold">Username and Password</b> for a default user on the
+            guest OS. </li>
+          <li>
+            <p>For Windows guests, enter the <b outputclass="bold">Product Key.</b> supplied with
+              Windows. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Guest Additions.</b> Enables
-            automatic installation of the Guest Additions, following
-            installation of the guest OS. Use the drop-down list to
-            select the location of the ISO image file for the Guest
-            Additions.
-          </p>
+            <p>Enter the <b outputclass="bold">Hostname</b> for the VM. By default, this is the same
+              as the VM name.</p>
       </li>
       <li>
-        <p><b outputclass="bold">Additional Options.</b> The
-            following options enable you to perform extra configuration
-            of the guest OS:
-          </p>
-        <ul>
-          <li>
-            <p><b outputclass="bold">Product Key.</b> For
-                Windows guests only. Enter the product key required for
-                Windows installation.
-              </p>
+            <p>Enter the <b outputclass="bold">Domain Name</b> for the VM. </p>
           </li>
-          <li>
-            <p><b outputclass="bold">Hostname.</b> Host name for
-                the guest. By default, this is the same as the VM name.
-              </p>
+          <li>Select <b outputclass="bold">Install in Background</b> if you want to enable headless
+            mode for the VM rather than using a graphical user interface. </li>
+          <li>Select <b outputclass="bold">Guest Additions</b> if you would like <ph
+              conkeyref="vbox-conkeyref-phrases/product-name"/> to install the Guest Additions after
+            the OS. Download the Guest Additions installation ISO to the host, and select the file
+            location.</li>
+          <li>Click <b outputclass="bold">Next</b> to <xref href="create-vm-wizard-hardware.dita"/>.
           </li>
-          <li>
-            <p><b outputclass="bold">Domain Name.</b> Domain
-                name for the guest.
-              </p>
-          </li>
-          <li>
-            <p><b outputclass="bold">Install in Background.</b>
-                Enable headless mode for the VM, where a graphical user
-                interface is not shown.
-              </p>
-          </li>
-        </ul>
-      </li>
-    </ul>
-    <p>
-        Click <b outputclass="bold">Next</b> to go to the next
-        wizard page.
-      </p>
+        </ol>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/create-vm-wizard-virtual-hard-disk.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/create-vm-wizard-virtual-hard-disk.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/create-vm-wizard-virtual-hard-disk.dita	(revision 105134)
@@ -2,137 +2,91 @@
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
 <topic xml:lang="en-us" id="create-vm-wizard-virtual-hard-disk">
-  <title>Create Virtual Machine Wizard: Virtual Hard Disk</title>
+  <title>Specify a Virtual Hard Disk</title>
   
   <body>
+    <p>There are many ways in which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can
+      provide hard disk space to a VM, see <xref href="storage.dita#storage"/>. </p>
+    <p>The most common way is to use a virtual hard disk. This is a large image file on your
+      physical hard disk, whose contents <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
+      presents to your VM as if it were a complete hard disk. You can copy this file to another
+      host, and use it with another <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM. </p>
+    <p>To prevent your physical hard disk on the host OS from filling up, <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> limits the size of the image file. But the
+      image file must be large enough to hold the contents of the guest OS and the applications you
+      want to install. For a Windows or Linux guest, you will probably need several gigabytes for
+      any serious use. The size limit of the image file can be changed later, see <xref
+        href="vboxmanage-modifymedium.dita"/>. </p>
     <p>
-        Use this page to specify a virtual hard disk for the virtual
-        machine.
-      </p>
-    <p>
-        There are many ways in which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can provide hard
-        disk space to a VM, see <xref href="storage.dita#storage"/>. The most
-        common way is to use a large image file on your physical hard
-        disk, whose contents <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to your VM as if it
-        were a complete hard disk. This file then represents an entire
-        hard disk, so you can even copy it to another host and use it
-        with another <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installation.
-      </p>
-    <fig id="fig-create-vm-hard-disk">
-      <title>Creating a New Virtual Machine: Virtual Hard Disk</title>
-      <xref href="images/create-vm-4.png" format="png" platform="htmlhelp">
-        <image href="images/create-vm-4.png" width="10cm" placement="break">
-          <alt>Creating a New Virtual Machine: Virtual Hard Disk</alt>
-        </image>
-      </xref>
-      <image platform="ohc" href="images/create-vm-4.png" width="10cm" placement="break">
-        <alt>Creating a New Virtual Machine: Virtual Hard Disk</alt>
-      </image>
-    </fig>
-    <p>
-        The following fields are available on this wizard page:
-      </p>
-    <ul>
-      <li>
-        <p><b outputclass="bold">Create a Virtual Hard Disk
-            Now</b>. Creates a new empty virtual hard disk image,
-            located in the VM's machine folder.
+      <note id="note_vc4_gjs_pbc">
+        <p>If you choose <b outputclass="bold">Do Not Add a Virtual Hard Disk</b> at this stage you
+          will need to attach a hard disk using VirtualBox Manager or VBoxManage commands before you
+          can install a guest operating system. </p>
+      </note>
+    </p>
+    <section id="section_wql_21r_pbc">
+      <title>Create a Virtual Hard Disk</title>
+    </section>
+    <p>Follow these steps to create a virtual hard disk to use with this VM. To prevent your
+      physical hard disk on the host OS from filling up, <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> limits the size of the image file. But the
+      image file must be large enough to hold the contents of the guest OS and the applications you
+      want to install. For a Windows or Linux guest, you will probably need several gigabytes for
+      any serious use. The limit of the image file size can be changed later, see <xref
+        href="vboxmanage-modifymedium.dita"/>. <ol id="ol_z2h_q5q_pbc">
+        <li>
+          <p>Select <b outputclass="bold">Create a Virtual Hard Disk Now</b>. This creates a new
+            empty virtual hard disk image, located in the VM's machine folder. </p>
+        </li>
+        <li>
+          <p> Enter the following settings: </p>
+          <ul id="ul_i3n_y1r_pbc">
+            <li>
+              <p><b outputclass="bold">Disk Size</b>. Use the slider to select a maximum size for
+                the hard disk in the new VM. </p>
+            </li>
+            <li>
+              <p><b outputclass="bold">Pre-Allocate Full Size.</b> This setting determines the type
+                of image file used for the disk image. Select this setting to use a <i>fixed-size
+                  file</i> for the disk image. Otherwise, <ph
+                  conkeyref="vbox-conkeyref-phrases/product-name"/> will use a <i>dynamically
+                  allocated file</i> for the disk image. </p>
+              <p>The different types of image file behave as follows: </p>
+              <ul id="ul_j3n_y1r_pbc">
+                <li>
+                  <p><b outputclass="bold">Dynamically allocated file.</b> This type of image file
+                    only grows in size when the guest actually stores data on its virtual hard disk.
+                    Therefore, this file is small initially. As the drive is filled with data, the
+                    file grows to the specified size. </p>
+                </li>
+                <li>
+                  <p><b outputclass="bold">Fixed-size file.</b> This type of image file immediately
+                    occupies the file specified, even if only a fraction of that virtual hard disk
+                    space is actually in use. While occupying much more space, a fixed-size file
+                    incurs less overhead and is therefore slightly faster than a dynamically
+                    allocated file. </p>
+                </li>
+              </ul>
+              <p> For more details about the differences, see <xref
+                  href="vdidetails.dita#vdidetails"/>. </p>
+            </li>
+          </ul>
+        </li>
+      </ol></p>
+    <section id="section_bdq_h1r_pbc">
+      <title>Use an Existing Virtual Hard Disk</title>
+    </section>
+    <p>Follow these steps to use a virtual hard disk that already exists on the host. Ensure the
+      image file is in a suitable location (usually the machine folder) and not in use by other
+        VMs.<ol id="ol_txk_str_pbc">
+        <li>
+          <p>Select <b outputclass="bold">Use an Existing Virtual Hard Disk File</b>
           </p>
-        <p>
-            Enter the following settings:
-          </p>
-        <ul>
-          <li>
-            <p><b outputclass="bold">Disk Size</b>. Use the
-                slider to select a maximum size for the hard disk in the
-                new VM.
-              </p>
-          </li>
-          <li>
-            <p><b outputclass="bold">Pre-Allocate Full Size.</b>
-                This setting determines the type of image file used for
-                the disk image. Select this setting to use a
-                <i>fixed-size file</i> for the disk image.
-                Deselect this setting to use a <i>dynamically
-                allocated file</i> for the disk image.
-              </p>
-            <p>
-                The different types of image file behave as follows:
-              </p>
-            <ul>
-              <li>
-                <p><b outputclass="bold">Dynamically allocated
-                    file.</b> This type of image file only grows
-                    in size when the guest actually stores data on its
-                    virtual hard disk. Therefore, this file is small
-                    initially. As the drive is filled with data, the
-                    file grows to the specified size.
-                  </p>
-              </li>
-              <li>
-                <p><b outputclass="bold">Fixed-size file.</b>
-                    This type of image file immediately occupies the
-                    file specified, even if only a fraction of that
-                    virtual hard disk space is actually in use. While
-                    occupying much more space, a fixed-size file incurs
-                    less overhead and is therefore slightly faster than
-                    a dynamically allocated file.
-                  </p>
-              </li>
-            </ul>
-            <p>
-                For more details about the differences, see
-                <xref href="vdidetails.dita#vdidetails"/>.
-              </p>
-          </li>
-        </ul>
-      </li>
-      <li>
-        <p><b outputclass="bold">Use an Existing Hard Disk
-            File.</b> Enables you to select an
-            <i>existing</i> disk image file to use with
-            the new VM.
-          </p>
-        <p>
-            The drop-down list presented in the window lists all disk
-            images which are known by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. These disk images
-            are currently attached to a virtual machine, or have been
-            attached to a virtual machine.
-          </p>
-        <p>
-            Alternatively, click on the small folder icon next to the
-            drop-down list. In the <b outputclass="bold">Hard Disk
-            Selector</b> window that is displayed, click
-            <b outputclass="bold">Add</b> to select a disk image
-            file on your host disk.
-          </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Do Not Add a Virtual Hard
-            Disk.</b> The new VM is created without a hard disk.
-          </p>
-      </li>
-    </ul>
-    <p>
-        To prevent your physical hard disk on the host OS from filling
-        up, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> limits the size of the image file. But the
-        image file must be large enough to hold the contents of the
-        guest OS and the applications you want to install. For a Windows
-        or Linux guest, you will probably need several gigabytes for any
-        serious use. The limit of the image file size can be changed
-        later, see <xref href="vboxmanage-modifymedium.dita"/>.
-      </p>
-    <note>
-      <p>
-          You can skip attaching a virtual hard disk file to the new
-          virtual machine you are creating. But you will then need to
-          attach an hard disk later on, in order to install a guest
-          operating system.
-        </p>
-    </note>
-    <p>
-        After having selected or created your image file, click
-        <b outputclass="bold">Next</b> to go to the next wizard
-        page.
-      </p>
+        </li>
+        <li>
+          <p>Select the image file to use with the new VM, and then click <b outputclass="bold"
+              >Add</b>. </p>
+        </li>
+      </ol></p>
+    <p> </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/create-vm-wizard.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/create-vm-wizard.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/create-vm-wizard.dita	(revision 105134)
@@ -5,14 +5,35 @@
   
   <body>
-    <p>
-      Click <b outputclass="bold">New</b> in the VirtualBox
-      Manager window. The <b outputclass="bold">Create Virtual
-      Machine</b> wizard is shown, to guide you through the
-      required steps for setting up a new virtual machine (VM).
-    </p>
-    <p>
-      The <b outputclass="bold">Create Virtual Machine</b> wizard
-      pages are described in the following sections.
-    </p>
+    <p>In the VirtualBox Manager window, click <b outputclass="bold">New</b>. The <b
+        outputclass="bold">Create Virtual Machine</b> wizard is shown, to guide you through the
+      required steps for setting up a new virtual machine (VM). </p>
+    <p>The steps are:<ul id="ul_yt4_cjt_pbc">
+        <li><xref href="create-vm-wizard-name-os.dita"/></li>
+        <li><xref href="create-vm-wizard-unattended-install.dita"/></li>
+        <li><xref href="create-vm-wizard-hardware.dita"/></li>
+        <li><xref href="create-vm-wizard-virtual-hard-disk.dita"/></li>
+      </ul></p>
+    <p>Once created, the virtual machine is displayed in the machine list on the left side of the
+        <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window, with the name that you entered on
+      the first page of the wizard.</p>
+    <p>You can change the settings later, after you have created the VM, using the Machine
+      Settings.</p>
+    <p>Before you start you must have an operating system image, in ISO format, for the operating
+      system you intend to install on the VM. <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
+      does not supply the OS or any license required to use it. </p>
+    <p><!--7.1: Note added re platforms and paragraph re ISO requirement. Reworded when removing screenshots. Subpages also updated.--></p>
+      <note>
+      <p>The settings on the wizard pages may vary depending on the architecture of the host
+        platform, as follows:</p>
+      <ul>
+        <li>
+          <p><b>x86 host platforms.</b> This includes Windows, macOS, and Linux platforms.</p>
+        </li>
+        <li>
+          <p><b>Arm host platforms.</b> This includes Apple silicon hosts and some Linux OSes.</p>
+        </li>
+      </ul>
+    </note>
+    <p> </p>
   </body>
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/diffimages.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/diffimages.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/diffimages.dita	(revision 105134)
@@ -64,13 +64,9 @@
       </image>
     </fig>
-    <p>
-      In all of these situations, from the point of view of the virtual
-      machine, the virtual hard disk behaves like any other disk. While
-      the virtual machine is running, there is a slight run-time I/O
-      overhead because <ph conkeyref="vbox-conkeyref-phrases/product-name"/> might need to look up sectors
-      several times. This is not noticeable however since the tables
-      with sector information are always kept in memory and can be
-      looked up quickly.
-    </p>
+    <p> In all of these situations, from the point of view of the virtual machine, the virtual hard
+      disk behaves like any other disk. While the virtual machine is running, there is a slight
+      runtime I/O overhead because <ph conkeyref="vbox-conkeyref-phrases/product-name"/> might need
+      to look up sectors several times. This is not noticeable however since the tables with sector
+      information are always kept in memory and can be looked up quickly. </p>
     <p>
       Differencing images are used in the following situations:
Index: trunk/doc/manual/en_US/dita/topics/diskencryption.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/diskencryption.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/diskencryption.dita	(revision 105134)
@@ -19,11 +19,8 @@
       encrypted.
     </p>
-    <p>
-      Since the DEK is stored as part of the VM configuration file, it
-      is important that it is kept safe. Losing the DEK means that the
-      data stored in the disk images is lost irrecoverably. Having
-      complete and up to date backups of all data related to the VM is
-      the responsibility of the user.
-    </p>
+    <p> Since the DEK is stored as part of the VM configuration file, it is important that it is
+      kept safe. Losing the DEK means that the data stored in the disk images is lost irrecoverably.
+      Having complete and up-to-date backups of all data related to the VM is the responsibility of
+      the user. </p>
   </body>
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/emul-hardware.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/emul-hardware.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/emul-hardware.dita	(revision 105134)
@@ -5,9 +5,7 @@
   
   <body>
-    <p>
-      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtualizes nearly all hardware of the host.
-      Depending on a VM's configuration, the guest will see the
-      following virtual hardware:
-    </p>
+    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtualizes nearly all of the host's
+      hardware. Depending on a VM's configuration, the guest will see the following virtual
+      hardware: </p>
     <ul>
       <li>
@@ -52,23 +50,10 @@
       </li>
       <li>
-        <p><b outputclass="bold">USB.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> emulates
-          these types of USB host controllers: xHCI, EHCI, and OHCI.
-          While xHCI handles all USB transfer speeds, some legacy guest
-          OSes may not support xHCI. Note that for some legacy Windows
-          guests, third party drivers must be installed for xHCI
-          support.
-        </p>
-        <p>
-          Legacy guest OSes typically support OHCI and EHCI. These two
-          controllers are needed because OHCI only handles USB low-speed
-          and full-speed devices (both USB 1.x and 2.0), while EHCI only
-          handles high-speed devices (USB 2.0 only).
-        </p>
-        <p>
-          The emulated USB controllers do not communicate directly with
-          devices on the host. Instead they communicate with a virtual
-          USB layer which abstracts the USB protocol and enables the use
-          of remote USB devices.
-        </p>
+        <p><b outputclass="bold">USB.</b>
+          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> emulates the most common USB host
+          controllers. See <xref href="usb-support.dita"/>.</p>
+        <p>The emulated USB controllers do not communicate directly with devices on the host.
+          Instead they communicate with a virtual USB layer that abstracts the USB protocol and
+          enables the use of remote USB devices. </p>
       </li>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/features-overview.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/features-overview.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/features-overview.dita	(revision 105134)
@@ -90,15 +90,12 @@
           <li>
             <p><b outputclass="bold">Hardware compatibility.</b>
-              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtualizes a vast array of virtual
-              devices, among them many devices that are typically
-              provided by other virtualization platforms. That includes
-              IDE, SCSI, and SATA hard disk controllers, several virtual
-              network cards and sound cards, virtual serial and parallel
-              ports and an Input/Output Advanced Programmable Interrupt
-              Controller (I/O APIC), which is found in many computer
-              systems. This enables easy cloning of disk images from
-              real machines and importing of third-party virtual
-              machines into <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
-            </p>
+              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtualizes a vast array of
+              virtual devices, among them many devices that are typically provided by other
+              virtualization platforms. That includes IDE, SCSI, and SATA hard disk controllers,
+              several virtual network cards and sound cards, virtual serial ports and an
+              Input/Output Advanced Programmable Interrupt Controller (I/O APIC), which is found in
+              many computer systems. This enables easy cloning of disk images from real machines and
+              importing of third-party virtual machines into <ph
+                conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
           </li>
           <li>
Index: trunk/doc/manual/en_US/dita/topics/flush-level1-data-cache-mitigation.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/flush-level1-data-cache-mitigation.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/flush-level1-data-cache-mitigation.dita	(revision 105134)
@@ -14,12 +14,8 @@
           usually not without performance side effects.
         </p>
-    <p>
-          Up to date CPU microcode is a prerequisite for the cache
-          flushing mitigations. Some host OSes may install these
-          automatically, though it has traditionally been a task best
-          performed by the system firmware. So, please check with your
-          system / mainboard manufacturer for the latest firmware
-          update.
-        </p>
+    <p> Up-to-date CPU microcode is a prerequisite for the cache flushing mitigations. Some host
+      OSes may install these automatically, though it has traditionally been a task best performed
+      by the system firmware. So, please check with your system / mainboard manufacturer for the
+      latest firmware update. </p>
     <p>
           We recommend disabling hyper threading on the host. This is
@@ -37,14 +33,10 @@
           similar without taking precautions.
         </p>
-    <p>
-          A more aggressive flushing option is provided via the
-          <userinput>VBoxManage modifyvm</userinput>
-           <codeph>--l1d-flush-on-vm-entry</codeph> option. When enabled
-          the level 1 data cache will be flushed on every VM entry. The
-          performance impact is greater than with the default option,
-          though this of course depends on the workload. Workloads
-          producing a lot of VM exits (like networking, VGA access, and
-          similiar) will probably be most impacted.
-        </p>
+    <p> A more aggressive flushing option is provided using the <userinput>VBoxManage
+        modifyvm</userinput>
+      <codeph>--l1d-flush-on-vm-entry</codeph> option. When enabled the level 1 data cache will be
+      flushed on every VM entry. The performance impact is greater than with the default option,
+      though this of course depends on the workload. Workloads producing a lot of VM exits (like
+      networking, VGA access, and similiar) will probably be most impacted. </p>
     <p>
           For users not concerned by this security issue, the default
Index: trunk/doc/manual/en_US/dita/topics/frontends.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/frontends.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/frontends.dita	(revision 105134)
@@ -2,6 +2,5 @@
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
 <topic xml:lang="en-us" id="frontends">
-  <title>Alternative Front-Ends</title>
-  
+  <title>Alternative Front Ends</title>
   <body>
     <p>
@@ -15,16 +14,13 @@
       and have all the graphical output redirected over the network.
     </p>
-    <p>
-      The following front-ends are shipped in the standard
-      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> package:
-    </p>
+    <p> The following front ends are shipped in the standard <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> package: </p>
     <ul>
       <li>
-        <p><b outputclass="bold">VirtualBox.</b> This is the
-          <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, a graphical user interface that uses the Qt
-          toolkit. This interface is described throughout this manual.
-          While this is the simplest and easiest front-end to use, some
-          of the more advanced <ph conkeyref="vbox-conkeyref-phrases/product-name"/> features are not included.
-        </p>
+        <p><b outputclass="bold">VirtualBox.</b> This is the <ph
+            conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, a graphical user interface that uses the
+          Qt toolkit. This interface is described throughout this manual. While this is the simplest
+          and easiest front end to use, some of the more advanced <ph
+            conkeyref="vbox-conkeyref-phrases/product-name"/> features are not included. </p>
       </li>
       <li>
@@ -36,23 +32,24 @@
       </li>
       <li>
-        <p><b outputclass="bold">VBoxHeadless.</b> A front-end
-          that produces no visible output on the host at all, but can
-          act as a RDP server if the VirtualBox Remote Desktop Extension
-          (VRDE) is installed and enabled for the VM. As opposed to the
-          other graphical interfaces, the headless front-end requires no
-          graphics support. This is useful, for example, if you want to
-          host your virtual machines on a headless Linux server that has
-          no X Window system installed. See
-          <xref href="vboxheadless.dita">VBoxHeadless, the Remote Desktop Server</xref>.
-        </p>
+        <p><b outputclass="bold">VBoxHeadless.</b> A front end that produces no visible output on
+          the host at all, but can act as a RDP server if the VirtualBox Remote Desktop Extension
+          (VRDE) is installed and enabled for the VM. As opposed to the other graphical interfaces,
+          the headless front end requires no graphics support. This is useful, for example, if you
+          want to host your virtual machines on a headless Linux server that has no X Window system
+          installed. See <xref href="vboxheadless.dita">VBoxHeadless, the Remote Desktop
+            Server</xref>. </p>
+      </li>
+      <li>
+        <!-- Separate mode: check with Klaus whether this needs to be covered in 7.1-->
+        <p><b>Separate mode.</b> A front end that is based on <userinput>VBoxHeadless</userinput>, 
+          but does not require VRDE or an RDP viewer. See <xref href="vboxheadless-separate-mode.dita">Separate Mode</xref>.</p>
       </li>
     </ul>
-    <p>
-      If the above front-ends still do not satisfy your particular
-      needs, it is possible to create yet another front-end to the
-      complex virtualization engine that is the core of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>,
-      as the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> core neatly exposes all of its features in a
-      clean API. See <xref href="VirtualBoxAPI.dita"><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Programming Interfaces</xref>.
-    </p>
+    <p> If the above front ends still do not satisfy your particular needs, it is possible to create
+      yet another front end to the complex virtualization engine that is the core of <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/>, as the <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> core neatly exposes all of its features in
+      a clean API. See <xref href="VirtualBoxAPI.dita"><ph
+          conkeyref="vbox-conkeyref-phrases/product-name"/> Programming Interfaces</xref>. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/guestadd-clipboard.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/guestadd-clipboard.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/guestadd-clipboard.dita	(revision 105134)
@@ -5,4 +5,5 @@
   
   <body>
+    <!-- 7.1: Shared clipboard check box; clarify operation with dev -->
     <p>
       <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to copy clipboard content from the host
Index: trunk/doc/manual/en_US/dita/topics/guestadd-gc-file-manager.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/guestadd-gc-file-manager.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/guestadd-gc-file-manager.dita	(revision 105134)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="guestadd-gc-file-manager">
   <title>Guest Control File Manager</title>
-  
+  <!-- 7.1: new icons added, new pic needed -->
   <body>
     <p>
Index: trunk/doc/manual/en_US/dita/topics/guestadd-intro.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/guestadd-intro.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/guestadd-intro.dita	(revision 105134)
@@ -52,11 +52,9 @@
       </li>
       <li>
-        <p><b outputclass="bold">Better video support.</b> While
-          the virtual graphics card which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> emulates for
-          any guest operating system provides all the basic features,
-          the custom video drivers that are installed with the Guest
-          Additions provide you with extra high and non-standard video
-          modes, as well as accelerated video performance.
-        </p>
+        <p><b outputclass="bold">Better video support.</b> While the virtual graphics card which <ph
+            conkeyref="vbox-conkeyref-phrases/product-name"/> emulates for any guest operating
+          system provides all the basic features, the custom video drivers that are installed with
+          the Guest Additions provide you with extra high and nonstandard video modes, as well as
+          accelerated video performance. </p>
         <p>
           In addition, with Windows, Linux, and Oracle Solaris guests,
Index: trunk/doc/manual/en_US/dita/topics/guestossupport.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/guestossupport.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/guestossupport.dita	(revision 105134)
@@ -10,4 +10,5 @@
       operating systems (OSes) of any kind.
     </p>
+    <!-- 7.1: Require info on supported aarch64 guest OSes -->
     <p>
       The following guest OS platforms are supported:
@@ -25,6 +26,5 @@
           for limited support because of the vintage of the technology involved. Therefore,
           resolution of customer issues for such legacy guest OS platforms cannot be assured. See
-            <xref href="#guestossupport/table-limited-support"/>.
-        </p>
+            <xref href="#guestossupport/table-limited-support"/>. </p>
       </li>
     </ul>
Index: trunk/doc/manual/en_US/dita/topics/gui-details-settings.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/gui-details-settings.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/gui-details-settings.dita	(revision 105134)
@@ -8,4 +8,8 @@
           A summary of settings is shown for the virtual machine.
         </p>
+    <note>
+      <p>Settings shown may vary, depending on the selected experience level for the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> user interface.</p>
+      <p>See <xref href="ui-experience-level.dita#gui-experience-level"/>.</p>
+    </note>
     <p>
           You can change some virtual machine settings, by clicking on
Index: trunk/doc/manual/en_US/dita/topics/gui-tools-global.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/gui-tools-global.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/gui-tools-global.dita	(revision 105134)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="gui-tools-global">
   <title>Global Tools</title>
-  
+  <!-- 7.1: May be best to remove screen shots of menus. Too much of a maintenance headache. -->
   <body>
     <p>
@@ -12,15 +12,4 @@
           Tools</b> menu is displayed.
         </p>
-    <fig id="fig-global-tools-menu">
-      <title>Global Tools Menu</title>
-      <xref href="images/global-tools-menu.png" format="png" platform="htmlhelp">
-        <image href="images/global-tools-menu.png" width="10cm" placement="break">
-          <alt>Global Tools Menu</alt>
-        </image>
-      </xref>
-      <image platform="ohc" href="images/global-tools-menu.png" width="10cm" placement="break">
-        <alt>Global Tools Menu</alt>
-      </image>
-    </fig>
     <p>
           A drop-down list enables you to select from the following
@@ -82,4 +71,8 @@
           you scroll down the entries in the machine list.
         </p>
+    <note>
+      <p>The available tools may vary, depending on the selected experience level for the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> user interface.</p>
+      <p>See <xref href="ui-experience-level.dita#gui-experience-level"/>.</p>
+    </note>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/gui-tools-machine.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/gui-tools-machine.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/gui-tools-machine.dita	(revision 105134)
@@ -15,15 +15,4 @@
           displayed.
         </p>
-    <fig id="fig-machine-tools-menu">
-      <title>Machine Tools Menu</title>
-      <xref href="images/machine-tools-menu.png" format="png" platform="htmlhelp">
-        <image href="images/machine-tools-menu.png" width="10cm" placement="break">
-          <alt>Machine Tools Menu</alt>
-        </image>
-      </xref>
-      <image platform="ohc" href="images/machine-tools-menu.png" width="10cm" placement="break">
-        <alt>Machine Tools Menu</alt>
-      </image>
-    </fig>
     <p>
           A drop-down list enables you to select from the following
@@ -69,4 +58,8 @@
       </li>
     </ul>
+    <note>
+      <p>The available tools may vary, depending on the selected experience level for the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> user interface.</p>
+      <p>See <xref href="ui-experience-level.dita#gui-experience-level"/>.</p>
+    </note>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/gui-virtualboxmanager.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/gui-virtualboxmanager.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/gui-virtualboxmanager.dita	(revision 105134)
@@ -22,4 +22,5 @@
       virtual machines.
     </p>
+    <!-- 7.1: Welcome screen now includes Experience Level selection button: new pics required?-->
     <fig id="fig-vbox-manager-initial">
       <title><ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, Showing Welcome Screen After Initial Startup</title>
Index: trunk/doc/manual/en_US/dita/topics/harddiskcontrollers.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/harddiskcontrollers.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/harddiskcontrollers.dita	(revision 105134)
@@ -15,16 +15,12 @@
     <ul>
       <li>
-        <p><b outputclass="bold">IDE (ATA)</b> controllers are a
-          backwards-compatible yet very advanced extension of the disk
-          controller in the IBM PC/AT (1984). Initially, this interface
-          worked only with hard disks, but was later extended to also
-          support CD-ROM drives and other types of removable media. In
-          physical PCs, this standard uses flat ribbon parallel cables
-          with 40 or 80 wires. Each such cable can connect two devices,
-          called device 0 and device 1, to a controller. Typical PCs had
-          two connectors for such cables. As a result, support for up to
-          four IDE devices was most common: primary device 0, primary
-          device 1, secondary device 0, and secondary device 1.
-        </p>
+        <p><b outputclass="bold">IDE (ATA)</b> controllers are a backward-compatible yet very
+          advanced extension of the disk controller in the IBM PC/AT (1984). Initially, this
+          interface worked only with hard disks, but was later extended to also support CD-ROM
+          drives and other types of removable media. In physical PCs, this standard uses flat ribbon
+          parallel cables with 40 or 80 wires. Each such cable can connect two devices, called
+          device 0 and device 1, to a controller. Typical PCs had two connectors for such cables. As
+          a result, support for up to four IDE devices was most common: primary device 0, primary
+          device 1, secondary device 0, and secondary device 1. </p>
         <p>
           In <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, each virtual machine may have one IDE
Index: trunk/doc/manual/en_US/dita/topics/hdimagewrites.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/hdimagewrites.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/hdimagewrites.dita	(revision 105134)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="hdimagewrites">
   <title>Special Image Write Modes</title>
-
+  
   <body>
     <p>
@@ -13,11 +13,9 @@
       allocated.
     </p>
-    <p>
-      By default, images are in <i>normal</i> mode. To mark an existing image with one of the
-      non-standard modes listed below, use <userinput>VBoxManage modifymedium</userinput>. See
-      <xref href="vboxmanage-modifymedium.dita"/>. Alternatively, use <userinput>VBoxManage
-      storageattach</userinput> to attach the image to a VM and specify the
-      <codeph>--mtype</codeph> argument. See <xref href="vboxmanage-storageattach.dita"/>.
-    </p>
+    <p> By default, images are in <i>normal</i> mode. To mark an existing image with one of the
+      nonstandard modes listed below, use <userinput>VBoxManage modifymedium</userinput>. See <xref
+        href="vboxmanage-modifymedium.dita"/>. Alternatively, use <userinput>VBoxManage
+        storageattach</userinput> to attach the image to a VM and specify the
+        <codeph>--mtype</codeph> argument. See <xref href="vboxmanage-storageattach.dita"/>. </p>
     <p>
       The available virtual disk image modes are as follows:
@@ -72,5 +70,5 @@
           way, and dynamically allocated images are rejected.
         </p>
-        <note type="attention">
+        <note type="caution">
           <p>
             This is an expert feature, and misuse can lead to data loss,
@@ -190,4 +188,4 @@
     </p>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/headless-vm-steps.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/headless-vm-steps.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/headless-vm-steps.dita	(revision 105134)
@@ -68,8 +68,6 @@
       </li>
       <li>
-        <p>
-            Make sure the settings for the VM are appropriate for the
-            guest operating system that we will install. For example:
-          </p>
+        <p> Ensure the settings for the VM are appropriate for the guest operating system that we
+          will install. For example: </p>
         <pre xml:space="preserve">VBoxManage modifyvm "Windows XP" --memory 256 --acpi on --boot1 dvd --nic1 nat</pre>
       </li>
Index: trunk/doc/manual/en_US/dita/topics/hostossupport.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/hostossupport.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/hostossupport.dita	(revision 105134)
@@ -3,9 +3,8 @@
 <topic xml:lang="en-us" id="hostossupport">
   <title>Supported Host Operating Systems</title>
-  
+  <!-- 7.1: Arm platforms; require statement on host support -->
   <body>
-    <p>
-      Currently, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> runs on the following host OSes:
-    </p>
+    <p>Currently, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> runs on the following host
+      OSes: </p>
     <ul>
       <li>
@@ -15,43 +14,16 @@
         <ul>
           <li>
-            <p>
-              Windows 8.1
-            </p>
+            <p>Windows 10 </p>
           </li>
           <li>
-            <p>
-              Windows 10
-            </p>
+            <p>Windows 11 </p>
           </li>
           <li>
-            <p>
-              Windows 11 21H2
-            </p>
+            <p>Windows Server 2019 </p>
           </li>
           <li>
-            <p>
-              Windows Server 2012
-            </p>
+            <p>Windows Server 2022 </p>
           </li>
-          <li>
-            <p>
-              Windows Server 2012 R2
-            </p>
-          </li>
-          <li>
-            <p>
-              Windows Server 2016
-            </p>
-          </li>
-          <li>
-            <p>
-              Windows Server 2019
-            </p>
-          </li>
-          <li>
-            <p>
-              Windows Server 2022
-            </p>
-          </li>
+          <li>Windows Server 2025</li>
         </ul>
       </li>
@@ -62,35 +34,22 @@
         <ul>
           <li>
-            <p>
-              10.15 (Catalina)
-            </p>
+            <p>11 (Big Sur) </p>
           </li>
           <li>
-            <p>
-              11 (Big Sur)
-            </p>
+            <p>12 (Monterey) </p>
           </li>
           <li>
-            <p>
-              12 (Monterey)
-            </p>
+            <p>13 (Ventura) </p>
           </li>
+          <li>14 (Sonoma)</li>
         </ul>
-        <p>
-          Intel hardware is required. See also
-          <xref href="KnownIssues.dita">Known Limitations</xref>.
-        </p>
-        <p>
-          An installer package is available for macOS/Arm64, for systems
-          using an Apple silicon CPU. With this package, you can run
-          some guest operating systems for Intel x86/x64 CPUs in an
-          emulation.
-        </p>
-        <p>
-          The macOS/Arm64 installer package for Apple silicon platform
-          is available as a Developer Preview release. This package
-          represents a work in progress project and the performance is
-          very modest.
-        </p>
+        <p>Intel hardware is required. See also <xref href="KnownIssues.dita">Known
+            Limitations</xref>. </p>
+        <p>An installer package is available for macOS/Arm64, for systems using an Apple silicon
+          CPU. With this package, you can run some guest operating systems for Intel x86/x64 CPUs in
+          an emulation. </p>
+        <p>The macOS/Arm64 installer package for Apple silicon platform is available as a Developer
+          Preview release. This package represents a work in progress project and the performance is
+          very modest. </p>
         <note>
           <p>
@@ -107,52 +66,31 @@
         <ul>
           <li>
-            <p>
-              Ubuntu 18.04 LTS, 20.04 LTS and 22.04
-            </p>
+            <p>Ubuntu 20.04 LTS, 22.04 and 24.04</p>
           </li>
           <li>
-            <p>
-              Debian GNU/Linux 10 ("Buster") and 11 ("Bullseye")
-            </p>
+            <p>Debian GNU/Linux 11 (Bullseye) and 12 (Bookworm)</p>
           </li>
           <li>
-            <p>
-              Oracle Linux 7, 8 and 9
-            </p>
+            <p>Oracle Linux 7, 8 and 9 </p>
           </li>
           <li>
-            <p>
-              CentOS/Red Hat Enterprise Linux 7, 8 and 9
-            </p>
+            <p>CentOS/Red Hat Enterprise Linux 8 and 9 </p>
           </li>
           <li>
-            <p>
-              Fedora 35 and 36
-            </p>
+            <p>Fedora 39 and 40 </p>
           </li>
           <li>
-            <p>
-              Gentoo Linux
-            </p>
+            <p>SUSE Linux Enterprise server 15 </p>
           </li>
           <li>
-            <p>
-              SUSE Linux Enterprise server 12 and 15
-            </p>
-          </li>
-          <li>
-            <p>
-              openSUSE Leap 15.3
-            </p>
+            <p>openSUSE Leap 15.3, 15.4 and 15.5</p>
           </li>
         </ul>
-        <p>
-          It should be possible to use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on most systems
-          based on Linux kernel 2.6, 3.x, 4.x or 5.x using either the
-          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installer or by doing a manual installation.
-          See <xref href="install-linux-host.dita#install-linux-host"/>. However, the
-          formally tested and supported Linux distributions are those
-          for which we offer a dedicated package.
-        </p>
+        <p> It should be possible to use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on
+          most systems based on Linux kernel 2.6 or later, using either the <ph
+            conkeyref="vbox-conkeyref-phrases/product-name"/> installer or by doing a manual
+          installation. See <xref href="install-linux-host.dita#install-linux-host"/>. However, the
+          formally tested and supported Linux distributions are those for which we offer a dedicated
+          package. </p>
         <p>
           Note that Linux 2.4-based host OSes are no longer supported.
Index: trunk/doc/manual/en_US/dita/topics/hostpowertweaks.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/hostpowertweaks.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/hostpowertweaks.dita	(revision 105134)
@@ -11,8 +11,6 @@
     <ul>
       <li>
-        <p><b outputclass="bold">Host Suspends.</b> This event is
-          generated when the host is about to suspend, that is, the host
-          saves the state to some non-volatile storage and powers off.
-        </p>
+        <p><b outputclass="bold">Host Suspends.</b> This event is generated when the host is about
+          to suspend, that is, the host saves the state to some nonvolatile storage and powers off. </p>
         <p>
           This event is currently only handled on Windows hosts and Mac
Index: trunk/doc/manual/en_US/dita/topics/install-mac-unattended.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/install-mac-unattended.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/install-mac-unattended.dita	(revision 105134)
@@ -5,8 +5,7 @@
   
   <body>
-    <p>
-        To perform a non-interactive installation of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> you
-        can use the command line version of the installer application.
-      </p>
+    <p> To perform a noninteractive installation of <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> you can use the command line version of
+      the installer application. </p>
     <p>
         Mount the <filepath>dmg</filepath> disk image file, as described
Index: trunk/doc/manual/en_US/dita/topics/install-solaris-performing.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/install-solaris-performing.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/install-solaris-performing.dita	(revision 105134)
@@ -6,13 +6,12 @@
   <body>
     <p>
-        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is available as a standard Oracle Solaris
-        package. Download the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> SunOS package, which
-        includes the 64-bit version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. <i>The
-        installation must be performed as root and from the global
-        zone</i>. This is because the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> installer
-        loads kernel drivers, which cannot be done from non-global
-        zones. To verify which zone you are currently in, execute the
-        <userinput>zonename</userinput> command.
-      </p>
+      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is available as a standard Oracle
+      Solaris package. Download the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> SunOS
+      package, which includes the 64-bit version of <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/>. <i>The installation must be performed as
+        root and from the global zone</i>. This is because the <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> installer loads kernel drivers, which
+      cannot be done from non-global zones. To verify which zone you are currently in, execute the
+        <userinput>zonename</userinput> command. </p>
     <p>
         To start installation, run the following commands:
@@ -24,15 +23,11 @@
       </p>
     <pre xml:space="preserve">pkgadd -d VirtualBox-<varname>version-number</varname>-SunOS.pkg</pre>
-    <p>
-        The installer will then prompt you to enter the package you wish
-        to install. Choose <b outputclass="bold">1</b> or
-        <b outputclass="bold">all</b> and proceed. Next the
-        installer will ask you if you want to allow the postinstall
-        script to be executed. Choose <b outputclass="bold">y</b>
-        and proceed, as it is essential to execute this script which
-        installs the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> kernel module. Following this
-        confirmation the installer will install <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and
-        execute the postinstall setup script.
-      </p>
+    <p> The installer will then prompt you to enter the package you want to install. Choose <b
+        outputclass="bold">1</b> or <b outputclass="bold">all</b> and proceed. Next the installer
+      will ask you if you want to allow the postinstall script to be executed. Choose <b
+        outputclass="bold">y</b> and proceed, as it is essential to execute this script which
+      installs the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> kernel module. Following
+      this confirmation the installer will install <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> and execute the postinstall setup script. </p>
     <p>
         Once the postinstall script has been executed your installation
Index: trunk/doc/manual/en_US/dita/topics/install-solaris-unattended.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/install-solaris-unattended.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/install-solaris-unattended.dita	(revision 105134)
@@ -5,10 +5,8 @@
   
   <body>
-    <p>
-        To perform a non-interactive installation of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
-        there is a response file named
-        <filepath>autoresponse</filepath>. The installer uses this for
-        responses to inputs, rather than prompting the user.
-      </p>
+    <p> To perform a noninteractive installation of <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> there is a response file named
+        <filepath>autoresponse</filepath>. The installer uses this for responses to inputs, rather
+      than prompting the user. </p>
     <p>
         Extract the tar.gz package as described in
@@ -17,8 +15,6 @@
       </p>
     <pre xml:space="preserve">pkgadd -d VirtualBox-<varname>version-number</varname>-SunOS-x86 -n -a autoresponse SUNWvbox</pre>
-    <p>
-        To perform a non-interactive uninstallation, open a root
-        terminal session and run the following command:
-      </p>
+    <p> To perform a noninteractive uninstallation, open a root terminal session and run the
+      following command: </p>
     <pre xml:space="preserve">pkgrm -n -a /opt/VirtualBox/autoresponse SUNWvbox</pre>
   </body>
Index: trunk/doc/manual/en_US/dita/topics/install-win-performing.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/install-win-performing.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/install-win-performing.dita	(revision 105134)
@@ -63,8 +63,5 @@
           </p>
         <note>
-          <p>
-              Python version at least 2.6 is required. Python 3 is also
-              supported.
-            </p>
+          <p> Python version 3 is required. Python version 2.x is no longer supported. </p>
         </note>
       </li>
Index: trunk/doc/manual/en_US/dita/topics/intro-save-machine-state.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/intro-save-machine-state.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/intro-save-machine-state.dita	(revision 105134)
@@ -3,5 +3,4 @@
 <topic xml:lang="en-us" id="intro-save-machine-state">
   <title>Saving the State of the Machine</title>
-  
   <body>
     <p>
Index: trunk/doc/manual/en_US/dita/topics/keyb_mouse_normal.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/keyb_mouse_normal.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/keyb_mouse_normal.dita	(revision 105134)
@@ -43,12 +43,12 @@
       </p>
     <fig id="fig-host-key">
-      <title>Host Key Setting on the Virtual Machine Taskbar</title>
+      <title>Host Key Setting on the Virtual Machine Status Bar</title>
       <xref href="images/vm-hostkey.png" format="png" platform="htmlhelp">
         <image href="images/vm-hostkey.png" width="7cm" placement="break">
-          <alt>Host Key Setting on the Virtual Machine Taskbar</alt>
+          <alt>Host Key Setting on the Virtual Machine Status Bar</alt>
         </image>
       </xref>
       <image platform="ohc" href="images/vm-hostkey.png" width="7cm" placement="break">
-        <alt>Host Key Setting on the Virtual Machine Taskbar</alt>
+        <alt>Host Key Setting on the Virtual Machine Status Bar</alt>
       </image>
     </fig>
Index: trunk/doc/manual/en_US/dita/topics/log-viewer.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/log-viewer.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/log-viewer.dita	(revision 105134)
@@ -11,4 +11,5 @@
       that enables you to view and analyze system logs.
     </p>
+    <!-- 7.1: New pic required? Tab operation changed. Log Viewer/Filter pane. bugref:10496 -->
     <fig id="fig-log-viewer-tool">
       <title>Log Viewer Tool, Showing System Events</title>
@@ -82,7 +83,6 @@
       </li>
       <li>
-        <p><b outputclass="bold">Options:</b> Configures the text
-          display used in the log message window.
-        </p>
+        <p><b outputclass="bold">Preferences:</b> Configures the text display used in the log
+          message window. </p>
       </li>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/mouse-capture.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/mouse-capture.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/mouse-capture.dita	(revision 105134)
@@ -17,8 +17,6 @@
         released.
       </p>
-    <p>
-        The default behavior is sometimes not desired. Therefore it can
-        be configured as follows:
-      </p>
+    <p> The default behavior is sometimes not appropriate. Therefore it can be configured as
+      follows: </p>
     <pre xml:space="preserve">VBoxManage setextradata <varname>VM-name</varname> GUI/MouseCapturePolicy <varname>mode</varname>
                   </pre>
Index: trunk/doc/manual/en_US/dita/topics/nat-adv-dns.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/nat-adv-dns.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/nat-adv-dns.dita	(revision 105134)
@@ -5,12 +5,8 @@
   
   <body>
-    <p>
-        The NAT engine by default offers the same DNS servers to the
-        guest that are configured on the host. In some scenarios, it can
-        be desirable to hide the DNS server IPs from the guest, for
-        example when this information can change on the host due to
-        expiring DHCP leases. In this case, you can tell the NAT engine
-        to act as DNS proxy using the following command:
-      </p>
+    <p> The NAT engine by default offers the same DNS servers to the guest that are configured on
+      the host. In some scenarios, it can be appropriate to hide the DNS server IPs from the guest,
+      for example when this information can change on the host due to expiring DHCP leases. In this
+      case, you can tell the NAT engine to act as DNS proxy using the following command: </p>
     <pre xml:space="preserve">$ VBoxManage modifyvm <varname>VM-name</varname> --natdnsproxy1 on</pre>
   </body>
Index: trunk/doc/manual/en_US/dita/topics/nat-limitations.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/nat-limitations.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/nat-limitations.dita	(revision 105134)
@@ -21,15 +21,10 @@
       </li>
       <li>
-        <p><b outputclass="bold">Receiving of UDP
-            broadcasts.</b> The guest does not reliably receive
-            UDP broadcasts. In order to save resources, it only listens
-            for a certain amount of time after the guest has sent UDP
-            data on a particular port. As a consequence, NetBios name
-            resolution based on broadcasts does not always work, but
-            WINS always works. As a workaround, you can use the numeric
-            IP of the desired server in the
-            <filepath>\\<varname>server</varname>\<varname>share</varname></filepath>
-            notation.
-          </p>
+        <p><b outputclass="bold">Receiving of UDP broadcasts.</b> The guest does not reliably
+          receive UDP broadcasts. In order to save resources, it only listens for a certain amount
+          of time after the guest has sent UDP data on a particular port. As a consequence, NetBios
+          name resolution based on broadcasts does not always work, but WINS always works. As a
+          workaround, you can use the numeric IP of the required server in the
+              <filepath>\\<varname>server</varname>\<varname>share</varname></filepath> notation. </p>
       </li>
       <li>
@@ -52,12 +47,8 @@
       </li>
     </ul>
-    <p>
-        These limitations normally do not affect standard network use.
-        But the presence of NAT has also subtle effects that may
-        interfere with protocols that are normally working. One example
-        is NFS, where the server is often configured to refuse
-        connections from non-privileged ports, which are those ports not
-        below 1024.
-      </p>
+    <p> These limitations normally do not affect standard network use. But the presence of NAT has
+      also subtle effects that may interfere with protocols that are normally working. One example
+      is NFS, where the server is often configured to refuse connections from non-privileged ports,
+      which are those ports above 1024. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/network_bridged.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/network_bridged.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/network_bridged.dita	(revision 105134)
@@ -82,10 +82,7 @@
           certain conditions.
         </p>
-        <p>
-          Some adapters strip VLAN tags in hardware. This does not allow
-          you to use VLAN trunking between VM and the external network
-          with pre-2.6.27 Linux kernels, or with host operating systems
-          other than Linux.
-        </p>
+        <p> Some adapters strip VLAN tags in hardware. This does not allow you to use VLAN trunking
+          between VM and the external network with Linux kernels before 2.6.27, or with host
+          operating systems other than Linux. </p>
       </li>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/network_hostonly.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/network_hostonly.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/network_hostonly.dita	(revision 105134)
@@ -111,14 +111,10 @@
       </p>
     </note>
-    <p>
-      On Linux, macOS and Solaris <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will only allow IP
-      addresses in 192.168.56.0/21 range to be assigned to host-only
-      adapters. For IPv6 only link-local addresses are allowed. If other
-      ranges are desired, they can be enabled by creating
-      <filepath>/etc/vbox/networks.conf</filepath> and specifying
-      allowed ranges there. For example, to allow 10.0.0.0/8 and
-      192.168.0.0/16 IPv4 ranges as well as 2001::/64 range put the
-      following lines into <filepath>/etc/vbox/networks.conf</filepath>:
-    </p>
+    <p> On Linux, macOS and Solaris <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will only
+      allow IP addresses in 192.168.56.0/21 range to be assigned to host-only adapters. For IPv6
+      only link-local addresses are allowed. If other ranges are required, they can be enabled by
+      creating <filepath>/etc/vbox/networks.conf</filepath> and specifying allowed ranges there. For
+      example, to allow 10.0.0.0/8 and 192.168.0.0/16 IPv4 ranges as well as 2001::/64 range put the
+      following lines into <filepath>/etc/vbox/networks.conf</filepath>: </p>
     <pre xml:space="preserve">      * 10.0.0.0/8 192.168.0.0/16
       * 2001::/64
Index: trunk/doc/manual/en_US/dita/topics/network_performance.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/network_performance.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/network_performance.dita	(revision 105134)
@@ -27,13 +27,9 @@
       </p>
                </note>
-               <p>
-      Three attachment types: Internal, Bridged, and Host-Only, have
-      nearly identical performance. The Internal type is a little bit
-      faster and uses less CPU cycles as the packets never reach the
-      host's network stack. The NAT attachment type is the slowest and
-      most secure of all attachment types, as it provides network
-      address translation. The generic driver attachment is special and
-      cannot be considered as an alternative to other attachment types.
-    </p>
+               <p> Three attachment types: Internal, Bridged, and Host-Only, have nearly identical
+      performance. The Internal type is slightly faster and uses less CPU cycles as the packets
+      never reach the host's network stack. The NAT attachment type is the slowest and most secure
+      of all attachment types, as it provides network address translation. The generic driver
+      attachment is special and cannot be considered as an alternative to other attachment types. </p>
                <p>
       The number of CPUs assigned to VM does not improve network
@@ -58,10 +54,7 @@
                   </li>
                   <li>
-                     <p>
-          Make sure segmentation offloading is enabled in the guest OS.
-          Usually it will be enabled by default. You can check and
-          modify offloading settings using the
-          <userinput>ethtool</userinput> command on Linux guests.
-        </p>
+                     <p> Ensure segmentation offloading is enabled in the guest OS. Usually it will
+          be enabled by default. You can check and modify offloading settings using the
+            <userinput>ethtool</userinput> command on Linux guests. </p>
                   </li>
                   <li>
Index: trunk/doc/manual/en_US/dita/topics/networkingmodes.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/networkingmodes.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/networkingmodes.dita	(revision 105134)
@@ -74,7 +74,5 @@
           with <ph conkeyref="vbox-conkeyref-phrases/product-name"/> or be distributed in an extension pack.
         </p>
-        <p>
-          The following sub-modes are available:
-        </p>
+        <p> The following submodes are available: </p>
         <ul>
           <li>
Index: trunk/doc/manual/en_US/dita/topics/pcspeaker_passthrough.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/pcspeaker_passthrough.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/pcspeaker_passthrough.dita	(revision 105134)
@@ -212,15 +212,11 @@
       some hints, but in general refer to the Linux documentation.
     </p>
-    <p>
-      If you have trouble getting any beeps even if the device
-      permissions are set up and VBox.log confirms that it uses evdev or
-      console for the PC speaker control, check if your system has a PC
-      speaker. Some systems do not have one. Other complications can
-      arise from Linux rerouting the PC speaker output to a sound card.
-      Check if the beeps are audible if you connect speakers to your
-      sound card. Today almost all systems have one. Finally, check if
-      the audio mixer control has a channel named "beep", which could be
-      hidden in the mixer settings, and that it is not muted.
-    </p>
+    <p> If you have trouble getting any beeps even if the device permissions are set up and VBox.log
+      confirms that it uses evdev or console for the PC speaker control, check if your system has a
+      PC speaker. Some systems do not have one. Other complications can arise from Linux rerouting
+      the PC speaker output to a sound card. Check if the beeps are audible if you connect speakers
+      to your sound card. Today almost all systems have one. Finally, check if the audio mixer
+      control has a channel named <i>beep</i>, which could be hidden in the mixer settings, and that
+      it is not muted. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/preface-accessibility.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/preface-accessibility.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/preface-accessibility.dita	(revision 105134)
@@ -5,6 +5,6 @@
   <body>
     <section id="accessibility-body">
-      <p> Oracle customers that have purchased support have access to electronic support through My
-        Oracle Support. For information, visit <xref href="https://www.oracle.com/corporate/accessibility/learning-support.html#support-tab" format="html" scope="external"/>. </p>
+      <p> Oracle customers that have purchased support have access to electronic support through
+          <xref href="https://www.oracle.com/corporate/accessibility/learning-support.html#support-tab" format="html" scope="external">Oracle Accessibility Learning and Support</xref>. </p>
     </section>
   </body>
Index: trunk/doc/manual/en_US/dita/topics/preface-doc-accessibility.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/preface-doc-accessibility.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/preface-doc-accessibility.dita	(revision 105134)
@@ -5,8 +5,5 @@
   <body>
     <section id="doc-accessibility-body">
-      <p> For information about Oracle's commitment to accessibility, visit the Oracle Accessibility
-        Program website at <xref href="http://www.oracle.com/pls/topic/lookup?ctx=acc&amp;id=docacc" format="html" scope="external"/>. </p>
-      <p>For information about the accessibility of the Oracle Help Center, see the Oracle
-        Accessibility Conformance Report at <xref href="https://www.oracle.com/corporate/accessibility/templates/t2-11535.html" format="html" scope="external"/>.</p>
+      <p>For information about Oracle's commitment to accessibility, visit the <xref href="https://www.oracle.com/corporate/accessibility/" format="html" scope="external">Oracle Accessibility Program</xref>. </p>
     </section>
   </body>
Index: trunk/doc/manual/en_US/dita/topics/preferences.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/preferences.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/preferences.dita	(revision 105134)
@@ -9,4 +9,9 @@
       to all virtual machines of the current user.
     </p>
+    <note>
+      <p>The available Preferences settings depend on the selected experience level. To display all
+        Preference settings, ensure the experience level is set to <b>Expert</b>.</p>
+    <p>See <xref href="ui-experience-level.dita#gui-experience-level"/>.</p>
+    </note>
     <p>
       To display the Preferences window, do either of the following:
@@ -20,8 +25,6 @@
       </li>
       <li>
-        <p>
-          Click <b outputclass="bold">Preferences</b> on the
-          Welcome screen in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
-        </p>
+        <p> Click <b outputclass="bold">Preferences</b> on the Welcome screen in <ph
+            conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. </p>
       </li>
     </ul>
@@ -52,8 +55,6 @@
       </li>
       <li>
-        <p><b outputclass="bold">Language.</b> Enables you to
-          specify the language used for menus, labels, and text in
-          <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.
-        </p>
+        <p><b outputclass="bold">Language.</b> Enables you to specify the language used for menus,
+          labels, and text in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. </p>
       </li>
       <li>
@@ -62,14 +63,14 @@
           default scale factor can be specified for all guest screens.
         </p>
+        <p>A default font scaling factor can be set for all guest screen displays.</p>
+        <p>Other extended features can be selected, to ensure that guest screens work well with the host display.</p>
       </li>
       <li>
-        <p><b outputclass="bold">Proxy.</b> Enables you to
-          configure an HTTP Proxy Server.
+        <p><b outputclass="bold">Proxy.</b> Enables you to configure an HTTP proxy server.
         </p>
       </li>
       <li>
-        <p><b outputclass="bold">Interface.</b> Enables you to
-          select a color theme for the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> user interface.
-        </p>
+        <p><b outputclass="bold">Interface.</b> Enables you to select a color theme for the <ph
+            conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> user interface. </p>
         <note>
           <p>
Index: trunk/doc/manual/en_US/dita/topics/rdp-viewers.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/rdp-viewers.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/rdp-viewers.dita	(revision 105134)
@@ -5,12 +5,8 @@
   
   <body>
-    <p>
-        Since VRDP is backwards-compatible to RDP, you can use any
-        standard RDP viewer to connect to such a remote virtual machine.
-        For this to work, you must specify the IP address of your
-        <i>host</i> system, not of the virtual machine, as
-        the server address to connect to. You must also specify the port
-        number that the VRDP server is using.
-      </p>
+    <p> Since VRDP is backward-compatible to RDP, you can use any standard RDP viewer to connect to
+      such a remote virtual machine. For this to work, you must specify the IP address of your
+        <i>host</i> system, not of the virtual machine, as the server address to connect to. You
+      must also specify the port number that the VRDP server is using. </p>
     <p>
         The following examples are for the most common RDP viewers:
Index: trunk/doc/manual/en_US/dita/topics/security-general.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/security-general.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/security-general.dita	(revision 105134)
@@ -11,13 +11,11 @@
     <ul>
       <li>
-        <p><b outputclass="bold">Keep software up to date</b>. One
-          of the principles of good security practise is to keep all
-          software versions and patches up to date. Activate the
-          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> update notification to get notified when a new
-          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> release is available. When updating
-          <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, do not forget to update the Guest Additions.
-          Keep the host operating system as well as the guest operating
-          system up to date.
-        </p>
+        <p><b outputclass="bold">Keep software up-to-date</b>. One of the principles of good
+          security practise is to keep all software versions and patches up-to-date. Activate the
+            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> update notification to get
+          notified when a new <ph conkeyref="vbox-conkeyref-phrases/product-name"/> release is
+          available. When updating <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, do not
+          forget to update the Guest Additions. Keep the host operating system as well as the guest
+          operating system up-to-date. </p>
       </li>
       <li>
@@ -55,9 +53,6 @@
       </li>
       <li>
-        <p><b outputclass="bold">Keep up to date on latest security
-          information.</b> Oracle continually improves its
-          software and documentation. Check this note yearly for
-          revisions.
-        </p>
+        <p><b outputclass="bold">Keep up-to-date on latest security information.</b> Oracle
+          continually improves its software and documentation. Check this note yearly for revisions. </p>
       </li>
     </ul>
Index: trunk/doc/manual/en_US/dita/topics/security-networking.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/security-networking.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/security-networking.dita	(revision 105134)
@@ -5,14 +5,10 @@
   
   <body>
-    <p>
-          The default networking mode for VMs is NAT which means that
-          the VM acts like a computer behind a router, see
-          <xref href="network_nat.dita">Network Address Translation (NAT)</xref>. The guest is part of a private
-          subnet belonging to this VM and the guest IP is not visible
-          from the outside. This networking mode works without any
-          additional setup and is sufficient for many purposes. Keep in
-          mind that NAT allows access to the host operating system's
-          loopback interface.
-        </p>
+    <p> The default networking mode for VMs is NAT which means that the VM acts like a computer
+      behind a router, see <xref href="network_nat.dita">Network Address Translation (NAT)</xref>.
+      The guest is part of a private subnet belonging to this VM and the guest IP is not visible
+      from the outside. This networking mode works without any additional setup and is sufficient
+      for many purposes. Remember that NAT allows access to the host operating system's loopback
+      interface. </p>
     <p>
           If bridged networking is used, the VM acts like a computer
Index: trunk/doc/manual/en_US/dita/topics/security_clipboard.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/security_clipboard.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/security_clipboard.dita	(revision 105134)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="security_clipboard">
   <title>Clipboard</title>
-  
+  <!-- 7.1: Shared clipboard toggle in guest VM, bugref:10481; input from dev required -->
   <body>
     <p>
@@ -14,11 +14,7 @@
           from the host which is shared over the clipboard.
         </p>
-    <p>
-          If the guest is able to read from and/or write to the host
-          clipboard then a remote user connecting to the guest over the
-          network will also gain this ability, which may not be
-          desirable. As a consequence, the shared clipboard is disabled
-          for new machines.
-        </p>
+    <p> If the guest is able to read from or write to the host clipboard then a remote user
+      connecting to the guest over the network will also gain this ability, which may not be
+      appropriate. As a consequence, the shared clipboard is disabled for new machines. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/serialports.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/serialports.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/serialports.dita	(revision 105134)
@@ -136,13 +136,10 @@
               </li>
             </ul>
-            <p>
-              In this case, you can configure whether <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
-              should create the named pipe, or the local domain socket
-              non-Windows hosts, itself or whether <ph conkeyref="vbox-conkeyref-phrases/product-name"/> should
-              assume that the pipe or socket exists already. With the
-              <userinput>VBoxManage</userinput> command-line options, this
-              is referred to as server mode or client mode,
-              respectively.
-            </p>
+            <p> In this case, you can configure whether <ph
+                conkeyref="vbox-conkeyref-phrases/product-name"/> should create the named pipe, or
+              the local domain socket on non-Windows hosts, itself or whether <ph
+                conkeyref="vbox-conkeyref-phrases/product-name"/> should assume that the pipe or
+              socket exists already. With the <userinput>VBoxManage</userinput> command-line
+              options, this is referred to as server mode or client mode, respectively. </p>
             <p>
               For a direct connection between two virtual machines,
Index: trunk/doc/manual/en_US/dita/topics/settings-basic.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/settings-basic.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/settings-basic.dita	(revision 105134)
@@ -17,6 +17,5 @@
             the VM's configuration files. If you change the name,
             <ph conkeyref="vbox-conkeyref-phrases/product-name"/> renames these files as well. As a result, you
-            can only use characters which are allowed for file names on
-            your host OS.
+            can only use characters which are allowed for file names on your host OS.
           </p>
         <p>
@@ -27,6 +26,8 @@
       </li>
       <li>
-        <p><b outputclass="bold">Type:</b> The type of the guest
-            OS for the VM. This is the same setting that is specified in
+        <p><b outputclass="bold">Type and Subtype:</b> The type and subtype of the guest
+            OS for the VM. For example, if the <b>Type</b> is Linux, the <b>Subtype</b> might be 
+          Oracle Linux.</p>
+        <p>These are the same settings that are specified in
             the <b outputclass="bold">New Virtual Machine</b>
             wizard. See <xref href="create-vm-wizard.dita#create-vm-wizard"/>.
Index: trunk/doc/manual/en_US/dita/topics/settings-capture.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/settings-capture.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/settings-capture.dita	(revision 105134)
@@ -49,9 +49,7 @@
       </li>
       <li>
-        <p><b outputclass="bold">Video Quality:</b> Use the
-            slider to set the the bit rate of the video in kilobits per
-            second. Increasing this value improves the appearance of the
-            video at the cost of an increased file size.
-          </p>
+        <p><b outputclass="bold">Video Quality:</b> Use the slider to set the bit rate of the video
+          in kilobits per second. Increasing this value improves the appearance of the video at the
+          cost of an increased file size. </p>
       </li>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/settings-general-advanced.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/settings-general-advanced.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/settings-general-advanced.dita	(revision 105134)
@@ -42,4 +42,5 @@
             virtual machine.
           </p>
+        <!--7.1: r159813: checkbox added to the Shared Clipboard menu? -->
       </li>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/settings-motherboard.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/settings-motherboard.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/settings-motherboard.dita	(revision 105134)
@@ -58,4 +58,5 @@
             for guest OSes which do not require it.
           </p>
+        <!-- 7.1: Any chipset options for Arm?-->
       </li>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/settings-screen.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/settings-screen.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/settings-screen.dita	(revision 105134)
@@ -7,11 +7,8 @@
     <ul>
       <li>
-        <p><b outputclass="bold">Video Memory:</b> Sets the size
-            of the memory provided by the virtual graphics card
-            available to the guest, in MB. As with the main memory, the
-            specified amount will be allocated from the host's resident
-            memory. Based on the amount of video memory, higher
-            resolutions and color depths may be available.
-          </p>
+        <p><b outputclass="bold">Video Memory:</b> Sets the size of the memory provided by the
+          virtual graphics card available to the guest, in megabytes. As with the main memory, the
+          specified amount will be allocated from the host's resident memory. Based on the amount of
+          video memory, higher resolutions and color depths may be available. </p>
         <p>
             <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> will show a warning if the amount of video memory
Index: trunk/doc/manual/en_US/dita/topics/settings-storage.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/settings-storage.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/settings-storage.dita	(revision 105134)
@@ -81,12 +81,8 @@
       format.
     </p>
-    <p>
-      You can modify these media attachments freely. For example, if you
-      wish to copy some files from another virtual disk that you
-      created, you can connect that disk as a second hard disk, as in
-      the above screenshot. You could also add a second virtual CD/DVD
-      drive, or change where these items are attached. The following
-      options are available:
-    </p>
+    <p> You can modify these media attachments freely. For example, if you want to copy some files
+      from another virtual disk that you created, you can connect that disk as a second hard disk,
+      as in the above screenshot. You could also add a second virtual CD/DVD drive, or change where
+      these items are attached. The following options are available: </p>
     <ul>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/settings-usb.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/settings-usb.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/settings-usb.dita	(revision 105134)
@@ -6,173 +6,101 @@
                
                <body>
+                  <p>The <b outputclass="bold">USB</b> section in a virtual machine's <b
+        outputclass="bold">Settings</b> window enables you to configure <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/>'s sophisticated USB support. </p>
+                  <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> can enable virtual
+      machines to access the USB devices on your host directly. To achieve this, <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> presents the guest OS with a virtual USB
+      controller. </p>
                   <p>
-        The <b outputclass="bold">USB</b> section in a virtual
-        machine's <b outputclass="bold">Settings</b> window
-        enables you to configure <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s sophisticated USB
-        support.
-      </p>
-                  <p>
-        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can enable virtual machines to access the USB
-        devices on your host directly. To achieve this, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
-        presents the guest OS with a virtual USB controller. As soon as
-        the guest system starts using a USB device, it will appear as
-        unavailable on the host.
+      <note id="note_bzl_prv_qbc" type="caution">
+        <p>As soon as the guest system starts using a USB device, it will be disconnected from the
+          host without a proper shutdown. This may cause data loss.</p>
+      </note>
       </p>
                   <note>
-                     <ul>
-                        <li>
-                           <p>
-              Be careful with USB devices that are currently in use on
-              the host. For example, if you allow your guest to connect
-              to your USB hard disk that is currently mounted on the
-              host, when the guest is activated, it will be disconnected
-              from the host without a proper shutdown. This may cause
-              data loss.
-            </p>
-                        </li>
-                        <li>
-                           <p>
-              Oracle Solaris hosts have a few known limitations
-              regarding USB support. See <xref href="KnownIssues.dita">Known Limitations</xref>.
-            </p>
-                        </li>
+      <p>Oracle Solaris hosts have a few known limitations regarding USB support. See <xref
+          href="KnownIssues.dita">Known Limitations</xref>. </p>
+    </note>
+                  <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> also enables your guests
+      to connect to remote USB devices by use of the VirtualBox Remote Desktop Extension (VRDE). See
+        <xref href="usb-over-rdp.dita">Remote USB</xref>. </p>
+    <section id="section_pfm_vsv_qbc">
+      <title>Enable USB for a VM</title>
+    </section>
+                  
+      <ol id="ol_fpr_wsv_qbc">
+        <li>Ensure the VM is not running.</li>
+        <li>Select the VM in the machine list, and then click <b outputclass="bold"
+          >Settings</b>.</li>
+        <li>On the USB tab, select <b outputclass="bold">Enable USB Controller</b> and choose the
+        USB Controller you need for your guest OS. In most cases this will be xHCI. Only use OHCI or
+        EHCI if your guest OS does not support xHCI. For some legacy Windows guests you'll need to
+        install third party drivers for xHCI support. <p>
+          <ul id="ul_rzz_l5v_qbc">
+            <li>OHCI supports USB 1.1 </li>
+            <li>EHCI supports USB 2.0. This also enables OHCI.</li>
+            <li>xHCI supports all USB speeds up to USB 3.0</li>
                      </ul>
-                  </note>
-                  <p>
-        In addition to allowing a guest access to your local USB
-        devices, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> even enables your guests to connect to
-        remote USB devices by use of the VirtualBox Remote Desktop
-        Extension (VRDE). See <xref href="usb-over-rdp.dita">Remote USB</xref>.
-      </p>
-                  <p>
-        To enable USB for a VM, select the <b outputclass="bold">Enable
-        USB Controller</b> check box. The following settings are
-        available:
-      </p>
-                  <ul>
+        </p></li>
+      
+   
+                  
+                     <li>Specify which devices can be attached to the guest by adding <b
+          outputclass="bold">USB Device Filters</b>. USB devices with a matching filter will be
+        automatically passed to the guest once they are attached to the host. USB devices without a
+        matching filter can be passed manually to the guest, for example by using the <b
+          outputclass="bold">Devices</b>, <b outputclass="bold">USB</b> menu. <ul
+          id="ul_jjz_cxv_qbc">
+          <li>Click the USB filter button to create a new filter with blank fields, and then
+            complete the fields. </li>
+          <li>Or, click the Add USB filter button to create a filter with the fields completed for
+            the selected USB device. </li>
+        </ul><p>Give the filter a name, for later reference, and specify the filter criteria. The
+          more criteria you specify, the more precisely devices will be selected. For instance, if
+          you specify only a vendor ID of 046d, all devices produced by Logitech will be available
+          to the guest. If you fill in all fields, on the other hand, the filter will only apply to
+          a particular device model from a particular vendor, and not even to other devices of the
+          same type with a different revision and serial number. </p><p>The following criteria are
+          available: </p><ul id="ul_av4_41w_qbc">
                      <li>
-                        <p>
-                           <b outputclass="bold">USB Controller:</b> Selects a
-            controller with the specified level of USB support, as
-            follows:
-          </p>
-                        <ul>
-                           <li>
-                              <p>
-                OHCI for USB 1.1
-              </p>
+            <p><b outputclass="bold">Vendor and Product ID.</b> With USB, each vendor of USB
+              products carries an identification number that is unique world-wide, called the
+                <i>vendor ID</i>. Similarly, each line of products is assigned a <i>product ID</i>
+              number. Both numbers are commonly written in hexadecimal, and a colon separates the
+              vendor from the product ID. For example, <codeph>046d:c016</codeph> stands for
+              Logitech as a vendor, and the M-UV69a Optical Wheel Mouse product. </p>
+            <p>Alternatively, you can also specify <b outputclass="bold">Manufacturer</b> and <b
+                outputclass="bold">Product</b> by name. </p>
+            <p>To list all the USB devices that are connected to your host machine with their
+              respective vendor IDs and product IDs, use the following command: </p>
+            <pre xml:space="preserve" id="pre_bv4_41w_qbc">VBoxManage list usbhost</pre>
+            <p>On Windows, you can also see all USB devices that are attached to your system in the
+              Device Manager. On Linux, you can use the <userinput>lsusb</userinput> command. </p>
                            </li>
                            <li>
-                              <p>
-                EHCI for USB 2.0. This also enables OHCI.
-              </p>
+            <p><b outputclass="bold">Serial Number.</b> While vendor ID and product ID are quite
+              specific to identify USB devices, if you have two identical devices of the same brand
+              and product line, you will also need their serial numbers to filter them out
+              correctly. </p>
                            </li>
                            <li>
-                              <p>
-                xHCI for USB 3.0. This supports all USB speeds.
-              </p>
+            <p><b outputclass="bold">Remote.</b> This setting specifies whether the device will be
+              local only, remote only, such as over VRDP, or either. </p>
                            </li>
-                        </ul>
-                     </li>
+        </ul><p>As an example, you could create a new USB filter and specify a vendor ID of 046d for
+          Logitech, Inc, a manufacturer index of 1, and <i>not remote</i>. Then any USB devices on
+          the host system produced by Logitech, Inc with a manufacturer index of 1 will be visible
+          to the guest system. </p><p>Several filters can select a single device. For example, a
+          filter which selects all Logitech devices, and one which selects a particular webcam.
+        </p></li>
                      <li>
-                        <p>
-                           <b outputclass="bold">USB Device Filters:</b> When
-            USB support is enabled for a VM, you can determine in detail
-            which devices will be automatically attached to the guest.
-            For this, you can create filters by specifying certain
-            properties of the USB device. USB devices with a matching
-            filter will be automatically passed to the guest once they
-            are attached to the host. USB devices without a matching
-            filter can be passed manually to the guest, for example by
-            using the <b outputclass="bold">Devices</b>,
-            <b outputclass="bold">USB</b> menu.
-          </p>
-                        <p>
-            Clicking on the <b outputclass="bold">+</b> button to
-            the right of the <b outputclass="bold">USB Device
-            Filters</b> window creates a new filter. You can give
-            the filter a name, for later reference, and specify the
-            filter criteria. The more criteria you specify, the more
-            precisely devices will be selected. For instance, if you
-            specify only a vendor ID of 046d, all devices produced by
-            Logitech will be available to the guest. If you fill in all
-            fields, on the other hand, the filter will only apply to a
-            particular device model from a particular vendor, and not
-            even to other devices of the same type with a different
-            revision and serial number.
-          </p>
-                        <p>
-            In detail, the following criteria are available:
-          </p>
-                        <ul>
-                           <li>
-                              <p>
-                                 <b outputclass="bold">Vendor and Product ID.</b>
-                With USB, each vendor of USB products carries an
-                identification number that is unique world-wide, called
-                the <i>vendor ID</i>. Similarly, each line
-                of products is assigned a <i>product
-                ID</i> number. Both numbers are commonly written
-                in hexadecimal, and a colon separates the vendor from
-                the product ID. For example,
-                <codeph>046d:c016</codeph> stands for Logitech as a
-                vendor, and the M-UV69a Optical Wheel Mouse product.
-              </p>
-                              <p>
-                Alternatively, you can also specify
-                <b outputclass="bold">Manufacturer</b> and
-                <b outputclass="bold">Product</b> by name.
-              </p>
-                              <p>
-                To list all the USB devices that are connected to your
-                host machine with their respective vendor IDs and
-                product IDs, use the following command:
-              </p>
-                              <pre xml:space="preserve">VBoxManage list usbhost</pre>
-                              <p>
-                On Windows, you can also see all USB devices that are
-                attached to your system in the Device Manager. On Linux,
-                you can use the <userinput>lsusb</userinput> command.
-              </p>
+        <p>On a Windows host, you will need to unplug and reconnect a USB device to use it after
+          creating a filter for it. </p>
                            </li>
                            <li>
-                              <p>
-                                 <b outputclass="bold">Serial Number.</b> While
-                vendor ID and product ID are quite specific to identify
-                USB devices, if you have two identical devices of the
-                same brand and product line, you will also need their
-                serial numbers to filter them out correctly.
-              </p>
-                           </li>
-                           <li>
-                              <p>
-                                 <b outputclass="bold">Remote.</b> This setting
-                specifies whether the device will be local only, remote
-                only, such as over VRDP, or either.
-              </p>
-                           </li>
-                        </ul>
-                        <p>
-            On a Windows host, you will need to unplug and reconnect a
-            USB device to use it after creating a filter for it.
-          </p>
-                        <p>
-            As an example, you could create a new USB filter and specify
-            a vendor ID of 046d for Logitech, Inc, a manufacturer index
-            of 1, and "not remote". Then any USB devices on the host
-            system produced by Logitech, Inc with a manufacturer index
-            of 1 will be visible to the guest system.
-          </p>
-                        <p>
-            Several filters can select a single device. For example, a
-            filter which selects all Logitech devices, and one which
-            selects a particular webcam.
-          </p>
-                        <p>
-            You can deactivate filters without deleting them by
-            deselecting the check box next to the filter name.
-          </p>
-                     </li>
-                  </ul>
+        <p>Ensure the filters you need immediately are selected in the list. Selected filters will
+          be attached automatically when the VM starts.</p>
+      </li></ol>
                </body>
                
Index: trunk/doc/manual/en_US/dita/topics/sf_mount_manual.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/sf_mount_manual.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/sf_mount_manual.dita	(revision 105134)
@@ -113,11 +113,8 @@
 VBoxControl sharedfolder unuse D:
 VBoxControl sharedfolder list</pre>
-                        <p>
-            As with Windows guests, shared folders can also be accessed
-            via UNC using <filepath>\\VBoxSF\</filepath>,
-            <filepath>\\VBoxSvr\</filepath> or
-            <filepath>\\VBoxSrv\</filepath> as the server name and the
-            shared folder name as <varname>sharename</varname>.
-          </p>
+                        <p> As with Windows guests, shared folders can also be accessed using UNC ,
+          with <filepath>\\VBoxSF\</filepath>, <filepath>\\VBoxSvr\</filepath> or
+            <filepath>\\VBoxSrv\</filepath> as the server name and the shared folder name as
+            <varname>sharename</varname>. </p>
                      </li>
                   </ul>
Index: trunk/doc/manual/en_US/dita/topics/sharedfolders.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/sharedfolders.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/sharedfolders.dita	(revision 105134)
@@ -37,10 +37,7 @@
                <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 on 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>
@@ -110,5 +107,5 @@
           For security reasons the guest OS is not allowed to create
           symlinks by default. If you trust the guest OS to not abuse
-          the functionality, you can enable the creation of symlinks for
+          this functionality, you can enable the creation of symlinks for
           a shared folder as follows:
         </p>
@@ -116,7 +113,7 @@
                   </li>
                </ul>
-               <p>
+            <p>
           If a symbolic link is created inside a shared folder on the host
-          and the installed Guest Additions don't support symbolic links
+          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
@@ -127,5 +124,5 @@
         </p>
                <p>
-          And then the shared folder is viewed on a Windows guest there
+          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>.
Index: trunk/doc/manual/en_US/dita/topics/soft-keyb-custom.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/soft-keyb-custom.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/soft-keyb-custom.dita	(revision 105134)
@@ -12,5 +12,5 @@
                   <note>
                      <p>
-          To permananently save a custom keyboard layout, you must save
+          To permanently save a custom keyboard layout, you must save
           it to a file. Otherwise, any changes you make are discarded
           when you close down the <b outputclass="bold">Soft
Index: trunk/doc/manual/en_US/dita/topics/soft-keyb.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/soft-keyb.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/soft-keyb.dita	(revision 105134)
@@ -4,7 +4,6 @@
 
 <topic xml:lang="en-us" id="soft-keyb">
+  <!-- 7.1: Updated pic added -->
   <title>Soft Keyboard</title>
-
-
   <body>
     <p>
@@ -13,6 +12,5 @@
       keyboard is an on-screen keyboard that can be used as an
       alternative to a physical keyboard. See
-      <xref href="soft-keyb-using.dita#soft-keyb-using"/>
- for details of how to use the
+      <xref href="soft-keyb-using.dita#soft-keyb-using"/> for details of how to use the
       soft keyboard.
     </p>
Index: trunk/doc/manual/en_US/dita/topics/solaris-zones.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/solaris-zones.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/solaris-zones.dita	(revision 105134)
@@ -4,5 +4,5 @@
 <topic xml:lang="en-us" id="solaris-zones">
                <title>Configuring a Non-Global Zone for Running <ph conkeyref="vbox-conkeyref-phrases/product-name"/></title>
-
+               
                <body>
                   <p>
@@ -21,5 +21,6 @@
       </p>
                   <p>
-        Use <userinput>zonecfg(8)</userinput> to add the <codeph>device</codeph> resource
+        Use <userinput>zonecfg(8)</userinput> to add the
+        <codeph>device</codeph> resource
         and the <codeph>match</codeph> property for each
         <ph conkeyref="vbox-conkeyref-phrases/product-name"/> device node in the global
@@ -38,12 +39,9 @@
         <filepath>/dev/vboxusbmon</filepath> device using the steps above.
       </p>
-                  <p>
-        Oracle Solaris 11 doesn't support sparse root zones so you will need to
-        loopback mount <filepath>/opt/VirtualBox</filepath> from the
-        global zone into the non-global zone at the same path.  This is
-        done using <userinput>zonecfg(8)</userinput> to set the <codeph>dir</codeph>
-        attribute and the <codeph>special</codeph> attribute for this directory.
-        For example:
-      </p>
+                  <p> Oracle Solaris 11 does not support sparse root zones so you will need to
+      loopback mount <filepath>/opt/VirtualBox</filepath> from the global zone into the non-global
+      zone at the same path. This is done using <userinput>zonecfg(8)</userinput> to set the
+        <codeph>dir</codeph> attribute and the <codeph>special</codeph> attribute for this
+      directory. For example: </p>
                   <pre xml:space="preserve">zonecfg:vboxzone&gt; add fs
 zonecfg:vboxzone:fs&gt; set dir=/opt/VirtualBox
@@ -57,5 +55,5 @@
         using <userinput>zoneadm(8)</userinput> as follows:
         </p>
-                  <pre xml:space="preserve">global$ zoneadm -z <varname>vboxzone</varname> reboot
+               <pre xml:space="preserve">global$ zoneadm -z <varname>vboxzone</varname> reboot
                   </pre>
                   <p>
@@ -65,4 +63,4 @@
       </p>
                </body>
-
+               
             </topic>
Index: trunk/doc/manual/en_US/dita/topics/solariscodedumper.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/solariscodedumper.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/solariscodedumper.dita	(revision 105134)
@@ -21,14 +21,10 @@
     <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> VBoxInternal2/CoreDumpDir <varname>path-to-directory</varname>
                </pre>
-    <p>
-      Make sure the directory you specify is on a volume with sufficient
-      free space and that the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> process has sufficient
-      permissions to write files to this directory. If you skip this
-      command and do not specify any core dump directory, the current
-      directory of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> executable will be used. This
-      would most likely fail when writing cores as they are protected
-      with root permissions. It is recommended you explicitly set a core
-      dump directory.
-    </p>
+    <p> Ensure the directory you specify is on a volume with sufficient free space and that the <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> process has sufficient permissions to
+      write files to this directory. If you skip this command and do not specify any core dump
+      directory, the current directory of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
+      executable will be used. This would most likely fail when writing cores as they are protected
+      with root permissions. It is recommended you explicitly set a core dump directory. </p>
     <p>
       You must specify when the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> CoreDumper should be
Index: trunk/doc/manual/en_US/dita/topics/startingvboxonlinux.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/startingvboxonlinux.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/startingvboxonlinux.dita	(revision 105134)
@@ -14,22 +14,16 @@
         required program for you.
       </p>
-                  <p>
-        The following detailed instructions should only be of interest
-        if you wish to execute <ph conkeyref="vbox-conkeyref-phrases/product-name"/> without installing it
-        first. You should start by compiling the
-        <userinput>vboxdrv</userinput> kernel module and inserting it into
-        the Linux kernel. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> consists of a service daemon,
-        <userinput>VBoxSVC</userinput>, and several application programs.
-        The daemon is automatically started if necessary. All
-        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> applications will communicate with the daemon
-        through UNIX local domain sockets. There can be multiple daemon
-        instances under different user accounts and applications can
-        only communicate with the daemon running under the user account
-        as the application. The local domain socket resides in a
-        subdirectory of your system's directory for temporary files
-        called <filepath>.vbox-&lt;username&gt;-ipc</filepath>. In case
-        of communication problems or server startup problems, you may
-        try to remove this directory.
-      </p>
+                  <p> The following detailed instructions should only be of interest if you want to
+      execute <ph conkeyref="vbox-conkeyref-phrases/product-name"/> without installing it first. You
+      should start by compiling the <userinput>vboxdrv</userinput> kernel module and inserting it
+      into the Linux kernel. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> consists of a
+      service daemon, <userinput>VBoxSVC</userinput>, and several application programs. The daemon
+      is automatically started if necessary. All <ph conkeyref="vbox-conkeyref-phrases/product-name"
+      /> applications will communicate with the daemon through UNIX local domain sockets. There can
+      be multiple daemon instances under different user accounts and applications can only
+      communicate with the daemon running under the user account as the application. The local
+      domain socket resides in a subdirectory of your system's directory for temporary files called
+        <filepath>.vbox-&lt;username&gt;-ipc</filepath>. In case of communication problems or server
+      startup problems, you may try to remove this directory. </p>
                   <p>
         All <ph conkeyref="vbox-conkeyref-phrases/product-name"/> applications (<userinput>VirtualBox</userinput>,
Index: trunk/doc/manual/en_US/dita/topics/sysprep.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/sysprep.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/sysprep.dita	(revision 105134)
@@ -5,15 +5,10 @@
   
   <body>
-    <p>
-        Microsoft offers a system preparation tool called Sysprep, to
-        prepare a Windows system for deployment or redistribution. Some
-        Windows releases include Sysprep on the installation medium, but
-        the tool is also available for download from the Microsoft web
-        site. In a standard For most Windows versions, Sysprep is
-        included in a default installation. Sysprep mainly consists of
-        an executable called <userinput>sysprep.exe</userinput> which is
-        invoked by the user to put the Windows installation into
-        preparation mode.
-      </p>
+    <p> Microsoft offers a system preparation tool called Sysprep, to prepare a Windows system for
+      deployment or redistribution. Some Windows releases include Sysprep on the installation
+      medium, but the tool is also available for download from the Microsoft website. In a standard
+      For most Windows versions, Sysprep is included in a default installation. Sysprep mainly
+      consists of an executable called <userinput>sysprep.exe</userinput> which is invoked by the
+      user to put the Windows installation into preparation mode. </p>
     <p>
         The Guest Additions offer a way to launch a system preparation
Index: trunk/doc/manual/en_US/dita/topics/technical-components.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/technical-components.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/technical-components.dita	(revision 105134)
@@ -3,5 +3,4 @@
 <topic xml:lang="en-us" id="technical-components">
   <title><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Executables and Components</title>
-  
   <body>
     <p>
@@ -58,11 +57,8 @@
       </li>
     </ul>
-    <p>
-      Any <ph conkeyref="vbox-conkeyref-phrases/product-name"/> front-end, or client, will communicate with the
-      service process and can both control and reflect the current
-      state. For example, either the VM selector or the VM window or
-      VBoxManage can be used to pause the running VM, and other
-      components will always reflect the changed state.
-    </p>
+    <p> Any <ph conkeyref="vbox-conkeyref-phrases/product-name"/> front end, or client, will
+      communicate with the service process and can both control and reflect the current state. For
+      example, either the VM selector or the VM window or VBoxManage can be used to pause the
+      running VM, and other components will always reflect the changed state. </p>
     <p>
       The <ph conkeyref="vbox-conkeyref-phrases/product-name"/> GUI application, called <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, is only one
Index: trunk/doc/manual/en_US/dita/topics/ts_host-freq-boost.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/ts_host-freq-boost.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/ts_host-freq-boost.dita	(revision 105134)
@@ -13,12 +13,8 @@
         behavior depends strongly on the specific processor model.
       </p>
-    <p>
-        As a consequence, benchmarking on systems which utilize
-        frequency boosting may produce unstable and non-repeatable
-        results. This is especially true if benchmark runs are short, of
-        the order of seconds. To obtain stable results, benchmarks must
-        be run over longer periods of time and with a constant system
-        load apart from the VM being tested.
-      </p>
+    <p> As a consequence, benchmarking on systems which utilize frequency boosting may produce
+      unstable and nonrepeatable results. This is especially true if benchmark runs are short, of
+      the order of seconds. To obtain stable results, benchmarks must be run over longer periods of
+      time and with a constant system load apart from the VM being tested. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/ts_host-powermgmt.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/ts_host-powermgmt.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/ts_host-powermgmt.dita	(revision 105134)
@@ -11,9 +11,6 @@
         clock behavior.
       </p>
-    <p>
-        Some of the problems may be caused by firmware and/or host
-        operating system bugs. Therefore, updating the firmware and
-        applying operating systems fixes is recommended.
-      </p>
+    <p> Some of the problems may be caused by firmware or host operating system bugs. Therefore,
+      updating the firmware and applying operating system fixes is recommended. </p>
     <p>
         For optimal virtualization performance, the C1E power state
Index: trunk/doc/manual/en_US/dita/topics/ts_ide-sata-flush.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/ts_ide-sata-flush.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/ts_ide-sata-flush.dita	(revision 105134)
@@ -5,11 +5,7 @@
   
   <body>
-    <p>
-        If desired, the virtual disk images can be flushed when the
-        guest issues the IDE FLUSH CACHE command. Normally these
-        requests are ignored for improved performance. The parameters
-        below are only accepted for disk drives. They must not be set
-        for DVD drives.
-      </p>
+    <p> If required, the virtual disk images can be flushed when the guest issues the IDE FLUSH
+      CACHE command. Normally these requests are ignored for improved performance. The parameters
+      below are only accepted for disk drives. They must not be set for DVD drives. </p>
     <p>
         To enable flushing for IDE disks, issue the following command:
Index: trunk/doc/manual/en_US/dita/topics/ts_linux-guest-x11-services.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/ts_linux-guest-x11-services.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/ts_linux-guest-x11-services.dita	(revision 105134)
@@ -22,15 +22,10 @@
         running.
       </p>
-    <p>
-        The <userinput>VBoxClient</userinput> processes create files in the
-        user's home directory with names of the form
-        <filepath>.vboxclient-*.pid</filepath> when they are running in
-        order to prevent a given service from being started twice. It
-        can happen due to misconfiguration that these files are created
-        owned by root and not deleted when the services are stopped,
-        which will prevent them from being started in future sessions.
-        If the services cannot be started, you may wish to check whether
-        these files still exist.
-      </p>
+    <p> The <userinput>VBoxClient</userinput> processes create files in the user's home directory
+      with names of the form <filepath>.vboxclient-*.pid</filepath> when they are running in order
+      to prevent a given service from being started twice. It can happen due to misconfiguration
+      that these files are created owned by root and not deleted when the services are stopped,
+      which will prevent them from being started in future sessions. If the services cannot be
+      started, you may want to check whether these files still exist. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/ts_usb-linux.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/ts_usb-linux.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/ts_usb-linux.dita	(revision 105134)
@@ -5,12 +5,8 @@
   
   <body>
-    <p>
-        If USB is not working on your Linux host, make sure that the
-        current user is a member of the <codeph>vboxusers</codeph>
-        group. Please keep in mind that group membership does not take
-        effect immediately but rather at the next login. If available,
-        the <userinput>newgrp</userinput> command may avoid the need for a
-        logout and login.
-      </p>
+    <p> If USB is not working on your Linux host, make sure that the current user is a member of the
+        <codeph>vboxusers</codeph> group. Please remember that group membership does not take effect
+      immediately but rather at the next login. If available, the <userinput>newgrp</userinput>
+      command may avoid the need for a logout and login. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/ts_win-dnd-uipi.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/ts_win-dnd-uipi.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/ts_win-dnd-uipi.dita	(revision 105134)
@@ -5,21 +5,16 @@
   
   <body>     
-    <p>
-      Microsoft Windows uses technologies like UAC (User Account Control) and
-      UIPI (User Interface Privilege Isolation) to prevent and/or mitigate
-      security issues. By default, UAC and UIPI are enabled.
-    </p>
-    <p>
-      When an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM process is running with a higher so-called
-      privilege level than another process that wants to interact with the
-      VM process via drag'n drop (or system clipboard), Windows prevents this
-      by default due to security reasons. This results in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> not
-      being able to receive any Windows messages for drag'n drop. To make this work, 
-      the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM process must be running with
-      the same (or lower) privilege level as the process it is interacting with
-      using drag'n drop.</p>
+    <p> Microsoft Windows uses technologies like UAC (User Account Control) and UIPI (User Interface
+      Privilege Isolation) to prevent and mitigate security issues. By default, UAC and UIPI are
+      enabled. </p>
+    <p> When an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> VM process is running with a
+      higher so-called privilege level than another process that wants to interact with the VM
+      process using drag'n drop (or system clipboard), Windows prevents this by default due to
+      security reasons. This results in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> not
+      being able to receive any Windows messages for drag'n drop. To make this work, the <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> VM process must be running with the same
+      (or lower) privilege level as the process it is interacting with using drag'n drop.</p>
       
-      <p>Disabling UAC and/or UIPI is not recommended.
-    </p>
+      <p>Disabling UAC or UIPI is not recommended. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/unattended-guest-install-example.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/unattended-guest-install-example.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/unattended-guest-install-example.dita	(revision 105134)
@@ -4,5 +4,4 @@
 <topic xml:lang="en-us" id="unattended-guest-install-example">
                <title>Using VBoxManage Commands for Unattended Guest Installation</title>
-
                <body>
                   <p>
@@ -184,4 +183,3 @@
                   </ol>
                </body>
-
             </topic>
Index: trunk/doc/manual/en_US/dita/topics/vboxbowsolaris11.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vboxbowsolaris11.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/vboxbowsolaris11.dita	(revision 105134)
@@ -29,9 +29,7 @@
     </p>
     <pre xml:space="preserve">$ modinfo | grep vbox</pre>
-    <p>
-      If the output contains "vboxbow", it indicates <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is
-      using the Crossbow network filter driver, while the name "vboxflt"
-      indicates usage of the older STREAMS network filter.
-    </p>
+    <p> If the output contains <i>vboxbow</i>, it indicates <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> is using the Crossbow network filter
+      driver, while the name <i>vboxflt</i> indicates usage of the older STREAMS network filter. </p>
   </body>
   
Index: trunk/doc/manual/en_US/dita/topics/vboxconfigdata-machine-folder.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vboxconfigdata-machine-folder.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/vboxconfigdata-machine-folder.dita	(revision 105134)
@@ -57,8 +57,6 @@
         VMs</filepath>.
       </p>
-    <p>
-        As an example, when you create a virtual machine called "Example
-        VM", <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates the following:
-      </p>
+    <p> As an example, when you create a virtual machine called <i>Example VM</i>, <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> creates the following: </p>
     <ul>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/vboxwatchdog-ballonctrl.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vboxwatchdog-ballonctrl.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/vboxwatchdog-ballonctrl.dita	(revision 105134)
@@ -5,9 +5,6 @@
   
   <body>
-    <p>
-        The memory ballooning control inflates and deflates the memory
-        balloon of VMs based on the VMs free memory and the desired
-        maximum balloon size.
-      </p>
+    <p> The memory ballooning control inflates and deflates the memory balloon of VMs based on the
+      VMs free memory and the requested maximum balloon size. </p>
     <p>
         To set up the memory ballooning control the maximum ballooning
Index: trunk/doc/manual/en_US/dita/topics/vboxwatchdog-hostisln.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vboxwatchdog-hostisln.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/vboxwatchdog-hostisln.dita	(revision 105134)
@@ -62,8 +62,6 @@
       </li>
       <li>
-        <p><codeph>save</codeph>. Saves the current machine state and
-            powers off the VM afterwards. If saving the machine state
-            fails the VM will be paused.
-          </p>
+        <p><codeph>save</codeph>. Saves the current machine state and then powers off the VM. If
+          saving the machine state fails the VM will be paused. </p>
       </li>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/vm-activity-overview.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vm-activity-overview.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/vm-activity-overview.dita	(revision 105134)
@@ -3,10 +3,10 @@
   PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
 <topic xml:lang="en-us" id="vm-activity-overview">
+  <!-- 7.1: Now shows activity info for cloud VMs -->
                <title>VM Activity Overview</title>
-               
                <body>
                   <p>
         The VM Activity Overview tool displays several performance
-        metrics for all running virtual machines and for the host
+        metrics for all running virtual machines and cloud VM instances, and for the host
         system. This provides an overview of system resources used by
         individual virtual machines and the host system.
@@ -38,4 +38,6 @@
         Virtual Machines</b>.
       </p>
+    <p>To show metrics for cloud VMs, right-click the list of virtual machines and select <b
+        outputclass="bold">Show Cloud Virtual Machines</b>. </p>
                   <p>
         To configure the set of metrics to be shown, click
Index: trunk/doc/manual/en_US/dita/topics/vm-activity-session-information.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vm-activity-session-information.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/vm-activity-session-information.dita	(revision 105134)
@@ -4,5 +4,6 @@
 <topic xml:lang="en-us" id="vm-activity-session-information">
                <title>Session Information Dialog</title>
-               
+  <!-- 7.1: metrics info for OCI instances-->  
+  <!-- 7.1: Add pic for cloud VM Activity info? -->
                <body>
                   <p>
@@ -46,10 +47,8 @@
                      </li>
                   </ul>
-                  <p>
-        To display the Session Information dialog, select
-        <b outputclass="bold">Machine</b>,
-        <b outputclass="bold">Session Information</b> in the
-        guest VM.
-      </p>
+                 <note><p>For cloud VMs, only the VM Activity tab is shown.</p></note>
+                  <p> To display session information for a guest virtual machine or a cloud VM,
+      select the VM name in the machine list and click <b>Activity</b> in the machine tools
+      menu.</p>
                  <fig id="fig-vm-session-information">
                    <title>Session Information Dialog, Showing VM Activity Tab</title>
Index: trunk/doc/manual/en_US/dita/topics/vm-info.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vm-info.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/vm-info.dita	(revision 105134)
@@ -4,10 +4,13 @@
 <topic xml:lang="en-us" id="vm-info">
             <title>Monitoring of Virtual Machines</title>
-            
+  <!-- 7.1: metrics info now included for OCI instances -->        
             <body>
                <p>
       <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> includes the following tools for viewing runtime
-      information and changing the configuration of virtual machines.
+      information, configuration details, and performance metrics of virtual machines and cloud VM instances.
     </p>
+              <note><p>To monitor a cloud VM, the Compute Instance Monitoring plugin must be enabled and running on the
+                <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance. See the <ph conkeyref="vbox-conkeyref-phrases/oci"/> 
+                documentation for more details.</p></note>
                <ul>
                   <li>
@@ -15,5 +18,5 @@
                         <b outputclass="bold"> VM Activity Overview.</b>
           Displays an overview of performance metrics for all running
-          VMs.
+          virtual machines and cloud VM instances.
         </p>
                      <p>
@@ -25,8 +28,8 @@
                         <b outputclass="bold">Session Information Dialog.</b>
           Displays configuration and runtime information for the
-          selected guest system.
+          selected guest system or cloud VM.
         </p>
                      <p>
-          See <xref href="vm-activity-session-information.dita#vm-activity-session-information"/>
+          See <xref href="vm-activity-session-information.dita#vm-activity-session-information"/>.
                      </p>
                   </li>
Index: trunk/doc/manual/en_US/dita/topics/vmencryption.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vmencryption.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/vmencryption.dita	(revision 105134)
@@ -17,11 +17,8 @@
       and is decrypted during VM startup.
     </p>
-    <p>
-      Since the DEK is stored as part of the VM configuration file, it
-      is important that the file is kept safe. Losing the DEK means that
-      the data stored in the VM is lost irrecoverably. Having complete
-      and up to date backups of all data related to the VM is the
-      responsibility of the user.
-    </p>
+    <p> Since the DEK is stored as part of the VM configuration file, it is important that the file
+      is kept safe. Losing the DEK means that the data stored in the VM is lost irrecoverably.
+      Having complete and up-to-date backups of all data related to the VM is the responsibility of
+      the user. </p>
     <p>
       The VM, even if it is encrypted, may contain media encrypted with
Index: trunk/doc/manual/en_US/dita/topics/vrde-crypt.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vrde-crypt.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/vrde-crypt.dita	(revision 105134)
@@ -41,9 +41,6 @@
             certificate to the client.
           </p>
-        <p>
-            The <codeph>Security/Method</codeph> VRDE property sets
-            the desired security method, which is used for a connection.
-            Valid values are as follows:
-          </p>
+        <p> The <codeph>Security/Method</codeph> VRDE property sets the required security method,
+          which is used for a connection. Valid values are as follows: </p>
         <ul>
           <li>
Index: trunk/doc/manual/en_US/dita/topics/vrde.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vrde.dita	(revision 105087)
+++ trunk/doc/manual/en_US/dita/topics/vrde.dita	(revision 105134)
@@ -26,9 +26,6 @@
       (VRDP) in such an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension package.
     </p>
-    <p>
-      VRDP is a backwards-compatible extension to Microsoft's Remote
-      Desktop Protocol (RDP). As a result, you can use any standard RDP
-      client to control the remote VM.
-    </p>
+    <p> VRDP is a backward-compatible extension to Microsoft's Remote Desktop Protocol (RDP). As a
+      result, you can use any standard RDP client to control the remote VM. </p>
     <p>
       Even when the extension is installed, the VRDP server is disabled
