Last minute style changes

xml/vt_scenarios.xml

@@ -93,7 +93,7 @@
       </listitem>
       <listitem>
         <para>
-          Faster and agile virtual machine provisioning.
+          Faster and agile virtual machine provisioning
         </para>
       </listitem>
       <listitem>

xml/vt_tools.xml

@@ -23,7 +23,7 @@
       </para>
 
       <para>
-        With &libvirt; you can also manage your &vmguest;s remotely. It
+        With &libvirt;, you can also manage your &vmguest;s remotely. It
         supports TLS encryption, x509 certificates and authentication with
         SASL. This enables managing &vmhost;s centrally from a single
         workstation, alleviating the need to access each &vmhost; individually.
@@ -41,7 +41,7 @@
     <title>Virtualization console tools</title>
 
     <para>
-      &libvirt; includes several command line utilities to manage virtual
+      &libvirt; includes several command-line utilities to manage virtual
       machines. The most important ones are:
     </para>
 
@@ -50,7 +50,7 @@
         <term><command>virsh</command> (Package: <package>libvirt-client</package>)</term>
         <listitem>
           <para>
-            A command line tool to manage &vmguest;s with similar functionality
+            A command-line tool to manage &vmguest;s with similar functionality
             as the &vmm;. &virsh; allows you to change a &vmguest;'s status,
             set up new guests and devices, or edit existing configurations.
             <command>virsh</command> is also useful to script &vmguest;
@@ -82,10 +82,10 @@ virsh # hostname
         <term><command>virt-install</command> (Package: <package>virt-install</package>)</term>
         <listitem>
           <para>
-            A command line tool for creating new &vmguest;s using the &libvirt;
+            A command-line tool for creating new &vmguest;s using the &libvirt;
             library. It supports graphical installations via VNC or
             <xref linkend="gloss-vt-acronym-spice"/> protocols. Given suitable
-            command line arguments, <command>virt-install</command> can run
+            command-line arguments, <command>virt-install</command> can run
             unattended. This allows for easy automation of guest installs.
             <command>virt-install</command> is the default installation tool
             used by the &vmm;.

xml/xen_administrating.xml

@@ -54,7 +54,7 @@
     <itemizedlist mark="bullet" spacing="normal">
       <listitem>
         <para>
-          Pass kernel command line parameters.
+          Pass kernel command-line parameters.
         </para>
       </listitem>
       <listitem>
@@ -179,8 +179,8 @@
 
     <para>
       With &xen; it is possible to migrate a &vmguest; system from one &vmhost;
-      to another with almost no service interruption. This could be used for
-      example to move a busy &vmguest; to a &vmhost; that has stronger hardware
+      to another with almost no service interruption. This could be used, for
+      example, to move a busy &vmguest; to a &vmhost; that has stronger hardware
       or is not yet loaded. Or, if a service of a &vmhost; is required, all
       &vmguest; systems running on this machine can be migrated to other
       machines to avoid interruption of service. These are only two
@@ -356,7 +356,7 @@ xlink:href="https://documentation.suse.com/sles-15/html/SLES-all/article-virtual
         <listitem>
           <para>
             <literal>NPIV</literal> is a special mode to use Fibre channel
-            disks. However, in this case all migration hosts must be attached
+            disks. However, in this case, all migration hosts must be attached
             to the same Fibre channel switch. For more information about NPIV,
             see <xref linkend="sec-xen-config-disk"/>. Commonly, this works if
             the Fibre channel environment supports 4 Gbps or faster
@@ -425,7 +425,7 @@ xlink:href="https://documentation.suse.com/sles-15/html/SLES-all/article-virtual
           <listitem>
             <para>
               Also display network statistics. Note, that only standard
-              configurations is displayed. If you use a special configuration
+              configurations are displayed. If you use a special configuration
               like a routed network, no network is displayed.
             </para>
           </listitem>
@@ -441,7 +441,7 @@ xlink:href="https://documentation.suse.com/sles-15/html/SLES-all/article-virtual
         </varlistentry>
       </variablelist>
       <para>
-        For more information about <command>xentop</command> see the manual
+        For more information about <command>xentop</command>, see the manual
         page <command>man 1 xentop</command>.
       </para>
       <tip>
@@ -473,7 +473,7 @@ xlink:href="https://documentation.suse.com/sles-15/html/SLES-all/article-virtual
           <term>ip</term>
           <listitem>
             <para>
-              The command line utility <command>ip</command> may be used to
+              The command-line utility <command>ip</command> may be used to
               monitor arbitrary network interfaces. This is especially useful
               if you have set up a network that is routed or applied a
               masqueraded network. To monitor a network interface with the name

xml/xen_host_network.xml

@@ -180,7 +180,7 @@
     <para>
       The following configuration only works when using fixed IP addresses.
       Using DHCP is not practicable with this procedure, because the IP address
-      must be known to both, the &vmguest; and the &vmhost; system.
+      must be known to both the &vmguest; and the &vmhost; system.
     </para>
 
     <para>

xml/xen_xenstore.xml

@@ -25,7 +25,7 @@
       between &vmguest;s and the management tools running in &dom0;. &vmguest;s
       and the management tools read and write to &xenstore; to convey
       configuration information, status updates, and state changes. The
-      &xenstore; database is managed by &dom0; and supports simple operations
+      &xenstore; database is managed by &dom0; and supports simple operations,
       such as reading and writing a key. &vmguest;s and management tools can be
       notified of any changes in &xenstore; by watching entries of interest.
       The <systemitem>xenstored</systemitem> daemon is managed by the
@@ -192,7 +192,7 @@ vcpu_avail
 bootloader
 name</screen>
       <para>
-        To read a value of an entry, for example the number of virtual CPUs
+        To read a value of an entry, for example, the number of virtual CPUs
         dedicated to the &vmguest;, use <command>xenstore-read</command>:
       </para>
 <screen>&prompt.sudo;xenstore-read /vm/9b30841b-43bc-2af9-2ed3-5a649f466d79-1/vcpus

xml/xen_xmtoxl.xml

@@ -55,11 +55,11 @@
       <command>xm</command> and &libvirt; see the same system state.
       <command>xend</command> maintains the state for the entire &xen; host. In
       libxl, client applications such as <command>xl</command> or &libvirt;
-      must maintain state. Thus domains created with <command>xl</command> or
+      must maintain state. Thus domains created with <command>xl</command> are
       not visible or known to other libxl applications such as &libvirt;.
       Generally, it is discouraged to mix and match libxl applications and is
       preferred that a single libxl application be used to manage a &xen; host.
-      In &productname;, we recommend to use &libvirt; to manage &xen; hosts.
+      In &productname;, we recommend using &libvirt; to manage &xen; hosts.
       This allows management of the &xen; system through &libvirt; applications
       such as <command>virt-manager</command>, <command>virt-install</command>,
       <command>virt-viewer</command>, libguestfs, etc. If <command>xl</command>