Fix typos/reformat a few paragraphs

1 files changed, 37 insertions, 19 deletions

diff --git a/books/docbook/SpiceUserManual-Introduction.xml b/books/docbook/SpiceUserManual-Introduction.xml
index 41280a2..fdaaaea 100644
--- a/books/docbook/SpiceUserManual-Introduction.xml
+++ b/books/docbook/SpiceUserManual-Introduction.xml
@@ -6,20 +6,20 @@
         xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0">
     <title>Introduction</title>
     <para>
-        Spice is an open remote computing solution, providing client access to remote  displays and devices (e.g. keyboard, mouse, audio). 
-        Spice provides a desktop like user experience, while trying to offload most of the intensive CPU and GPU tasks to the client. 
+        Spice is an open remote computing solution, providing client access to remote displays and devices (e.g. keyboard, mouse, audio).
+        Spice provides a desktop-like user experience, while trying to offload most of the intensive CPU and GPU tasks to the client.
         
         The basic building blocks of Spice are:
     </para>
     
     <orderedlist>
         <listitem><para><link linkend="spice_server">Spice Server</link></para></listitem>
-        <listitem><para><link linkend="spice_client">Spice CLient</link></para></listitem>
+        <listitem><para><link linkend="spice_client">Spice Client</link></para></listitem>
         <listitem><para>Spice Protocol</para></listitem>
     </orderedlist>
     
     <para>
-        The following sections provide basic iformation on Spice components and features, obtaining, building installing and using Spice.
+        The following sections provide basic information on Spice components and features, obtaining, building installing and using Spice.
     </para>
     
     <section>
@@ -27,10 +27,10 @@
         <section xml:id="spice_server">
             <title>Spice Server</title>
             <para>
-                Spice server is implemented in libspice, a VDI pluggable library. 
-                Virtual Device Interface (VDI) defines a set of interfaces that provide a standard way to publish virtual devices (e.g. display device, keyboard, mouse) 
-                and enables different Spice components to interact with those devices. 
-                On one side, the server communicates with the remote client using the Spice protocol and on the other side, it interacts with the VDI host application (e.g QEMU). 
+                Spice server is implemented in libspice, a VDI pluggable library.
+                Virtual Device Interface (VDI) defines a set of interfaces that provide a standard way to publish virtual devices (e.g. display device, keyboard, mouse)
+                and enables different Spice components to interact with those devices.
+                On one side, the server communicates with the remote client using the Spice protocol and on the other side, it interacts with the VDI host application (e.g QEMU).
             </para>
         </section>
         
@@ -44,17 +44,17 @@
         <section>
             <title>QXL Device and Drivers</title>
             <para>
-                Spice server supports QXL VDI interface. When libspice is used with QEMU, a specific QEMU  QXL PCI device can be used for improving
+                Spice server supports QXL VDI interface. When libspice is used with QEMU, a specific QEMU QXL PCI device can be used for improving
                 remote display performance and enhancing the graphic capabilities of the guest graphic system.
                 QXL device requires guest QXL drivers for full functionality.
-                However, standard VGA is supported when no driver exists. 
+                However, standard VGA is supported when no driver exists.
             </para>
         </section>
         
         <section>
             <title>VDI Port Device</title>
             <para>
-                Spice protocol supports a communication channel between the client and the agent on the server side. 
+                Spice protocol supports a communication channel between the client and the agent on the server side.
                 When using QEMU, Spice agent resides on the guest. VDI port is a QEMU PCI device used for communication with the agent.
             </para>
         </section>
@@ -65,7 +65,7 @@
                 The Spice agent is an optional component for enhancing user experience and performing guest-oriented management tasks.
                 For example, the agent injects mouse position and state to the guest when using client mouse mode. It also enables you to
                 move cursor freely between guest and client. Other features of agent are shared clipboard and
-                aligning guest resolution with client while entering fullscreen mode.
+                aligning guest resolution with client when entering fullscreen mode.
                 
             </para>
         </section>
@@ -96,7 +96,7 @@
                     <para><emphasis role="bold">Playback</emphasis> - audio received from the server to be played by the client</para>
                 </listitem>
                 <listitem>
-                    <para><emphasis role="bold">Record</emphasis> - audio capture on the client side</para>
+                    <para><emphasis role="bold">Record</emphasis> - audio captured on the client side</para>
                 </listitem>
             </orderedlist>
         </section>
@@ -105,7 +105,18 @@
             <title>Image Compression</title>
             
             <para>
-                Spice offers several image compression algorithms, which can be chosen on server initiation and  dynamically at run-time. Quic is a Spice proprietary image compression technology based on the SFALIC algorithm. The Lempel-Ziv (LZ) algorithm is another option. Both Quic and LZ are local algorithms encoding each image separately. Global LZ (GLZ) is another proprietary Spice technology that uses LZ with history based global dictionary. GLZ takes advantage of repeating patterns among images to shrink the traffic and save bandwidth, which is critical in a WAN environment. Spice also offers an automatic mode for compression selection per image, where the choice between LZ/GLZ and Quic is heuristically based on image properties. Conceptually, synthetic images are better compressed with LZ/GLZ and real images are better with Quic. 
+                Spice offers several image compression algorithms, which
+                can be chosen on server initiation and  dynamically at run-time. Quic is a
+                Spice proprietary image compression technology based on the SFALIC
+                algorithm. The Lempel-Ziv (LZ) algorithm is another option. Both Quic and
+                LZ are local algorithms encoding each image separately. Global LZ (GLZ) is
+                another proprietary Spice technology that uses LZ with history-based global
+                dictionary. GLZ takes advantage of repeating patterns among images to
+                shrink the traffic and save bandwidth, which is critical in a WAN
+                environment. Spice also offers an automatic mode for compression selection
+                per image, where the choice between LZ/GLZ and Quic is heuristically based
+                on image properties. Conceptually, synthetic images are better compressed
+                with LZ/GLZ and real images are better with Quic.
             </para>
         </section>
         
@@ -113,7 +124,14 @@
             <title>Video Compression</title>
             
             <para>
-                Spice uses loss-less compression for images sent to the client. However, video streams are handled differently. Spice server heuristically identifies video areas and sends them as a video stream coded using M-JPEG. This handling saves a lot of traffic, improving Spice performance, especially in a WAN environment. However, in some circumstances the heuristic behavior might cause low quality image (e.g.  identifying updated text area as a video stream). Video streaming can be chosen on server initiation and dynamically at run-time.
+                Spice uses loss-less compression for images sent to the
+                client. However, video streams are handled differently. Spice server
+                heuristically identifies video areas and sends them as a video stream coded
+                using M-JPEG. This handling saves a lot of traffic, improving Spice
+                performance, especially in a WAN environment. However, in some
+                circumstances the heuristic behavior might cause low quality images (e.g.
+                identifying updated text area as a video stream). Video streaming can be
+                chosen on server initiation and dynamically at run-time.
             </para>
         </section>
         
@@ -126,13 +144,13 @@
             <orderedlist>
                 <listitem>
                     <para>
-                        <emphasis role="bold">Server mouse</emphasis> - When a user clicks inside the Spice client window, the client mouse is captured and set invisible. In this mode, the server controls the mouse position on display. However, it might be problematic on WAN or a loaded server, where mouse cursor might have some latency or non-responsiveness.
+                        <emphasis role="bold">Server mouse</emphasis> - When a user clicks inside the Spice client window, the client mouse is captured and set invisible. In this mode, the server controls the mouse position on display. However, it might be problematic on WAN or on a loaded server, where mouse cursor might have some latency or non-responsiveness.
                     </para>
                 </listitem>
                 
                 <listitem>
                     <para>
-                        <emphasis role="bold">Client mouse</emphasis> - Not captured and is used as the effective pointing device. For enabling client mouse, VDI host application must register an absolute pointing device (e.g. USB tablet in QEMU). This mode is appropriate for WAN or loaded server, since cursor has smooth motion and responsiveness. However, the cursor might loose synchronization (position and shape) for a while.
+                        <emphasis role="bold">Client mouse</emphasis> - Not captured and is used as the effective pointing device. To enable client mouse, the VDI host application must register an absolute pointing device (e.g. USB tablet in QEMU). This mode is appropriate for WAN or or for a loaded server, since cursor has smooth motion and responsiveness. However, the cursor might lose synchronization (position and shape) for a while.
                     </para>
                 </listitem>
                 
@@ -164,13 +182,13 @@
                 
                 <listitem>
                     <para>
-                        <emphasis role="bold">Migration</emphasis> - switching channel connectivity for  supporting server migration
+                        <emphasis role="bold">Migration</emphasis> - switching channel connectivity for supporting server migration
                     </para>
                 </listitem>
                 
                 <listitem>
                     <para>
-                        <emphasis role="bold">Pixmap and Pallete caching</emphasis>
+                        <emphasis role="bold">Pixmap and Palette caching</emphasis>
                     </para>
                 </listitem>