Admin Guide proofing corrections part 2

- all proofing corrections are in now,
  the other 5 guides/articles did not see any proofing changes

xml/ha_clvm.xml

@@ -173,7 +173,7 @@ cLVM) for more information and details to integrate here - really helpful-->
    <listitem>
     <para>
      Check if the <systemitem class="daemon">lvmetad</systemitem> daemon is
-     disabled because it cannot work with cLVM. In <filename>/etc/lvm/lvm.conf</filename>,
+     disabled, because it cannot work with cLVM. In <filename>/etc/lvm/lvm.conf</filename>,
      the keyword <literal>use_lvmetad</literal> must be set to <literal>0</literal>
      (the default is <literal>1</literal>).
      Copy the configuration to all nodes, if necessary.
@@ -516,7 +516,7 @@ cLVM) for more information and details to integrate here - really helpful-->
 
 
   <sect2 xml:id="sec.ha.clvm.scenario.iscsi">
-   <title>Scenario: cLVM With iSCSI on SANs</title>
+   <title>Scenario: cLVM 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

xml/ha_docupdates.xml

@@ -146,7 +146,7 @@ toms 2014-08-12:
         (<link xlink:href="&bsc;1098429"/>,
         <link xlink:href="&bsc;1108586"/>,
         <link xlink:href="&bsc;1108604"/>,
-        <link xlink:href="&bsc;1108624"/>.
+        <link xlink:href="&bsc;1108624"/>).
        </para>
       </listitem>
     </itemizedlist>
@@ -203,7 +203,7 @@ toms 2014-08-12:
        </listitem>
        <listitem>
         <para>
-         Added chapter <xref linkend="cha.ha.maintenance"/>. Moved respective
+         Added <xref linkend="cha.ha.maintenance"/>. Moved respective
          sections from <xref linkend="cha.ha.config.basics"/>,
          <xref linkend="cha.conf.hawk2"/>, and <xref linkend="cha.ha.manual_config"/>
          there. The new chapter gives an overview of different options the cluster stack
@@ -464,7 +464,7 @@ toms 2014-08-12:
      <listitem>
       <para>
        In <xref linkend="sec.ha.cluster-md.overview"/>, mentioned that each
-       disk need to be accessible by Cluster MD on each node (<link
+       disk needs to be accessible by Cluster MD on each node (<link
         xlink:href="https://bugzilla.suse.com/show_bug.cgi?id=938502"/>).
       </para>
      </listitem>

xml/ha_maintenance.xml

@@ -20,7 +20,7 @@
    </para>
    <para>
     This chapter explains how to manually take down a cluster node without
-    negative side-effects. It also gives an overview of different options the
+    negative side effects. It also gives an overview of different options the
     cluster stack provides for executing maintenance tasks.
    </para>
   </abstract>
@@ -175,7 +175,7 @@ Node <replaceable>&node2;</replaceable>: standby
      <para>
       A node that is in standby mode can no longer run resources. Any resources
       running on the node will be moved away or stopped (in case no other node
-      is eligible to run the resource). Also, all monitor operations will be
+      is eligible to run the resource). Also, all monitoring operations will be
       stopped on the node (except for those with
       <literal>role="Stopped"</literal>).
      </para>
@@ -190,7 +190,7 @@ Node <replaceable>&node2;</replaceable>: standby
     <term><xref linkend="sec.ha.maint.mode.rsc" xrefstyle="select:title"/></term>
     <listitem>
      <para>
-      When this mode is enabled for a resource, no monitor operations will be
+      When this mode is enabled for a resource, no monitoring operations will be
       triggered for the resource.
      </para>
      <para>
@@ -551,7 +551,7 @@ Node <replaceable>&node2;</replaceable>: standby
    <step>
     <para>
      Check if you have resources of the type <literal>ocf:pacemaker:controld</literal>
-     or any dependencies on this type of resources. Resources of the type
+     or any dependencies on this type of resource. Resources of the type
      <literal>ocf:pacemaker:controld</literal> are DLM resources.
     </para>
     <substeps>
@@ -564,7 +564,7 @@ Node <replaceable>&node2;</replaceable>: standby
       <para>
        The reason is that stopping &pace; also stops the &corosync; service, on
        whose membership and messaging services DLM depends. If &corosync; stops,
-       the DLM resource will assume a split-brain scenario and trigger a fencing
+       the DLM resource will assume a split brain scenario and trigger a fencing
        operation.
       </para>
      </step>

xml/ha_rear.xml

@@ -66,7 +66,7 @@
     <para>
      Understanding &rear;'s complex functionality is essential for making the
      tool work as intended. Therefore, read this chapter carefully and
-     familiarize with &rear; before a disaster strikes. You should also be
+     familiarize yourself with &rear; before a disaster strikes. You should also be
      aware of &rear;'s known limitations and test your system in advance.
     </para>
    </note>

xml/ha_storage_basics.xml

@@ -24,7 +24,7 @@
   <title>Protocols for DLM Communication</title>
 
   <para>
-   To avoid single point of failure, redundant communication paths are important
+   To avoid single points of failure, redundant communication paths are important
    for &ha; clusters. This is also true for DLM communication. If network bonding
    (Link Aggregation Control Protocol, LACP) cannot be used for any reason, we
    highly recommend to define a redundant communication channel (a second ring)
@@ -33,15 +33,15 @@
   </para>
   <para>
    Depending on the configuration in &corosync.conf;, DLM then decides
-   if to use the TCP or SCTP protocol for its communication:
+   whether to use the TCP or SCTP protocol for its communication:
   </para>
  <itemizedlist>
   <listitem>
    <para>
      If <guimenu>rrp_mode</guimenu> is set to <literal>none</literal> (which
      means redundant ring configuration is disabled), DLM automatically uses
      TCP. However, without a redundant communication channel, DLM communication
-     will fail in case the TCP link is down.
+     will fail if the TCP link is down.
    </para>
   </listitem>
   <listitem>
@@ -59,7 +59,7 @@
 
   <para>
    DLM uses the cluster membership services from &pace; which run in user
-   space. Therefore, DLM needs to be configured as clone resource that is
+   space. Therefore, DLM needs to be configured as a clone resource that is
    present on each node in the cluster.
   </para>
 
@@ -82,7 +82,7 @@
     The configuration consists of a base group that includes several primitives
     and a base clone. Both base group and base clone can be used in various
     scenarios afterward (for both &ocfs; and cLVM, for example). You only need
-    to extended the base group with the respective primitives as needed. As the
+    to extend the base group with the respective primitives as needed. As the
     base group has internal colocation and ordering, this simplifies the
     overall setup as you do not need to specify several individual groups,
     clones and their dependencies.