Fixed typos

for better results in SiteImprove.

Author: chabowski

adoc/OS_Security_Hardening_Guide_for_SAP_HANA_SLES12.adoc

@@ -573,7 +573,7 @@ NOTE: This section only covers settings for IPv4. There are similar IPv6 paramet
 
 Description::
 `sysctl` (system control) variables change certain kernel parameters that influence the behavior of different parts of the operating system, such as the Linux network stack. 
-These kernel parameters can be looked up in the proc file system, in `/proc/sys/`. Many kernel parameters can be directly changed by echo'ing a value into a parameter file. 
+These kernel parameters can be looked up in the proc file system, in `/proc/sys/`. Many kernel parameters can be directly changed by echoing a value into a parameter file. 
 However, these changes are not persisted and are lost after a system reboot. 
 Therefore we recommend to make all changes in the `sysctl` configuration file.
 

adoc/OS_Security_Hardening_Guide_for_SAP_HANA_SLES15.adoc

@@ -560,7 +560,7 @@ NOTE: This section only covers settings for IPv4. There a similar IPv6 parameter
 Description::
 `sysctl` (system control) variables change certain kernel parameters that influence the behavior of different parts of the operating system, 
 such as the Linux network stack. These kernel parameters can be looked up in the `proc` filesystem, in `/proc/sys/`. 
-Many kernel parameters can directly be changed by echo'ing a value into a parameter file. 
+Many kernel parameters can directly be changed by echoing a value into a parameter file. 
 However, these changes are not persisted and are lost after a system reboot. 
 Therefore we recommend to make all changes in the `sysctl` configuration file.
 

adoc/SAP-EIC-SLEMicro.adoc

@@ -111,7 +111,7 @@ Now create the logical volume; use 100% of the disk.
 sudo lvcreate -n lvlonghorn -l100%FREE vgdata
 ----
 
-On the logical volume, create the XFS file system. You do not need to create a partion on top of it.
+On the logical volume, create the XFS file system. You do not need to create a partition on top of it.
 [source, bash]
 ----
 sudo mkfs.xfs /dev/vgdata/lvlonghorn

adoc/SAP-Rancher-RKE2-Installation.adoc

@@ -29,7 +29,7 @@ In the next step, make sure you select a Kubernetes version that is supported by
 
 
 If you do not have any further requirements to Kubernetes, you can click the *Create* button at the very bottom.
-In any other cases, talk to your administrators before making adjustements.
+In any other cases, talk to your administrators before making adjustments.
 
 After you clicked *Create*, you should see a screen similar to the below:
 
@@ -42,7 +42,7 @@ A common high availability setup holds:
 * 3 x worker nodes
 
 The next step is to copy the registration command to the target machines' shell and execute it.
-If your {rancher} instance holds a self-signed certifcate, make sure to activate the text bar holding the registration command in the check box below.
+If your {rancher} instance holds a self-signed certificate, make sure to activate the text bar holding the registration command in the check box below.
 
 You can run the command on all nodes in parallel. You do not need to wait until a single node is down.
 When all machines are registered, you can see the cluster status at the top, changing from "updating" to "active".

adoc/SAP-S4HA10-setup-simplemount-sle15.adoc

@@ -192,7 +192,7 @@ image::sles4sap_s4hana2021_resources_classic_compared_to_simple_mount.svg[SVG]
   side. The new enqueue architecture is also named ENSA2.
 
 - Use of native *systemd* integration for {sap} hostagent and instance´s `sapstartsrv`.
-  Refer to the {sap} documentation for the neccessary product version. See also SAP note 3139184.
+  Refer to the {sap} documentation for the necessary product version. See also SAP note 3139184.
   SUSE *systemd* version 234 at least is needed. For details refer to the {sles4sap} product documentation.
   SUSE resource agents are needed, at least _sapstartsrv-resource-agents 0.9.1_ and _resource-agents 4.x_ from November 2021.
 
@@ -1990,7 +1990,7 @@ The next step requires the following information:
 
 .Post Step Procedure after SAP Preparation Step
 ==========
-- Add the user _{mySapAdm}_ to the unix user group _haclient_.
+- Add the user _{mySapAdm}_ to the Unix user group _haclient_.
 +
 [subs="specialchars,attributes,quotes"]
 ----
@@ -2108,7 +2108,7 @@ We will cover some advantages and disadvantages of special configuration below:
 * The three node cluster and three locations
     - Advantage: symmetric spread of all nodes over all locations
     - Advantage: diskless SBD feature is allowed
-    - Disadvantage: higher planing effort and complexity for infrastructure planning
+    - Disadvantage: higher planning effort and complexity for infrastructure planning
 
 == References
 
@@ -2155,7 +2155,7 @@ include::SAPNotes_s4_2101.adoc[]
 
 Find below the complete crm configuration for {sap} system {mySid}. This example
 is for the two node cluster, but without priority fencing.
-In a multi-node cluster you will find additonal node entries like *node 3: {my3nd3}*.
+In a multi-node cluster you will find additional node entries like *node 3: {my3nd3}*.
 
 [subs="attributes"]
 ----

adoc/SAP-S4HA10-setupguide-sle15.adoc

@@ -168,7 +168,7 @@ for the cluster fencing mechanism STONITH.
 - For {s4Hana} the new concept implies that, after a resource failure, the ASCS does not need to be started at the ERS
   side. The new enqueue architecture is also named ENSA2.
 - Use of native systemd integration for {sap} hostagent and instance´s sapstartsrv.
-  Refer to the {sap} documentation for the neccessary  product version. See also SAP Note 3139184.
+  Refer to the {sap} documentation for the necessary  product version. See also SAP Note 3139184.
   SUSE *systemd* version 234 at least is needed. For details refer to the {sles4sap} product documentation.
   SUSE resource agents are needed; at least *sapstartsrv-resource-agents 0.9.1* and *resource-agents 4.x* from November 2021.
 
@@ -484,7 +484,7 @@ Prepare the three servers for the distributed {sap} installation. Server 1
 
 - Mount the instance and database file systems on one specific node:
 
-.Mount several file systes for {sapS4} on different nodes
+.Mount several file systems for {sapS4} on different nodes
 =============================================================
 
 [subs="attributes"]
@@ -723,7 +723,7 @@ service/halib = $(DIR_EXECUTABLE)/saphascriptco.so
 service/halib_cluster_connector = /usr/bin/sap_suse_cluster_connector
 ----
 
-Add the user _{mySapAdm}_ to the unix user group _haclient_.
+Add the user _{mySapAdm}_ to the Unix user group _haclient_.
 
 [subs="attributes"]
 ----
@@ -1461,7 +1461,7 @@ The task list to set up the three node cluster is similar to the task list of th
 details are described different here to get a diskless SBD setup.
 Such a diskless SBD setup is an optional improvement for three nodes, but does not work for two nodes.
 On the other hand, priority fencing is an optional improvement for two nodes, but does not work for three nodes.
-Ssee the {sleHA} product documentation for details
+See the {sleHA} product documentation for details
 (https://documentation.suse.com/sle-ha/15-SP3/single-html/SLE-HA-administration/#pro-ha-storage-protect-fencing).
 
 NOTE: When extending a cluster from two to three nodes, make sure to not use priority fencing.

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

@@ -223,7 +223,7 @@ via network. The service´s virtual host name or virtual IP address managed by t
 cluster should not be used when called by RA monitor actions.
 
 - Technical  users and groups are defined locally in the Linux system. If users are
-resolved by remote service, local caching is neccessary. `Substitute user` (su) to
+resolved by remote service, local caching is necessary. `Substitute user` (su) to
 the mzadmin needs to work reliable and without customized actions or messages.
 
 - Name resolution for host names and virtual host names is crucial. Host names of
@@ -1709,7 +1709,7 @@ 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. 
+back under cluster control. It is necessary to wait for the completion of each step and to check the results. 
 Finally, ControlZone application and HA cluster are again checked for a clean and idle state.
 
 [subs="specialchars,attributes"]

adoc/SAPDI3-Vsphere-Vsan.adoc

@@ -18,7 +18,7 @@
 === Install RKE 2 cluster on top of the {vmw} virtual machines.
 
 Before you start the installation of RKE 2, create the configuration below for the RKE 2 cluster.
-This is neccessary to use the vSAN as backing storage for the storage class in RKE 2. You will need the following data:
+This is necessary to use the vSAN as backing storage for the storage class in RKE 2. You will need the following data:
 
 * user on vSphere/vSAN with the necessary access rights 
 * vCenter hostname

adoc/SLES4SAP-HANAonKVM-15SP2.adoc

@@ -258,7 +258,7 @@ The guest VM must:
 * run {sles4sap} 15 SP2 or later.
 * be a {sles} supported VM guest as per Section 7.1 "Supported VM Guests" of the https://documentation.suse.com/sles/15-SP2/html/SLES-all/cha-virt-support.html#virt-support-guests[SUSE Virtualization Guide].
 * comply with KVM limits as per https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP2/#allArch-virtualization-kvm-limits["SUSE Linux Enterprise Server 15 SP2 release notes]".
-* fulfill the SAP HANA Hardware and Cloud Measurent Tools (HCMT) storage KPI's as per {launchpadnotes}2493172[SAP Note 2493172 "SAP HANA Hardware and Cloud Measurement Tools"]. 
+* fulfill the SAP HANA Hardware and Cloud Measurement Tools (HCMT) storage KPI's as per {launchpadnotes}2493172[SAP Note 2493172 "SAP HANA Hardware and Cloud Measurement Tools"]. 
   Refer to <<_sec_storage>> for storage configuration details.
 * be configured according to the *SUSE Best Practices for SAP HANA on KVM - {sles4sap} {slesProdVersion}* document at hand.
 
@@ -1041,7 +1041,7 @@ When using a virtual disk for `vhostmd`, the virtual disk device must be world-r
 [[_sec_configuring_guest_at_boot_time]]
 ==== Configuring the Guest at boot time
 
-The folling settings need to be configured at boot time of the VM. 
+The following settings need to be configured at boot time of the VM. 
 To persist these configurations it is recommended to put the commands provided below into a script which is executed as part of the boot process.
 
 ===== Disabling `irqbalance` 

adoc/SLES4SAP-HANAonKVM-15SP4.adoc

@@ -276,7 +276,7 @@ The guest VM must:
 * run {sles} or {sles4sap} 15 SP4 or later.
 * be a {sles} supported VM guest as per Section 7.4 "Supported guest operating systems" of the https://documentation.suse.com/sles/15-SP4/single-html/SLES-virtualization/#book-virtualization[SUSE Virtualization Guide].
 * comply with KVM limits as per https://documentation.suse.com/sles/15-SP4/single-html/SLES-virtualization/#virt-hypervisors-limits["SUSE Linux Enterprise Server 15 SP4 Hypervisor Limits"].
-* fulfill the SAP HANA Hardware and Cloud Measurent Tools (HCMT) storage KPI's as per {launchpadnotes}2493172[SAP Note 2493172 "SAP HANA Hardware and Cloud Measurement Tools"]. 
+* fulfill the SAP HANA Hardware and Cloud Measurement Tools (HCMT) storage KPI's as per {launchpadnotes}2493172[SAP Note 2493172 "SAP HANA Hardware and Cloud Measurement Tools"]. 
   Refer to <<_sec_storage>> for storage configuration details.
 * be configured according to the *SUSE Best Practices for SAP HANA on KVM* ({sles4sap} {slesProdVersion}) document at hand.
 
@@ -363,7 +363,7 @@ It can be loaded with the `modprobe` command, but chances are high that it is al
 If the SR-IOV-capable module is not in use by default and it also fails to load with `modprobe`, this could mean that another driver, potentially one that is not SR-IOV-capable, 
 is currently loaded instead. In which case, it should be removed with the `rmmod` command.
 
-When the proper module is loaded, creating at least one VF can be done by issueing the following command (which creates four of them):
+When the proper module is loaded, creating at least one VF can be done by issuing the following command (which creates four of them):
 
 ----
 echo 4 > /sys/bus/pci/devices/0000\:17\:00.0/sriov_numvfs
@@ -728,7 +728,7 @@ The memory unit can be set to GiB to ease the memory computations.
 It is important to map the host topology into the guest VM, as described below.
 This allows HANA to spread its own workload threads across many virtual CPUs and NUMA nodes.
 
-For example, for a 4-socket system, with 28 cores per socket and hyperthreading enabled, the virtual CPU configuration for a single VM will also have 4 sockets, 28 cores, 2 threads. In a multi-VM scenario it is also imperative that the hosts NUMA topology is maped to the VMs. Two VMs on a 4-socket systems would both reflect the NUMA topology of two of the hosts NUMA nodes/sockets. Four VMs on a 4-socket system would reflect the NUMA topology of a single NUMA node/socket.
+For example, for a 4-socket system, with 28 cores per socket and hyperthreading enabled, the virtual CPU configuration for a single VM will also have 4 sockets, 28 cores, 2 threads. In a multi-VM scenario it is also imperative that the hosts NUMA topology is mapped to the VMs. Two VMs on a 4-socket systems would both reflect the NUMA topology of two of the hosts NUMA nodes/sockets. Four VMs on a 4-socket system would reflect the NUMA topology of a single NUMA node/socket.
 
 Always make sure that, in the guest VM configuration file:
 
@@ -1076,7 +1076,7 @@ When using a virtual disk for `vhostmd`, the virtual disk device must be world-r
 [[_sec_configuring_guest_at_boot_time]]
 ==== Configuring the Guest at boot time
 
-The folling settings need to be configured at boot time of the VM. 
+The following settings need to be configured at boot time of the VM. 
 To persist these configurations, it is recommended to put the commands provided below into a script which is executed as part of the boot process.
 
 ===== Disabling `irqbalance`