SAP-convergent-mediation-ha-setup-sle15.adoc: formatting

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

@@ -85,21 +85,21 @@ include::common_intro_feedback.adoc[]
 
 The CM ControlZone platform is responsible for providing services to other instances.
 Several platform containers may exist in a CM system, for high availability,
-but only one is active at a time. The CM central ControlZone UI is used to query, edit,
-import, and export data.
+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
 the {sleha} cluster and specfic HA resource agents.
 
 From the application perspective the following variants are covered:
 
-- Convergent Mediation platform service running alone.
+- ControlZone platform service running alone.
 
-- Convergent Mediation platform and UI services running together.
+- ControlZone platform and UI services running together.
 
-- Convergent Mediation binaries stored and started on central NFS (not recommended).
+- ControlZone binaries stored and started on central NFS (not recommended).
 
-- Convergent Mediation binaries copied to and started from local disks.
+- ControlZone binaries copied to and started from local disks.
 
 - Java VM stored and started on central NFS (not recommended).
 
@@ -190,9 +190,9 @@ one UI service per cluster.
 
 - The platform and UI are installed into the same MZ_HOME.
 
-- Linux shell of the mzadmin user is ´/bin/bash´.
+- Linux shell of the mzadmin user is `/bin/bash`.
 
-- The mzadmin´s ´~/.bashrc´ inherits MZ_HOME, JAVA_HOME and MZ_PLATFORM
+- The mzadmin´s `~/.bashrc` inherits MZ_HOME, JAVA_HOME and MZ_PLATFORM
 from SAPCMControlZone RA. This variables need to be set as described in the RA´s
 documentation, i.e. manual page ocf_suse_SAPCMControlZone(7).
 
@@ -210,7 +210,7 @@ cluster nodes and services are resolved locally in the Linux system.
 - Strict time synchronization between the cluster nodes, e.g. NTP. All nodes of a
 cluster have configured the same timezone.
 
-- Needed NFS shares (e.g. ´/usr/sap/<SID>´) are mounted statically or by automounter.
+- Needed NFS shares (e.g. `/usr/sap/<SID>`) are mounted statically or by automounter.
 No client-side write caching. File locking might be configured for application
 needs.
 
@@ -233,7 +233,7 @@ the mzsh should be accessed on the cluster nodes´ local filesystems.
 The mzsh is called with the arguments startup, shutdown and status. Its return
 code and output is interpreted by the RA. Thus the command and its output needs
 to be stable. The mzsh shall not be customized. Particularly environment
-variables set thru _~/.bashrc_ must not be changed.
+variables set thru `~/.bashrc` must not be changed.
 
 - The mzsh is called on the active node with a defined interval for regular resource
 monitor operations. It also is called on the active or passive node in certain situations.
@@ -242,11 +242,11 @@ Those calls might run in parallel.
 === The setup procedure at a glance
 
 For a better understanding and overview, the installation and setup is divided into
-nine steps.
+nine nice steps.
 
 // - Collecting information
 - <<sec.information>>
-// - Checking the operating system
+// - Checking the operating system basic setup 
 - <<sec.os-basic-check>>
 // - Checking the HA cluster basic setup 
 - <<sec.ha-basic-check>>
@@ -284,65 +284,65 @@ already in place. It is good practice to first fill out the parameter sheet.
 |Value
 
 | NFS server and share
-| ´{myNFSSrv}:/s/{mySid}/cm´
+| `{myNFSSrv}:/s/{mySid}/cm`
 |
 
 | NFS mount options
-| ´vers=4,rw,noac,sync,default´
+| `vers=4,rw,noac,sync,default`
 |
 
 | central MZ_HOME
-| ´/usr/sap/{mySid}´
+| `/usr/sap/{mySid}`
 |
 
 | local MZ_HOME
-| ´{mzhome}´
+| `{mzhome}`
 |
 
 | MZ_PLATFORM
-| ´{mzPlatf}´
-| ´{mzPlatf}´
+| `{mzPlatf}`
+| `{mzPlatf}`
 
 | JAVA_HOME
-| ´{mzJavah}´
+| `{mzJavah}`
 |
 
 | node1 hostname
-| ´{myNode1}´
+| `{myNode1}`
 |
 
 | node2 hostname
-| ´{myNode2}´
+| `{myNode2}`
 |
 
 | node1 IP addr 
-| ´{myIPNode1}´
+| `{myIPNode1}`
 |
 
 | node2 IP addr
-| ´{myIPNode2}´
+| `{myIPNode2}`
 |
 
 | SID
-| ´{mySid}´
+| `{mySid}`
 |
 
 | mzadmin user
-| ´{mySapAdm}´
+| `{mySapAdm}`
 |
 
 | virtual IP addr
-| ´{myVipAcz}´
+| `{myVipAcz}`
 |
 
 | virtual hostname
-| ´{myVipNcz}´
+| `{myVipNcz}`
 |
 
 |====
 
 [[sec.os-basic-check]]
-=== Checking the operating system
+=== Checking the operating system basic setup 
 
 // TODO PRIO2: content ... on both nodes
 
@@ -382,9 +382,9 @@ i | java-17-openjdk          | OpenJDK 17 Runtime Environment     | package
 
 ==== IP addresses and virtual names
 
-Check if the file ´/etc/hosts´ contains at least the address resolution for
-both cluster nodes ´{myNode1}´, ´{myNode1}´ as well as the ControlZone virtual
-hostname ´sap{mySidLc}cz´. Add those entries if they are missing.
+Check if the file `/etc/hosts` contains at least the address resolution for
+both cluster nodes `{myNode1}`, `{myNode1}` as well as the ControlZone virtual
+hostname `sap{mySidLc}cz`. Add those entries if they are missing.
 
 [subs="attributes"]
 ----
@@ -399,7 +399,7 @@ See also manual page hosts(8).
 
 ==== Mount points and NFS shares
 
-Check if the file ´/etc/fstab´ contains the central NFS share MZ_HOME.
+Check if the file `/etc/fstab` contains the central NFS share MZ_HOME.
 The filesystem is statically mounted on all nodes of the cluster.
 The correct mount options are depending on the NFS server. However, client-side
 write caching has to be disabled in any case.
@@ -414,13 +414,13 @@ write caching has to be disabled in any case.
 
 ...
 ----
-// TODO PRIO: above output
+// TODO PRIO1: above output
 Check this on both nodes.
 See also manual page mount(8), fstab(5) and nfs(5).
 
 ==== Linux user and group number scheme
 
-Check if the file ´/etc/passwd´ contains the mzadmin user ´{mySapAdm}´.
+Check if the file `/etc/passwd` contains the mzadmin user `{mySapAdm}`.
 
 [subs="attributes"]
 ----
@@ -433,7 +433,7 @@ See also manual page passwd(5).
 
 ==== Password-free ssh login
 
-// TODO PRIO1: content
+// TODO PRIO2: content
 
 [subs="attributes"]
 ----
@@ -447,7 +447,7 @@ See also manual page ssh(1) and ssh-keygen(1).
 
 ==== Time synchronisation
 
-// TODO PRIO1: content 
+// TODO PRIO2: content 
 
 [subs="attributes"]
 ----
@@ -465,9 +465,9 @@ Check this on both nodes.
 See also manual page chronyc(1) and chrony.conf(5).
 
 [[sec.ha-basic-check]]
-=== Checking the HA cluster basic setup
+=== Checking HA cluster basic setup 
 
-// TODO PRIO2: content 
+// TODO PRIO2: content
 
 ==== Watchdog
 
@@ -550,7 +550,7 @@ RING ID 0
         status  = ring 0 active with no faults
 ----
 Check this on both nodes.
-See appendix <<sec.appendix-coros>> for a _corosync.conf_ example.
+See appendix <<sec.appendix-coros>> for a `corosync.conf` example.
 See also manual page systemctl(1) and corosync-cfgtool(1).
 
 ==== systemd cluster services