Changeset 55484 in vbox

Timestamp:

Apr 28, 2015 1:49:36 PM (9 years ago)

Author:

vboxsync

Message:

doc/manual: typos.

File:

• trunk/doc/manual/en_US/user_AdvancedTopics.xml (modified) (9 diffs)

trunk/doc/manual/en_US/user_AdvancedTopics.xml

@@ -3732 +3732 @@
 
     <para>
-      Starting with VirtualBox 5.0 it is possible to encrypt the data stored in
+      Starting with VirtualBox 5.0, it is possible to encrypt the data stored in
       hard disk images transparently for the guest. It does not depend on a specific
       image format to be used. Images which have the data encrypted are not portable
@@ -3756 +3756 @@
 
         <listitem>
-          <para>This feature is currently closed source and requires the Oracle extension
+          <para>This feature is currently closed source and requires the VirtualBox extension
             pack to be installed to work.</para>
         </listitem>
 
         <listitem>
-          <para>Because encryption works only on the stored user data
-            it is not possible to check for metadata integrity of the disk image currently.
-            Attackers might take advantage of this to remove or insert blocks of database
+          <para>Since encryption works only on the stored user data,
+            it is currently not possible to check for metadata integrity of the disk image.
+            Attackers might take advantage of this to remove or insert blocks of data
             into the image or change certain metadata items such as the disk size.</para>
         </listitem>
@@ -3775 +3775 @@
         <listitem>
           <para>The DEK is kept in memory while the VM is running to be able to
-            decrpt data read and encrypt data written by the guest. While this should
+            decrypt data read and encrypt data written by the guest. While this should
             be obvious the user needs to be aware of this because an attacker might be able
             to extract the key on a compromised host and get access to the data later.</para>
@@ -3781 +3781 @@
 
         <listitem>
-          <para>When encrypting or decrypting the images the password is passed unencrypted
-            via the Main API from the frontend to VBoxSVC. This needs to be kept in mind
+          <para>When encrypting or decrypting the images, the password is passed unencrypted
+            via the Main API from the frontend to VBoxSVC. This needs to be kept in mind,
             especially when using third party frontends which make use of the webservice
             where the password might be transmitted unencrypted over the network.</para>
@@ -3789 +3789 @@
         <listitem>
           <para>Encrypting images with differencing images is only possible if there
-            are no branches exisiting. This limitation will be lifted in the future.</para>
+            are no branches. This limitation may be addressed in a future
+            VirtualBox version.</para>
         </listitem>
 
@@ -3801 +3802 @@
       <para>
         Encrypting disk images can be done either using the GUI or VBoxManage.
-        While the GUI is easier to use it works on a per VM basis and encrypts
+        While the GUI is easier to use, it works on a per VM basis and encrypts
         all disk images attached to the specific VM.
         With VBoxManage one can encrypt individual images (including all differencing
-        images). To encrypt an unencrypted medium with VBoxManage use:
+        images). To encrypt an unencrypted medium with VBoxManage, use:
       </para>
 
@@ -3832 +3833 @@
 
       <para>
-        When a VM is started using the GUI a dialog will open where the user
+        When a VM is started using the GUI, a dialog will open where the user
         needs to enter all passwords for all encrypted images attached to the VM.
-        If another frontend like VBoxHeadless is used the VM will be paused as soon
+        If another frontend like VBoxHeadless is used, the VM will be paused as soon
         as the guest tries to access an encrypted disk.
         The user needs to provide the passwords through VBoxManage using the following
@@ -3848 +3849 @@
         <computeroutput>--removeonsuspend "yes|no"</computeroutput> to specify whether
         to remove the password from VM memory when the VM is suspended. Before the VM can be
-        resumed the user needs to supply the passwords again. This is useful when
+        resumed, the user needs to supply the passwords again. This is useful when
         a VM is suspended by a host suspend event and the user doesn't want
-        that the password remains in memory.
+        the password to remain in memory.
       </para>
     </sect2>
@@ -3858 +3859 @@
 
       <para>
-        In some circumstanes it might be required to decrypt previously encrypted
+        In some circumstances it might be required to decrypt previously encrypted
         images. This can be done in the GUI for a complete VM or using VBoxManage
         with the following command: