Changeset 35232 in vbox

Timestamp:

Dec 20, 2010 8:22:37 AM (14 years ago)

Author:

vboxsync

Message:

some corrections

Location:

trunk/doc/manual/en_US

Files:

• user_BasicConcepts.xml (modified) (3 diffs)
• user_Storage.xml (modified) (1 diff)
• user_Troubleshooting.xml (modified) (1 diff)
• user_VBoxManage.xml (modified) (1 diff)

trunk/doc/manual/en_US/user_BasicConcepts.xml

@@ -543 +543 @@
             <glossdef>
               <para>This enables Extensible Firmware Interface (EFI), which
-              replaces the legacy BIOS, which may be useful for certain
+              replaces the legacy BIOS and may be useful for certain
               advanced use cases. Please refer to <xref linkend="efi" /> for
               details.</para>
@@ -1263 +1263 @@
     To switch back to using the BIOS, use: <screen>VBoxManage modifyvm "VM name" --firmware bios</screen>One
     notable user of EFI is Apple's Mac OS X, but recent Linuxes (such as
-    Fedora 11) and Windows (starting with Vista) can be booted using EFI as
-    well.</para>
+    Fedora 11) and Windows (starting with Vista) offer special versions that can
+    be booted using EFI as well.</para>
 
     <para>Another possible use of EFI in VirtualBox is development and testing
@@ -1272 +1272 @@
     enhanced as EFI matures and becomes more widespread. While Mac OS X and
     Linux guests are known to work fine, Windows guests are currently unable
-    to boot using EFI.</para>
+    to boot with the VirtualBox EFI implementation.</para>
 
     <sect2 id="efividmode">

trunk/doc/manual/en_US/user_Storage.xml

@@ -412 +412 @@
     <title>Special image write modes</title>
 
-    <para>For each virtual disk image supported by VirtualBox, you can use
+    <para>For each virtual disk image supported by VirtualBox, you can
     determine separately how it should be affected by write operations from a
     virtual machine and snapshot operations. This applies to all of the

trunk/doc/manual/en_US/user_Troubleshooting.xml

@@ -585 +585 @@
       show you which one failed the test. This usually means that you are
       running an outdated or misconfigured OpenGL driver on your host. It can
-      also mean that your video chip is lacking require functionality.</para>
+      also mean that your video chip is lacking required functionality.</para>
     </sect2>
   </sect1>

trunk/doc/manual/en_US/user_VBoxManage.xml

@@ -1944 +1944 @@
           zero the free disk space before compressing the virtual disk image.
           </para>
+          
+          <para>Please note that compacting is currently only available for
+          VDI images. A similar effect can be achieved by zeroing out free
+          blocks and then cloning the disk to any other dynamically expanding
+          format. You can use this workaround until compacting is also supported
+          for disk formats other than VDI.</para>
         </listitem>