Fixed smaller typos

Author: chabowski

adoc/SLES4SAP-hana-angi-perfopt-15.adoc

@@ -395,7 +395,7 @@ by the Linux cluster. All administrative actions need to be aligned with the clu
 * No firewall rules must block any needed port.
 * No SELinux rules must block any needed action.
 * Sizing of both {HANA} sites needs to be done according to SAP rules. The scale-up
-scenarios require both sites prepared for running the primary {HANA} database.
+scenarios require both sites to be prepared to run the primary {HANA} database.
 
 // TODO PRIO3: align with manual pages SAPHanaSR(7) and susHanaSR.py(7)
 For the HA/DR provider hook scripts _susHanaSR.py_ and _susTkOver.py_, the following

adoc/SLES4SAP-hana-angi-scaleout-perfopt-15.adoc

@@ -320,10 +320,10 @@ feature AUTOMATED_REGISTER=true is not possible with pure Multi-Tier replication
 See also the requirements section below.
 
 Multi-Target Replication ([A \<= B] \-> C)::
-This scenario and setup is described in this document. A Multi-Target system
+This scenario and setup is described in this document. A multi-target system
 replication has an additional target, which is connected to
 either the secondary (chain topology) or to the primary (star topology).
-Multi-Target replication is possible since {saphana} 2.0 SPS04.
+Multi-target replication is possible since {saphana} 2.0 SPS04.
 See also the requirements section below.
 
 
@@ -416,13 +416,13 @@ However, all nodes in one Linux cluster need to use the same style.
 * No firewall rules must block any needed port. 
 * No SELinux rules must block any needed action. 
 * Sizing of both {HANA} sites needs to be done according to SAP rules. The scale-out
-  scenarios require both sites prepared for running the primary {HANA} database.
+  scenarios require both sites to be prepared to run the primary {HANA} database.
 * {HANA} 2.0 SPS05 rev.059.04 and later provides Python 3 and the HA/DR provider hook
   method srConnectionChanged() with needed parameters for _susHanaSR.py_.
 * {HANA} 2.0 SPS05 or later provides the HA/DR provider hook method srServiceStateChanged()
   with needed parameters for susChkSrv.py.
 * {HANA} 2.0 SPS06 or later provides the HA/DR provider hook method preTakeover() with
-  multi-target aware parameters and separate return code for Linux HA clusters.
+  multi-target-aware parameters and separate return code for Linux HA clusters.
 * No other HA/DR provider hook script should be configured for the above mentioned methods.
   Hook scripts for other methods, provided in SAPHanaSR-angi, can  be used in parallel,
   if not documented contradictingly.
@@ -2666,7 +2666,7 @@ IIt covers configuring the third site in a multi-target setup after reinstalling
 === Setting up third {saphana} site in a multi-target architecture
 
 This section applies only if you plan to attach a 3rd replication site to the
-existing multi-targe aware cluster. This is a general approach. Neverteless, a
+existing multi-target-aware cluster. This is a general approach. Neverteless, a
 3rd site could have been prepared already.
 
 When the existing or newly created part of the scale-out performance optimized cluster is ready, complete the following steps to configure the third {saphana} site into multi-target.

adoc/SLES4SAP-hana-scaleOut-PerfOpt-15.adoc

@@ -304,16 +304,16 @@ managed all together by the Linux cluster. See also the requirements section
 below.
 
 Multi-Tier Replication ([A \=> B] \-> C)::
-A Multi-Tier system replication has an additional target, which must be
+A multi-tier system replication has an additional target, which must be
 connected to the secondary (chain topology). This is a special case of the
-Multi-Target replication. Because of the mandatory chain topology, the RA
-feature AUTOMATED_REGISTER=true is not possible with pure Multi-Tier replication.
+multi-target replication. Because of the mandatory chain topology, the RA
+feature AUTOMATED_REGISTER=true is not possible with pure multi-tier replication.
 See also the requirements section below.
 
 Multi-Target Replication ([A \<= B] \-> C)::
-A Multi-Target system replication has an additional target, which is connected to
+A multi-target system replication has an additional target, which is connected to
 either the secondary (chain topology) or to the primary (star topology).
-Multi-Target replication is possible since {HANA} 2.0 SPS04.
+Multi-target replication is possible since {HANA} 2.0 SPS04.
 See also the requirements section below.
 
 
@@ -396,7 +396,7 @@ However, all nodes in one Linux cluster have to use the same style.
 * No firewall rules must block any needed port. 
 * No SELinux rules must block any needed action. 
 * Sizing of both {HANA} sites needs to be done according to SAP rules. The scale-out
-  scenarios require both sites prepared for running the primary {HANA} database.
+  scenarios require both sites to be prepared to run the primary {HANA} database.
 * {HANA} 2.0 SPS05 rev.059 and later provides Python 3 as well as the HA/DR provider hook
   method srConnectionChanged() with needed parameters for SAPHanaSrMultiTarget.py.
 * {HANA} 2.0 SPS05 or later provides the HA/DR provider hook method srServiceStateChanged()

adoc/SLES4SAP-hana-scaleout-multitarget-perfopt-15.adoc

@@ -311,15 +311,15 @@ below.
 Multi-Tier Replication ([A \=> B] \-> C)::
 A Multi-Tier system replication has an additional target, which must be
 connected to the secondary (chain topology). This is a special case of the
-Multi-Target replication. Because of the mandatory chain topology, the RA
+multi-target replication. Because of the mandatory chain topology, the RA
 feature AUTOMATED_REGISTER=true is not possible with pure Multi-Tier replication.
 See also the requirements section below.
 
 Multi-Target Replication ([A \<= B] \-> C)::
-This scenario and setup is described in this document. A Multi-Target system
+This scenario and setup is described in this document. A multi-target system
 replication has an additional target, which is connected to
 either the secondary (chain topology) or to the primary (star topology).
-Multi-Target replication is possible since {saphana} 2.0 SPS04.
+Multi-target replication is possible since {saphana} 2.0 SPS04.
 See also the requirements section below.
 
 
@@ -411,13 +411,13 @@ However, all nodes in one Linux cluster have to use the same style.
 * No firewall rules must block any needed port. 
 * No SELinux rules must block any needed action. 
 * Sizing of both {HANA} sites needs to be done according to SAP rules. The scale-out
-  scenarios require both sites prepared for running the primary {HANA} database.
+  scenarios require both sites to be prepared to run the primary {HANA} database.
 * {HANA} 2.0 SPS05 rev.059 and later provides Python 3 as well as the HA/DR provider hook
   method srConnectionChanged() with needed parameters for SAPHanaSrMultiTarget.py.
 * {HANA} 2.0 SPS05 or later provides the HA/DR provider hook method srServiceStateChanged()
   with needed parameters for susChkSrv.py.
 * {HANA} 2.0 SPS06 or later provides the HA/DR provider hook method preTakeover() with
-  multi-target aware parameters and separate return code for Linux HA clusters.
+  multi-target-aware parameters and separate return code for Linux HA clusters.
 * No other HA/DR provider hook script should be configured for the above mentioned methods.
   Hook scripts for other methods, provided in SAPHanaSR-ScaleOut, can  be used in parallel,
   if not documented contradictingly.
@@ -2522,14 +2522,14 @@ image::SAPHanaSR-ScaleOut-MultiTarget-Plan-Phase7.svg[scaledwidth="100%"]
 [[MultiTarget]]
 This chapter is divided into two sections. Both are optional, depending oon your needs.
 
-- The first section describes the procedure to upgrade an existing scale-out performance optimized setup into a multi-target ready setup. It applies only if you plan to upgrade an existing not multi-target aware scale-out cluster.
+- The first section describes the procedure to upgrade an existing scale-out performance optimized setup into a multi-target-ready setup. It applies only if you plan to upgrade an existing not multi-target-aware scale-out cluster.
 
 - The second section is about configuring the 3rd site in a multi-target setup after freshly installing the whole landscape using the procedures mentioned in the document so far.  
 
 
 === Upgrading an existing cluster of scale-out performance optimized HANA
 
-This section applies only if you plan to upgrade an existing not multi-target aware scale-out cluster into a multi-target aware one. This is not the general approach. Usually you should start with a fresh installation for {saphana} scale-out multi-target systems.
+This section applies only if you plan to upgrade an existing not multi-target-aware scale-out cluster into a multi-target-aware one. This is not the general approach. Usually you should start with a fresh installation for {saphana} scale-out multi-target systems.
 
 ==== Prerequisites for the upgrade
 
@@ -2557,7 +2557,7 @@ At a glance the upgrade procedure looks like this:
 
 * Initially check if everything looks fine.
 * Set {sleha} cluster resources SAPHanaController and SAPHanaTopology into maintenance.
-* Install multi-target aware SAPHanaSR-ScaleOut package on all nodes.
+* Install multi-target-aware SAPHanaSR-ScaleOut package on all nodes.
 * Adapt sudoers permission on all nodes.
 * Replace HANA HA/DR provider configuration on both sites.
 * Check {sleha} and HANA HA/DR provider for matching defined upgrade entry state.

adoc/SLES4SAP-hana-sr-guide-PerfOpt-15.adoc

@@ -426,15 +426,15 @@ by the Linux cluster. All administrative actions need to be aligned with the clu
 * No firewall rules must block any needed port. 
 * No SELinux rules must block any needed action. 
 * Sizing of both {HANA} sites needs to be done according to SAP rules. The scale-up
-scenarios require both sites prepared for running the primary {HANA} database.
+scenarios require both sites to be prepared to run the primary {HANA} database.
 
 // TODO PRIO3: align with manual pages SAPHanaSR(7) and SAPHanaSR.py(7)
 For the HA/DR provider hook scripts SAPHanaSR.py and susTkOver.py, the following
 requirements apply:
 
 * {HANA} 2.0 SPS05 rev.059 and later provides Python3 as well as the HA/DR provider hook
-method srConnectionChanegd() with multi-target aware parameters. {HANA} 1.0 does not
-provide them. Python 3 and multi-target aware parameters are needed for the SAPHanaSR
+method srConnectionChanegd() with multi-target-aware parameters. {HANA} 1.0 does not
+provide them. Python 3 and multi-target-aware parameters are needed for the SAPHanaSR
 scale-up package.
 * {HANA} 2.0 SPS04 or later provides the HA/DR provider hook method preTakeover().
 // TODO PRIO1: check above version

adoc/SLES4SAP-hana-sr-guide-costopt-15.adoc

@@ -393,7 +393,7 @@ _{refsidadm}_ is not allowed to terminate the processes of the other tenant user
 scenario. Hence, only one replicating database pair and one non-replicating database
 in the same cluster as described in this guide are supported for the cost-optimized
 scenario.
-* RA and srHook runtime almost completely depends on call-outs to controlled
+* RA and srHook runtime almost completely depend on call-outs to controlled
 resources, OS and Linux cluster. The infrastructure needs to allow these call-outs
 to return in time.
 * Colocation constraints between the SAPHanaController or SAPHana RA and other
@@ -409,7 +409,7 @@ by the Linux cluster. All administrative actions need to be aligned with the clu
 * No firewall rules must block any needed port.
 * No SELinux rules must block any needed action.
 * Sizing of both {HANA} sites needs to be done according to SAP rules. The scale-up
-scenarios require both sites prepared for running the primary {HANA} database.
+scenarios require both sites to be prepared to run the primary {HANA} database.
 
 The {SLES4SAP} versions are:
 
@@ -422,8 +422,8 @@ For the HA/DR provider hook scripts SAPHanaSR.py and susCostOpt.py, the followin
 requirements apply:
 
 * {HANA} 2.0 SPS05 rev.059 and later provides Python3 as well as the HA/DR provider hook
-method srConnectionChanegd() with multi-target aware parameters. {sap} HANA 1.0 does not
-provide them. Python 3 and multi-target aware parameters are needed for the SAPHanaSR
+method srConnectionChanegd() with multi-target-aware parameters. {sap} HANA 1.0 does not
+provide them. Python 3 and multi-target-aware parameters are needed for the SAPHanaSR
 scale-up package.
 * {HANA} 2.0 SPS04 or later provides the HA/DR provider hook method postTakeover().
 // TODO PRIO1: check above version