Index: trunk/doc/manual/en_US/dita/topics/KnownProblems.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/KnownProblems.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/KnownProblems.dita	(revision 105303)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="KnownProblems">
   <title>Known Issues</title>
-
+  
   <body>
     <p>
@@ -183,6 +183,5 @@
       <li>
         <p>
-          <b outputclass="bold">macOS/Arm64 (Apple silicon) host
-          package</b>
+          <b outputclass="bold">macOS/Arm64 (Apple silicon) host package</b>
         </p>
       </li>
@@ -331,4 +330,4 @@
     </ul>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/arm-host-limitations.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/arm-host-limitations.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/arm-host-limitations.dita	(revision 105303)
@@ -5,5 +5,5 @@
   <!-- 7.1: Arm platform limitations -->
   <body>
-    <p> The following limitations apply when using an Arm platform host:</p>
+    <p>The following limitations apply when using an Arm platform host:</p>
     <ul><li><p>Virtual machines must use an Arm-based guest operating system. Running an x86-based guest operating 
       system on an Arm host platform is not supported. </p></li>
Index: trunk/doc/manual/en_US/dita/topics/auth-config-using.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/auth-config-using.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/auth-config-using.dita	(revision 105303)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="auth-config-using">
   <title>Configuring and Using Authentication</title>
-
+  
   <body>
     <p>
@@ -11,13 +11,11 @@
     <ul>
       <li>
-        <p>
-          When using remote iSCSI storage and the storage server requires authentication, an
+        <p> When using remote iSCSI storage and the storage server requires authentication, an
           initiator secret can optionally be supplied with the <userinput>VBoxManage
-          storageattach</userinput> command. As long as no settings password is provided, by using
+            storageattach</userinput> command. As long as no settings password is provided, by using
           the command line option <codeph>--settingspwfile</codeph>, then this secret is stored
-          <i>unencrypted</i> in the machine configuration and is therefore potentially readable on
+            <i>unencrypted</i> in the machine configuration and is therefore potentially readable on
           the host. See <xref href="storage-iscsi.dita">iSCSI Servers</xref> and <xref
-          href="vboxmanage-storageattach.dita">VBoxManage storageattach</xref>.
-        </p>
+            href="vboxmanage-storageattach.dita">VBoxManage storageattach</xref>. </p>
       </li>
       <li>
@@ -32,4 +30,4 @@
     </ul>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/clone.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/clone.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/clone.dita	(revision 105303)
@@ -135,18 +135,10 @@
       </li>
     </ul>
-    <p>
-      Click <b outputclass="bold">Finish</b> to start the clone
-      operation.
-    </p>
-    <p>
-      The duration of the clone operation depends on the size and number
-      of attached disk images. In addition, the clone operation saves
-      all the differencing disk images of a snapshot.
-    </p>
-    <p>
-      You can also use the <userinput>VBoxManage clonevm</userinput> command to clone a VM. See
-      <xref href="vboxmanage-clonevm.dita"/>.
-    </p>
+    <p>Click <b outputclass="bold">Finish</b> to start the clone operation. </p>
+    <p>The duration of the clone operation depends on the size and number of attached disk images. In addition, the
+      clone operation saves all the differencing disk images of a snapshot. </p>
+    <p>You can also use the <userinput>VBoxManage clonevm</userinput> command to clone a VM. See <xref
+        href="vboxmanage-clonevm.dita"/>. </p>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/cloud-create-cloud-profile.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/cloud-create-cloud-profile.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/cloud-create-cloud-profile.dita	(revision 105303)
@@ -71,50 +71,29 @@
     <ul>
       <li>
-        <p>
-            Automatically, by using the <b outputclass="bold">Cloud
-            Profile Manager</b>. See
-            <xref href="cloud-using-cloud-profile-manager.dita#cloud-using-cloud-profile-manager"/>.
-          </p>
-        <p>
-            The Cloud Profile Manager is a <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> tool that enables
-            you to create, edit, and manage cloud profiles for your
-            cloud service accounts.
-          </p>
+        <p>Automatically, by using the <b outputclass="bold">Cloud Profile Manager</b>. See <xref
+            href="cloud-using-cloud-profile-manager.dita#cloud-using-cloud-profile-manager"/>. </p>
+        <p>The Cloud Profile Manager is a <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> tool that enables you to
+          create, edit, and manage cloud profiles for your cloud service accounts. </p>
       </li>
       <li>
-        <p>
-          Automatically, by using the <userinput>VBoxManage cloudprofile</userinput> command. See
-          <xref href="vboxmanage-cloudprofile.dita"/>.
-        </p>
+        <p>Automatically, by using the <userinput>VBoxManage cloudprofile</userinput> command. See <xref
+            href="vboxmanage-cloudprofile.dita"/>. </p>
       </li>
       <li>
-        <p>
-            Manually, by creating an <filepath>oci_config</filepath>
-            file in your <ph conkeyref="vbox-conkeyref-phrases/product-name"/> global configuration directory.
-            For example, this is
-            <filepath>$HOME/.config/VirtualBox/oci_config</filepath> on
-            a Linux host.
-          </p>
+        <p>Manually, by creating an <filepath>oci_config</filepath> file in your <ph
+            conkeyref="vbox-conkeyref-phrases/product-name"/> global configuration directory. For example, this is
+            <filepath>$HOME/.config/VirtualBox/oci_config</filepath> on a Linux host. </p>
       </li>
       <li>
-        <p>
-            Manually, by creating a <filepath>config</filepath> file in
-            your <ph conkeyref="vbox-conkeyref-phrases/oci"/> configuration directory. For example, this is
-            <filepath>$HOME/.oci/config</filepath> on a Linux host.
-          </p>
-        <p>
-            This is the same file that is used by the <ph conkeyref="vbox-conkeyref-phrases/oci"/> command line
-            interface.
-          </p>
-        <p>
-            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> automatically uses the
-            <filepath>config</filepath> file if no cloud profile file is
-            present in your global configuration directory.
-            Alternatively, you can import this file manually into the
-            Cloud Profile Manager.
-          </p>
+        <p>Manually, by creating a <filepath>config</filepath> file in your <ph conkeyref="vbox-conkeyref-phrases/oci"/>
+          configuration directory. For example, this is <filepath>$HOME/.oci/config</filepath> on a Linux host. </p>
+        <p>This is the same file that is used by the <ph conkeyref="vbox-conkeyref-phrases/oci"/> command line
+          interface. </p>
+        <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> automatically uses the <filepath>config</filepath> file
+          if no cloud profile file is present in your global configuration directory. Alternatively, you can import this
+          file manually into the Cloud Profile Manager. </p>
       </li>
     </ul>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/cloud-export-oci.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/cloud-export-oci.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/cloud-export-oci.dita	(revision 105303)
@@ -78,37 +78,20 @@
           </li>
         </ul>
-        <p>
-            Click <b outputclass="bold">Finish</b> to continue.
-          </p>
+        <p>Click <b outputclass="bold">Finish</b> to continue. </p>
       </li>
       <li>
-        <p>
-            (Optional) Depending on the selection in the
-            <b outputclass="bold">Machine Creation</b> field, the
-            <b outputclass="bold">Appliance Settings</b> page may
-            be displayed before or after export. This screen enables you
-            to configure settings for the cloud instance, such as Shape
-            and Disk Size.
-          </p>
-        <p>
-            Click <b outputclass="bold">Finish</b>. The VM is
-            exported to <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
-          </p>
-        <p>
-            Depending on the <b outputclass="bold">Machine
-            Creation</b> setting, a cloud instance may be started
-            after upload to <ph conkeyref="vbox-conkeyref-phrases/oci"/> is completed.
-          </p>
+        <p>(Optional) Depending on the selection in the <b outputclass="bold">Machine Creation</b> field, the <b
+            outputclass="bold">Appliance Settings</b> page may be displayed before or after export. This screen enables
+          you to configure settings for the cloud instance, such as Shape and Disk Size. </p>
+        <p>Click <b outputclass="bold">Finish</b>. The VM is exported to <ph conkeyref="vbox-conkeyref-phrases/oci"/>. </p>
+        <p>Depending on the <b outputclass="bold">Machine Creation</b> setting, a cloud instance may be started after
+          upload to <ph conkeyref="vbox-conkeyref-phrases/oci"/> is completed. </p>
       </li>
       <li>
-        <p>
-            Monitor the export process by using the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console.
-          </p>
+        <p>Monitor the export process by using the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console. </p>
       </li>
     </ol>
-    <p>
-        You can also use the <userinput>VBoxManage export</userinput> command to export a VM to
-        <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="vboxmanage-export.dita"/>.
-    </p>
+    <p>You can also use the <userinput>VBoxManage export</userinput> command to export a VM to <ph
+        conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="vboxmanage-export.dita"/>. </p>
   </body>
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/cloud-import-oci.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/cloud-import-oci.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/cloud-import-oci.dita	(revision 105303)
@@ -33,19 +33,13 @@
           </image>
         </fig>
-        <p>
-            Click <b outputclass="bold">Finish</b> to import the
-            instance from <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
-          </p>
+        <p>Click <b outputclass="bold">Finish</b> to import the instance from <ph conkeyref="vbox-conkeyref-phrases/oci"
+          />. </p>
       </li>
       <li>
-        <p>
-            Monitor the import process by using the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console.
-          </p>
+        <p>Monitor the import process by using the <ph conkeyref="vbox-conkeyref-phrases/oci"/> Console. </p>
       </li>
     </ol>
-    <p>
-        You can also use the <userinput>VBoxManage import</userinput> command to import an instance
-        from <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="vboxmanage-import.dita"/>.
-    </p>
+    <p>You can also use the <userinput>VBoxManage import</userinput> command to import an instance from <ph
+        conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="vboxmanage-import.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 105300)
+++ trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-networks.dita	(revision 105303)
@@ -4,70 +4,40 @@
   <title>Using a Cloud Network</title>
   <body>
-    <p>
-        A cloud network is a type of network that can be used for
-        connections from a local VM to a remote <ph conkeyref="vbox-conkeyref-phrases/oci"/> cloud instance.
-      </p>
-    <p>
-        To create and use a cloud network, do the following:
-      </p>
+    <p>A cloud network is a type of network that can be used for connections from a local VM to a remote <ph
+        conkeyref="vbox-conkeyref-phrases/oci"/> cloud instance. </p>
+    <p>To create and use a cloud network, do the following: </p>
     <ol>
       <li>
-        <p>
-            Set up a virtual cloud network on <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
-          </p>
-        <p>
-            The following steps create and configure a virtual cloud
-            network (VCN) on <ph conkeyref="vbox-conkeyref-phrases/oci"/>. The VCN is used to tunnel network
-            traffic across the cloud.
-          </p>
+        <p>Set up a virtual cloud network on <ph conkeyref="vbox-conkeyref-phrases/oci"/>. </p>
+        <p>The following steps create and configure a virtual cloud network (VCN) on <ph
+            conkeyref="vbox-conkeyref-phrases/oci"/>. The VCN is used to tunnel network traffic across the cloud. </p>
         <ol>
           <li>
-            <p>
-                Ensure that you have a cloud profile for connecting to
-                <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See <xref href="cloud-create-cloud-profile.dita#cloud-create-cloud-profile"/>.
-              </p>
+            <p>Ensure that you have a cloud profile for connecting to <ph conkeyref="vbox-conkeyref-phrases/oci"/>. See
+                <xref href="cloud-create-cloud-profile.dita#cloud-create-cloud-profile"/>. </p>
           </li>
           <li>
-            <p>
-                Run the following <userinput>VBoxManage cloud</userinput>
-                command:
-              </p>
+            <p>Run the following <userinput>VBoxManage cloud</userinput> command: </p>
             <pre xml:space="preserve">VBoxManage cloud --provider="OCI" --profile="vbox-oci" network setup</pre>
-            <p>
-                where <codeph>vbox-oci</codeph> is the name of your
-                cloud profile.
-              </p>
-            <p>
-                Other options are available for the <userinput>VBoxManage cloud network
-                setup</userinput> command, to enable you to configure details for the VCN. For
-                example, you can configure the operating system used for the cloud gateway instance
-                and the IP address range used by the tunneling network. See <xref href="vboxmanage-cloud.dita"/>.
-            </p>
-            <p>
-                For best results, use an Oracle Linux 7 instance for the
-                cloud gateway. This is the default option.
-              </p>
+            <p>where <codeph>vbox-oci</codeph> is the name of your cloud profile. </p>
+            <p>Other options are available for the <userinput>VBoxManage cloud network setup</userinput> command, to
+              enable you to configure details for the VCN. For example, you can configure the operating system used for
+              the cloud gateway instance and the IP address range used by the tunneling network. See <xref
+                href="vboxmanage-cloud.dita"/>. </p>
+            <p>For best results, use an Oracle Linux 7 instance for the cloud gateway. This is the default option. </p>
           </li>
         </ol>
       </li>
       <li>
-        <p>
-            Register the new cloud network with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
-          </p>
-        <p>
-            Use the <b outputclass="bold">Cloud Networks</b> tab
-            in the <b outputclass="bold">Network Manager</b>
-            tool. See
-            <xref href="network-manager-cloud-network-tab.dita#network-manager-cloud-network-tab"/>.
-          </p>
+        <p>Register the new cloud network with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
+        <p>Use the <b outputclass="bold">Cloud Networks</b> tab in the <b outputclass="bold">Network Manager</b> tool.
+          See <xref href="network-manager-cloud-network-tab.dita#network-manager-cloud-network-tab"/>. </p>
       </li>
       <li>
-        <p>
-            Add cloud network adaptors to the local VMs that will use
-            the cloud network. See <xref href="network_cloud.dita#network_cloud"/>.
-          </p>
+        <p>Add cloud network adaptors to the local VMs that will use the cloud network. See <xref
+            href="network_cloud.dita#network_cloud"/>. </p>
       </li>
     </ol>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-profile-manager.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-profile-manager.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-profile-manager.dita	(revision 105303)
@@ -125,5 +125,5 @@
       <li>
         <p>Click <b outputclass="bold">Properties</b> to show the cloud profile settings. </p>
-        <p> Double-click the appropriate field to change the value. </p>
+        <p>Double-click the appropriate field to change the value. </p>
       </li>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/cloud-vm-add.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/cloud-vm-add.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/cloud-vm-add.dita	(revision 105303)
@@ -11,5 +11,5 @@
     <ol>
       <li>
-        <p> Click a cloud profile in the <b outputclass="bold">OCI</b> group. </p>
+        <p>Click a cloud profile in the <b outputclass="bold">OCI</b> group. </p>
         <p>The cloud VMs for the selected cloud profile are displayed. </p>
       </li>
Index: trunk/doc/manual/en_US/dita/topics/collect-debug-info.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/collect-debug-info.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/collect-debug-info.dita	(revision 105303)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="collect-debug-info">
   <title>Collecting Debugging Information</title>
-
+  
   <body>
     <p>
@@ -56,8 +56,6 @@
     <p><ph>http://www.virtualbox.org/wiki/Core_dump</ph>.
       </p>
-    <p>
-        You can also use <userinput>VBoxManage debugvm</userinput> to create a dump of a complete
-        virtual machine. See <xref href="vboxmanage-debugvm.dita">VBoxManage debugvm</xref>.
-    </p>
+    <p> You can also use <userinput>VBoxManage debugvm</userinput> to create a dump of a complete
+      virtual machine. See <xref href="vboxmanage-debugvm.dita">VBoxManage debugvm</xref>. </p>
     <p>
         For network related problems, it is often helpful to capture a
@@ -81,4 +79,4 @@
       </p>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/glossentry-com.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/glossentry-com.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/glossentry-com.dita	(revision 105303)
@@ -7,6 +7,7 @@
     COM enables applications to provide application programming interfaces which can be
     accessed from various other programming languages and applications.
-        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> makes use of COM both internally and externally to provide a 
+    <ph conkeyref="vbox-conkeyref-phrases/product-name"/> makes use of COM both internally and externally to provide a 
     comprehensive API to third party developers.
   </glossdef>
 </glossentry>
+
Index: trunk/doc/manual/en_US/dita/topics/glossentry-vrde.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/glossentry-vrde.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/glossentry-vrde.dita	(revision 105303)
@@ -5,6 +5,6 @@
   <glossdef>
     VirtualBox Remote Desktop Extension. This interface is built into
-        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to allow <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension packages 
-        to supply remote access to virtual machines. An <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension 
+    <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to allow <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 
+    extension packages to supply remote access to virtual machines. An <ph conkeyref="vbox-conkeyref-phrases/product-name"/> extension 
     package by Oracle provides VRDP support.
     See <xref href="vrde.dita">Remote Display (VRDP Support)</xref>.
Index: trunk/doc/manual/en_US/dita/topics/guestadd-guestprops.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/guestadd-guestprops.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/guestadd-guestprops.dita	(revision 105303)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="guestadd-guestprops">
   <title>Guest Properties</title>
-
+  
   <body>
     <p>
@@ -51,10 +51,8 @@
       virtual machine's <b outputclass="bold">Machine</b> menu.
     </p>
-    <p>
-      A more flexible way to use this channel is with the <userinput>VBoxManage
-      guestproperty</userinput> command. See <xref href="vboxmanage-guestproperty.dita"/>.
-      For example, to have <i>all</i> the available guest properties for a given running VM
-      listed with their respective values, use this command:
-    </p>
+    <p> A more flexible way to use this channel is with the <userinput>VBoxManage
+                guestproperty</userinput> command. See <xref href="vboxmanage-guestproperty.dita"/>.
+            For example, to have <i>all</i> the available guest properties for a given running VM
+            listed with their respective values, use this command: </p>
     <pre xml:space="preserve">$ VBoxManage guestproperty enumerate "Windows Vista III"
 VirtualBox Command Line Management Interface Version <varname>version-number</varname>
Index: trunk/doc/manual/en_US/dita/topics/gui-machine-list.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/gui-machine-list.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/gui-machine-list.dita	(revision 105303)
@@ -9,8 +9,8 @@
     <ul>
       <li>
-        <p> Right-click the virtual machine name, to display menu options. </p>
+        <p>Right-click the virtual machine name, to display menu options. </p>
       </li>
       <li>
-        <p> Click the Machine Tools menu icon, to the right of the virtual machine name. See <xref
+        <p>Click the Machine Tools menu icon, to the right of the virtual machine name. See <xref
             href="gui-tools-machine.dita#gui-tools-machine"/>. </p>
       </li>
Index: trunk/doc/manual/en_US/dita/topics/harddiskcontrollers.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/harddiskcontrollers.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/harddiskcontrollers.dita	(revision 105303)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="harddiskcontrollers">
   <title>Hard Disk Controllers</title>
-
+  
   <body>
     <p>
@@ -109,8 +109,6 @@
           virtual disks to it.
         </p>
-        <p>
-            To change the IDE compatibility mode settings for the SATA controller, see <xref
-            href="vboxmanage-storagectl.dita"/>.
-        </p>
+        <p> To change the IDE compatibility mode settings for the SATA controller, see <xref
+            href="vboxmanage-storagectl.dita"/>. </p>
       </li>
       <li>
@@ -298,4 +296,4 @@
     </p>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/hostossupport.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/hostossupport.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/hostossupport.dita	(revision 105303)
@@ -84,5 +84,5 @@
           </li>
         </ul>
-        <p> It should be possible to use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> on
+        <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
Index: trunk/doc/manual/en_US/dita/topics/install-mac-performing.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/install-mac-performing.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/install-mac-performing.dita	(revision 105303)
@@ -9,5 +9,5 @@
     <ol>
       <li>
-        <p> Double-click the <filepath>dmg</filepath> file, to mount the contents. </p>
+        <p>Double-click the <filepath>dmg</filepath> file, to mount the contents. </p>
       </li>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/install-win-performing.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/install-win-performing.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/install-win-performing.dita	(revision 105303)
@@ -48,5 +48,5 @@
         <p>See, for example: <ph>http://www.python.org/download/windows/</ph>. </p>
         <note>
-          <p> Python version 3 is required. Python version 2.x is no longer 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-running.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/intro-running.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/intro-running.dita	(revision 105303)
@@ -14,9 +14,7 @@
       </li>
       <li>
-        <p>
-          Select the VM's entry in the machine list in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, and
-          click <b outputclass="bold">Start</b> in the toolbar
-          the top of the window.
-        </p>
+        <p> Select the VM's name in the machine list in <ph
+            conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, and click <b outputclass="bold">Start</b>
+          in the toolbar the top of the window. </p>
       </li>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/mountingadditionsiso.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/mountingadditionsiso.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/mountingadditionsiso.dita	(revision 105303)
@@ -71,9 +71,9 @@
           </li>
           <li>
-            <p>On macOS hosts, this file is in the application bundle of <ph
+            <p> On macOS hosts, this file is in the application bundle of <ph
                 conkeyref="vbox-conkeyref-phrases/product-name"/>. Right-click the <ph
                 conkeyref="vbox-conkeyref-phrases/product-name"/> icon in Finder and choose <b
                 outputclass="bold">Show Package Contents</b>. The file is located in the
-                <filepath>Contents/MacOS</filepath> folder.</p>
+                <filepath>Contents/MacOS</filepath> folder. </p>
           </li>
           <li>
Index: trunk/doc/manual/en_US/dita/topics/nested-virt.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/nested-virt.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/nested-virt.dita	(revision 105303)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="nested-virt">
   <title>Nested Virtualization</title>
-
+  
   <body>
     <p>
@@ -32,12 +32,10 @@
       </li>
       <li>
-        <p>
-          Use the <codeph>--nested-hw-virt</codeph> option of the <userinput>VBoxManage
-          modifyvm</userinput> command to enable or disable nested virtualization. See
-          <xref href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>.
-        </p>
+        <p> Use the <codeph>--nested-hw-virt</codeph> option of the <userinput>VBoxManage
+            modifyvm</userinput> command to enable or disable nested virtualization. See <xref
+            href="vboxmanage-modifyvm.dita">VBoxManage modifyvm</xref>. </p>
       </li>
     </ul>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/nestedpaging.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/nestedpaging.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/nestedpaging.dita	(revision 105303)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="nestedpaging">
   <title>Nested Paging and VPIDs</title>
-
+  
   <body>
     <p>
@@ -41,11 +41,9 @@
           Core i7 (Nehalem) processors.
         </p>
-        <p>
-          If nested paging is enabled, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> hypervisor can also use <i>large
-          pages</i> to reduce TLB usage and overhead. This can yield a performance improvement of
-          up to 5%. To enable this feature for a VM, you use the <userinput>VBoxManage modifyvm --large-pages</userinput>
-          command. See <xref href="vboxmanage-modifyvm.dita">VBoxManage
-          modifyvm</xref>.
-        </p>
+        <p> If nested paging is enabled, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> hypervisor can also use <i>large
+            pages</i> to reduce TLB usage and overhead. This can yield a performance improvement of
+          up to 5%. To enable this feature for a VM, you use the <userinput>VBoxManage modifyvm
+            --large-pages</userinput> command. See <xref href="vboxmanage-modifyvm.dita">VBoxManage
+            modifyvm</xref>. </p>
         <p>
           If you have an Intel CPU with EPT, please consult
@@ -67,4 +65,4 @@
     </ul>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/ovf-export-appliance.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/ovf-export-appliance.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/ovf-export-appliance.dita	(revision 105303)
@@ -51,31 +51,17 @@
       </li>
       <li>
-        <p>
-            Click <b outputclass="bold">Next</b> to show the
-            <b outputclass="bold">Appliance Settings</b> page.
-          </p>
-        <p>
-            You can edit settings for the virtual appliance. For
-            example, you can change the name of the virtual appliance or
-            add product information, such as vendor details or license
-            text.
-          </p>
-        <p>
-            Double-click the appropriate field to change its value.
-          </p>
+        <p>Click <b outputclass="bold">Next</b> to show the <b outputclass="bold">Appliance Settings</b> page. </p>
+        <p>You can edit settings for the virtual appliance. For example, you can change the name of the virtual
+          appliance or add product information, such as vendor details or license text. </p>
+        <p>Double-click the appropriate field to change its value. </p>
       </li>
       <li>
-        <p>
-            Click <b outputclass="bold">Finish</b> to begin the
-            export process. Note that this operation might take several
-            minutes.
-          </p>
+        <p>Click <b outputclass="bold">Finish</b> to begin the export process. Note that this operation might take
+          several minutes. </p>
       </li>
     </ol>
-    <p>
-      You can use the <userinput>VBoxManage export</userinput> command to export an appliance. See
-      <xref href="vboxmanage-export.dita"/>.
-    </p>
+    <p>You can use the <userinput>VBoxManage export</userinput> command to export an appliance. See <xref
+        href="vboxmanage-export.dita"/>. </p>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/serialports.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/serialports.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/serialports.dita	(revision 105303)
@@ -3,46 +3,25 @@
 <topic xml:lang="en-us" id="serialports">
   <title>Serial Ports</title>
-
+  
   <body>
-    <p>
-      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports the use of virtual serial ports in a
-      virtual machine.
-    </p>
-    <p>
-      Ever since the original IBM PC, personal computers have been
-      equipped with one or two serial ports, also called COM ports by
-      DOS and Windows. Serial ports were commonly used with modems, and
-      some computer mice used to be connected to serial ports before USB
-      became commonplace.
-    </p>
-    <p>
-      While serial ports are no longer as common as they used to be,
-      there are still some important uses left for them. For example,
-      serial ports can be used to set up a primitive network over a
-      null-modem cable, in case Ethernet is not available. Also, serial
-      ports are indispensable for system programmers needing to do
-      kernel debugging, since kernel debugging software usually
-      interacts with developers over a serial port. With virtual serial
-      ports, system programmers can do kernel debugging on a virtual
-      machine instead of needing a real computer to connect to.
-    </p>
-    <p>
-      If a virtual serial port is enabled, the guest OS sees a standard
-      16550A compatible UART device. Other UART types can be configured
-      using the <userinput>VBoxManage modifyvm</userinput> command. Both
-      receiving and transmitting data is supported. How this virtual
-      serial port is then connected to the host is configurable, and the
-      details depend on your host OS.
-    </p>
-    <p>
-      You can use either the Settings tabs or the <userinput>VBoxManage</userinput> command to set
-      up virtual serial ports. For the latter, see <xref href="vboxmanage-modifyvm.dita"/> for
-      information on the <codeph>--uart</codeph>, <codeph>--uart-mode</codeph> and
-      <codeph>--uart-type</codeph> options.
-    </p>
-    <p>
-      You can configure up to four virtual serial ports per virtual
-      machine. For each device, you must set the following:
-    </p>
+    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports the use of virtual serial ports in a virtual
+      machine. </p>
+    <p>Ever since the original IBM PC, personal computers have been equipped with one or two serial ports, also called
+      COM ports by DOS and Windows. Serial ports were commonly used with modems, and some computer mice used to be
+      connected to serial ports before USB became commonplace. </p>
+    <p>While serial ports are no longer as common as they used to be, there are still some important uses left for them.
+      For example, serial ports can be used to set up a primitive network over a null-modem cable, in case Ethernet is
+      not available. Also, serial ports are indispensable for system programmers needing to do kernel debugging, since
+      kernel debugging software usually interacts with developers over a serial port. With virtual serial ports, system
+      programmers can do kernel debugging on a virtual machine instead of needing a real computer to connect to. </p>
+    <p>If a virtual serial port is enabled, the guest OS sees a standard 16550A compatible UART device. Other UART types
+      can be configured using the <userinput>VBoxManage modifyvm</userinput> command. Both receiving and transmitting
+      data is supported. How this virtual serial port is then connected to the host is configurable, and the details
+      depend on your host OS. </p>
+    <p>You can use either the Settings tabs or the <userinput>VBoxManage</userinput> command to set up virtual serial
+      ports. For the latter, see <xref href="vboxmanage-modifyvm.dita"/> for information on the <codeph>--uart</codeph>,
+        <codeph>--uart-mode</codeph> and <codeph>--uart-type</codeph> options. </p>
+    <p>You can configure up to four virtual serial ports per virtual machine. For each device, you must set the
+      following: </p>
     <ol>
       <li>
Index: trunk/doc/manual/en_US/dita/topics/settings-motherboard.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/settings-motherboard.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/settings-motherboard.dita	(revision 105303)
@@ -31,9 +31,7 @@
             settings), the network, or none of these.
           </p>
-        <p>
-            If you select <b outputclass="bold">Network</b>, the VM will attempt to boot from a
-            network using the PXE mechanism. This needs to be configured in detail on the command
-            line. See <xref href="vboxmanage-modifyvm.dita"/>.
-        </p>
+        <p>If you select <b outputclass="bold">Network</b>, the VM will attempt to boot from a network using the PXE
+          mechanism. This needs to be configured in detail on the command line. See <xref
+            href="vboxmanage-modifyvm.dita"/>. </p>
       </li>
       <li>
@@ -121,25 +119,16 @@
       </li>
     </ul>
-    <p>
-        In addition, you can turn off the <b outputclass="bold">Advanced
-        Configuration and Power Interface (ACPI)</b> which
-        <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to the guest OS by default.
-      </p>
-    <p>
-        ACPI is the current industry standard to allow OSes to recognize hardware, configure
-        motherboards and other devices and manage power. As most computers contain this feature and
-        Windows and Linux support ACPI, it is also enabled by default in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. ACPI
-        can only be turned off using the command line. See <xref href="vboxmanage-modifyvm.dita"/>.
-    </p>
+    <p>In addition, you can turn off the <b outputclass="bold">Advanced Configuration and Power Interface (ACPI)</b>
+      which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to the guest OS by default. </p>
+    <p>ACPI is the current industry standard to allow OSes to recognize hardware, configure motherboards and other
+      devices and manage power. As most computers contain this feature and Windows and Linux support ACPI, it is also
+      enabled by default in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. ACPI can only be turned off using the
+      command line. See <xref href="vboxmanage-modifyvm.dita"/>. </p>
     <note>
-      <p>
-          All Windows OSes install different kernels, depending on
-          whether ACPI is available. This means that ACPI <i>must
-          not be turned off</i> after installation of a Windows
-          guest OS. However, turning it on after installation will have
-          no effect.
-        </p>
+      <p>All Windows OSes install different kernels, depending on whether ACPI is available. This means that ACPI
+          <i>must not be turned off</i> after installation of a Windows guest OS. However, turning it on after
+        installation will have no effect. </p>
     </note>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/snapshots-contents.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/snapshots-contents.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/snapshots-contents.dita	(revision 105303)
@@ -6,70 +6,39 @@
                
                <body>
-                  <p>
-        Think of a snapshot as a point in time that you have preserved.
-        More formally, a snapshot consists of the following:
-      </p>
+                  <p>Think of a snapshot as a point in time that you have preserved. More formally, a snapshot consists
+      of the following: </p>
                   <ul>
                      <li>
-                        <p>
-            The snapshot contains a complete copy of the VM settings,
-            including the hardware configuration, so that when you
-            restore a snapshot, the VM settings are restored as well.
-            For example, if you changed the hard disk configuration or
-            the VM's system settings, that change is undone when you
-            restore the snapshot.
-          </p>
-                        <p>
-            The copy of the settings is stored in the machine
-            configuration, an XML text file, and thus occupies very
-            little space.
-          </p>
+                        <p>The snapshot contains a complete copy of the VM settings, including the hardware
+          configuration, so that when you restore a snapshot, the VM settings are restored as well. For example, if you
+          changed the hard disk configuration or the VM's system settings, that change is undone when you restore the
+          snapshot. </p>
+                        <p>The copy of the settings is stored in the machine configuration, an XML text file, and thus
+          occupies very little space. </p>
                      </li>
                      <li>
-                        <p>
-            The complete state of all the virtual disks attached to the
-            machine is preserved. Going back to a snapshot means that
-            all changes that had been made to the machine's disks, file
-            by file and bit by bit, will be undone as well. Files that
-            were since created will disappear, files that were deleted
-            will be restored, changes to files will be reverted.
-          </p>
-                        <p>
-            Strictly speaking, this is only true for virtual hard disks
-            in "normal" mode. You can configure disks to behave
-            differently with snapshots, see
-            <xref href="hdimagewrites.dita#hdimagewrites"/>. In technical terms, it is
-            not the virtual disk itself that is restored when a snapshot
-            is restored. Instead, when a snapshot is taken,
-            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates differencing images which contain
-            only the changes since the snapshot were taken. When the
-            snapshot is restored, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> throws away that
-            differencing image, thus going back to the previous state.
-            This is both faster and uses less disk space. For the
-            details, which can be complex, see
-            <xref href="diffimages.dita#diffimages"/>.
-          </p>
-                        <p>
-            Creating the differencing image as such does not occupy much
-            space on the host disk initially, since the differencing
-            image will initially be empty and grow dynamically later
-            with each write operation to the disk. The longer you use
-            the machine after having created the snapshot, however, the
-            more the differencing image will grow in size.
-          </p>
+                        <p>The complete state of all the virtual disks attached to the machine is preserved. Going back
+          to a snapshot means that all changes that had been made to the machine's disks, file by file and bit by bit,
+          will be undone. Files that were since created will disappear, files that were deleted will be restored,
+          changes to files will be reverted. </p>
+                        <p>Strictly speaking, this is only true for virtual hard disks in "normal" mode. You can
+          configure disks to behave differently with snapshots, see <xref href="hdimagewrites.dita#hdimagewrites"/>. In
+          technical terms, it is not the virtual disk itself that is restored when a snapshot is restored. Instead, when
+          a snapshot is taken, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates differencing images which
+          contain only the changes since the snapshot were taken. When the snapshot is restored, <ph
+            conkeyref="vbox-conkeyref-phrases/product-name"/> throws away that differencing image, thus going back to
+          the previous state. This is both faster and uses less disk space. For the details, which can be complex, see
+            <xref href="diffimages.dita#diffimages"/>. </p>
+                        <p>Creating the differencing image as such does not occupy much space on the host disk
+          initially, since the differencing image will initially be empty and grow dynamically later with each write
+          operation to the disk. The longer you use the machine after having created the snapshot, however, the more the
+          differencing image will grow in size. </p>
                      </li>
                      <li>
-                        <p>
-            If you took a snapshot while the machine was running, the
-            memory state of the machine is also saved in the snapshot.
-            This is in the same way that memory can be saved when you
-            close a VM window. When you restore such a snapshot,
-            execution resumes at exactly the point when the snapshot was
-            taken.
-          </p>
-                        <p>
-            The memory state file can be as large as the memory size of
-            the VM and will therefore occupy considerable disk space.
-          </p>
+                        <p>If you took a snapshot while the machine was running, the memory state of the machine is also
+          saved in the snapshot. This is in the same way that memory can be saved when you close a VM window. When you
+          restore such a snapshot, execution resumes at exactly the point when the snapshot was taken. </p>
+                        <p>The memory state file can be as large as the memory size of the VM and will therefore occupy
+          considerable disk space. </p>
                      </li>
                   </ul>
Index: trunk/doc/manual/en_US/dita/topics/vbox-auth.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vbox-auth.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/vbox-auth.dita	(revision 105303)
@@ -3,13 +3,11 @@
 <topic xml:lang="en-us" id="vbox-auth">
   <title>RDP Authentication</title>
-
+  
   <body>
-    <p>
-        For each virtual machine that is remotely accessible using RDP, you can individually
-        determine if and how client connections are authenticated. For this, use the
+    <p> For each virtual machine that is remotely accessible using RDP, you can individually
+      determine if and how client connections are authenticated. For this, use the
         <userinput>VBoxManage modifyvm</userinput> command with the
-        <codeph>--vrde-auth-type</codeph> option. See <xref href="vboxmanage-modifyvm.dita">
-        VBoxManage modifyvm</xref>. The following methods of authentication are available:
-    </p>
+        <codeph>--vrde-auth-type</codeph> option. See <xref href="vboxmanage-modifyvm.dita"
+        >VBoxManage modifyvm</xref>. The following methods of authentication are available: </p>
     <ul>
       <li>
@@ -160,4 +158,4 @@
       </p>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/vboxconfigdata-machine-folder.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vboxconfigdata-machine-folder.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/vboxconfigdata-machine-folder.dita	(revision 105303)
@@ -3,5 +3,5 @@
 <topic xml:lang="en-us" id="vboxconfigdata-machine-folder">
   <title>The Machine Folder</title>
-
+  
   <body>
     <p>
@@ -89,12 +89,11 @@
         change the location of its snapshots folder in the VM settings.
       </p>
-    <p>
-        You can change the default machine folder by selecting <b outputclass="bold">Preferences</b>
-        from the <b outputclass="bold">File</b> menu in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> main window. Then, in
-        the displayed window, click on the <b outputclass="bold">General</b> tab. Alternatively, use
-        the <userinput>VBoxManage setproperty machinefolder</userinput> command. See
-        <xref href="vboxmanage-setproperty.dita">VBoxManage setproperty</xref>.
-    </p>
+    <p> You can change the default machine folder by selecting <b outputclass="bold">Preferences</b>
+      from the <b outputclass="bold">File</b> menu in the <ph
+        conkeyref="vbox-conkeyref-phrases/product-name"/> main window. Then, in the displayed
+      window, click the <b outputclass="bold">General</b> tab. Alternatively, use the
+        <userinput>VBoxManage setproperty machinefolder</userinput> command. See <xref
+        href="vboxmanage-setproperty.dita">VBoxManage setproperty</xref>. </p>
   </body>
-
+  
 </topic>
Index: trunk/doc/manual/en_US/dita/topics/vboxheadless-examples.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vboxheadless-examples.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/vboxheadless-examples.dita	(revision 105303)
@@ -1,16 +1,16 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic rev="refsect1" id="vboxheadless-examples"><title>Examples</title><body>
-    
-    
+<topic rev="refsect1" id="vboxheadless-examples">
+  <title>Examples</title>
+  <body>
     <p rev="para">
       The following command starts the <codeph rev="literal">ol7u4</codeph> VM:
     </p>
-<screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u4"</screen>
+    <screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u4"</screen>
     <p rev="para">
       The following command starts the <codeph rev="literal">ol7u6</codeph> VM in
       the Paused state.
     </p>
-<screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u6" --start-paused</screen>
+    <screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u6" --start-paused</screen>
     <p rev="para">
       The following command starts the <codeph rev="literal">ol7u6</codeph> VM and
@@ -18,4 +18,5 @@
       <filepath rev="filename">ol7u6-recording</filepath> WebM file.
     </p>
-<screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u6" --capture --filename ol7u6-recording.webm</screen>
-  </body></topic>
+    <screen xml:space="preserve">$ VBoxHeadless --startvm "ol7u6" --capture --filename ol7u6-recording.webm</screen>
+  </body>
+</topic>
Index: trunk/doc/manual/en_US/dita/topics/vboxheadless-see-also.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/vboxheadless-see-also.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/vboxheadless-see-also.dita	(revision 105303)
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="utf-8"?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic rev="refsect1" id="vboxheadless-see-also"><title>See Also</title><body>
-    
-    <p rev="para">
-      <xref href="vboxmanage-list.dita#vboxmanage-list"/>,
-      <xref href="vboxmanage-startvm.dita#vboxmanage-startvm"/>
-    </p>
-  </body></topic>
+<topic rev="refsect1" id="vboxheadless-see-also">
+  <title>See Also</title>
+  <body>
+    <p rev="para"><xref href="vboxmanage-list.dita#vboxmanage-list"/>,
+      <xref href="vboxmanage-startvm.dita#vboxmanage-startvm"/></p>
+  </body>
+</topic>
Index: trunk/doc/manual/en_US/dita/topics/virt-why-useful.dita
===================================================================
--- trunk/doc/manual/en_US/dita/topics/virt-why-useful.dita	(revision 105300)
+++ trunk/doc/manual/en_US/dita/topics/virt-why-useful.dita	(revision 105303)
@@ -12,71 +12,40 @@
                <ul>
                   <li>
-                     <p>
-                        <b outputclass="bold">Running multiple operating systems
-          simultaneously.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to run
-          more than one OS at a time. This way, you can run software
-          written for one OS on another, such as Windows software on
-          Linux or a Mac, without having to reboot to use it. Since you
-          can configure what kinds of <i>virtual</i>
-          hardware should be presented to each such OS, you can install
-          an old OS such as DOS or OS/2 even if your real computer's
-          hardware is no longer supported by that OS.
-        </p>
+                     <p><b outputclass="bold">Running multiple operating systems simultaneously.</b>
+          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to run more than one OS at a time. This way,
+          you can run software written for one OS on another, such as Windows software on Linux or a Mac, without having
+          to reboot to use it. Since you can configure what kinds of <i>virtual</i> hardware should be presented to each
+          such OS, you can install an old OS such as DOS or OS/2 even if your real computer's hardware is no longer
+          supported by that OS. </p>
                   </li>
                   <li>
-                     <p>
-                        <b outputclass="bold">Easier software
-          installations.</b> Software vendors can use virtual
-          machines to ship entire software configurations. For example,
-          installing a complete mail server solution on a real machine
-          can be a tedious task. With <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, such a complex
-          setup, often called an <i>appliance</i>, can be
-          packed into a virtual machine. Installing and running a mail
-          server becomes as easy as importing such an appliance into
-          <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.
-        </p>
+                     <p><b outputclass="bold">Easier software installations.</b> Software vendors can use virtual
+          machines to ship entire software configurations. For example, installing a complete mail server solution on a
+          real machine can be a tedious task. With <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, such a complex
+          setup, often called an <i>appliance</i>, can be packed into a virtual machine. Installing and running a mail
+          server becomes as easy as importing such an appliance into <ph conkeyref="vbox-conkeyref-phrases/product-name"
+          />. </p>
                   </li>
                   <li>
-                     <p>
-                        <b outputclass="bold">Testing and disaster
-          recovery.</b> Once installed, a virtual machine and its
-          virtual hard disks can be considered a
-          <i>container</i> that can be arbitrarily frozen,
-          woken up, copied, backed up, and transported between hosts.
-        </p>
-                     <p>
-          Using virtual machines enables you to build and test a
-          multi-node networked service, for example. Issues with
-          networking, operating system, and software configuration can
-          be investigated easily.
-        </p>
-                     <p>
-          In addition to that, with the use of another <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
-          feature called <i>snapshots</i>, one can save a
-          particular state of a virtual machine and revert back to that
-          state, if necessary. This way, one can freely experiment with
-          a computing environment. If something goes wrong, such as
-          problems after installing software or infecting the guest with
-          a virus, you can easily switch back to a previous snapshot and
-          avoid the need of frequent backups and restores.
-        </p>
-                     <p>
-          Any number of snapshots can be created, allowing you to travel
-          back and forward in virtual machine time. You can delete
-          snapshots while a VM is running to reclaim disk space.
-        </p>
+                     <p><b outputclass="bold">Testing and disaster recovery.</b> Once installed, a virtual machine and
+          its virtual hard disks can be considered a <i>container</i> that can be arbitrarily frozen, woken up, copied,
+          backed up, and transported between hosts. </p>
+                     <p>Using virtual machines enables you to build and test a multinode networked
+          service, for example. Issues with networking, operating system, and software configuration
+          can be investigated easily. </p>
+                     <p>In addition to that, with the use of another <ph conkeyref="vbox-conkeyref-phrases/product-name"
+          /> feature called <i>snapshots</i>, one can save a particular state of a virtual machine and revert back to
+          that state, if necessary. This way, one can freely experiment with a computing environment. If something goes
+          wrong, such as problems after installing software or infecting the guest with a virus, you can easily switch
+          back to a previous snapshot and avoid the need of frequent backups and restores. </p>
+                     <p>Any number of snapshots can be created, allowing you to travel back and forward in virtual
+          machine time. You can delete snapshots while a VM is running to reclaim disk space. </p>
                   </li>
                   <li>
-                     <p>
-                        <b outputclass="bold">Infrastructure consolidation.</b>
-          Virtualization can significantly reduce hardware and
-          electricity costs. Most of the time, computers today only use
-          a fraction of their potential power and run with low average
-          system loads. A lot of hardware resources as well as
-          electricity is thereby wasted. So, instead of running many
-          such physical computers that are only partially used, one can
-          pack many virtual machines onto a few powerful hosts and
-          balance the loads between them.
-        </p>
+                     <p><b outputclass="bold">Infrastructure consolidation.</b> Virtualization can significantly reduce
+          hardware and electricity costs. Most of the time, computers today only use a fraction of their potential power
+          and run with low average system loads. A lot of hardware resources as well as electricity is thereby wasted.
+          So, instead of running many such physical computers that are only partially used, one can pack many virtual
+          machines onto a few powerful hosts and balance the loads between them. </p>
                   </li>
                </ul>
