Merge pull request #381 from SUSE/sp6-prio3-guide-checks

SP6 prio3 guide checks

xml/article_nfs_storage.xml

@@ -161,7 +161,7 @@
       </para>
       <screen>&prompt.root;<command>crm cluster run "lvcreate -n state -L 8G nfs"</command></screen>
       <para>
-       This volume is for the NFS client states. The 8 GB volume size
+       This volume is for the NFS client states. The 8&nbsp;GB volume size
        used in this example should support several thousand concurrent NFS clients.
       </para>
      </step>

xml/article_pacemaker_remote.xml

@@ -118,7 +118,7 @@
      <listitem>
       <para>
        A service daemon that makes it possible to use a node as a &pace; node
-       without deploying the full cluster stack. Note that &pmremote; is the
+       without deploying the full cluster stack. &pmremote; is the
        name of the systemd service. However, the name of the daemon
        is &pmrm_daemon; (with a trailing d after its name).
       </para>

xml/geo_booth_i.xml

@@ -252,10 +252,10 @@ ticket = "&ticket2;" <xref linkend="co-ha-geo-booth-config-ticket" xrefstyle="se
     <callout arearefs="co-ha-geo-booth-config-expiry">
      <para>
       Optional parameter. Defines the ticket&apos;s expiry time in seconds. A
-      site that has been granted a ticket will renew the ticket regularly. If
+      site that has been granted a ticket renews the ticket regularly. If
       booth does not receive any information about renewal of the ticket within
-      the defined expiry time, the ticket will be revoked and granted to
-      another site. If no expiry time is specified, the ticket will expire
+      the defined expiry time, the ticket is revoked and granted to
+      another site. If no expiry time is specified, the ticket expires
       after <literal>600</literal> seconds by default. The parameter should not
       be set to a value less than 120 seconds. The default value set by the
       bootstrap scripts is <literal>600</literal>.
@@ -264,7 +264,7 @@ ticket = "&ticket2;" <xref linkend="co-ha-geo-booth-config-ticket" xrefstyle="se
     <callout arearefs="co-ha-geo-booth-config-timeout">
      <para>
       Optional parameter. Defines a timeout period in seconds. After that time,
-      booth will resend packets if it did not receive a reply within this
+      booth resends packets if it did not receive a reply within this
       period. The timeout defined should be long enough to allow packets to
       reach other booth members (all arbitrators and sites).
      </para>
@@ -273,7 +273,7 @@ ticket = "&ticket2;" <xref linkend="co-ha-geo-booth-config-ticket" xrefstyle="se
      <para>
       Optional parameter. Defines how many times booth retries sending packets
       before giving up waiting for confirmation by other sites. Values smaller
-      than <literal>3</literal> are invalid and will prevent booth from
+      than <literal>3</literal> are invalid and prevent booth from
       starting.
      </para>
     </callout>
@@ -347,7 +347,7 @@ ticket = "&ticket2;" <xref linkend="co-ha-geo-booth-config-ticket" xrefstyle="se
     </callout>
     <callout arearefs="co-ha-geo-booth-config-acquire-after">
      <para>
-      Optional parameter. After a ticket is lost, booth will wait this time in
+      Optional parameter. After a ticket is lost, booth waits this time in
       addition before acquiring the ticket. This is to allow for the site that
       lost the ticket to relinquish the resources, by either stopping them or
       fencing a node. A typical delay might be <literal>60</literal> seconds,
@@ -516,7 +516,7 @@ ticket = "&ticket2;" <xref linkend="co-ha-geo-booth-config-ticket" xrefstyle="se
            have an existing key, specify the path and file name in
            <guimenu>Authentication file</guimenu>. To generate a key file for a
            new &geo; cluster, click <guimenu>Generate Authentication Key
-           File</guimenu>. The key will be created and written to the location
+           File</guimenu>. The key is created and written to the location
            specified in <guimenu>Authentication file</guimenu>.
           </para>
          </formalpara>
@@ -720,7 +720,7 @@ ticket = "tkt-sap-prod" <xref linkend="co-ha-geo-booth-config-ticket" xrefstyle=
    </callout>
    <callout arearefs="co-ha-geo-booth-config-handler">
     <para>
-     Optional parameter. If set, the specified command will be called before
+     Optional parameter. If set, the specified command is called before
      &boothd; tries to acquire or renew a ticket. On exit code other than
      <literal>0</literal>, &boothd; relinquishes the ticket.
     </para>
@@ -841,7 +841,7 @@ ticket = "tkt-sap-prod" <xref linkend="co-ha-geo-booth-config-ticket" xrefstyle=
       Starting with &sle; 12, booth arbitrators are managed with systemd. The
       unit file is named <filename>[email protected]</filename>. The
       <literal>@</literal> denotes the possibility to run the service with a
-      parameter, which is in this case the name of the configuration file.
+      parameter, which is, in this case, the name of the configuration file.
      </para>
      <para>
       To <emphasis>enable</emphasis> the booth service on an arbitrator, use

xml/geo_ip_i.xml

@@ -37,8 +37,6 @@
     on how to do so with BIND/named, see the <literal>named</literal>
     documentation, or refer to
     <link xlink:href="https://www.semicomplete.com/articles/dynamic-dns-with-dhcp/"/>.
-    <remark>taroth 2014-11-21: lmb, would you consider the aforementioned link appropriate (WRT to
-     our customers and the kind of setup that is needed here)?</remark>
     More information on how to set up DNS, including dynamic update of zone
     data, can be found in the <link
      xlink:href="https://documentation.suse.com/sles-15/html/SLES-all/cha-dns.html">

xml/geo_manage_i.xml

@@ -295,7 +295,7 @@ booth[27900]: 2014/08/13_10:21:23 info: revoke succeeded!</screen>
     <screen>&prompt.root;<command>booth list</command></screen>
     <para>It should show <literal>&cluster2;</literal> as ticket owner for
       <literal>&ticket3;</literal> now. All resources that depend on this
-     ticket will be started on <literal>&cluster2;</literal>.</para>
+     ticket are started on <literal>&cluster2;</literal>.</para>
    </step>
    <step>
     <para>Before trying to bring back <literal>&cluster1;</literal> into the

xml/geo_resources_i.xml

@@ -198,7 +198,7 @@
   params config="nfs" op monitor interval="10s"</command>
 &prompt.crm.conf;<command>group g-booth ip-booth booth-site</command></screen>
     <para>
-     With this configuration, each booth daemon will be available at its
+     With this configuration, each booth daemon is available at its
      individual IP address, independent of the node the daemon is running on.
     </para>
    </step>

xml/geo_sync_i.xml

@@ -18,8 +18,6 @@
  <para>
   To replicate important configuration files across all nodes in the cluster
   and across &geo; clusters, use &csync;.
-<!--taroth 2014-09-25: the following is copied from ha_installation.xml,
-     varlistentry vle.csync2-->
   &csync; can handle any number of hosts, sorted into synchronization groups.
   Each synchronization group has its own list of member hosts and its
   include/exclude patterns that define which files should be synchronized in
@@ -33,8 +31,8 @@
   synchronization group and copy it to all group members.
  </para>
  <para>
-  &csync; will contact other servers via a TCP port (by default
-  <literal>30865</literal>), and start remote &csync; instances. For detailed
+  &csync; contacts other servers via a TCP port (by default
+  <literal>30865</literal>), and starts remote &csync; instances. For detailed
   information about &csync;, refer to
   <link xlink:href="https://oss.linbit.com/csync2/paper.pdf"/>
  </para>

xml/ha_acl.xml

@@ -244,7 +244,8 @@
     </step>
     <step>
      <para>
-      In the left navigation bar, select <guimenu>Roles</guimenu>.
+      In the left navigation bar, select
+      <menuchoice><guimenu>Configuration</guimenu><guimenu>Roles</guimenu></menuchoice>.
      </para>
     </step>
     <step>
@@ -322,7 +323,8 @@
     </step>
     <step>
      <para>
-      In the left navigation bar, select <guimenu>Targets</guimenu>.
+      In the left navigation bar, select
+      <menuchoice><guimenu>Configuration</guimenu><guimenu>Targets</guimenu></menuchoice>.
      </para>
     </step>
     <step>
@@ -471,7 +473,8 @@
      </step>
      <step>
       <para>
-       In the left navigation bar, select <guimenu>Targets</guimenu>.
+       In the left navigation bar, select
+       <menuchoice><guimenu>Configuration</guimenu><guimenu>Targets</guimenu></menuchoice>.
       </para>
      </step>
      <step>
@@ -524,7 +527,8 @@
      </step>
      <step>
       <para>
-       In the left navigation bar, select <guimenu>Roles</guimenu>.
+       In the left navigation bar, select
+       <menuchoice><guimenu>Configuration</guimenu><guimenu>Roles</guimenu></menuchoice>.
       </para>
      </step>
      <step>