Index: /trunk/doc/manual/en_US/dita/UserManual.ditamap
===================================================================
--- /trunk/doc/manual/en_US/dita/UserManual.ditamap	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/UserManual.ditamap	(revision 108921)
@@ -11,5 +11,5 @@
          <published>
             <completed>
-          <month>March</month>
+          <month>April</month>
           <year>2025</year>
         </completed>
@@ -105,5 +105,5 @@
             <topicref href="topics/unattended-guest-install-example.dita"/>
   </chapter>
-  <chapter href="topics/BasicConcepts.dita" chunk="to-content">
+  <chapter href="topics/working-with-vms.dita" chunk="to-content">
     <topicref href="topics/intro-running.dita">
       <topicref href="topics/intro-starting-vm-first-time.dita"/>
Index: unk/doc/manual/en_US/dita/topics/BasicConcepts.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/BasicConcepts.dita	(revision 108920)
+++ 	(revision )
@@ -1,26 +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="BasicConcepts">
-  <title>Working with Virtual Machines</title>
-  
-  <body>
-    <p>This chapter provides detailed steps for configuring an <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
-      virtual machine (VM). For an introduction to <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and steps to
-      get your first virtual machine running, see <xref href="Introduction.dita#Introduction"/>. </p>
-    <p>You have considerable latitude when deciding what virtual hardware to provide to the guest. Use virtual hardware
-      to communicate with the host system or with other guests. For example, you can use virtual hardware in the
-      following ways: </p>
-    <ul>
-      <li>
-        <p>Have <ph conkeyref="vbox-conkeyref-phrases/product-name"/> present an ISO CD-ROM image to a guest system as
-          if it were a physical CD-ROM. </p>
-      </li>
-      <li>
-        <p>Provide a guest system access to the physical network through its virtual network card. </p>
-      </li>
-      <li>
-        <p>Provide the host system, other guests, and computers on the Internet access to the guest system. </p>
-      </li>
-    </ul>
-  </body>
-</topic>
Index: /trunk/doc/manual/en_US/dita/topics/Introduction.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/Introduction.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/Introduction.dita	(revision 108921)
@@ -1,7 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="Introduction">
+<topic xml:lang="en-us" id="ct_about-virtualbox">
   <title>About <ph conkeyref="vbox-conkeyref-phrases/product-name"/></title>
-  
   <body>
     <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> is a cross-platform virtualization application. That means it extends the capabilities of your existing computer so that it can run multiple operating systems, inside multiple virtual machines (VMs), at the same time. As an example, you can run Windows and Linux on your Mac, run Windows Server on your Linux server, run Linux on your Windows PC, and so on, all alongside your existing applications.</p>
Index: /trunk/doc/manual/en_US/dita/topics/Security.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/Security.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/Security.dita	(revision 108921)
@@ -2,5 +2,5 @@
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
 <topic xml:lang="en-us" id="Security">
-  <title><?oxy_comment_start author="Mhari Duncan" timestamp="20250131T161634+0000" comment="This can probably be removed, and security built in to the normal tasks"?>Security Guide<?oxy_comment_end?></title>
+  <title>Security Guide</title>
   
   <body/>
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 108920)
+++ /trunk/doc/manual/en_US/dita/topics/cloud-create-cloud-profile.dita	(revision 108921)
@@ -71,6 +71,5 @@
     <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>Automatically, by using the <b outputclass="bold">Cloud Profile Manager</b>. See <xref href="cloud-using-cloud-profile-manager.dita"/>.</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>
Index: /trunk/doc/manual/en_US/dita/topics/cloud-integration.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/cloud-integration.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/cloud-integration.dita	(revision 108921)
@@ -5,22 +5,7 @@
   
   <body>
-    <p>This section describes how to use the features of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to
-      integrate with <ph conkeyref="vbox-conkeyref-phrases/oci"/>. </p>
-    <p>Integrating with <ph conkeyref="vbox-conkeyref-phrases/oci"/> involves the following steps: </p>
-    <ul>
-      <li>
-        <p><b outputclass="bold">Prepare for <ph conkeyref="vbox-conkeyref-phrases/oci"/>
-          Integration.</b> Before using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with <ph conkeyref="vbox-conkeyref-phrases/oci"/>
-          there are some initial configuration steps you may need to do.
-          See <xref href="cloud-integration-steps.dita#cloud-integration-steps"/>.
-        </p>
-      </li>
-      <li>
-        <p><b outputclass="bold">Use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with
-          <ph conkeyref="vbox-conkeyref-phrases/oci"/>.</b><xref href="cloud-vbox-oci-tasks.dita#cloud-vbox-oci-tasks"/>
-          describes how you can use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with <ph conkeyref="vbox-conkeyref-phrases/oci"/>.
-        </p>
-      </li>
-    </ul>
+    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> can integrate with <ph conkeyref="vbox-conkeyref-phrases/oci"/>. For example you can create cloud VMs, or import Compute instances to <ph conkeyref="vbox-conkeyref-phrases/product-name"/>.</p>
+    <p><xref href="cloud-vbox-oci-tasks.dita#cloud-vbox-oci-tasks"/> describes how you can use <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with <ph conkeyref="vbox-conkeyref-phrases/oci"/>.</p>
+    <p>Before using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with <ph conkeyref="vbox-conkeyref-phrases/oci"/> there are some initial configuration steps you may need to do. See <xref href="cloud-integration-steps.dita#cloud-integration-steps"/>.</p>
   </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 108920)
+++ /trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-profile-manager.dita	(revision 108921)
@@ -1,7 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="cloud-using-cloud-profile-manager">
+<topic xml:lang="en-us" id="tk_using-cloud-profile-manager">
   <title>Using the Cloud Profile Manager</title>
-  
   <body>
     <p>To open the Cloud Profile Manager click <b outputclass="bold">File</b>, <b>Tools</b>, <b outputclass="bold">Cloud Profile Manager</b> in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. </p>
@@ -12,9 +11,7 @@
       </li>
       <li>
-        <p>To create a cloud profile by importing settings from your <ph conkeyref="vbox-conkeyref-phrases/oci"/>
-          configuration file. </p>
+        <p>To create a cloud profile by importing settings from your <ph conkeyref="vbox-conkeyref-phrases/oci"/> configuration file. </p>
       </li>
     </ul>
   </body>
-  
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/cloud-vm.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/cloud-vm.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/cloud-vm.dita	(revision 108921)
@@ -4,44 +4,28 @@
   <title>Using Cloud Virtual Machines</title>
   <body>
-    <p>A cloud virtual machine (<i>cloud VM</i>) is a type of VM that represents an instance on a cloud service. Cloud
-      VMs are shown in the machine list in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, in the same way as local
-      VMs are. </p>
-    <p>By using cloud VMs you can create, manage, and control your <ph conkeyref="vbox-conkeyref-phrases/oci"/>
-      instances from <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. </p>
+    <p>A cloud virtual machine (<i>cloud VM</i>) is a type of VM that represents an instance on a cloud service. Cloud VMs are shown in the machine list in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, in the same way as local VMs are.</p>
+    <p>By using cloud VMs you can create, manage, and control your <ph conkeyref="vbox-conkeyref-phrases/oci"/> instances from <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.</p>
     <note>
-      <p>Cloud VMs do not install, export, or import instances to the <ph
-          conkeyref="vbox-conkeyref-phrases/product-name"/> host. All operations are done remotely on the cloud service. </p>
+      <p>Cloud VMs do not install, export, or import instances to the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> host. All operations are done remotely on the cloud service.</p>
     </note>
-    <p>Cloud VMs can be used to do the following tasks in <ph conkeyref="vbox-conkeyref-phrases/oci"/>: </p>
+    <p>Cloud VMs can be used to do the following tasks in <ph conkeyref="vbox-conkeyref-phrases/oci"/>:</p>
     <ul>
       <li>
-        <p><b outputclass="bold">Create a new <ph conkeyref="vbox-conkeyref-phrases/oci"/>
-            instance.</b> See <xref href="cloud-vm-new.dita#cloud-vm-new"/>.
-          </p>
+        <p><b outputclass="bold">Create a new <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance.</b> See <xref href="cloud-vm-new.dita#cloud-vm-new"/>.</p>
       </li>
       <li>
-        <p><b outputclass="bold">Use an existing <ph conkeyref="vbox-conkeyref-phrases/oci"/>
-            instance.</b> See <xref href="cloud-vm-add.dita#cloud-vm-add"/>.
-          </p>
+        <p><b outputclass="bold">Use an existing <ph conkeyref="vbox-conkeyref-phrases/oci"/> 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>
+        <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>
-        <p><b outputclass="bold">Configure an <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance.</b> You can change settings for the instance, such as display name. See <xref href="cloud-vm-settings.dita#cloud-vm-settings"/>. </p>
+        <p><b outputclass="bold">Configure an <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance.</b> You can change settings for the instance, such as display name. See <xref href="cloud-vm-settings.dita#cloud-vm-settings"/>.</p>
       </li>
       <li>
-        <p><b outputclass="bold">Control an <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance.</b>
-            Stop, start, and terminate the instance. See
-            <xref href="cloud-vm-control.dita#cloud-vm-control"/>
-                        </p>
+        <p><b outputclass="bold">Control an <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance.</b> Stop, start, and terminate the instance. See <xref href="cloud-vm-control.dita#cloud-vm-control"/>.</p>
       </li>
       <li>
-        <p><b outputclass="bold">Create a console connection to an
-            <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance</b>. See
-            <xref href="cloud-vm-instance-console.dita#cloud-vm-instance-console"/>.
-          </p>
+        <p><b outputclass="bold">Create a console connection to an <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance</b>. See <xref href="cloud-vm-instance-console.dita#cloud-vm-instance-console"/>.</p>
       </li>
     </ul>
Index: /trunk/doc/manual/en_US/dita/topics/config-network.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/config-network.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/config-network.dita	(revision 108921)
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic id="config-network">
+<topic id="tk_config-network">
     <title>Configure Networking</title>
     <body>
Index: /trunk/doc/manual/en_US/dita/topics/configbasics.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/configbasics.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/configbasics.dita	(revision 108921)
@@ -16,5 +16,5 @@
           settings as required. </li>
       </ol></p>
-    <p>The settings are described in detail in <xref href="BasicConcepts.dita#BasicConcepts"/>. </p>
+    <p>The settings are described in detail in <xref href="settings-window.dita"/>.</p>
     <p>Even more parameters are available when using the <userinput>VBoxManage</userinput> command line interface. See
         <xref href="vboxmanage.dita#vboxmanage"/>. </p>
Index: /trunk/doc/manual/en_US/dita/topics/create-floppy-disk-image.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/create-floppy-disk-image.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/create-floppy-disk-image.dita	(revision 108921)
@@ -1,13 +1,11 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="create-floppy-disk-image">
+<topic xml:lang="en-us" id="tk_create-floppy-disk-image">
   <title>Creating a Virtual Floppy Disk Image</title>
-  
   <body>
     <p>Use the <b outputclass="bold">Floppy Disk Creator</b> tool to create a floppy disk image. </p>
     <ol>
       <li>
-        <p>Display the <b outputclass="bold">Floppy Disks</b> tab in Virtual Media Manager and click <b
-            outputclass="bold">Create</b>. </p>
+        <p>Display the <b outputclass="bold">Floppy Disks</b> tab in Virtual Media Manager and click <b outputclass="bold">Create</b>. </p>
         <p>The <b outputclass="bold">Floppy Disk Creator</b> tool is shown. </p>
       </li>
@@ -16,18 +14,11 @@
         <ul>
           <li>
-            <p><b outputclass="bold">File Path:</b> The name and
-                location of the floppy disk image.
-              </p>
+            <p><b outputclass="bold">File Path:</b> The name and location of the floppy disk image. </p>
           </li>
           <li>
-            <p><b outputclass="bold">Size:</b> Select from the
-                list of supported floppy disk sizes.
-              </p>
+            <p><b outputclass="bold">Size:</b> Select from the list of supported floppy disk sizes. </p>
           </li>
           <li>
-            <p><b outputclass="bold">Format Disk as FAT 12:</b>
-                This is the default format used for most floppy disks.
-                For an unformatted disk, do not select this option.
-              </p>
+            <p><b outputclass="bold">Format Disk as FAT 12:</b> This is the default format used for most floppy disks. For an unformatted disk, do not select this option. </p>
           </li>
         </ul>
@@ -36,9 +27,7 @@
         <p>Create the floppy disk image file. </p>
         <p>Click <b outputclass="bold">Create</b>. </p>
-        <p>The floppy disk image is created in the specified location and added to the <b outputclass="bold">Floppy
-            Disks</b> tab in Virtual Media Manager. </p>
+        <p>The floppy disk image is created in the specified location and added to the <b outputclass="bold">Floppy Disks</b> tab in Virtual Media Manager. </p>
       </li>
     </ol>
   </body>
-  
 </topic>
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 108920)
+++ /trunk/doc/manual/en_US/dita/topics/create-optical-disk-image.dita	(revision 108921)
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="create-optical-disk-image">
+<topic xml:lang="en-us" id="tk_create-optical-disk-image">
   <title>Creating a Virtual Optical Disk Image</title>
   <body>
@@ -8,6 +8,5 @@
     <ol>
       <li>
-        <p>Display the <b outputclass="bold">Optical Disks</b> tab in Virtual Media Manager and click <b
-            outputclass="bold">Create</b>. </p>
+        <p>Display the <b outputclass="bold">Optical Disks</b> tab in Virtual Media Manager and click <b outputclass="bold">Create</b>. </p>
         <p>The <b outputclass="bold">VISO Creator</b> tool is shown. </p>
       </li>
@@ -17,13 +16,10 @@
           <li>
             <p>Configure the name of the ISO file. </p>
-            <p>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>
+            <p>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>
           </li>
           <li>
             <p>Add files to your virtual ISO. </p>
-            <p>In the <b outputclass="bold">Host File System</b> pane, select files to copy from the host system to the
-              virtual ISO. </p>
-            <p>Click <b outputclass="bold">Add Items To VISO</b>. The files are displayed in the <b outputclass="bold"
-                >VISO Content</b> pane. </p>
+            <p>In the <b outputclass="bold">Host File System</b> pane, select files to copy from the host system to the virtual ISO. </p>
+            <p>Click <b outputclass="bold">Add Items To VISO</b>. The files are displayed in the <b outputclass="bold">VISO Content</b> pane. </p>
             <p>The following file operations are also available: </p>
             <ul>
@@ -32,17 +28,12 @@
               </li>
               <li>
-                <p>To remove files from the virtual ISO, select files in the <b outputclass="bold">VISO Content</b> pane
-                  and click <b outputclass="bold">Remove Items From VISO</b>. </p>
+                <p>To remove files from the virtual ISO, select files in the <b outputclass="bold">VISO Content</b> pane and click <b outputclass="bold">Remove Items From VISO</b>. </p>
               </li>
               <li>
-                <p>To remove <i>all</i> files from the virtual ISO, click <b outputclass="bold">Reset the VISO
-                    Content</b>. </p>
+                <p>To remove <i>all</i> files from the virtual ISO, click <b outputclass="bold">Reset the VISO Content</b>. </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>
+                <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>
@@ -57,4 +48,3 @@
     </ol>
   </body>
-  
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/create-virtual-hard-disk-image.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/create-virtual-hard-disk-image.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/create-virtual-hard-disk-image.dita	(revision 108921)
@@ -1,12 +1,10 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="create-virtual-hard-disk-image">
+<topic xml:lang="en-us" id="tk_create-virtual-hard-disk-image">
   <title>Creating a Virtual Hard Disk Image </title>
-  
   <body>
     <ol>
       <li>
-        <p>Display the <b outputclass="bold">Hard Disks</b> tab in Virtual Media Manager and click <b outputclass="bold"
-            >Create</b>. </p>
+        <p>Display the <b outputclass="bold">Hard Disks</b> tab in Virtual Media Manager and click <b outputclass="bold">Create</b>. </p>
       </li>
       <li>
@@ -17,12 +15,9 @@
       </li>
       <li>
-        <p>Configure the location of the virtual hard disk file and use the slider to set the size limit for the virtual
-          hard disk. </p>
+        <p>Configure the location of the virtual hard disk file and use the slider to set the size limit for the virtual hard disk. </p>
         <p>Click <b outputclass="bold">Finish</b> to create the virtual hard disk file. </p>
-        <p>The virtual hard disk image is created in the specified location and added to the <b outputclass="bold">Hard
-            Disks</b> tab in Virtual Media Manager. </p>
+        <p>The virtual hard disk image is created in the specified location and added to the <b outputclass="bold">Hard Disks</b> tab in Virtual Media Manager. </p>
       </li>
     </ol>
   </body>
-  
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/create-vm-hardware.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/create-vm-hardware.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/create-vm-hardware.dita	(revision 108921)
@@ -1,5 +1,5 @@
 <?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-hardware">
+<topic xml:lang="en-us" id="tk_create-vm-hardware">
   <title>Specify Virtual Hardware</title>
   <body>
Index: /trunk/doc/manual/en_US/dita/topics/create-vm-name-os.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/create-vm-name-os.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/create-vm-name-os.dita	(revision 108921)
@@ -1,5 +1,5 @@
 <?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-name-os">
+<topic xml:lang="en-us" id="tk_create-vm-name-os">
   <title>Specify Name and Operating System</title>
   <body>
Index: /trunk/doc/manual/en_US/dita/topics/create-vm-unattended-install.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/create-vm-unattended-install.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/create-vm-unattended-install.dita	(revision 108921)
@@ -1,5 +1,5 @@
 <?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-unattended-install">
+<topic xml:lang="en-us" id="tk_create-vm-unattended-install">
   <title>Configure Unattended Installation of Guest OS</title>
   <body>
Index: /trunk/doc/manual/en_US/dita/topics/create-vm.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/create-vm.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/create-vm.dita	(revision 108921)
@@ -1,5 +1,5 @@
 <?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">
+<topic xml:lang="en-us" id="tk_create-vm">
   <title>Creating a New Virtual Machine</title>
   <body>
Index: /trunk/doc/manual/en_US/dita/topics/efi.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/efi.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/efi.dita	(revision 108921)
@@ -9,5 +9,5 @@
     <p>To switch back to using the BIOS:</p>
     <pre xml:space="preserve">VBoxManage modifyvm "VM name" --firmware bios</pre>
-    <p>Most modern macOS and Windows releases require UEFI.</p>
+    <p>Most modern macOS and Windows releases require UEFI. All Arm VMs require UEFI.</p>
     <p>Another possible use of UEFI in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is development and testing of UEFI applications, without booting any OS.</p>
   </body>
Index: /trunk/doc/manual/en_US/dita/topics/emul-hardware.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/emul-hardware.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/emul-hardware.dita	(revision 108921)
@@ -58,7 +58,5 @@
       </li>
       <li>
-        <p><b outputclass="bold">Audio.</b> See
-          <xref href="settings-audio.dita#settings-audio"/>.
-        </p>
+        <p><b outputclass="bold">Audio.</b> See <xref href="settings-audio.dita"/>.</p>
       </li>
     </ul>
Index: /trunk/doc/manual/en_US/dita/topics/extensions.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/extensions.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/extensions.dita	(revision 108921)
@@ -1,5 +1,5 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="extensions">
+<topic xml:lang="en-us" id="ct_extensions">
   <title>Managing <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Extensions</title>
   <body>
Index: /trunk/doc/manual/en_US/dita/topics/features-overview.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/features-overview.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/features-overview.dita	(revision 108921)
@@ -51,5 +51,5 @@
         <li>
           <p><b outputclass="bold">Multigeneration branched snapshots.</b>
-            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can save arbitrary snapshots of the state of the VM. You can go back in time and revert the VM to any such snapshot and start an alternative VM configuration from there, effectively creating a whole snapshot tree. This can be useful for experimenting with a computing environment, testing, or troubleshooting without the need for frequent backups and restores. See <xref href="snapshots.dita#snapshots"/>. You can create and delete snapshots while the VM is running.</p>
+            <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can save arbitrary snapshots of the state of the VM. You can go back in time and revert the VM to any such snapshot and start an alternative VM configuration from there, effectively creating a whole snapshot tree. This can be useful for experimenting with a computing environment, testing, or troubleshooting without the need for frequent backups and restores. See <xref href="snapshots.dita"/>. You can create and delete snapshots while the VM is running.</p>
         </li>
         <li>
Index: /trunk/doc/manual/en_US/dita/topics/generalsettings.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/generalsettings.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/generalsettings.dita	(revision 108921)
@@ -1,7 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="generalsettings">
+<topic xml:lang="en-us" id="ct_generalsettings">
   <title>General Settings</title>
-  
   <body>
     <p>In the <b outputclass="bold">Settings</b> window, under <b outputclass="bold">General</b>, you can configure the most fundamental aspects of the virtual machine such as memory and essential hardware. The following tabs are available.</p>
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 108920)
+++ /trunk/doc/manual/en_US/dita/topics/guestadd-gc-file-manager.dita	(revision 108921)
@@ -1,14 +1,11 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="guestadd-gc-file-manager">
+<topic xml:lang="en-us" id="ct_guestadd-gc-file-manager">
   <title>Guest Control File Manager</title>
   <body>
-    <p>If you have Guest Additions installed, you can use the Guest Control File Manager to copy files between a virtual
-      machine (VM) and the host system. You can also create new folders, rename files and delete files. </p>
-    <p>This feature is useful when the VM window of a guest is not visible. For example, when the guest is running in
-      headless mode. </p>
+    <p>If you have Guest Additions installed, you can use the Guest Control File Manager to copy files between a virtual machine (VM) and the host system. You can also create new folders, rename files and delete files. </p>
+    <p>This feature is useful when the VM window of a guest is not visible. For example, when the guest is running in headless mode. </p>
     <note>
-      <p>To use the Guest Control File Manager, the guest must be running. For powered-off guests, it is disabled
-        automatically. </p>
+      <p>To use the Guest Control File Manager, the guest must be running. For powered-off guests, it is disabled automatically. </p>
     </note>
   </body>
Index: /trunk/doc/manual/en_US/dita/topics/guestadd-install.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/guestadd-install.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/guestadd-install.dita	(revision 108921)
@@ -19,5 +19,5 @@
           <ol>
             <li>
-              <p>From the <uicontrol>Devices</uicontrol> menu, choose <uicontrol>Optical Drives</uicontrol>, and then<uicontrol> Choose/Create a Disk Image</uicontrol>. This displays the <xref href="virtual-media-manager.dita#virtual-media-manager"/>.</p>
+              <p>From the <uicontrol>Devices</uicontrol> menu, choose <uicontrol>Optical Drives</uicontrol>, and then<uicontrol> Choose/Create a Disk Image</uicontrol>. This displays <xref href="virtual-media-manager.dita"/>.</p>
             </li>
             <li>
Index: /trunk/doc/manual/en_US/dita/topics/hdimagewrites.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/hdimagewrites.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/hdimagewrites.dita	(revision 108921)
@@ -17,7 +17,5 @@
           disk. This is the default image mode.
         </p>
-        <p>When you take a snapshot of your virtual machine as described in <xref href="snapshots.dita#snapshots"/>, the
-          state of a normal hard disk is recorded together with the snapshot, and when reverting to the snapshot, its
-          state will be fully reset. </p>
+        <p>When you take a snapshot of your virtual machine as described in <xref href="snapshots.dita"/>, the state of a normal hard disk is recorded together with the snapshot, and when reverting to the snapshot, its state will be fully reset. </p>
         <p>The image file itself is not reset. Instead, when a snapshot is taken, <ph
             conkeyref="vbox-conkeyref-phrases/product-name"/>
Index: /trunk/doc/manual/en_US/dita/topics/installation-packages.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/installation-packages.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/installation-packages.dita	(revision 108921)
@@ -29,5 +29,5 @@
       <li>
         <p>
-          <b outputclass="bold"><?oxy_comment_start author="Mhari Duncan" timestamp="20241213T115547+0000" comment="Put limitations here, after list?"?>macOS / Intel hosts<?oxy_comment_end?></b>:</p>
+          <b outputclass="bold">macOS / Intel hosts</b>:</p>
         <ul>
           <li>
@@ -80,9 +80,5 @@
       </li>
       <li>
-        <p><b outputclass="bold">Solaris hosts</b><?oxy_comment_start author="Mhari Duncan" timestamp="20241213T115909+0000" comment="Removed
-The following versions are supported with the restrictions listed in Known Limitations: 
-
-Need to state restrictions somewhere"?> and<?oxy_comment_end?>
-          <b outputclass="bold">Solaris 11 IPS hosts</b></p>
+        <p><b outputclass="bold">Solaris hosts</b> and <b outputclass="bold">Solaris 11 IPS hosts</b></p>
         <ul>
           <li>
Index: /trunk/doc/manual/en_US/dita/topics/intro-removable-media-changing.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/intro-removable-media-changing.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/intro-removable-media-changing.dita	(revision 108921)
@@ -1,20 +1,11 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="intro-removable-media-changing">
+<topic xml:lang="en-us" id="ct_intro-removable-media-changing">
   <title>Changing Removable Media</title>
-  
   <body>
-    <p>While a virtual machine is running, you can change removable media in the <b outputclass="bold">Devices</b> menu
-      of the VM's window. Here you can select in detail what <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
-      presents to your VM as a CD, DVD, or floppy drive. </p>
-    <p>The settings are the same as those available for the VM in the <b outputclass="bold">Settings</b> window of <ph
-        conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. But as the <b outputclass="bold">Settings</b> window is disabled
-      while the VM is in the Running or Saved state, the <b outputclass="bold">Devices</b> menu saves you from having to
-      shut down and restart the VM every time you want to change media. </p>
-    <p>Using the <b outputclass="bold">Devices</b> menu, you can attach the host drive to the guest or select a floppy
-      or DVD image, as described in <xref href="settings-storage.dita#settings-storage"/>. </p>
-    <p>The <b outputclass="bold">Devices</b> menu also includes an option for creating a virtual ISO (VISO) from
-      selected files on the host. </p>
+    <p>While a virtual machine is running, you can change removable media in the <b outputclass="bold">Devices</b> menu of the VM's window. Here you can select in detail what <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to your VM as a CD, DVD, or floppy drive. </p>
+    <p>The settings are the same as those available for the VM in the <b outputclass="bold">Settings</b> window of <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. But as the <b outputclass="bold">Settings</b> window is disabled while the VM is in the Running or Saved state, the <b outputclass="bold">Devices</b> menu saves you from having to shut down and restart the VM every time you want to change media. </p>
+    <p>Using the <b outputclass="bold">Devices</b> menu, you can attach the host drive to the guest or select a floppy or DVD image, as described in <xref href="settings-storage.dita"/>.</p>
+    <p>The <b outputclass="bold">Devices</b> menu also includes an option for creating a virtual ISO (VISO) from selected files on the host. </p>
   </body>
-  
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/intro-removing.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/intro-removing.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/intro-removing.dita	(revision 108921)
@@ -22,5 +22,5 @@
       </li>
     </ul>
-    <p>For information about removing or moving a disk image file from <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, see <xref href="virtual-media-manager.dita#virtual-media-manager"/>.</p>
+    <p>For information about removing or moving a disk image file from <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, see <xref href="virtual-media-manager.dita"/>.</p>
   </body>
   
Index: /trunk/doc/manual/en_US/dita/topics/intro-running.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/intro-running.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/intro-running.dita	(revision 108921)
@@ -5,5 +5,5 @@
   
   <body>
-    <p> To start a virtual machine (VM), you have the following options: </p>
+    <p> To start a virtual machine (VM), you have the following options:</p>
     <ul>
       <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 108920)
+++ /trunk/doc/manual/en_US/dita/topics/intro-save-machine-state.dita	(revision 108921)
@@ -1,55 +1,27 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="intro-save-machine-state">
+<topic xml:lang="en-us" id="ct_save-machine-state">
   <title>Saving the State of the Machine</title>
   <body>
-    <p>When you click the <b outputclass="bold">Close</b> button of your virtual machine window, at the top right of the
-      window, just like you would close any other window on your system, <ph
-        conkeyref="vbox-conkeyref-phrases/product-name"/> asks you whether you want to save or power off the VM. As a
-      shortcut, you can also press <b outputclass="bold">Host key + Q</b>. </p>
-    <p>
-        The difference between the three options is crucial. They mean
-        the following:
-      </p>
+    <p>When you click the <b outputclass="bold">Close</b> button of your virtual machine window, at the top right of the window, just like you would close any other window on your system, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> asks you whether you want to save or power off the VM. As a shortcut, you can also press <b outputclass="bold">Host key + Q</b>. </p>
+    <p> The difference between the three options is crucial. They mean the following: </p>
     <ul>
       <li>
-        <p><b outputclass="bold">Save the machine state:</b>
-            With this option, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
-            <i>freezes</i> the virtual machine by
-            completely saving its state to your local disk.
-          </p>
-        <p>When you start the VM again later, you will find that the VM continues exactly where it was left off. All
-          your programs will still be open, and your computer resumes operation. Saving the state of a virtual machine
-          is thus in some ways similar to suspending a laptop computer by closing its lid. </p>
+        <p><b outputclass="bold">Save the machine state:</b> With this option, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
+          <i>freezes</i> the virtual machine by completely saving its state to your local disk. </p>
+        <p>When you start the VM again later, you will find that the VM continues exactly where it was left off. All your programs will still be open, and your computer resumes operation. Saving the state of a virtual machine is thus in some ways similar to suspending a laptop computer by closing its lid. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Send the shutdown signal.</b>
-            This will send an ACPI shutdown signal to the virtual
-            machine, which has the same effect as if you had pressed the
-            power button on a real computer. This should trigger a
-            proper shutdown mechanism from within the VM.
-          </p>
+        <p><b outputclass="bold">Send the shutdown signal.</b> This will send an ACPI shutdown signal to the virtual machine, which has the same effect as if you had pressed the power button on a real computer. This should trigger a proper shutdown mechanism from within the VM. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Power off the machine:</b> With
-            this option, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also stops running the virtual
-            machine, but <i>without</i> saving its state.
-          </p>
+        <p><b outputclass="bold">Power off the machine:</b> With this option, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also stops running the virtual machine, but <i>without</i> saving its state. </p>
         <note type="caution">
-          <p>This is equivalent to pulling the power plug on a real computer without shutting it down properly. If you
-            start the machine again after powering it off, your OS will have to reboot completely and may begin a
-            lengthy check of its virtual system disks. As a result, this should not normally be done, since it can
-            potentially cause data loss or an inconsistent state of the guest system on disk. </p>
+          <p>This is equivalent to pulling the power plug on a real computer without shutting it down properly. If you start the machine again after powering it off, your OS will have to reboot completely and may begin a lengthy check of its virtual system disks. As a result, this should not normally be done, since it can potentially cause data loss or an inconsistent state of the guest system on disk. </p>
         </note>
-        <p>As an exception, if your virtual machine has any snapshots, see <xref href="snapshots.dita#snapshots"/>, you
-          can use this option to quickly <b outputclass="bold">restore the current snapshot</b> of the virtual machine.
-          In that case, powering off the machine will discard the current state and any changes made since the previous
-          snapshot was taken will be lost. </p>
+        <p>As an exception, if your virtual machine has any snapshots, see <xref href="snapshots.dita"/>, you can use this option to quickly <b outputclass="bold">restore the current snapshot</b> of the virtual machine. In that case, powering off the machine will discard the current state and any changes made since the previous snapshot was taken will be lost. </p>
       </li>
     </ul>
-    <p>The <b outputclass="bold">Discard</b> button in the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window
-      discards a virtual machine's saved state. This has the same effect as powering it off, and the same warnings
-      apply. </p>
+    <p>The <b outputclass="bold">Discard</b> button in the <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> window discards a virtual machine's saved state. This has the same effect as powering it off, and the same warnings apply. </p>
   </body>
-  
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/keyb_mouse_normal.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/keyb_mouse_normal.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/keyb_mouse_normal.dita	(revision 108921)
@@ -17,9 +17,5 @@
       keyboard and the mouse. Both cannot own the keyboard and mouse at the same time. You will see a <i>second</i>
       mouse pointer which is always confined to the limits of the VM window. You activate the VM by clicking inside it. </p>
-    <p>To return ownership of keyboard and mouse to your host OS, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
-      reserves a special key on your keyboard: the <i>Host key</i>. By default, this is the <i>right Ctrl key</i> on
-      your keyboard. On a Mac host, the default Host key is the left Command key. You can change this default using the
-      Preferences window. See <xref href="preferences.dita#preferences"/>. The current setting for the Host key is
-      always displayed at the bottom right of your VM window. </p>
+    <p>To return ownership of keyboard and mouse to your host OS, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> reserves a special key on your keyboard: the <i>Host key</i>. By default, this is the <i>right Ctrl key</i> on your keyboard. On a Mac host, the default Host key is the left Command key. You can change this default using the Preferences window. See <xref href="preferences.dita"/>. The current setting for the Host key is always displayed at the bottom right of your VM window. </p>
     <fig id="fig-host-key">
       <title>Host Key Setting on the Virtual Machine Status Bar</title>
Index: /trunk/doc/manual/en_US/dita/topics/log-viewer.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/log-viewer.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/log-viewer.dita	(revision 108921)
@@ -1,11 +1,8 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="log-viewer">
+<topic xml:lang="en-us" id="ct_log-viewer">
   <title>The Log Viewer</title>
-  
   <body>
-    <p>Every time you start up a VM, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates a log file that
-      records system configuration and events. The <b outputclass="bold">Log Viewer</b> is a <ph
-        conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> tool that enables you to view and analyze system logs. </p>
+    <p>Every time you start up a VM, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> creates a log file that records system configuration and events. The <b outputclass="bold">Log Viewer</b> is a <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> tool that enables you to view and analyze system logs. </p>
     <p>To display the Log Viewer, do either of the following: </p>
     <ul>
@@ -17,70 +14,39 @@
       </li>
     </ul>
-    <p>Log messages for the VM are displayed in tabs in the Log Viewer window. See <xref href="collect-debug-info.dita"
-        >Collecting Debugging Information</xref> for details of the various log files generated by <ph
-        conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
+    <p>Log messages for the VM are displayed in tabs in the Log Viewer window. See <xref href="collect-debug-info.dita">Collecting Debugging Information</xref> for details of the various log files generated by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
     <p>If you select multiple VMs in the machine list, logs are listed for each VM. </p>
     <p>The toolbar of the Log Viewer includes the following options: </p>
     <ul>
       <li>
-        <p><b outputclass="bold">Save:</b> Exports the contents of
-          the selected log file to a text file. Specify the destination
-          filename and location in the displayed dialog.
-        </p>
+        <p><b outputclass="bold">Save:</b> Exports the contents of the selected log file to a text file. Specify the destination filename and location in the displayed dialog. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Find:</b> Searches for a text
-          string in the log file.
-        </p>
+        <p><b outputclass="bold">Find:</b> Searches for a text string in the log file. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Filter:</b> Uses filter terms to
-          display specific types of log messages. Common log message
-          terms used by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, such as Audio and NAT, are
-          included by default. Select one or more terms from the
-          drop-down list. To add your own filter term, enter the text
-          string in the text box field.
-        </p>
+        <p><b outputclass="bold">Filter:</b> Uses filter terms to display specific types of log messages. Common log message terms used by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, such as Audio and NAT, are included by default. Select one or more terms from the drop-down list. To add your own filter term, enter the text string in the text box field. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Bookmark:</b> Saves the location of a log message, enabling you to
-          find it quickly. To create a bookmark, either click the line number, or select some text
-          and then click <b outputclass="bold">Bookmark</b>. </p>
+        <p><b outputclass="bold">Bookmark:</b> Saves the location of a log message, enabling you to find it quickly. To create a bookmark, either click the line number, or select some text and then click <b outputclass="bold">Bookmark</b>. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Preferences:</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>
-        <p><b outputclass="bold">Refresh:</b> Refreshes the log
-          file you are currently viewing. Only log messages in the
-          current tab are updated.
-        </p>
+        <p><b outputclass="bold">Refresh:</b> Refreshes the log file you are currently viewing. Only log messages in the current tab are updated. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Reload:</b> Refreshes all log
-          files. Log messages in every tab are updated.
-        </p>
+        <p><b outputclass="bold">Reload:</b> Refreshes all log files. Log messages in every tab are updated. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Settings:</b> Displays the
-          <b outputclass="bold">Settings</b> window for the VM,
-          enabling you to make configuration changes.
-        </p>
+        <p><b outputclass="bold">Settings:</b> Displays the <b outputclass="bold">Settings</b> window for the VM, enabling you to make configuration changes. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Discard:</b> For a running VM,
-          discards the saved state for the VM and closes it down.
-        </p>
+        <p><b outputclass="bold">Discard:</b> For a running VM, discards the saved state for the VM and closes it down. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Show/Start:</b> For a running VM,
-          <b outputclass="bold">Show</b> displays the VM window.
-          For a stopped VM, <b outputclass="bold">Start</b>
-          displays options for powering up the VM.
-        </p>
+        <p><b outputclass="bold">Show/Start:</b> For a running VM, <b outputclass="bold">Show</b> displays the VM window. For a stopped VM, <b outputclass="bold">Start</b> displays options for powering up the VM. </p>
       </li>
     </ul>
   </body>
-  
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/networkingdetails.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/networkingdetails.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/networkingdetails.dita	(revision 108921)
@@ -5,7 +5,5 @@
   
   <body>
-    <p>As mentioned in <xref href="settings-network.dita#settings-network"/>, <ph
-        conkeyref="vbox-conkeyref-phrases/product-name"/> provides up to eight virtual PCI Ethernet cards for each
-      virtual machine. For each such card, you can individually select the following: </p>
+    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides up to eight virtual PCI Ethernet cards for each virtual machine. For each such card, you can individually select the following: </p>
     <ul>
       <li>
@@ -18,5 +16,4 @@
     </ul>
     <p>Four of the network cards can be configured in the <b outputclass="bold">Network</b> section of the <b outputclass="bold">Settings</b> window in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. You can configure all eight network cards on the command line using <userinput>VBoxManage modifyvm</userinput>. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
-    <p>This chapter explains the various networking settings in more detail. </p>
   </body>
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/preferences.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/preferences.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/preferences.dita	(revision 108921)
@@ -1,7 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="preferences">
+<topic xml:lang="en-us" id="tk_preferences">
   <title>Set <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Preferences</title>
-  
   <body>
     <p>Use the <uicontrol>Preferences</uicontrol> to change settings that apply to all virtual machines.</p>
@@ -27,5 +26,5 @@
       </li>
       <li>
-        <p>On the <uicontrol>Language</uicontrol> tab,  choose the language used for menus, labels, and text in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.</p>
+        <p>On the <uicontrol>Language</uicontrol> tab, choose the language used for menus, labels, and text in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.</p>
       </li>
       <li>
@@ -37,4 +36,3 @@
     </ol>
   </body>
-  
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/serialports.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/serialports.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/serialports.dita	(revision 108921)
@@ -1,151 +1,68 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="serialports">
+<topic xml:lang="en-us" id="ct_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 with an x86 architecture.  Serial ports are not available on Arm VMs.</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><ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports the use of virtual serial ports in a virtual machine with an x86 architecture. Serial ports are not available on Arm VMs.</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="../cli_topics/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>You can configure up to four virtual serial ports per virtual machine. For each device, you must set the following: </p>
     <ol>
       <li>
-        <p><b outputclass="bold">Port Number:</b> This determines
-          the serial port that the virtual machine should see. For best
-          results, use the traditional values as follows:
-        </p>
+        <p><b outputclass="bold">Port Number:</b> This determines the serial port that the virtual machine should see. For best results, use the traditional values as follows: </p>
         <ul>
           <li>
-            <p>
-              COM1: I/O base 0x3F8, IRQ 4
-            </p>
+            <p> COM1: I/O base 0x3F8, IRQ 4 </p>
           </li>
           <li>
-            <p>
-              COM2: I/O base 0x2F8, IRQ 3
-            </p>
+            <p> COM2: I/O base 0x2F8, IRQ 3 </p>
           </li>
           <li>
-            <p>
-              COM3: I/O base 0x3E8, IRQ 4
-            </p>
+            <p> COM3: I/O base 0x3E8, IRQ 4 </p>
           </li>
           <li>
-            <p>
-              COM4: I/O base 0x2E8, IRQ 3
-            </p>
+            <p> COM4: I/O base 0x2E8, IRQ 3 </p>
           </li>
         </ul>
-        <p>
-          You can also configure a user-defined serial port. Enter an
-          I/O base address and interrupt (IRQ).
-        </p>
+        <p> You can also configure a user-defined serial port. Enter an I/O base address and interrupt (IRQ). </p>
       </li>
       <li>
-        <p><b outputclass="bold">Port Mode:</b> What the virtual
-          port is connected to. For each virtual serial port, you have
-          the following options:
-        </p>
+        <p><b outputclass="bold">Port Mode:</b> What the virtual port is connected to. For each virtual serial port, you have the following options: </p>
         <ul>
           <li>
-            <p><b outputclass="bold">Disconnected:</b> The guest
-              will see the device, but it will behave as if no cable had
-              been connected to it.
-            </p>
+            <p><b outputclass="bold">Disconnected:</b> The guest will see the device, but it will behave as if no cable had been connected to it. </p>
           </li>
           <li>
-            <p><b outputclass="bold">Host Device:</b> Connects the
-              virtual serial port to a physical serial port on your
-              host. On a Windows host, this will be a name like
-              <codeph>COM1</codeph>. On Linux or Oracle Solaris hosts,
-              it will be a device node like
-              <filepath>/dev/ttyS0</filepath>. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will then
-              simply redirect all data received from and sent to the
-              virtual serial port to the physical device.
-            </p>
+            <p><b outputclass="bold">Host Device:</b> Connects the virtual serial port to a physical serial port on your host. On a Windows host, this will be a name like <codeph>COM1</codeph>. On Linux or Oracle Solaris hosts, it will be a device node like <filepath>/dev/ttyS0</filepath>. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will then simply redirect all data received from and sent to the virtual serial port to the physical device. </p>
           </li>
           <li>
-            <p><b outputclass="bold">Host Pipe:</b> Configure
-              <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to connect the virtual serial port to a
-              software pipe on the host. This depends on your host OS,
-              as follows:
-            </p>
+            <p><b outputclass="bold">Host Pipe:</b> Configure <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to connect the virtual serial port to a software pipe on the host. This depends on your host OS, as follows: </p>
             <ul>
               <li>
-                <p>On a Windows host, data will be sent and received through a named pipe. The pipe name must be in the
-                  format <filepath>\\.\pipe\<varname>name</varname>
-                  </filepath> where <varname>name</varname> should identify the virtual machine but may be freely
-                  chosen. </p>
+                <p>On a Windows host, data will be sent and received through a named pipe. The pipe name must be in the format <filepath>\\.\pipe\<varname>name</varname>
+                  </filepath> where <varname>name</varname> should identify the virtual machine but may be freely chosen. </p>
               </li>
               <li>
-                <p>On a Mac OS, Linux, or Oracle Solaris host, a local domain socket is used instead. The socket
-                  filename must be chosen such that the user running <ph conkeyref="vbox-conkeyref-phrases/product-name"
-                  /> has sufficient privileges to create and write to it. The <filepath>/tmp</filepath> directory is
-                  often a good candidate. </p>
-                <p>On Linux there are various tools which can connect to a local domain socket or create one in server
-                  mode. The most flexible tool is <userinput>socat</userinput> and is available as part of many
-                  distributions. </p>
+                <p>On a Mac OS, Linux, or Oracle Solaris host, a local domain socket is used instead. The socket filename must be chosen such that the user running <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has sufficient privileges to create and write to it. The <filepath>/tmp</filepath> directory is often a good candidate. </p>
+                <p>On Linux there are various tools which can connect to a local domain socket or create one in server mode. The most flexible tool is <userinput>socat</userinput> and is available as part of many distributions. </p>
               </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 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, corresponding to a null-modem cable, simply
-              configure one VM to create a pipe or socket and another to attach to it. </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, corresponding to a null-modem cable, simply configure one VM to create a pipe or socket and another to attach to it. </p>
           </li>
           <li>
-            <p><b outputclass="bold">Raw File:</b> Send the
-              virtual serial port output to a file. This option is very
-              useful for capturing diagnostic output from a guest. Any
-              file may be used for this purpose, as long as the user
-              running <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has sufficient privileges to create
-              and write to the file.
-            </p>
+            <p><b outputclass="bold">Raw File:</b> Send the virtual serial port output to a file. This option is very useful for capturing diagnostic output from a guest. Any file may be used for this purpose, as long as the user running <ph conkeyref="vbox-conkeyref-phrases/product-name"/> has sufficient privileges to create and write to the file. </p>
           </li>
           <li>
-            <p><b outputclass="bold">TCP:</b> Useful for
-              forwarding serial traffic over TCP/IP, acting as a server,
-              or it can act as a TCP client connecting to other servers.
-              This option enables a remote machine to directly connect
-              to the guest's serial port using TCP.
-            </p>
+            <p><b outputclass="bold">TCP:</b> Useful for forwarding serial traffic over TCP/IP, acting as a server, or it can act as a TCP client connecting to other servers. This option enables a remote machine to directly connect to the guest's serial port using TCP. </p>
             <ul>
               <li>
-                <p><b outputclass="bold">TCP Server:</b> Deselect
-                  the <b outputclass="bold">Connect to Existing
-                  Pipe/Socket</b> check box and specify the port
-                  number in the
-                  <b outputclass="bold">Path/Address</b> field.
-                  This is typically 23 or 2023. Note that on UNIX-like
-                  systems you will have to use a port a number greater
-                  than 1024 for regular users.
-                </p>
-                <p>The client can use software such as <userinput>PuTTY</userinput> or the <userinput>telnet</userinput>
-                  command line tool to access the TCP Server. </p>
+                <p><b outputclass="bold">TCP Server:</b> Deselect the <b outputclass="bold">Connect to Existing Pipe/Socket</b> check box and specify the port number in the <b outputclass="bold">Path/Address</b> field. This is typically 23 or 2023. Note that on UNIX-like systems you will have to use a port a number greater than 1024 for regular users. </p>
+                <p>The client can use software such as <userinput>PuTTY</userinput> or the <userinput>telnet</userinput> command line tool to access the TCP Server. </p>
               </li>
               <li>
-                <p><b outputclass="bold">TCP Client:</b> To create
-                  a virtual null-modem cable over the Internet or LAN,
-                  the other side can connect using TCP by specifying
-                  <codeph><varname>hostname</varname>:<varname>port</varname></codeph>
-                  in the <b outputclass="bold">Path/Address</b>
-                  field. The TCP socket will act in client mode if you
-                  select the <b outputclass="bold">Connect to Existing
-                  Pipe/Socket</b> check box.
-                </p>
+                <p><b outputclass="bold">TCP Client:</b> To create a virtual null-modem cable over the Internet or LAN, the other side can connect using TCP by specifying <codeph><varname>hostname</varname>:<varname>port</varname></codeph> in the <b outputclass="bold">Path/Address</b> field. The TCP socket will act in client mode if you select the <b outputclass="bold">Connect to Existing Pipe/Socket</b> check box. </p>
               </li>
             </ul>
@@ -154,8 +71,5 @@
       </li>
     </ol>
-    <p>Up to four serial ports can be configured per virtual machine, but you can pick any port numbers out of the
-      above. However, serial ports cannot reliably share interrupts. If both ports are to be used at the same time, they
-      must use different interrupt levels, for example COM1 and COM2, but not COM1 and COM3. </p>
+    <p>Up to four serial ports can be configured per virtual machine, but you can pick any port numbers out of the above. However, serial ports cannot reliably share interrupts. If both ports are to be used at the same time, they must use different interrupt levels, for example COM1 and COM2, but not COM1 and COM3. </p>
   </body>
-  
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/settings-audio.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/settings-audio.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/settings-audio.dita	(revision 108921)
@@ -1,44 +1,26 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="settings-audio">
+<topic xml:lang="en-us" id="ct_settings-audio">
   <title>Audio Settings</title>
-  
   <body>
-    <p>The <b outputclass="bold">Audio</b> section in a virtual machine's <b outputclass="bold">Settings</b> window
-      determines whether the VM will detect a connected sound card, and if the audio output should be played on the host
-      system. </p>
-    <p>To enable audio for a guest, select the <b outputclass="bold">Enable Audio</b> check box. The following settings
-      are available: </p>
+    <p>The <b outputclass="bold">Audio</b> section in a virtual machine's <b outputclass="bold">Settings</b> window determines whether the VM will detect a connected sound card, and if the audio output should be played on the host system. </p>
+    <p>To enable audio for a guest, select the <b outputclass="bold">Enable Audio</b> check box. The following settings are available: </p>
     <ul>
       <li>
-        <p><b outputclass="bold">Host Audio Driver:</b> The audio
-          driver that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses on the host.
-        </p>
-        <p>The <b outputclass="bold">Default</b> option is enabled by default for all new VMs. This option selects the
-          best audio driver for the host platform automatically. This enables you to move VMs between different
-          platforms without having to change the audio driver. </p>
-        <p>On a Linux host, depending on your host configuration, you can select between the OSS, ALSA, or the
-          PulseAudio subsystem. On newer Linux distributions, the PulseAudio subsystem is preferred. </p>
-        <p>Only OSS is supported on Oracle Solaris hosts. The Oracle Solaris Audio audio backend is no longer supported
-          on Oracle Solaris hosts. </p>
+        <p><b outputclass="bold">Host Audio Driver:</b> The audio driver that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses on the host. </p>
+        <p>The <b outputclass="bold">Default</b> option is enabled by default for all new VMs. This option selects the best audio driver for the host platform automatically. This enables you to move VMs between different platforms without having to change the audio driver. </p>
+        <p>On a Linux host, depending on your host configuration, you can select between the OSS, ALSA, or the PulseAudio subsystem. On newer Linux distributions, the PulseAudio subsystem is preferred. </p>
+        <p>Only OSS is supported on Oracle Solaris hosts. The Oracle Solaris Audio audio backend is no longer supported on Oracle Solaris hosts. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Audio Controller:</b> You can
-          choose between the emulation of an Intel AC'97 controller, an
-          Intel HD Audio controller, or a SoundBlaster 16 card.
-        </p>
+        <p><b outputclass="bold">Audio Controller:</b> You can choose between the emulation of an Intel AC'97 controller, an Intel HD Audio controller, or a SoundBlaster 16 card. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Enable Audio Output:</b> Enables
-          audio output only for the VM.
-        </p>
+        <p><b outputclass="bold">Enable Audio Output:</b> Enables audio output only for the VM. </p>
       </li>
       <li>
-        <p><b outputclass="bold">Enable Audio Input:</b> Enables
-          audio input only for the VM.
-        </p>
+        <p><b outputclass="bold">Enable Audio Input:</b> Enables audio input only for the VM. </p>
       </li>
     </ul>
   </body>
-  
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/settings-display.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/settings-display.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/settings-display.dita	(revision 108921)
@@ -1,7 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="settings-display">
+<topic xml:lang="en-us" id="ct_settings-display">
   <title>Display Settings</title>
-  
   <body>
     <p>The following tabs are available for configuring the display for a virtual machine. </p>
Index: /trunk/doc/manual/en_US/dita/topics/settings-network.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/settings-network.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/settings-network.dita	(revision 108921)
@@ -1,23 +1,11 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="settings-network">
+<topic xml:lang="en-us" id="ct_settings-network">
   <title>Network Settings</title>
-  
   <body>
-    <p>The <b outputclass="bold">Network</b> section in a virtual machine's <b outputclass="bold">Settings</b> window
-      enables you to configure how <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents virtual network cards
-      to your VM, and how they operate. </p>
-    <p>When you first create a virtual machine, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> by default enables
-      one virtual network card and selects the Network Address Translation (NAT) mode for it. This way the guest can
-      connect to the outside world using the host's networking and the outside world can connect to services on the
-      guest which you choose to make visible outside of the virtual machine. </p>
-    <p>This default setup is good for the majority of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> users.
-      However, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is extremely flexible in how it can virtualize
-      networking. It supports many virtual network cards per virtual machine. The first four virtual network cards can
-      be configured in detail in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. Additional network cards can be
-      configured using the <userinput>VBoxManage</userinput> command. </p>
-    <p>Many networking options are available. See <xref href="networkingdetails.dita#networkingdetails"/> for more
-      information. </p>
+    <p>The <b outputclass="bold">Network</b> section in a virtual machine's <b outputclass="bold">Settings</b> window enables you to configure how <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents virtual network cards to your VM, and how they operate. </p>
+    <p>When you first create a virtual machine, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> by default enables one virtual network card and selects the Network Address Translation (NAT) mode for it. This way the guest can connect to the outside world using the host's networking and the outside world can connect to services on the guest which you choose to make visible outside of the virtual machine. </p>
+    <p>This default setup is good for the majority of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> users. However, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is extremely flexible in how it can virtualize networking. It supports many virtual network cards per virtual machine. The first four virtual network cards can be configured in detail in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. Additional network cards can be configured using the <userinput>VBoxManage</userinput> command. </p>
+    <p>Many networking options are available. See <xref href="networkingdetails.dita#networkingdetails"/> for more information. </p>
   </body>
-  
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/settings-storage.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/settings-storage.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/settings-storage.dita	(revision 108921)
@@ -1,93 +1,48 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="settings-storage">
+<topic xml:lang="en-us" id="ct_settings-storage">
   <title>Storage Settings</title>
-  
   <body>
-    <p>The <b outputclass="bold">Storage</b> category in the VM settings enables you to connect virtual hard disk and
-      CD/DVD images and drives to your virtual machine. </p>
-    <p>In a real computer, so-called <i>storage controllers</i> connect physical disk drives to the rest of the
-      computer. Similarly, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents virtual storage controllers to
-      a virtual machine. Under each controller, the virtual devices, such as hard disks and CD/DVD drives, attached to
-      the controller are shown. </p>
+    <p>The <b outputclass="bold">Storage</b> category in the VM settings enables you to connect virtual hard disk and CD/DVD images and drives to your virtual machine. </p>
+    <p>In a real computer, so-called <i>storage controllers</i> connect physical disk drives to the rest of the computer. Similarly, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents virtual storage controllers to a virtual machine. Under each controller, the virtual devices, such as hard disks and CD/DVD drives, attached to the controller are shown. </p>
     <note>
-      <p>This section gives a quick introduction to the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> storage
-        settings. See <xref href="storage.dita#storage"/> for a full description of the available storage settings in
-          <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
+      <p>This section gives a quick introduction to the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> storage settings. See <xref href="storage.dita#storage"/> for a full description of the available storage settings in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
     </note>
-    <p>Depending on the guest OS type that you selected when you created the VM, a new VM includes the following storage
-      devices: </p>
+    <p>Depending on the guest OS type that you selected when you created the VM, a new VM includes the following storage devices: </p>
     <ul>
       <li>
-        <p><b outputclass="bold">IDE controller.</b> A virtual
-          CD/DVD drive is attached to device 0 on the secondary channel
-          of the IDE controller.
-        </p>
+        <p><b outputclass="bold">IDE controller.</b> A virtual CD/DVD drive is attached to device 0 on the secondary channel of the IDE controller. </p>
       </li>
       <li>
-        <p><b outputclass="bold">SATA controller.</b> This is a
-          modern type of storage controller for higher hard disk data
-          throughput, to which the virtual hard disks are attached.
-          Initially you will normally have one such virtual disk, but as
-          shown in the previous screenshot, you can have more than one.
-          Each is represented by a disk image file, such as a VDI file
-          in this example.
-        </p>
+        <p><b outputclass="bold">SATA controller.</b> This is a modern type of storage controller for higher hard disk data throughput, to which the virtual hard disks are attached. Initially you will normally have one such virtual disk, but as shown in the previous screenshot, you can have more than one. Each is represented by a disk image file, such as a VDI file in this example. </p>
       </li>
     </ul>
     <p>VMs with an Arm architecture have VirtIO SCSI only.</p>
-    <p>If you created your VM with an older version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, the
-      default storage layout may differ. You might then only have an IDE controller to which both the CD/DVD drive and
-      the hard disks have been attached. This might also apply if you selected an older OS type when you created the VM.
-      Since older OSes do not support SATA without additional drivers, <ph
-        conkeyref="vbox-conkeyref-phrases/product-name"/> will make sure that no such devices are present initially. See
-        <xref href="harddiskcontrollers.dita#harddiskcontrollers"/>. </p>
-    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> also provides a <i>floppy controller</i>. You cannot add
-      devices other than floppy drives to this controller. Virtual floppy drives, like virtual CD/DVD drives, can be
-      connected to either a host floppy drive, if you have one, or a disk image, which in this case must be in RAW
-      format. </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>
+    <p>If you created your VM with an older version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, the default storage layout may differ. You might then only have an IDE controller to which both the CD/DVD drive and the hard disks have been attached. This might also apply if you selected an older OS type when you created the VM. Since older OSes do not support SATA without additional drivers, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will make sure that no such devices are present initially. See <xref href="harddiskcontrollers.dita#harddiskcontrollers"/>. </p>
+    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> also provides a <i>floppy controller</i>. You cannot add devices other than floppy drives to this controller. Virtual floppy drives, like virtual CD/DVD drives, can be connected to either a host floppy drive, if you have one, or a disk image, which in this case must be in RAW format. </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>
-        <p>To <b outputclass="bold">add another virtual hard disk, or a CD/DVD or floppy drive</b>, select the storage
-          controller to which it should be added (such as IDE, SATA, SCSI, SAS, floppy controller) and then click the <b
-            outputclass="bold">Add Disk</b> button below the tree. You can then either select <b outputclass="bold"
-            >Optical Drive</b> or <b outputclass="bold">Hard Disk</b>. If you clicked on a floppy controller, you can
-          add a floppy drive instead. Alternatively, right-click the storage controller and select a menu item there. </p>
-        <p>A dialog is displayed, enabling you to select an existing disk image file or to create a new disk image file.
-          Depending on the type of disk image, the dialog is called <b outputclass="bold">Hard Disk Selector</b>, <b
-            outputclass="bold">Optical Disk Selector</b>, or <b outputclass="bold">Floppy Disk Selector</b>. </p>
-        <p>See <xref href="vdidetails.dita#vdidetails"/> for information on the image file types that are supported by
-            <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
-        <p>For virtual CD/DVD drives, the image files will typically be in the standard ISO format instead. Most
-          commonly, you will select this option when installing an OS from an ISO file that you have obtained from the
-          Internet. For example, most Linux distributions are available in this way. </p>
-        <p>Depending on the type of disk image, you can set the following <b outputclass="bold">Attributes</b> for the
-          disk image in the right part of the Storage settings page: </p>
+        <p>To <b outputclass="bold">add another virtual hard disk, or a CD/DVD or floppy drive</b>, select the storage controller to which it should be added (such as IDE, SATA, SCSI, SAS, floppy controller) and then click the <b outputclass="bold">Add Disk</b> button below the tree. You can then either select <b outputclass="bold">Optical Drive</b> or <b outputclass="bold">Hard Disk</b>. If you clicked on a floppy controller, you can add a floppy drive instead. Alternatively, right-click the storage controller and select a menu item there. </p>
+        <p>A dialog is displayed, enabling you to select an existing disk image file or to create a new disk image file. Depending on the type of disk image, the dialog is called <b outputclass="bold">Hard Disk Selector</b>, <b outputclass="bold">Optical Disk Selector</b>, or <b outputclass="bold">Floppy Disk Selector</b>. </p>
+        <p>See <xref href="vdidetails.dita#vdidetails"/> for information on the image file types that are supported by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
+        <p>For virtual CD/DVD drives, the image files will typically be in the standard ISO format instead. Most commonly, you will select this option when installing an OS from an ISO file that you have obtained from the Internet. For example, most Linux distributions are available in this way. </p>
+        <p>Depending on the type of disk image, you can set the following <b outputclass="bold">Attributes</b> for the disk image in the right part of the Storage settings page: </p>
         <ul>
           <li>
-            <p>The <b outputclass="bold">device slot</b> of the controller that the virtual disk is connected to. IDE
-              controllers have four slots: primary device 0, primary device 1, secondary device 0, and secondary device
-              1. By contrast, SATA and SCSI controllers offer you up to 30 slots for attaching virtual devices. </p>
+            <p>The <b outputclass="bold">device slot</b> of the controller that the virtual disk is connected to. IDE controllers have four slots: primary device 0, primary device 1, secondary device 0, and secondary device 1. By contrast, SATA and SCSI controllers offer you up to 30 slots for attaching virtual devices. </p>
           </li>
           <li><b outputclass="bold">Solid-state Drive</b> presents a virtual disk to the guest as a solid-state device. </li>
           <li><b outputclass="bold">Hot-pluggable</b> presents a virtual disk to the guest as a hot-pluggable device. </li>
           <li>
-            <p>For virtual CD/DVD drives, you can select <b outputclass="bold">Live CD/DVD</b>. This means that the
-              virtual optical disk is not removed from when the guest system ejects it. </p>
+            <p>For virtual CD/DVD drives, you can select <b outputclass="bold">Live CD/DVD</b>. This means that the virtual optical disk is not removed from when the guest system ejects it. </p>
           </li>
         </ul>
       </li>
       <li>
-        <p>To <b outputclass="bold">remove an attachment</b>, either select it and click the <b outputclass="bold"
-            >Remove</b> icon at the bottom, or right-click the attachment and select the menu item. </p>
+        <p>To <b outputclass="bold">remove an attachment</b>, either select it and click the <b outputclass="bold">Remove</b> icon at the bottom, or right-click the attachment and select the menu item. </p>
       </li>
     </ul>
-    <p>Removable media, such as CD/DVDs and floppies, can be changed while the guest is running. Since the <b
-        outputclass="bold">Settings</b> window is not available at that time, you can also access these settings from
-      the <b outputclass="bold">Devices</b> menu of your virtual machine window. </p>
+    <p>Removable media, such as CD/DVDs and floppies, can be changed while the guest is running. Since the <b outputclass="bold">Settings</b> window is not available at that time, you can also access these settings from the <b outputclass="bold">Devices</b> menu of your virtual machine window. </p>
   </body>
-  
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/settings-system.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/settings-system.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/settings-system.dita	(revision 108921)
@@ -2,19 +2,12 @@
 <!DOCTYPE topic
   PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="settings-system">
-            <title>System Settings</title>
-            
-            <body>
-               <p>The <b outputclass="bold">System</b> category groups various settings that are related to the basic
-      hardware that is presented to the virtual machine. </p>
-               <note>
-                  <p>As the activation mechanism of Microsoft Windows is sensitive to hardware changes, if you are
-        changing hardware settings for a Windows guest, some of these changes may trigger a request for another
-        activation with Microsoft. </p>
-               </note>
-               <p>The following tabs are available. </p>
-            </body>
-            
-            
-            
-         </topic>
+<topic xml:lang="en-us" id="ct_settings-system">
+  <title>System Settings</title>
+  <body>
+    <p>The <b outputclass="bold">System</b> category groups various settings that are related to the basic hardware that is presented to the virtual machine. </p>
+    <note>
+      <p>As the activation mechanism of Microsoft Windows is sensitive to hardware changes, if you are changing hardware settings for a Windows guest, some of these changes may trigger a request for another activation with Microsoft. </p>
+    </note>
+    <p>The following tabs are available. </p>
+  </body>
+</topic>
Index: /trunk/doc/manual/en_US/dita/topics/settings-window.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/settings-window.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/settings-window.dita	(revision 108921)
@@ -1,7 +1,6 @@
 <?xml version='1.0' encoding='UTF-8'?>
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="settings-window">
+<topic xml:lang="en-us" id="ct_settings-window">
   <title>The Settings Window</title>
-  
   <body>
     <p>Settings for a virtual machine are configured using the <b>Settings</b> window.</p>
@@ -9,10 +8,8 @@
     <ul>
       <li>
-        <p>In the machine list, right-click the virtual machine name. Select the <b>Settings</b> 
-           menu option.</p>
+        <p>In the machine list, right-click the virtual machine name. Select the <b>Settings</b> menu option.</p>
       </li>
       <li>
-        <p>In the machine list, click the virtual machine name. Select the <b>Machine</b>, <b>Settings</b> 
-          menu option.</p>
+        <p>In the machine list, click the virtual machine name. Select the <b>Machine</b>, <b>Settings</b> menu option.</p>
       </li>
       <li>
@@ -20,8 +17,6 @@
       </li>
     </ul>
-    
     <note>
-      <p>The available settings depend on the selected experience level. To display all
-       available settings, ensure the experience level is set to <b>Expert</b>.</p>
+      <p>The available settings depend on the selected experience level. To display all available 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>
Index: /trunk/doc/manual/en_US/dita/topics/snapshots.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/snapshots.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/snapshots.dita	(revision 108921)
@@ -2,57 +2,38 @@
 <!DOCTYPE topic
   PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="snapshots">
-            <title>Snapshots</title>
-            
-            <body>
-               <p>With snapshots, you can save a particular state of a virtual machine for later use. At any later time,
-      you can revert to that state, even though you may have changed the VM considerably since then. A snapshot of a
-      virtual machine is thus similar to a machine in Saved state, but there can be many of them, and these saved states
-      are preserved. </p>
-               <p>To see the snapshots of a virtual machine, click the machine name in <ph
-        conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. In the machine tools menu for the VM, click <b outputclass="bold"
-        >Snapshots</b>. The Snapshots tool is displayed. </p>
-               <p>If you select multiple VMs in the machine list, all snapshots are listed for each VM. </p>
-               <p>Until you take a snapshot of the virtual machine, the list of snapshots will be empty, except for the
-        <b outputclass="bold">Current State</b> item. This item represents the current point in the lifetime of the
-      virtual machine. </p>
-               <p>The Snapshots window includes a toolbar, enabling you to perform the following snapshot operations: </p>
-               <ul>
-                  <li>
-                     <p><b outputclass="bold">Take.</b> Takes a snapshot of the selected VM. See <xref
-            href="snapshots-take-restore-delete.dita#snapshots-take-restore-delete"/>. </p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Delete.</b> Removes a snapshot from the list of snapshots. See <xref
-            href="snapshots-take-restore-delete.dita#snapshots-take-restore-delete"/>. </p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Restore.</b> Restores the VM state to be the same as the selected
-          snapshot. See <xref href="snapshots-take-restore-delete.dita#snapshots-take-restore-delete"/>. </p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Properties.</b> Displays the properties for the selected snapshot. The <b
-            outputclass="bold">Attributes</b> tab is used to specify a Name and Description for the snapshot. The <b
-            outputclass="bold">Information</b> tab shows VM settings for the snapshot. </p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Clone.</b> Displays the <b outputclass="bold">Clone Virtual Machine</b>
-          wizard. This enables you to create a clone of the VM, based on the selected snapshot. </p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Settings.</b> Available for the Current State snapshot only. Displays the
-            <b outputclass="bold">Settings</b> window for the VM, enabling you to make configuration changes. </p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Discard.</b> For a running VM, discards the saved state for the VM and
-          closes it down. </p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Start.</b> Start the VM. This operation is available for the <b
-            outputclass="bold">Current State</b> item. </p>
-                  </li>
-               </ul>
-            </body>
-            
-            
-         </topic>
+<topic xml:lang="en-us" id="ct_snapshots">
+   <title>Snapshots</title>
+   <body>
+      <p>With snapshots, you can save a particular state of a virtual machine for later use. At any later time, you can revert to that state, even though you may have changed the VM considerably since then. A snapshot of a virtual machine is thus similar to a machine in Saved state, but there can be many of them, and these saved states are preserved. </p>
+      <p>To see the snapshots of a virtual machine, click the machine name in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. In the machine tools menu for the VM, click <b outputclass="bold">Snapshots</b>. The Snapshots tool is displayed. </p>
+      <p>If you select multiple VMs in the machine list, all snapshots are listed for each VM. </p>
+      <p>Until you take a snapshot of the virtual machine, the list of snapshots will be empty, except for the <b outputclass="bold">Current State</b> item. This item represents the current point in the lifetime of the virtual machine. </p>
+      <p>The Snapshots window includes a toolbar, enabling you to perform the following snapshot operations: </p>
+      <ul>
+         <li>
+            <p><b outputclass="bold">Take.</b> Takes a snapshot of the selected VM. See <xref href="snapshots-take-restore-delete.dita#snapshots-take-restore-delete"/>. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Delete.</b> Removes a snapshot from the list of snapshots. See <xref href="snapshots-take-restore-delete.dita#snapshots-take-restore-delete"/>. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Restore.</b> Restores the VM state to be the same as the selected snapshot. See <xref href="snapshots-take-restore-delete.dita#snapshots-take-restore-delete"/>. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Properties.</b> Displays the properties for the selected snapshot. The <b outputclass="bold">Attributes</b> tab is used to specify a Name and Description for the snapshot. The <b outputclass="bold">Information</b> tab shows VM settings for the snapshot. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Clone.</b> Displays the <b outputclass="bold">Clone Virtual Machine</b> wizard. This enables you to create a clone of the VM, based on the selected snapshot. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Settings.</b> Available for the Current State snapshot only. Displays the <b outputclass="bold">Settings</b> window for the VM, enabling you to make configuration changes. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Discard.</b> For a running VM, discards the saved state for the VM and closes it down. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Start.</b> Start the VM. This operation is available for the <b outputclass="bold">Current State</b> item. </p>
+         </li>
+      </ul>
+   </body>
+</topic>
Index: /trunk/doc/manual/en_US/dita/topics/soft-keyb.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/soft-keyb.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/soft-keyb.dita	(revision 108921)
@@ -3,25 +3,18 @@
   PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
 
-<topic xml:lang="en-us" id="soft-keyb">
+<topic xml:lang="en-us" id="ct_soft-keyb">
   <title>Soft Keyboard</title>
   <body>
-    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a <i>soft keyboard</i> that enables you to input
-      keyboard characters on the guest. A soft 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 soft
-      keyboard. </p>
+    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides a <i>soft keyboard</i> that enables you to input keyboard characters on the guest. A soft 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 soft keyboard. </p>
     <note type="caution">
-      <p>For best results, ensure that the keyboard layout configured on the guest OS matches the keyboard layout used
-        by the soft keyboard. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> does not do this automatically. </p>
+      <p>For best results, ensure that the keyboard layout configured on the guest OS matches the keyboard layout used by the soft keyboard. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> does not do this automatically. </p>
     </note>
     <p>The soft keyboard can be used in the following scenarios: </p>
     <ul>
       <li>
-        <p>When the physical keyboard on the host is not the same as the keyboard layout configured on the guest. For
-          example, if the guest is configured to use an international keyboard, but the host keyboard is US English. </p>
+        <p>When the physical keyboard on the host is not the same as the keyboard layout configured on the guest. For example, if the guest is configured to use an international keyboard, but the host keyboard is US English. </p>
       </li>
       <li>
-        <p>To send special key combinations to the guest. Note that some common key combinations are also available in
-          the <b outputclass="bold">Input</b>, <b outputclass="bold">Keyboard</b> menu of the guest VM window. See <xref
-            href="specialcharacters.dita#specialcharacters"/>. </p>
+        <p>To send special key combinations to the guest. Note that some common key combinations are also available in the <b outputclass="bold">Input</b>, <b outputclass="bold">Keyboard</b> menu of the guest VM window. See <xref href="specialcharacters.dita#specialcharacters"/>. </p>
       </li>
       <li>
@@ -32,8 +25,5 @@
       </li>
     </ul>
-    <p>By default, the soft keyboard includes some common international keyboard layouts. You can copy and modify these
-      to meet your own requirements. See <xref href="soft-keyb-custom.dita#soft-keyb-custom"/>. </p>
+    <p>By default, the soft keyboard includes some common international keyboard layouts. You can copy and modify these to meet your own requirements. See <xref href="soft-keyb-custom.dita#soft-keyb-custom"/>. </p>
   </body>
-
-
 </topic>
Index: /trunk/doc/manual/en_US/dita/topics/specialcharacters.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/specialcharacters.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/specialcharacters.dita	(revision 108921)
@@ -65,6 +65,5 @@
                      </li>
                      <li>
-                        <p>A soft keyboard can be used to input key combinations in the guest. See <xref
-            href="soft-keyb.dita#soft-keyb"/>. </p>
+                        <p>A soft keyboard can be used to input key combinations in the guest. See <xref href="soft-keyb-using.dita"/>.</p>
                      </li>
                   </ul>
Index: /trunk/doc/manual/en_US/dita/topics/ts_scale-mode.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/ts_scale-mode.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/ts_scale-mode.dita	(revision 108921)
@@ -2,5 +2,5 @@
 <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
 <topic id="ts-scale-mode">
-    <title><?oxy_comment_start author="Mhari Duncan" timestamp="20241210T152423+0000" comment="kespenla: Sergey wants to get rid of Scale Mode (with my support) and replace it with the usual UI scaling functionality. Then this can also go."?>Preserving the Aspect Ratio in Scale Mode Not Available on All Hosts<?oxy_comment_end?></title>
+    <title><?oxy_comment_start author="Mhari Duncan" timestamp="20241210T152423+0000" comment="When Scale Mode is removed, and replaced with the usual UI scaling functionality, then this can also go."?>Preserving the Aspect Ratio in Scale Mode Not Available on All Hosts<?oxy_comment_end?></title>
     <body>
         <dl>
Index: /trunk/doc/manual/en_US/dita/topics/usb-support.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/usb-support.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/usb-support.dita	(revision 108921)
@@ -2,9 +2,6 @@
 <!DOCTYPE topic
   PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="usb-support">
-            <title>USB Support</title>
-            
-            <body/>
-            
-            
-         </topic>
+<topic xml:lang="en-us" id="ct_usb-support">
+  <title>USB Support</title>
+  <body/>
+</topic>
Index: /trunk/doc/manual/en_US/dita/topics/user-interface.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/user-interface.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/user-interface.dita	(revision 108921)
@@ -2,35 +2,21 @@
 <!DOCTYPE topic
   PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="user-interface">
-            <title>User Interface</title>
-            
-            <body>
-               <p>The <b outputclass="bold">User Interface</b> section enables you to change certain aspects of the user
-      interface of the selected VM. </p>
-               <ul>
-                  <li>
-                     <p><b outputclass="bold">Menu Bar:</b> This widget enables you to disable a complete menu, by
-          clicking on the menu name to deselect it. Menu entries can be disabled, by deselecting the check box next to
-          the entry. On Windows and Linux hosts, the complete menu bar can be disabled by deselecting the check box on
-          the right. </p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Mini ToolBar:</b> In full screen or seamless mode, <ph
-            conkeyref="vbox-conkeyref-phrases/product-name"/> can display a small toolbar that contains some of the
-          items that are normally available from the virtual machine's menu bar. This toolbar reduces itself to a small
-          gray line unless you move the mouse over it. With the toolbar, you can return from full screen or seamless
-          mode, control machine execution, or enable certain devices. If you do not want to see the toolbar, disable the
-            <b outputclass="bold">Show in Full Screen/Seamless</b> setting. </p>
-                     <p>The <b outputclass="bold">Show at Top of Screen</b> setting enables you to show the toolbar at
-          the top of the screen, instead of showing it at the bottom. </p>
-                     <p>The Mini Toolbar is not available on macOS hosts. </p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Status Bar:</b> This widget enables you to disable and reorder icons on
-          the status bar. Deselect the check box of an icon to disable it, or rearrange icons by dragging and dropping
-          the icon. To disable the complete status bar deselect the check box on the left. </p>
-                  </li>
-               </ul>
-            </body>
-            
-         </topic>
+<topic xml:lang="en-us" id="ct_user-interface">
+   <title>User Interface</title>
+   <body>
+      <p>The <b outputclass="bold">User Interface</b> section enables you to change certain aspects of the user interface of the selected VM. </p>
+      <ul>
+         <li>
+            <p><b outputclass="bold">Menu Bar:</b> This widget enables you to disable a complete menu, by clicking on the menu name to deselect it. Menu entries can be disabled, by deselecting the check box next to the entry. On Windows and Linux hosts, the complete menu bar can be disabled by deselecting the check box on the right. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Mini ToolBar:</b> In full screen or seamless mode, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can display a small toolbar that contains some of the items that are normally available from the virtual machine's menu bar. This toolbar reduces itself to a small gray line unless you move the mouse over it. With the toolbar, you can return from full screen or seamless mode, control machine execution, or enable certain devices. If you do not want to see the toolbar, disable the <b outputclass="bold">Show in Full Screen/Seamless</b> setting. </p>
+            <p>The <b outputclass="bold">Show at Top of Screen</b> setting enables you to show the toolbar at the top of the screen, instead of showing it at the bottom. </p>
+            <p>The Mini Toolbar is not available on macOS hosts. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Status Bar:</b> This widget enables you to disable and reorder icons on the status bar. Deselect the check box of an icon to disable it, or rearrange icons by dragging and dropping the icon. To disable the complete status bar deselect the check box on the left. </p>
+         </li>
+      </ul>
+   </body>
+</topic>
Index: /trunk/doc/manual/en_US/dita/topics/virtual-media-manager.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/virtual-media-manager.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/virtual-media-manager.dita	(revision 108921)
@@ -2,142 +2,116 @@
 <!DOCTYPE topic
   PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="virtual-media-manager">
-            <title>The Virtual Media Manager</title>
-            
-            <body>
-               <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> keeps track of all the hard disk, CD/DVD-ROM, and floppy disk images which are in use by virtual machines. These are often referred to as <i>known media</i> and come from two sources:</p>
-               <ul>
-                  <li>
-                     <p>All media currently attached to virtual machines.</p>
-                  </li>
-                  <li>
-                     <p>Registered media, for compatibility with legacy <ph conkeyref="vbox-conkeyref-phrases/product-name"/> versions.</p>
-                  </li>
-               </ul>
-               <p>To view and change the known media, click <uicontrol>Media</uicontrol>  in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.</p>
-               <p>The known media are conveniently grouped in separate tabs for the supported formats. These formats
-      are: </p>
-               <ul>
-                  <li>
-                     <p>Hard disk images, either in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s own Virtual
-               Disk Image (VDI) format, or in the third-party formats listed in <xref href="vdidetails.dita#vdidetails"
-               />. </p>
-                  </li>
-                  <li>
-                     <p>CD/DVD images in standard ISO format. </p>
-                  </li>
-                  <li>
-                     <p>Floppy images in standard RAW format. </p>
-                  </li>
-               </ul>
-               <p>For each image, the Virtual Media Manager shows you the full path of the image file and other
-      information, such as the virtual machine the image is currently attached to. </p>
-               <p>The Virtual Media Manager enables you to do the following: </p>
-               <ul>
-                  <li>
-                     <p><b outputclass="bold">Add</b> an image to the known media. </p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Create</b> a new disk image. </p>
-                     <ul>
-                        <li>
-                           <p>For hard disks, the <b outputclass="bold">Create Virtual Hard Disk</b> wizard is shown.
-              See <xref href="create-virtual-hard-disk-image.dita#create-virtual-hard-disk-image"/>. </p>
-                        </li>
-                        <li>
-                           <p>For optical disks, the <b outputclass="bold">VISO Creator</b> tool is shown. See <xref
-                href="create-optical-disk-image.dita#create-optical-disk-image"/>. </p>
-                        </li>
-                        <li>
-                           <p>For floppy disks, the <b outputclass="bold">Floppy Disk Creator</b> tool is shown. See
-                <xref href="create-floppy-disk-image.dita#create-floppy-disk-image"/>. </p>
-                        </li>
-                     </ul>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Copy</b> an image to create another one. </p>
-                     <p>For virtual hard disks, you can specify one of the following target types: VDI, VHD, or VMDK. </p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Move</b> an image to another location. </p>
-                     <p>A file dialog prompts you for the new image file location. </p>
-                     <p>When you use the Virtual Media Manager to move a disk image, <ph
-            conkeyref="vbox-conkeyref-phrases/product-name"/> updates all related configuration files automatically. </p>
-                     <note>
-                        <p>Always use the Virtual Media Manager or the <userinput>VBoxManage modifymedium</userinput>
-            command to move a disk image. </p>
-                        <p>If you use a file management feature of the host OS to move a disk image to a new location,
-            run the <userinput>VBoxManage modifymedium --setlocation</userinput> command to configure the new path of
-            the disk image on the host file system. This command updates the <ph
-              conkeyref="vbox-conkeyref-phrases/product-name"/> configuration automatically. </p>
-                     </note>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Remove</b> an image from the known media. You can optionally delete the image file when removing the image.</p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Release</b> an image to detach it from a VM. This action only applies if the image is currently attached to a VM as a virtual hard disk.</p>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Clear</b> all inaccessible disk images from the list. The disk images are released from the VMs they are attached to and removed from the known media.</p>
-                     <note>
-                        <p>This option is for optical disks and floppy disks only.</p>
-                     </note>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Search</b> for an image by name or UUID.</p>
-                  </li>
-                  <li>
-                     <p>View and edit the <b outputclass="bold">Properties</b> of a disk image.</p>
-                     <p>Available properties include the following:</p>
-                     <ul>
-                        <li>
-                           <p><b outputclass="bold">Type:</b> Specifies the snapshot behavior of the disk. See <xref
-                href="hdimagewrites.dita#hdimagewrites"/>. </p>
-                        </li>
-                        <li>
-                           <p><b outputclass="bold">Location:</b> Specifies the location of the disk image file on the host system. You can use a file dialog to browse for the disk image location.</p>
-                        </li>
-                        <li>
-                           <p><b outputclass="bold">Description:</b> Specifies a short description of the disk image.</p>
-                        </li>
-                        <li>
-                           <p><b outputclass="bold">Size:</b> Specifies the size of the disk image. You can use the slider to increase or decrease the disk image size.</p>
-                        </li>
-                        <li>
-                           <p><b outputclass="bold">Information:</b> Specifies detailed information about the disk image.</p>
-                        </li>
-                     </ul>
-                  </li>
-                  <li>
-                     <p><b outputclass="bold">Refresh</b> the property values of the selected disk image.</p>
-                  </li>
-               </ul>
-               <p>To perform these actions, highlight the medium in the Virtual Media Manager and then do one of the
-      following: </p>
-               <ul>
-                  <li>
-                     <p>Click an icon in the Virtual Media Manager toolbar. </p>
-                  </li>
-                  <li>
-                     <p>Right-click the medium and select an option. </p>
-                  </li>
-               </ul>
-               <p>Use the <b outputclass="bold">Storage</b> page in a VM's <b outputclass="bold">Settings</b> window to
-      create a new disk image. By default, disk images are stored in the VM's folder. </p>
-               <p>You can copy hard disk image files to other host systems and then import them in to VMs from the host
-      system. However, some Windows guest OSes may require that you configure the new VM in a similar way to the old
-      one. </p>
-               <note>
-                  <p>Do not simply make copies of virtual disk images. If you import such a second copy into a VM, <ph
-          conkeyref="vbox-conkeyref-phrases/product-name"/> issues an error because <ph
-          conkeyref="vbox-conkeyref-phrases/product-name"/> assigns a universally unique identifier (UUID) to each disk
-        image to ensure that it is only used one time. See <xref href="cloningvdis.dita#cloningvdis"/>. Also, if you
-        want to copy a VM to another system, use the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> import and
-        export features. See <xref href="ovf.dita#ovf"/>. </p>
-               </note>
-            </body>
-            
-            
-            
-         </topic>
+<topic xml:lang="en-us" id="ct_virtual-media-manager">
+   <title>The Virtual Media Manager</title>
+   <body>
+      <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> keeps track of all the hard disk, CD/DVD-ROM, and floppy disk images which are in use by virtual machines. These are often referred to as <i>known media</i> and come from two sources:</p>
+      <ul>
+         <li>
+            <p>All media currently attached to virtual machines.</p>
+         </li>
+         <li>
+            <p>Registered media, for compatibility with legacy <ph conkeyref="vbox-conkeyref-phrases/product-name"/> versions.</p>
+         </li>
+      </ul>
+      <p>To view and change the known media, click <uicontrol>Media</uicontrol> in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.</p>
+      <p>The known media are conveniently grouped in separate tabs for the supported formats. These formats are: </p>
+      <ul>
+         <li>
+            <p>Hard disk images, either in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s own Virtual Disk Image (VDI) format, or in the third-party formats listed in <xref href="vdidetails.dita#vdidetails"/>. </p>
+         </li>
+         <li>
+            <p>CD/DVD images in standard ISO format. </p>
+         </li>
+         <li>
+            <p>Floppy images in standard RAW format. </p>
+         </li>
+      </ul>
+      <p>For each image, the Virtual Media Manager shows you the full path of the image file and other information, such as the virtual machine the image is currently attached to. </p>
+      <p>The Virtual Media Manager enables you to do the following: </p>
+      <ul>
+         <li>
+            <p><b outputclass="bold">Add</b> an image to the known media. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Create</b> a new disk image. </p>
+            <ul>
+               <li>
+                  <p>For hard disks, the <b outputclass="bold">Create Virtual Hard Disk</b> wizard is shown. See <xref href="create-virtual-hard-disk-image.dita"/>.</p>
+               </li>
+               <li>
+                  <p>For optical disks, the <b outputclass="bold">VISO Creator</b> tool is shown. See <xref href="create-optical-disk-image.dita"/>.</p>
+               </li>
+               <li>
+                  <p>For floppy disks, the <b outputclass="bold">Floppy Disk Creator</b> tool is shown. See <xref href="create-floppy-disk-image.dita"/>.</p>
+               </li>
+            </ul>
+         </li>
+         <li>
+            <p><b outputclass="bold">Copy</b> an image to create another one. </p>
+            <p>For virtual hard disks, you can specify one of the following target types: VDI, VHD, or VMDK. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Move</b> an image to another location. </p>
+            <p>A file dialog prompts you for the new image file location. </p>
+            <p>When you use the Virtual Media Manager to move a disk image, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> updates all related configuration files automatically. </p>
+            <note>
+               <p>Always use the Virtual Media Manager or the <userinput>VBoxManage modifymedium</userinput> command to move a disk image. </p>
+               <p>If you use a file management feature of the host OS to move a disk image to a new location, run the <userinput>VBoxManage modifymedium --setlocation</userinput> command to configure the new path of the disk image on the host file system. This command updates the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> configuration automatically. </p>
+            </note>
+         </li>
+         <li>
+            <p><b outputclass="bold">Remove</b> an image from the known media. You can optionally delete the image file when removing the image.</p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Release</b> an image to detach it from a VM. This action only applies if the image is currently attached to a VM as a virtual hard disk.</p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Clear</b> all inaccessible disk images from the list. The disk images are released from the VMs they are attached to and removed from the known media.</p>
+            <note>
+               <p>This option is for optical disks and floppy disks only.</p>
+            </note>
+         </li>
+         <li>
+            <p><b outputclass="bold">Search</b> for an image by name or UUID.</p>
+         </li>
+         <li>
+            <p>View and edit the <b outputclass="bold">Properties</b> of a disk image.</p>
+            <p>Available properties include the following:</p>
+            <ul>
+               <li>
+                  <p><b outputclass="bold">Type:</b> Specifies the snapshot behavior of the disk. See <xref href="hdimagewrites.dita#hdimagewrites"/>. </p>
+               </li>
+               <li>
+                  <p><b outputclass="bold">Location:</b> Specifies the location of the disk image file on the host system. You can use a file dialog to browse for the disk image location.</p>
+               </li>
+               <li>
+                  <p><b outputclass="bold">Description:</b> Specifies a short description of the disk image.</p>
+               </li>
+               <li>
+                  <p><b outputclass="bold">Size:</b> Specifies the size of the disk image. You can use the slider to increase or decrease the disk image size.</p>
+               </li>
+               <li>
+                  <p><b outputclass="bold">Information:</b> Specifies detailed information about the disk image.</p>
+               </li>
+            </ul>
+         </li>
+         <li>
+            <p><b outputclass="bold">Refresh</b> the property values of the selected disk image.</p>
+         </li>
+      </ul>
+      <p>To perform these actions, highlight the medium in the Virtual Media Manager and then do one of the following: </p>
+      <ul>
+         <li>
+            <p>Click an icon in the Virtual Media Manager toolbar. </p>
+         </li>
+         <li>
+            <p>Right-click the medium and select an option. </p>
+         </li>
+      </ul>
+      <p>Use the <b outputclass="bold">Storage</b> page in a VM's <b outputclass="bold">Settings</b> window to create a new disk image. By default, disk images are stored in the VM's folder. </p>
+      <p>You can copy hard disk image files to other host systems and then import them in to VMs from the host system. However, some Windows guest OSes may require that you configure the new VM in a similar way to the old one. </p>
+      <note>
+         <p>Do not simply make copies of virtual disk images. If you import such a second copy into a VM, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> issues an error because <ph conkeyref="vbox-conkeyref-phrases/product-name"/> assigns a universally unique identifier (UUID) to each disk image to ensure that it is only used one time. See <xref href="cloningvdis.dita#cloningvdis"/>. Also, if you want to copy a VM to another system, use the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> import and export features. See <xref href="ovf.dita#ovf"/>. </p>
+      </note>
+   </body>
+</topic>
Index: /trunk/doc/manual/en_US/dita/topics/vm-activity-overview.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/vm-activity-overview.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/vm-activity-overview.dita	(revision 108921)
@@ -2,22 +2,15 @@
 <!DOCTYPE topic
   PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="vm-activity-overview">
-               <title>VM Activity Overview</title>
-               <body>
-                  <p>The VM Activity Overview tool displays several performance 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.</p>
-                  <p>To display the VM Activity Overview tool, in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> click <b outputclass="bold">Activities</b>. The <b outputclass="bold">VM Activity Overview</b> window is shown.</p>
+<topic xml:lang="en-us" id="tk_vm-activity-overview">
+  <title>VM Activity Overview</title>
+  <body>
+    <p>The VM Activity Overview tool displays several performance 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.</p>
+    <p>To display the VM Activity Overview tool, in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/> click <b outputclass="bold">Activities</b>. The <b outputclass="bold">VM Activity Overview</b> window is shown.</p>
     <ul id="ul_hqh_5hg_ccc">
-      <li>To show metrics for <i>all</i> virtual machines, including those that are not running, right-click the list of
-        virtual machines and select <b outputclass="bold">List All Virtual Machines</b>. </li>
-      <li>To show metrics for cloud VMs, right-click the list of virtual machines and select <b outputclass="bold">Show
-          Cloud Virtual Machines</b>.</li>
-      <li>To configure the set of metrics to be shown, click <b outputclass="bold">Columns</b> in the toolbar. You can
-        then sort the list of virtual machines by a particular metric.</li>
-      <li>To see more performance information for a virtual machine, select the VM name and click <b outputclass="bold"
-          >VM Activity</b> in the toolbar. The <b outputclass="bold">VM Activity</b> tab of the <b outputclass="bold"
-          >Session Information</b> dialog is shown, see <xref
-          href="vm-activity-session-information.dita#vm-activity-session-information"/>.</li>
+      <li>To show metrics for <i>all</i> virtual machines, including those that are not running, right-click the list of virtual machines and select <b outputclass="bold">List All Virtual Machines</b>. </li>
+      <li>To show metrics for cloud VMs, right-click the list of virtual machines and select <b outputclass="bold">Show Cloud Virtual Machines</b>.</li>
+      <li>To configure the set of metrics to be shown, click <b outputclass="bold">Columns</b> in the toolbar. You can then sort the list of virtual machines by a particular metric.</li>
+      <li>To see more performance information for a virtual machine, select the VM name and click <b outputclass="bold">VM Activity</b> in the toolbar. The <b outputclass="bold">VM Activity</b> tab of the <b outputclass="bold">Session Information</b> dialog is shown, see <xref href="vm-activity-session-information.dita"/>.</li>
     </ul>
-               </body>
-               
-            </topic>
+  </body>
+</topic>
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 108920)
+++ /trunk/doc/manual/en_US/dita/topics/vm-activity-session-information.dita	(revision 108921)
@@ -2,34 +2,26 @@
 <!DOCTYPE topic
   PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
-<topic xml:lang="en-us" id="vm-activity-session-information">
-               <title>Session Information Dialog</title>
-               <body>
-                  <p>The Session Information dialog includes multiple tabs that show important configuration and runtime
-      information for the guest system. The tabs are as follows: </p>
-                  <ul>
-                     <li>
-                        <p><b outputclass="bold">Configuration Details</b>. Displays the system configuration of the
-          virtual machine in a tabular format. The displayed information includes details such as storage configuration
-          and audio settings. </p>
-                     </li>
-                     <li>
-                        <p><b outputclass="bold">Runtime Information</b>. Displays runtime information for the guest
-          session in a tabular format similar to the Configuration Details tab. </p>
-                     </li>
-                     <li>
-                        <p><b outputclass="bold">VM Activity</b>. Includes several time series charts which monitor
-          guest resource usage including CPU, RAM, Disk I/O, and Network. Note that the RAM chart requires the Guest
-          Additions to be running on the guest system. The VM Activity tab can also be accessed directly from the VM
-          Activity Overview tool. See <xref href="vm-activity-overview.dita#vm-activity-overview"/>. </p>
-                     </li>
-                     <li>
-                        <p><b outputclass="bold">Guest Control</b>. Details of processes used by the Guest Control File
-          Manager. See <xref href="guestadd-gc-file-manager.dita#guestadd-gc-file-manager"/>. </p>
-                     </li>
-                  </ul>
-                 <note><p>For cloud VMs, only the VM Activity tab is shown.</p></note>
-                  <p>To display session information for a guest VM or a cloud VM, select the VM name in the machine list
-      and click <b>Activity</b> in the machine tools menu.</p>
-               </body>
-               
-            </topic>
+<topic xml:lang="en-us" id="tk_vm-activity-session-information">
+   <title>Session Information Dialog</title>
+   <body>
+      <p>The Session Information dialog includes multiple tabs that show important configuration and runtime information for the guest system. The tabs are as follows: </p>
+      <ul>
+         <li>
+            <p><b outputclass="bold">Configuration Details</b>. Displays the system configuration of the virtual machine in a tabular format. The displayed information includes details such as storage configuration and audio settings. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Runtime Information</b>. Displays runtime information for the guest session in a tabular format similar to the Configuration Details tab. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">VM Activity</b>. Includes several time series charts which monitor guest resource usage including CPU, RAM, Disk I/O, and Network. Note that the RAM chart requires the Guest Additions to be running on the guest system. The VM Activity tab can also be accessed directly from the VM Activity Overview tool. See <xref href="vm-activity-overview.dita"/>. </p>
+         </li>
+         <li>
+            <p><b outputclass="bold">Guest Control</b>. Details of processes used by the Guest Control File Manager. See <xref href="guestadd-gc-file-manager.dita"/>.</p>
+         </li>
+      </ul>
+      <note>
+         <p>For cloud VMs, only the VM Activity tab is shown.</p>
+      </note>
+      <p>To display session information for a guest VM or a cloud VM, select the VM name in the machine list and click <b>Activity</b> in the machine tools menu.</p>
+   </body>
+</topic>
Index: /trunk/doc/manual/en_US/dita/topics/vm-info.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/vm-info.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/vm-info.dita	(revision 108921)
@@ -14,12 +14,10 @@
                      <p><b outputclass="bold"> VM Activity Overview.</b> Displays an overview of performance metrics for
           all running virtual machines and cloud VM instances. </p>
-                     <p>
-          See <xref href="vm-activity-overview.dita#vm-activity-overview"/>.
-        </p>
+                     <p> See <xref href="vm-activity-overview.dita"/>.</p>
                   </li>
                   <li>
                      <p><b outputclass="bold">Session Information Dialog.</b> Displays configuration and runtime
           information for the selected guest system or cloud VM. </p>
-                     <p>See <xref href="vm-activity-session-information.dita#vm-activity-session-information"/>. </p>
+                     <p>See <xref href="vm-activity-session-information.dita"/>.</p>
                   </li>
                </ul>
Index: /trunk/doc/manual/en_US/dita/topics/vm-status-bar.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/vm-status-bar.dita	(revision 108920)
+++ /trunk/doc/manual/en_US/dita/topics/vm-status-bar.dita	(revision 108921)
@@ -13,7 +13,4 @@
       </li>
     </ul>
-   
-   <p>See <xref href="BasicConcepts.dita#BasicConcepts"/> for detailed information about the available virtual 
-      machine settings.</p>
     
     <p><xref href="#vm-status-bar/table-status-bar-icons"/> describes the icons on the status bar.</p>
@@ -54,5 +51,5 @@
               <p><b>Storage (SATA)</b></p>
               <p>Settings for attached SATA storage devices, such as hard disk drives.</p>
-              <p>See also <xref href="settings-storage.dita#settings-storage"/>.</p>
+              <p>See also <xref href="settings-storage.dita"/>.</p>
               
             </entry>
@@ -74,7 +71,7 @@
               <p><b>Storage (IDE)</b></p>
               <p>Settings for attached IDE storage devices, such as optical CD-ROM drives.</p>
-              <p>See also <xref href="settings-storage.dita#settings-storage"/>.</p>
+              <p>See also <xref href="settings-storage.dita"/>.</p>
               <p>Right-click to show options for adding and removing IDE devices.</p>
-              <p>See also <xref href="intro-removable-media-changing.dita#intro-removable-media-changing"/>.</p>
+              <p>See also <xref href="virtual-media-manager.dita"/>.</p>
             </entry>
           </row>
@@ -97,5 +94,5 @@
               <p>Right-click to change a setting. The status bar icon is updated automatically to show 
                 which settings are enabled.</p>
-              <p>See also <xref href="settings-audio.dita#settings-audio"/>.</p>
+              <p>See also <xref href="settings-audio.dita"/>.</p>
             </entry>
           </row>
@@ -117,5 +114,5 @@
               <p>Settings for attached network adapters.</p>
               <p>Right-click to connect or disconnect a network adapter.</p>
-              <p>See also <xref href="settings-network.dita#settings-network"/>.</p>
+              <p>See also <xref href="settings-network.dita"/>.</p>
             </entry>
           </row>
@@ -322,5 +319,5 @@
           </ul>
           <p>Click the check mark button to save your changes to the status bar.</p>
-          <p>See also <xref href="user-interface.dita#user-interface"/> for other options to change the status bar.</p>
+          <p>See also <xref href="user-interface.dita"/> for other options to change the status bar.</p>
         </li>     
       </ul>  
Index: /trunk/doc/manual/en_US/dita/topics/working-with-vms.dita
===================================================================
--- /trunk/doc/manual/en_US/dita/topics/working-with-vms.dita	(revision 108921)
+++ /trunk/doc/manual/en_US/dita/topics/working-with-vms.dita	(revision 108921)
@@ -0,0 +1,20 @@
+<?xml version='1.0' encoding='UTF-8'?>
+<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
+<topic xml:lang="en-us" id="ct_working-with-vms">
+  <title>Working with Virtual Machines</title>
+  <body>
+    <p>This chapter provides detailed steps for configuring an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtual machine (VM). For an introduction to <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and steps to get your first virtual machine running, see <xref href="Introduction.dita"/>.</p>
+    <p>You have considerable latitude when deciding what virtual hardware to provide to the guest. Use virtual hardware to communicate with the host system or with other guests. For example, you can use virtual hardware in the following ways: </p>
+    <ul>
+      <li>
+        <p>Have <ph conkeyref="vbox-conkeyref-phrases/product-name"/> present an ISO CD-ROM image to a guest system as if it were a physical CD-ROM. </p>
+      </li>
+      <li>
+        <p>Provide a guest system access to the physical network through its virtual network card. </p>
+      </li>
+      <li>
+        <p>Provide the host system, other guests, and computers on the Internet access to the guest system. </p>
+      </li>
+    </ul>
+  </body>
+</topic>
Index: /trunk/doc/manual/en_US/man_VBoxManage-clonemedium.xml
===================================================================
--- /trunk/doc/manual/en_US/man_VBoxManage-clonemedium.xml	(revision 108920)
+++ /trunk/doc/manual/en_US/man_VBoxManage-clonemedium.xml	(revision 108921)
@@ -92,5 +92,5 @@
       You can use the Virtual Media Manager to transfer the cloned image
       to another host system or reimport it into &product-name;. See
-      <xref linkend="virtual-media-manager" /> and <xref linkend="cloningvdis" />.
+      <xref linkend="ct_virtual-media-manager" /> and <xref linkend="cloningvdis" />.
     </para>
     <variablelist>
Index: /trunk/doc/manual/en_US/man_VBoxManage-controlvm.xml
===================================================================
--- /trunk/doc/manual/en_US/man_VBoxManage-controlvm.xml	(revision 108920)
+++ /trunk/doc/manual/en_US/man_VBoxManage-controlvm.xml	(revision 108921)
@@ -1176,5 +1176,5 @@
         and <literal>bidirectional</literal>. The default value is
         <literal>disabled</literal>. See
-        <xref linkend="generalsettings" />.
+        <xref linkend="ct_generalsettings" />.
       </para>
       <para>
Index: /trunk/doc/manual/en_US/man_VBoxManage-list.xml
===================================================================
--- /trunk/doc/manual/en_US/man_VBoxManage-list.xml	(revision 108920)
+++ /trunk/doc/manual/en_US/man_VBoxManage-list.xml	(revision 108921)
@@ -216,5 +216,5 @@
       <para>
         This command performs the same function as the Virtual Media
-        Manager. See <xref linkend="virtual-media-manager"/>.
+        Manager. See <xref linkend="ct_virtual-media-manager"/>.
       </para>
     </refsect2>
@@ -247,5 +247,5 @@
       <para>
         This command performs the same function as the Virtual Media
-        Manager. See <xref linkend="virtual-media-manager"/>.
+        Manager. See <xref linkend="ct_virtual-media-manager"/>.
       </para>
     </refsect2>
@@ -290,5 +290,5 @@
       <para>
         This command performs the same function as the Virtual Media
-        Manager. See <xref linkend="virtual-media-manager"/>.
+        Manager. See <xref linkend="ct_virtual-media-manager"/>.
       </para>
     </refsect2>
Index: /trunk/doc/manual/en_US/man_VBoxManage-modifyvm.xml
===================================================================
--- /trunk/doc/manual/en_US/man_VBoxManage-modifyvm.xml	(revision 108920)
+++ /trunk/doc/manual/en_US/man_VBoxManage-modifyvm.xml	(revision 108921)
@@ -694,5 +694,5 @@
       shown in each VM's <emphasis role="bold">Settings</emphasis>
       dialog in the VirtualBox Manager. See
-      <xref linkend="BasicConcepts" />. However, some settings can only
+      <xref linkend="ct_working-with-vms" />. However, some settings can only
       be viewed and managed with the <command>VBoxManage</command>
       command.
@@ -769,5 +769,5 @@
               Specifies the amount of host system RAM to allocate to the
               VM. The size is in MB. See
-              <xref linkend="create-vm" />.
+              <xref linkend="tk_create-vm" />.
             </para></listitem>
         </varlistentry>
@@ -786,5 +786,5 @@
           <listitem><para>
               Specifies the amount of RAM to allocate to the virtual
-              graphics card. See <xref linkend="settings-display" />.
+              graphics card. See <xref linkend="ct_settings-display" />.
             </para></listitem>
         </varlistentry>
@@ -1781,5 +1781,5 @@
               the port or an I/O base address and IRQ. For information
               about the traditional COM port I/O base address and IRQ
-              values, see <xref linkend="serialports" />.
+              values, see <xref linkend="ct_serialports" />.
             </para></listitem>
         </varlistentry>
@@ -1789,5 +1789,5 @@
               Specifies how &product-name; connects the specified
               virtual serial port to the host system that runs the VM.
-              See <xref linkend="serialports" />.
+              See <xref linkend="ct_serialports" />.
             </para><para>
               Ensure that you first configure the virtual serial port by
@@ -1972,5 +1972,5 @@
               <literal>guesttohost</literal>, and
               <literal>bidirectional</literal>. See
-              <xref linkend="generalsettings" />.
+              <xref linkend="ct_generalsettings" />.
             </para><para>
               The clipboard feature is available only if you have the
@@ -2010,5 +2010,5 @@
           <listitem><para>
               Enables you to configure multiple monitors. See
-              <xref linkend="settings-display" />.
+              <xref linkend="ct_settings-display" />.
             </para></listitem>
         </varlistentry>
Index: /trunk/doc/manual/ru_RU/man_VBoxManage-clonemedium.xml
===================================================================
--- /trunk/doc/manual/ru_RU/man_VBoxManage-clonemedium.xml	(revision 108920)
+++ /trunk/doc/manual/ru_RU/man_VBoxManage-clonemedium.xml	(revision 108921)
@@ -86,5 +86,5 @@
       Можно использовать Менеджер Виртуальных Носителей для передачи
       клонированного носителя на другой хост или импортировать его в &product-name;.
-      Смотрите <xref linkend="virtual-media-manager" /> и <xref linkend="cloningvdis" />.
+      Смотрите <xref linkend="ct_virtual-media-manager" /> и <xref linkend="cloningvdis" />.
     </para>
     <variablelist>
Index: /trunk/doc/manual/ru_RU/man_VBoxManage-controlvm.xml
===================================================================
--- /trunk/doc/manual/ru_RU/man_VBoxManage-controlvm.xml	(revision 108920)
+++ /trunk/doc/manual/ru_RU/man_VBoxManage-controlvm.xml	(revision 108921)
@@ -1247,5 +1247,5 @@
         <literal>guesttohost</literal> и <literal>bidirectional</literal>.
         Значение по умолчанию <literal>disabled</literal>. Смотрите
-        <xref linkend="generalsettings" />.
+        <xref linkend="ct_generalsettings" />.
       </para>
       <para>
Index: /trunk/doc/manual/ru_RU/man_VBoxManage-list.xml
===================================================================
--- /trunk/doc/manual/ru_RU/man_VBoxManage-list.xml	(revision 108920)
+++ /trunk/doc/manual/ru_RU/man_VBoxManage-list.xml	(revision 108921)
@@ -202,5 +202,5 @@
       <para>
         Эта команда выполняет ту же функцию, что и Менеджер виртуальных
-        носителей. Смотрите <xref linkend="virtual-media-manager"/>.
+        носителей. Смотрите <xref linkend="ct_virtual-media-manager"/>.
       </para>
     </refsect2>
@@ -233,5 +233,5 @@
       <para>
         Эта команда выполняет ту же функцию, что и Менеджер виртуальных
-        носителей. Смотрите <xref linkend="virtual-media-manager"/>.
+        носителей. Смотрите <xref linkend="ct_virtual-media-manager"/>.
       </para>
     </refsect2>
@@ -275,5 +275,5 @@
       <para>
         Эта команда выполняет ту же функцию, что и Менеджер виртуальных
-        носителей. Смотрите <xref linkend="virtual-media-manager"/>.
+        носителей. Смотрите <xref linkend="ct_virtual-media-manager"/>.
       </para>
     </refsect2>
Index: /trunk/doc/manual/ru_RU/man_VBoxManage-modifyvm.xml
===================================================================
--- /trunk/doc/manual/ru_RU/man_VBoxManage-modifyvm.xml	(revision 108920)
+++ /trunk/doc/manual/ru_RU/man_VBoxManage-modifyvm.xml	(revision 108921)
@@ -654,5 +654,5 @@
       Большинство этих свойств соответствуют настройкам ВМ отображаемых
       в диалоге <emphasis role="bold">Настройки</emphasis> Менеджера
-      VirtualBox для каждой ВМ. Смотрите <xref linkend="BasicConcepts" />.
+      VirtualBox для каждой ВМ. Смотрите <xref linkend="ct_working-with-vms" />.
       Однако, некоторые настройки могут отображаться или управляться
       только командой <command>VBoxManage</command>.
@@ -728,5 +728,5 @@
           <listitem><para>
               Задает количество оперативной памяти хоста, выделенной ВМ.
-              Размер в МБ. Смотрите <xref linkend="create-vm" />.
+              Размер в МБ. Смотрите <xref linkend="tk_create-vm" />.
             </para></listitem>
         </varlistentry>
@@ -745,5 +745,5 @@
           <listitem><para>
               Задает количество оперативной памяти, выделенной
-              графической карте. Смотрите <xref linkend="settings-display" />.
+              графической карте. Смотрите <xref linkend="ct_settings-display" />.
             </para></listitem>
         </varlistentry>
@@ -1757,5 +1757,5 @@
               <literal>off</literal>, отключающее порт или базу I/O и
               IRQ. Для информации по значениям базы I/O и IRQ традиционных
-              COM портов смотрите <xref linkend="serialports" />.
+              COM портов смотрите <xref linkend="ct_serialports" />.
             </para></listitem>
         </varlistentry>
@@ -1765,5 +1765,5 @@
               Указывает, как &product-name; соединяет указанный
               виртуальный последовательный порт к хост-системе, где
-              работает ВМ. Смотрите <xref linkend="serialports" />.
+              работает ВМ. Смотрите <xref linkend="ct_serialports" />.
             </para><para>
               Убедитесь, что сначала настроили виртуальный последовательный
@@ -1945,5 +1945,5 @@
               <literal>guesttohost</literal> и
               <literal>bidirectional</literal>. Смотрите
-              <xref linkend="generalsettings" />.
+              <xref linkend="ct_generalsettings" />.
             </para><para>
               Функционал буфера обмена доступен только если
@@ -1970,5 +1970,5 @@
           <listitem><para>
               Позволяет настроить несколько мониторов. Смотрите
-              <xref linkend="settings-display" />.
+              <xref linkend="ct_settings-display" />.
             </para></listitem>
         </varlistentry>
