Admin Guide: integrate proofing corrections by Dublin

xml/ha_cluster_lvm.xml

@@ -17,7 +17,7 @@ cLVM) for more information and details to integrate here - really helpful-->
     about changes that are done to the storage subsystem. The Linux Volume
     Manager 2 (LVM2), which is widely used to manage local storage,
     has been extended to support transparent management of volume groups
-    across the whole cluster. The shared volume groups among multiple hosts
+    across the whole cluster. Volume groups shared among multiple hosts
     can be managed using the same commands as local storage.
    </para>
       </abstract>
@@ -58,7 +58,7 @@ cLVM) for more information and details to integrate here - really helpful-->
     <term>Logical Volume Manager (LVM2)</term>
     <listitem>
      <para>
-      LVM2 provides a virtual pool of disk space, enables flexible distribution of
+      LVM2 provides a virtual pool of disk space and enables flexible distribution of
       one logical volume over several disks.
      </para>
     </listitem>
@@ -108,15 +108,15 @@ cLVM) for more information and details to integrate here - really helpful-->
    </listitem>
    <listitem>
     <para>
-     Make sure the packages have been installed: <systemitem
+     Make sure the following packages have been installed: <systemitem
      class="resource">lvm2</systemitem> and <systemitem
      class="resource">lvm2-lockd</systemitem>.
     </para>
    </listitem>
    <listitem>
     <para>
      From &sle; 15 onward, we use lvmlockd as the LVM2 cluster extension,
-     to replace clvmd. Make sure the clvmd daemon is not running,
+     rather than clvmd. Make sure the clvmd daemon is not running,
      otherwise lvmlockd will fail to start.
     </para>
    </listitem>
@@ -302,7 +302,7 @@ cLVM) for more information and details to integrate here - really helpful-->
   </sect2>
 
   <sect2 xml:id="sec.ha.clvm.scenario.iscsi">
-   <title>Scenario: LVM2 With iSCSI on SANs</title>
+   <title>Scenario: LVM2 with iSCSI on SANs</title>
    <para>
     The following scenario uses two SAN boxes which export their iSCSI
     targets to several clients. The general idea is displayed in
@@ -591,13 +591,13 @@ Login to [iface: default, target: iqn.2010-03.de.&wsI;:san1, portal: &wwwip;,326
    <para>
     After you have created the volumes and started your resources you should have new device
     names under <filename>/dev/testvg</filename>, for example <filename>/dev/testvg/lv1</filename>.
-    That indicates the LV has been activated for use.
+    This indicates the LV has been activated for use.
    </para>
   </sect2>
 
 
   <sect2 xml:id="sec.ha.clvm.scenario.drbd">
-   <title>Scenario: LVM2 With DRBD</title>
+   <title>Scenario: LVM2 with DRBD</title>
    <para>
     The following scenarios can be used if you have data centers located in
     different parts of your city, country, or continent.
@@ -781,7 +781,7 @@ Login to [iface: default, target: iqn.2010-03.de.&wsI;:san1, portal: &wwwip;,326
   <title>For More Information</title>
 
   <para>
-   For more information about lvmlockd , see the man page of the
+   For more information about lvmlockd, see the man page of the
    <command>lvmlockd</command> command (<command>man 8 lvmlockd</command>).
   </para>
   <para>

xml/ha_config_hawk2.xml

@@ -47,7 +47,7 @@
 
   <variablelist>
    <varlistentry>
-    <term>Package <package>hawk2</package></term>
+    <term><package>hawk2</package> Package</term>
     <listitem>
      <para>
       The <package>hawk2</package> package must be installed on all

xml/ha_fencing.xml

@@ -60,7 +60,7 @@
     <term>Resource Level Fencing</term>
     <listitem>
      <para>Resource level fencing ensures exclusive access to a given resource.
-      Common examples for this are changing the zoning of the node from a SAN fiber
+      Common examples of this are changing the zoning of the node from a SAN fiber
       channel switch (thus locking the node out of access to its disks) or methods
       like SCSI reserve. For examples, refer to <xref
       linkend="sec.ha.storage.protect.rsc.fencing"/>.

xml/ha_install.xml

@@ -22,7 +22,7 @@
    </para>
    <para>
     If you want to upgrade an existing cluster that runs an older version of 
-    &productname;, refer to chapter <xref linkend="cha.ha.migration"/>.
+    &productname;, refer to <xref linkend="cha.ha.migration"/>.
    </para>
   </abstract>
   <dm:docmanager xmlns:dm="urn:x-suse:ns:docmanager">

xml/ha_naming.xml

@@ -41,7 +41,7 @@
    <term>Cluster Site Names</term>
    <listitem>
     <para>
-     Clusters sites are named after cities:
+     Cluster sites are named after cities:
     </para>
     <para>
      &cluster1;, &cluster2;, &cluster3;, &cluster4;,

xml/ha_rear.xml

@@ -191,7 +191,7 @@
     <itemizedlist>
      <listitem>
      <para>
-      To allow disaster recover on UEFI systems, you need at least &rear;
+      To allow disaster recovery on UEFI systems, you need at least &rear;
       version 1.18.a and the package <package>ebiso</package>.
       Only this version supports the new helper tool
       <filename>/usr/bin/ebiso</filename>. This helper tool is