Fixed some more typos

in adoc and docinfo files.

adoc/SAP-convergent-mediation-ha-setup-sle15-docinfo.xml

@@ -84,7 +84,7 @@
         <para>SUSE® Linux Enterprise Server for SAP Applications is optimized in various ways for SAP® applications.
 	This document explains how to configure a Convergent Mediation ControlZone High Availability Cluster solution.
 	It is based on SUSE Linux Enterprise Server for SAP Applications 15 SP4.
-	The concept however can also be used with
+	The concept, however, can also be used with
 	newer service packs of SUSE Linux Enterprise Server for SAP Applications.
         </para>
 

adoc/SAP-convergent-mediation-ha-setup-sle15.adoc

@@ -59,26 +59,29 @@ NOTE: This solution is supported only in the context of {SAP} RISE
 Several chapters in this document contain links to additional documentation resources
 which are available either in the system or on the Internet.
 
-For the latest product documentation updates, see https://documentation.suse.com/.
+For the latest product documentation updates, see: 
+
+https://documentation.suse.com/
 
 More whitepapers, guides and best practices documents referring to {SLES} and {SAP}
 can be found and downloaded at the SUSE Best Practices Web page:
+
 https://documentation.suse.com/sbp/sap/
 
 Here you can access guides for {SAPHANA} system replication automation and High Availability
 (HA) scenarios for {SAPNw} and {s4hana}.
 
-Supported high availability solutions by {sles4sap} overview:
+Find an overview of high availability solutions supported by {sles4sap} here:
+
 https://documentation.suse.com/sles-sap/sap-ha-support/html/sap-ha-support/article-sap-ha-support.html
 
-Lastly, there are manual pages shipped with the product.
+Finally, there are manual pages shipped with the product.
 
 // Standard SUSE includes
 === Feedback
 include::common_intro_feedback.adoc[]
 
 
-
 [[cha.overview]]
 == Overview
 
@@ -90,7 +93,7 @@ Several platform containers may exist in a CM system, for high availability,
 but only one is active at a time. The CM ControlZone UI is used to query, edit, import,
 and export data.
 
-{sles4sap} is optimized in various ways for {SAP} applications. Particularly contains
+{sles4sap} is optimized in various ways for {SAP} applications. Particularly, it contains
 the {sleha} cluster and specfic HA resource agents.
 
 From the application perspective the following variants are covered:
@@ -126,8 +129,8 @@ details)
 
 === High availability for the {ConMed} ControlZone platform and UI
 
-The HA solution for CM ControlZone is a two node active/passive cluster. 
-A shared NFS file system is statically mounted by OS on both cluster nodes. This
+The HA solution for CM ControlZone is a two-node active/passive cluster. 
+A shared NFS file system is statically mounted by the operating system on both cluster nodes. This
 file system holds work directories. Client-side write caching needs to be disabled.
 The ControlZone software is installed into the central shared NFS, but is also
 copied to both nodes´ local file systems. The HA cluster uses the central directory
@@ -174,11 +177,12 @@ and UI, together with related IP address.
 NOTE: Neither installation of the basic {sleha} cluster, nor installation of the
 CM ControlZone software is covered in the document at hand.
 
-Consult the {sleha} product documentation for installation instructions
-(https://documentation.suse.com/sle-ha/15-SP4/single-html/SLE-HA-administration/#part-install).
+Consult the {sleha} product documentation at 
+https://documentation.suse.com/sle-ha/15-SP4/single-html/SLE-HA-administration/#part-install for installation instructions. 
+
 For Convergent Mediation installation instructions, refer to the respective
-product documentation 
-(https://infozone.atlassian.net/wiki/spaces/MD9/pages/4849683/Installation+Instructions). 
+product documentation at 
+https://infozone.atlassian.net/wiki/spaces/MD9/pages/4849683/Installation+Instructions. 
 
 
 [[sec.prerequisites]]
@@ -410,7 +414,7 @@ Check this on both nodes.
 
 Check if the file `/etc/hosts` contains at least the address resolution for
 both cluster nodes `{myNode1}`, `{myNode1}`, and the ControlZone virtual
-host name `sap{mySidLc}cz`. Add those entries if they are missing.
+host name `sap{mySidLc}cz`. Add these entries if they are missing.
 
 [subs="attributes"]
 ----
@@ -564,9 +568,12 @@ Timeout (msgwait)  : 120
      Active: active (running) since Tue 2024-05-14 16:37:22 CEST; 13min ago
 ----
 
-Check this on both nodes. For more information on SBD configuration, see
+Check this on both nodes. For more information on SBD configuration, see:
+
 * https://documentation.suse.com/sle-ha/15-SP4/single-html/SLE-HA-administration/#cha-ha-storage-protect 
+
 * TID 7016880 and TID 7008216
+
 * manual page sbd(8), stonith_sbd(7), and cs_show_sbd_devices(8)
 
 ==== Corosync cluster communication
@@ -1200,7 +1207,7 @@ Unless otherwise stated, the test prerequisites are always that
 * SBD and corosync are fine.
 * NFS and local disks are fine. 
 * the ControlZone resources are all running.
-* no failcounts or migration constraints are in the CIB.
+* no fail counts or migration constraints are in the CIB.
 * the cluster is idle, no actions are pending.
 
 [[sec.test-restart]]
@@ -1210,7 +1217,7 @@ Unless otherwise stated, the test prerequisites are always that
 - ControlZone resources
 
 .{testDescr}
-- The ControlZone resources are stopped and re-started in-place.
+- The ControlZone resources are stopped and restarted in-place.
 
 .{testProc}
 . Check the ControlZone resources and cluster.
@@ -1316,7 +1323,7 @@ Unless otherwise stated, the test prerequisites are always that
 - ControlZone resources (UI)
 
 .{testDescr}
-- The ControlZone UI is re-started on same node.
+- The ControlZone UI is restarted on same node.
 
 .{testProc}
 . Check the ControlZone resources and cluster.
@@ -1335,7 +1342,7 @@ Unless otherwise stated, the test prerequisites are always that
 # cs_wait_for_idle -s 5; crm_mon -1r
 ----
 +
-. Cleanup failcount.
+. Clean up fail count.
 +
 [subs="specialchars,attributes"]
 ----
@@ -1364,7 +1371,7 @@ Unless otherwise stated, the test prerequisites are always that
 - ControlZone resources (platform)
 
 .{testDescr}
-- The ControlZone resources are stopped and re-started on same node.
+- The ControlZone resources are stopped and restarted on same node.
 
 .{testProc}
 . Check the ControlZone resources and cluster.
@@ -1382,7 +1389,7 @@ Unless otherwise stated, the test prerequisites are always that
 # cs_wait_for_idle -s 5; crm_mon -1r
 ----
 +
-. Cleanup failcount.
+. Clean up fail count.
 +
 [subs="specialchars,attributes"]
 ----
@@ -1509,7 +1516,7 @@ Unless otherwise stated, the test prerequisites are always that
 ==== Testing cluster reaction on network split-brain
 ==========
 .{testComp}
-- Network (for corosync)
+- Network (for Corosync)
 
 .{testDescr}
 - The network fails, node without resources gets fenced, resources keep running.
@@ -1522,7 +1529,7 @@ Unless otherwise stated, the test prerequisites are always that
 {mynode2}:~ # cs_wait_for_idle -s 5; crm_mon -1r
 ----
 +
-. Manually block ports for corosync.
+. Manually block ports for Corosync.
 +
 [subs="specialchars,attributes"]
 ----
@@ -1551,7 +1558,7 @@ Unless otherwise stated, the test prerequisites are always that
 // TODO PRIO1: more test details
 
 .{testExpect}
-. The cluster detects failed corosync.
+. The cluster detects failed Corosync.
 . The cluster fences the node.
 . The cluster keeps all resources on the same node.
 . The fenced node needs to be connected to the cluster.
@@ -1569,7 +1576,7 @@ Define additional test cases according to your needs. Some test cases you should
 - Isolate the SBD.
 - Maintenance procedure with cluster is continuously running, but application restarts.
 - Maintenance procedure with cluster restarts, but application is running.
-- Kill the corosync process of one cluster node.
+- Kill the Corosync process of one cluster node.
 
 See also manual page crm(8) for cluster crash_test.
 
@@ -1585,7 +1592,7 @@ known. This chapter describes general administrative tasks.
 [[sec.best-practice]]
 === Dos and don'ts
 
-The following five basic rules will help you avoid known issues: 
+The following basic rules will help you avoid known issues: 
 
 - Carefully test all configuration changes and administrative procedures on the
 test cluster before applying them to the production cluster.
@@ -1659,10 +1666,12 @@ See also manual page SAPCMControlZone_maintenance_examples(7), crm(8).
 
 === Migrating the ControlZone resources
 
-ControlZone application and Linux cluster are checked for a clean and idle state.
+To migrate the ControlZone resources to another node, the following steps are performed 
+(see commands below):
+ControlZone application and Linux cluster are initially checked for a clean and idle state.
 The ControlZone resources are moved to the other node. 
-The associated location rule will be removed after the takeover took place. ControlZone 
-application and HA cluster are then checked for a clean and idle state.
+The associated location rule will be removed after the takeover took place. Finally, ControlZone 
+application and HA cluster are again checked for a clean and idle state.
 
 [subs="specialchars,attributes"]
 ----
@@ -1687,11 +1696,12 @@ See also manual page SAPCMControlZone_maintenance_examples(7).
 Find below a generic procedure, mainly for maintenance of the ControlZone components. 
 The resources are temporarily removed from cluster control. The Linux cluster remains active.
 
-ControlZone application and HA cluster are checked for a clean and idle state.
+The individual steps are carried out as follows (see commands below):
+ControlZone application and HA cluster are initially checked for a clean and idle state.
 The ControlZone resource group is set to maintenance mode. This is required to enable manual 
 actions on the resources. After the manual actions are completed, the resource group is placed 
 back under cluster control. It is neccessary to wait for the completion of each step and to check the results. 
-ControlZone application and HA cluster are finally checked for a clean and idle state.
+Finally, ControlZone application and HA cluster are again checked for a clean and idle state.
 
 [subs="specialchars,attributes"]
 ----
@@ -1714,17 +1724,17 @@ See also manual page SAPCMControlZone_maintenance_examples(7).
 
 === Showing resource agent log messages
 
-Failed RA actions on a node are displayed in the current message file..
+Failed RA actions on a node are displayed in the current message file.
 
 [subs="specialchars,attributes"]
 ----
 # grep "SAPCMControlZone.*rc=[1-7,9]" /var/log/messages
 ----
 See also manual page ocf_suse_SAPCMControlZone(7).
 
-=== Cleaning up resource failcount
+=== Cleaning up resource fail count
 
-Cleaning up resource failcount can be done after the cluster has recovered the resource from a failure.
+Cleaning up resource fail count can be done after the cluster has recovered the resource from a failure.
 
 [subs="specialchars,attributes"]
 ----
@@ -1853,7 +1863,7 @@ op_defaults op-options: \
 [[sec.appendix-coros]]
 === Corosync configuration of the two-node cluster
 
-Find below the corosync configuration for one corosync ring. Ideally two rings would be used.
+Find below the Corosync configuration for one Corosync ring. Ideally two rings would be used.
 
 [subs="specialchars,attributes"]
 ----