Fixed typos

for better SiteImprove results.

Author: chabowski

adoc/SAPNotes_HANA20_15.adoc

@@ -49,7 +49,7 @@ XFS file system::
  {sumadoc}
 {RMT} = {rmtool} documentation::
  {rmtGuide15}
-{scc} Fequently Asked Questions::
+{scc} Frequently Asked Questions::
  {sccfaq}
 
 

adoc/SAPNotes_HANA20_angi_15.adoc

@@ -49,7 +49,7 @@ XFS file system::
  {sumadoc}
 {RMT} = {rmtool} documentation::
  {rmtGuide15}
-{scc} Fequently Asked Questions::
+{scc} Frequently Asked Questions::
  {sccfaq}
 
 

adoc/SAP_HA740_SetupGuide_AWS.adoc

@@ -2055,7 +2055,7 @@ Use the following command as root and modify ASCS group in the editor.
 
 NOTE: Version 1.0.2 of the Route 53 agent
 will not work if the EC2 metadata contains a
-string like "local-ipv4" in the userdata section!
+string like "local-ipv4" in the user data section!
 
 ==== Configuring the Resources for the ERS
 

adoc/SLES-SQL-server-linux.adoc

@@ -1170,7 +1170,7 @@ curl --location https://github.com/Microsoft/sql-server-samples/releases/downloa
     --output /tmp/WideWorldImporters-Full.bak
 ----
 
-Restore full backup into `mssql-server` with `sqlcmd` while updating paths for the data, userdata, transaction log, and in-memory data:
+Restore full backup into `mssql-server` with `sqlcmd` while updating paths for the data, user data, transaction log, and in-memory data:
 (Adapt the password and storage location to your setup)
 
 [source,sql]

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

@@ -2817,7 +2817,7 @@ Expected observation: The cluster initiates a takeover. The master name server a
 
 * Manually registering a failed primary site as new secondary.
 
-Prerequistes: A failed former primary sites has been manually registered. The exact site name has been used as already known to the cluster, see parameter sheet.
+Prerequisites: A failed former primary sites has been manually registered. The exact site name has been used as already known to the cluster, see parameter sheet.
 
 Expected observation: The cluster accepts the registered site as secondary. The HANA resources are looking fine. After a while, system replication for the new secondary site gets okay (srHook SOK). 
 

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

@@ -2413,7 +2413,7 @@ This test category is simulating a complete site failure.
 
 * Manually registering a failed primary site as new secondary.
 
-Prerequistes: A failed former primary sites has been manually registered. The exact site name has been used as already known to the cluster, see parameter sheet.
+Prerequisites: A failed former primary sites has been manually registered. The exact site name has been used as already known to the cluster, see parameter sheet.
 
 ==== Tests regarding the {HANA} instances of the primary site
 

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

@@ -2709,7 +2709,7 @@ Expected observation: The cluster initiates a takeover. The master name server a
 
 * Manually registering a failed primary site as new secondary.
 
-Prerequistes: A failed former primary sites has been manually registered. The exact site name has been used as already known to the cluster, see parameter sheet.
+Prerequisites: A failed former primary sites has been manually registered. The exact site name has been used as already known to the cluster, see parameter sheet.
 
 Expected observation: The cluster accepts the registered site as secondary. The HANA resources are looking fine. After a while, system replication for the new secondary site gets okay (srHook SOK). 
 

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

@@ -847,7 +847,7 @@ to check the SAP hostagent:
 # /usr/sap/hostctrl/exe/saphostctrl -function ListInstances
 Inst Info : {sapsid} - {sapino} - {sapnode1} - 753, patch 819, changelist 2069355
 ----
-The SystemV style sapinit is running and the hostagent recognises the installed
+The SystemV style sapinit is running and the hostagent recognizes the installed
 database.
 
 === Verify that both databases are up and running

adoc/SLES4SAP-hana-systemv-appendix.adoc

@@ -14,7 +14,7 @@ to check the SAP hostagent:
 # /usr/sap/hostctrl/exe/saphostctrl -function ListInstances
 Inst Info : {sapsid} - {sapino} - {sapnode1} - 753, patch 819, changelist 2069355
 ----
-The SystemV style sapinit is running and the hostagent recognises the installed
+The SystemV style sapinit is running and the hostagent recognizes the installed
 database.
 
 As Linux user _{refsidadm}_, use the command line tool `HDB` to get an

xml/MAIN-SBP-AMD-EPYC-4-SLES15SP4.xml

@@ -2997,7 +2997,7 @@ dmesg | grep SEV
       </figure>
 
       <para>We see in <xref linkend="fig-stream-single-vms-avg"/> how the single STREAM bandwidth stays flat until (and including when) 6 VMs are used.
-        Then it starts to decline a bit, as more VMs are packed on the NUMA nodes and, hence, compete for the bandwith of the memory controllers. However,
+        Then it starts to decline a bit, as more VMs are packed on the NUMA nodes and, hence, compete for the bandwidth of the memory controllers. However,
          <xref linkend="fig-stream-single-vms-sum"/> reminds us how the total bandwidth achieved, if we consider all the VMs involved in each experiments, actually goes up,
         until it reaches the same level that we know (for example, from <xref linkend="fig-stream-bm-vm"/>) it can touch.
       </para>