Changeset 58485 in vbox for trunk

Timestamp:

Oct 29, 2015 1:49:50 PM (9 years ago)

Author:

vboxsync

Message:

doc/manual: typos, spaces.

Location:

trunk/doc/manual/en_US

Files:

• user_BasicConcepts.xml (modified) (3 diffs)
• user_GuestAdditions.xml (modified) (2 diffs)
• user_Installation.xml (modified) (1 diff)
• user_Introduction.xml (modified) (6 diffs)
• user_Networking.xml (modified) (3 diffs)
• user_Security.xml (modified) (6 diffs)
• user_Storage.xml (modified) (5 diffs)
• user_Technical.xml (modified) (1 diff)
• user_Troubleshooting.xml (modified) (7 diffs)

trunk/doc/manual/en_US/user_BasicConcepts.xml

@@ -172 +172 @@
             <para>These license restrictions are also enforced on a technical
             level. Mac OS X verifies whether it is running on Apple hardware,
-            and most DVDs that that come with Apple hardware even check for an
+            and most DVDs that come with Apple hardware even check for an
             exact model. These restrictions are <emphasis>not</emphasis>
             circumvented by VirtualBox and continue to apply.</para>
@@ -658 +658 @@
       <para>On this tab you can also set the <emphasis role="bold">"CPU execution
       cap"</emphasis>. This setting
-      limits the amount of time a host CPU spents to emulate a virtual CPU.
+      limits the amount of time a host CPU spends to emulate a virtual CPU.
       The default setting is 100% meaning that there is no limitation. A setting
       of 50% implies a single virtual CPU can use up to 50% of a single host
@@ -715 +715 @@
       operating systems. The options available are documented under the
       <computeroutput>paravirtprovider</computeroutput> option
-      in <xref linkend="vboxmanage-modifyvm" />. For futher details on
+      in <xref linkend="vboxmanage-modifyvm" />. For further details on
       the paravirtualization providers, please refer to
       <xref linkend="gimproviders" />.</para>

trunk/doc/manual/en_US/user_GuestAdditions.xml

@@ -360 +360 @@
         <title>Unattended Installation</title>
 
-        <para>As a prerequiste for performing an unattended installation of the
+        <para>As a prerequisite for performing an unattended installation of the
         VirtualBox Guest Additions on a Windows guest, there need to be
         Oracle CA (Certificate Authority)
-        certificates installed in order to prevent user intervention popus which
+        certificates installed in order to prevent user intervention popups which
         will undermine a silent installation.</para>
 
@@ -1339 +1339 @@
       <para>As VirtualBox can run on a variety of host OSes and also supports a wide
       range of guests, certain data formats must be translated after those
-      got transfered over so that the target OS (that is, the side which receiving the
+      got transferred over so that the target OS (that is, the side which receiving the
       data) is able to handle them in an appropriate manner.</para>
 

trunk/doc/manual/en_US/user_Installation.xml

@@ -869 +869 @@
 zonecfg:vboxzone&gt;exit</screen>
 
-      <para>If you are running VirtualBox 2.2.0 or above on Solaris 11 or 
+      <para>If you are running VirtualBox 2.2.0 or above on Solaris 11 or
       above, you may add a device for <computeroutput>/dev/vboxusbmon</computeroutput>
       too, similar to what was shown above. This does not apply to Solaris 10
       hosts due to lack of USB support.</para>
-      
+
       <para>Next reboot the zone using <computeroutput>zoneadm</computeroutput>
       and you should be able to run VirtualBox from within the configured zone.</para>

trunk/doc/manual/en_US/user_Introduction.xml

@@ -421 +421 @@
               <para>Windows 8 (32-bit and 64-bit)</para>
             </listitem>
-            
+
             <listitem>
               <para>Windows 8.1 (32-bit and 64-bit)</para>
             </listitem>
-            
+
             <listitem>
               <para>Windows 10 RTM build 10240 (32-bit and 64-bit)</para>
             </listitem>
-            
+
             <listitem>
               <para>Windows Server 2012 (64-bit)</para>
@@ -1266 +1266 @@
     <title>Using VM groups</title>
 
-    <para>VM groups enable the user to create ad hoc groups of VMs, and to 
-    manage and perform functions on them collectively, as well as individually. 
+    <para>VM groups enable the user to create ad hoc groups of VMs, and to
+    manage and perform functions on them collectively, as well as individually.
     There are a number of features relating to groups:</para>
- 
+
     <orderedlist>
         <listitem>
           <para>
             Create a group using GUI option 1) Drag one VM on top of another
-            VM. 
+            VM.
           </para>
           <para>
@@ -1583 +1583 @@
     an existing VM.<footnote><para>Cloning support was introduced with VirtualBox
     4.1.</para></footnote></para>
-    
+
     <para>A wizard will guide you through the clone process:</para>
 
@@ -1592 +1592 @@
       </imageobject>
     </mediaobject>
-    
+
     <para>This wizard can be invoked from the context menu of the Manager's VM
     list (select "Clone") or the "Snapshots" view of the selected VM. First
@@ -1621 +1621 @@
       </listitem>
     </itemizedlist>
-        
+
     <para>After selecting the clone mode, you need to decide about what exactly
     should be cloned. You can always create a clone of the <emphasis
@@ -1630 +1630 @@
     children, you can also clone the <emphasis role="italic">current state and
         all children</emphasis>. This creates a clone starting with this
-    snapshot and includes all child snaphots.</para>
+    snapshot and includes all child snapshots.</para>
 
     <para>The clone operation itself can be a lengthy operation depending on

trunk/doc/manual/en_US/user_Networking.xml

@@ -419 +419 @@
   <sect1 id="network_nat_service">
     <title>Network Address Translation Service (experimental)</title>
-    
+
     <para>The Network Address Translation (NAT) service works in a similar way
     to a home router, grouping the systems using it into a network and
@@ -445 +445 @@
     <para>To disable it again, use:</para>
     <para><screen>VBoxManage natnetwork modify --netname natnet1 --dhcp off</screen></para>
-    <para>DHCP server provides list of registered nameservers, but doesn't map 
+    <para>DHCP server provides list of registered nameservers, but doesn't map
     servers from 127/8 network.</para>
     <para>To start the NAT service, use the following command:</para>
@@ -703 +703 @@
       "File" -&gt; "Preferences" -&gt; "Network" -&gt; "Host-only network"
       -&gt; "(+)Add host-only network", or via command line with</para>
-      <screen>VBoxManage hostonlyif create</screen> 
+      <screen>VBoxManage hostonlyif create</screen>
       <para>see <xref linkend="vboxmanage-hostonlyif" /> for details.</para>
 

trunk/doc/manual/en_US/user_Security.xml

@@ -72 +72 @@
             <para>
               Oracle continually improves its software and documentation. Check this
-              note note yearly for revisions.
+              note yearly for revisions.
             </para>
           </glossdef>
@@ -124 +124 @@
       </para>
     </sect2>
-  
+
     <sect2>
       <title>Post Installation Configuration</title>
@@ -140 +140 @@
     </sect2>
   </sect1>
-  
+
   <sect1>
     <title>Security Features</title>
@@ -161 +161 @@
       </para>
     </sect2>
-    
+
     <sect2>
       <title>Secure Configuration of Virtual Machines</title>
@@ -331 +331 @@
           <para>When Page Fusion (see <xref linkend="guestadd-pagefusion"/>)
           is enabled, it is possible that a side-channel opens up that allows
-          a malicious guest to determin the address space layout (i.e. where
+          a malicious guest to determine the address space layout (i.e. where
           DLLs are typically loaded) of one other VM running on the same host.
           This information leak in it self is harmless, however the malicious
@@ -351 +351 @@
           default, the service binds to localhost preventing any remote connection.</para>
         </listitem>
-        
+
         <listitem>
           <para>Traffic sent over a UDP Tunnel network attachment is not

trunk/doc/manual/en_US/user_Storage.xml

@@ -63 +63 @@
 
           <para>In VirtualBox, each virtual machine may have one IDE
-          contoller enabled, which gives you up to four virtual storage
+          controller enabled, which gives you up to four virtual storage
           devices that you can attach to the machine. (By default, one of
           these four -- the secondary master -- is preconfigured to be the
@@ -194 +194 @@
         <listitem>
           <para>The <emphasis role="bold">USB mass storage device class</emphasis>
-          is a standard to connect external storage devices like hard disksor flash
+          is a standard to connect external storage devices like hard disks or flash
           drives to a host through USB. All major operating systems support these
           devices for a long time and ship generic drivers making third-party
@@ -556 +556 @@
         only a small amount of data and the majority of the disk content
         remains unchanged. The modified blocks are stored in differencing
-        images which remain reletively small and the shared content is stored
+        images which remain relatively small and the shared content is stored
         only once at the host.</para>
       </listitem>
@@ -723 +723 @@
     unique identity number (UUID) to each disk image, which is also stored
     inside the image, and VirtualBox will refuse to work with two images that
-    use the same number. If you do accidentally try to reimport a disk image
+    use the same number. If you do accidentally try to re-import a disk image
     which you copied normally, you can make a second copy using VirtualBox's
     utility and import that instead.</para>
@@ -761 +761 @@
     linkend="storage-iscsi" />).</para>
 
-    <para>While buffering is a useful default setting for virtualizating a few
+    <para>While buffering is a useful default setting for virtualizing a few
     machines on a desktop computer, there are some disadvantages to this
     approach:<orderedlist>

trunk/doc/manual/en_US/user_Technical.xml

@@ -82 +82 @@
       snapshots, they will appear in a
       <computeroutput>Snapshots</computeroutput> subfolder. For each VM, you
-      can change the location of its snapsnots folder in the VM
+      can change the location of its snapshots folder in the VM
       settings.</para>
 

trunk/doc/manual/en_US/user_Troubleshooting.xml

@@ -413 +413 @@
       <xref linkend="vboxmanage-debugvm" />. The VM core file contain the
       memory and CPU dumps of the VM and can be useful for debugging your
-      guest OS. The 64-bit ELF object format specficiation can be obtained
+      guest OS. The 64-bit ELF object format specification can be obtained
       here: <literal><ulink
       url="http://downloads.openwatcom.org/ftp/devel/docs/elf-64-gen.pdf">http://downloads.openwatcom.org/ftp/devel/docs/elf-64-gen.pdf</ulink></literal>.</para>
@@ -878 +878 @@
           for rendering so that corrupted d3d8.dll and d3d9.dll system files will
           have no effect on the actual rendering.</para></note>
-          
-      <para>This is why such a detected file corruption is not considered as fatal 
+
+      <para>This is why such a detected file corruption is not considered as fatal
           for the basic Direct3D installation on all supported Windows guests,
           and for WDDM Direct3D installation on Windows 7 and later guests.</para>
@@ -962 +962 @@
       up to 64 MB on standard PCs.</para>
 
-      <para>This is a HIMEM.SYS limitation documented by Microsoft in Knowledge base 
+      <para>This is a HIMEM.SYS limitation documented by Microsoft in Knowledge base
       article KB 116256.
       Windows 3.1 memory limits are described in detail in Microsoft Knowledge base
@@ -1068 +1068 @@
 
       <para>Solaris 10 releases up to and including Solaris 10 8/07 ("S10U4")
-          incorrectly detect newer Intel processors produced since 2007. This 
+          incorrectly detect newer Intel processors produced since 2007. This
           problem leads to the 64-bit Solaris kernel crashing (and usually causing
           a triple fault) almost immediately during startup, in both virtualized
@@ -1074 +1074 @@
       </para>
       <para>
-          The recommended solution is upgrading to at least Solaris 10 5/08 
-          ("S10U5"). Alternative solutions include forcing Solaris to always 
-          boot the 32-bit kernel or applying a patch for bug 6574102 (while 
+          The recommended solution is upgrading to at least Solaris 10 5/08
+          ("S10U5"). Alternative solutions include forcing Solaris to always
+          boot the 32-bit kernel or applying a patch for bug 6574102 (while
           Solaris is using the 32-bit kernel).
       </para>
-    
+
     </sect2>
 
@@ -1088 +1088 @@
           Solaris 2.6, 7 and 8 releases up to and including Solaris 8 4/01 ("S8U4")
           incorrectly set up Machine Check Exception (MCE) MSRs on Pentium 4 and
-          somene later Intel CPUs. The problem leads to the Solaris kernel crashing
+          some later Intel CPUs. The problem leads to the Solaris kernel crashing
           (and usually causing a triple fault) almost immediately during startup, in both
           virtualized and physical environments. Solaris 9 and later releases are
@@ -1094 +1094 @@
       </para>
       <para>
-          The recommended solution is upgrading to at least Solaris 8 7/01 
+          The recommended solution is upgrading to at least Solaris 8 7/01
           ("S8U5"). Alternative solutions include applying a patch for bugs 4408508
           and 4414557 (on an unaffected system).