Changeset 46821 in vbox for trunk/doc

Timestamp:

Jun 27, 2013 8:25:49 AM (12 years ago)

Author:

vboxsync

Message:

doc/manual: fixed a few typos

Location:

trunk/doc/manual/en_US

Files:

• user_AdvancedTopics.xml (modified) (1 diff)
• user_BasicConcepts.xml (modified) (1 diff)
• user_Glossary.xml (modified) (1 diff)
• user_GuestAdditions.xml (modified) (3 diffs)
• user_KnownIssues.xml (modified) (1 diff)
• user_Networking.xml (modified) (3 diffs)
• user_Security.xml (modified) (1 diff)
• user_VBoxManage.xml (modified) (1 diff)

trunk/doc/manual/en_US/user_AdvancedTopics.xml

@@ -2638 +2638 @@
       for users which are not in the exception list.
       The exception list starts with <computeroutput>exception_list</computeroutput>
-      and contains a comma seperated list with usernames. Furthermore a separate
+      and contains a comma separated list with usernames. Furthermore a separate
       startup delay can be configured for every user to avoid overloading the host.
       A sample configuration is given below:</para>

trunk/doc/manual/en_US/user_BasicConcepts.xml

@@ -506 +506 @@
               result, VirtualBox 4.0 introduced an emulation of the more
               modern ICH9 chipset, which supports PCI express, three PCI
-              buses, PCI-to-PCI bridges and Message Signalled Interrupts
+              buses, PCI-to-PCI bridges and Message Signaled Interrupts
               (MSI). This allows modern operating systems to address more PCI
               devices and no longer requires IRQ sharing. Note that the ICH9

trunk/doc/manual/en_US/user_Glossary.xml

@@ -229 +229 @@
 
       <glossdef>
-        <para>Message Signalled Interrupts, as supported by modern chipsets
+        <para>Message Signaled Interrupts, as supported by modern chipsets
         such as the ICH9; see <xref linkend="settings-motherboard" />. As
         opposed to traditional pin-based interrupts, with MSI, a small amount

trunk/doc/manual/en_US/user_GuestAdditions.xml

@@ -523 +523 @@
       <itemizedlist>
         <listitem>
-          <para>Oracle Linux as of version 5 including UEK kernels</para>
+          <para>Oracle Linux as of version 5 including UEK kernels;</para>
         </listitem>
 
@@ -785 +785 @@
                 <para>Install the GNU C compiler and the kernel development
                 packages using <screen>yum install gcc</screen> followed by
-                <screen>yum install kernel-devel</screen> If the Oracle UEK
-                kernel is used, use <screen>yum install kernel-uek-devel</screen>
+                <screen>yum install kernel-devel</screen> For Oracle UEK
+                kernels, use <screen>yum install kernel-uek-devel</screen>
                 to install the UEK kernel headers.</para>
               </listitem>
@@ -1341 +1341 @@
           <listitem>
             <para>In Windows Vista guest: right-click on the desktop, in the
-            contect menu select "Personalize", then select "Windows Color and Appearance"
+            context menu select "Personalize", then select "Windows Color and Appearance"
             in the "Personalization" window, in the "Appearance Settings" dialog select
             "Windows Aero" and press "OK"</para></listitem>
           <listitem>
             <para>In Windows 7 guest: right-click on the desktop, in the
-            contect menu select "Personalize" and select any Aero theme
+            context menu select "Personalize" and select any Aero theme
             in the "Personalization" window</para></listitem>
           </itemizedlist>

trunk/doc/manual/en_US/user_KnownIssues.xml

@@ -286 +286 @@
           To solve this problem, one should uninstall the VirtualBox WDDM Video driver manually.
           To do that open Device Manager, and check whether the Display Adapter is named 
-          "VirtualBox Graphics Adapter ..". If no - there is nothing to be done. If yes - right-clik 
+          "VirtualBox Graphics Adapter ..". If no - there is nothing to be done. If yes - right-click 
           the VirtualBox Graphics Adapter in Device Manager, select "Uninstall", check "Delete the driver software for this device"
           and click "OK". Once uninstallation is done - in Device Manager go to menu "Action" and select 

trunk/doc/manual/en_US/user_Networking.xml

@@ -595 +595 @@
     bridged and internal networking modes: as with bridged networking, the
     virtual machines can talk to each other and the host as if they were
-    connected through a physical ethernet switch. Similarly, as with internal
+    connected through a physical Ethernet switch. Similarly, as with internal
     networking however, a physical networking interface need not be present,
     and the virtual machines cannot talk to the world outside the host since
@@ -831 +831 @@
       types of adapters and attachments are used the network performance will
       be different. Performance-wise the <emphasis>virtio</emphasis> network
-      adapter is preferrable over <emphasis>Intel PRO/1000</emphasis> emulated
+      adapter is preferable over <emphasis>Intel PRO/1000</emphasis> emulated
       adapters, which are preferred over <emphasis>PCNet</emphasis> family of
       adapters. Both <emphasis>virtio</emphasis> and <emphasis>Intel PRO/1000
       </emphasis> adapters enjoy the benefit of segmentation and checksum
       offloading. Segmentation offloading is essential for high performance as
-      it allows for less context switches, drammatically increasing the sizes
-      of packets that cross VM/host bondary.</para>
+      it allows for less context switches, dramatically increasing the sizes
+      of packets that cross VM/host boundary.</para>
     <note><para>Neither <emphasis>virtio</emphasis> nor <emphasis>Intel PRO/1000
         </emphasis> drivers for Windows XP support segmentation
@@ -853 +853 @@
       cannot be considered as an alternative to other attachment types.</para>
     <para>The number of CPUs assigned to VM does not improve network
-      performance and in some cases may hurt it due to increased concurency in
+      performance and in some cases may hurt it due to increased concurrency in
       the guest.</para>
     <para>Here is the short summary of things to check in order to improve

trunk/doc/manual/en_US/user_Security.xml

@@ -343 +343 @@
           <xref linkend="vboxwebsrv-daemon"/> to find out how to start this
           service and how to enable SSL/TLS support. It has to be started as
-          a regular user and only the VMs of that user can be controled. By
+          a regular user and only the VMs of that user can be controlled. By
           default, the service binds to localhost preventing any remote connection.</para>
         </listitem>

trunk/doc/manual/en_US/user_VBoxManage.xml

@@ -1597 +1597 @@
 
     <para>If you have a saved state file (<computeroutput>.sav</computeroutput>)
-    that is seperate from the VM configuration, you can use this command to
+    that is separate from the VM configuration, you can use this command to
     "adopt" the file. This will change the VM to saved state and when you
     start it, VirtualBox will attempt to restore it from the saved state file