Index: /trunk/doc/manual/en_US/user_AdvancedTopics.xml =================================================================== --- /trunk/doc/manual/en_US/user_AdvancedTopics.xml (revision 46820) +++ /trunk/doc/manual/en_US/user_AdvancedTopics.xml (revision 46821) @@ -2638,5 +2638,5 @@ for users which are not in the exception list. The exception list starts with exception_list - 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: Index: /trunk/doc/manual/en_US/user_BasicConcepts.xml =================================================================== --- /trunk/doc/manual/en_US/user_BasicConcepts.xml (revision 46820) +++ /trunk/doc/manual/en_US/user_BasicConcepts.xml (revision 46821) @@ -506,5 +506,5 @@ 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 Index: /trunk/doc/manual/en_US/user_Glossary.xml =================================================================== --- /trunk/doc/manual/en_US/user_Glossary.xml (revision 46820) +++ /trunk/doc/manual/en_US/user_Glossary.xml (revision 46821) @@ -229,5 +229,5 @@ - Message Signalled Interrupts, as supported by modern chipsets + Message Signaled Interrupts, as supported by modern chipsets such as the ICH9; see . As opposed to traditional pin-based interrupts, with MSI, a small amount Index: /trunk/doc/manual/en_US/user_GuestAdditions.xml =================================================================== --- /trunk/doc/manual/en_US/user_GuestAdditions.xml (revision 46820) +++ /trunk/doc/manual/en_US/user_GuestAdditions.xml (revision 46821) @@ -523,5 +523,5 @@ - Oracle Linux as of version 5 including UEK kernels + Oracle Linux as of version 5 including UEK kernels; @@ -785,6 +785,6 @@ Install the GNU C compiler and the kernel development packages using yum install gcc followed by - yum install kernel-devel If the Oracle UEK - kernel is used, use yum install kernel-uek-devel + yum install kernel-devel For Oracle UEK + kernels, use yum install kernel-uek-devel to install the UEK kernel headers. @@ -1341,10 +1341,10 @@ 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" 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 Index: /trunk/doc/manual/en_US/user_KnownIssues.xml =================================================================== --- /trunk/doc/manual/en_US/user_KnownIssues.xml (revision 46820) +++ /trunk/doc/manual/en_US/user_KnownIssues.xml (revision 46821) @@ -286,5 +286,5 @@ 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 Index: /trunk/doc/manual/en_US/user_Networking.xml =================================================================== --- /trunk/doc/manual/en_US/user_Networking.xml (revision 46820) +++ /trunk/doc/manual/en_US/user_Networking.xml (revision 46821) @@ -595,5 +595,5 @@ 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,11 +831,11 @@ types of adapters and attachments are used the network performance will be different. Performance-wise the virtio network - adapter is preferrable over Intel PRO/1000 emulated + adapter is preferable over Intel PRO/1000 emulated adapters, which are preferred over PCNet family of adapters. Both virtio and Intel PRO/1000 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. + it allows for less context switches, dramatically increasing the sizes + of packets that cross VM/host boundary. Neither virtio nor Intel PRO/1000 drivers for Windows XP support segmentation @@ -853,5 +853,5 @@ cannot be considered as an alternative to other attachment types. 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. Here is the short summary of things to check in order to improve Index: /trunk/doc/manual/en_US/user_Security.xml =================================================================== --- /trunk/doc/manual/en_US/user_Security.xml (revision 46820) +++ /trunk/doc/manual/en_US/user_Security.xml (revision 46821) @@ -343,5 +343,5 @@ 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. Index: /trunk/doc/manual/en_US/user_VBoxManage.xml =================================================================== --- /trunk/doc/manual/en_US/user_VBoxManage.xml (revision 46820) +++ /trunk/doc/manual/en_US/user_VBoxManage.xml (revision 46821) @@ -1597,5 +1597,5 @@ If you have a saved state file (.sav) - 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