Fixed typos

Author: chabowski

adoc/SAP-EIC-General.adoc

@@ -41,7 +41,7 @@ The following excerpt shows how to create such a CSR:
 openssl req -newkey rsa:2048 -keyout domain.key -out domain.csr -passout pass:<csr-passphrase> -subj  "/C=DE/ST=BW/L=Nuremberg/O=SUSE"
 ----
 
-Before you can sign the CSR, you need to add the DNS names of your Kuberntes Services to the CSR.
+Before you can sign the CSR, you need to add the DNS names of your Kubernetes Services to the CSR.
 Therefore, create a file with the content below and replace the *<servicename>* and *<namespace>* with the name of your Kubernetes service and the namespace in which it is placed:
 
 [source, bash]
@@ -164,7 +164,7 @@ spec:
     - key encipherment
 ----
 
-Apply the yaml file to your kubernetes cluster.
+Apply the yaml file to your Kubernetes cluster.
 [source, bash]
 ----
 kubectl apply -f selfsigned-issuer.yaml

adoc/SAP-EIC-Harvester-main.adoc

@@ -118,14 +118,14 @@ For a graphical overview of what is needed, take a look at the landscape overvie
 
 image::SAP-EIC-Harvester-Architecture.svg[title=Architecture EIC Cluster,scaledwidth=99%,opts=inline,Embedded]
 
-* The grey rectangles represent phyiscal servers (hardware).
+* The grey rectangles represent physical servers (hardware).
 * The orange rectangles represent {harvester} instances.
 * The blue rectangles represent Kubernetes clusters.
 * The green rectangles represent virtual machines.
 
 We will use this graphic overview in the guide to illustrate what the next step is and what it is for.
 
-NOTE: If you want to test upgrades of {harvester}, we recommend setting up an additional {harvester} cluster and seperate the production {eic} instances from the development and test instances.
+NOTE: If you want to test upgrades of {harvester}, we recommend setting up an additional {harvester} cluster and separate the production {eic} instances from the development and test instances.
 
 Starting with installing {harvester}, we will walk you through all the steps you need to take to get a fully set-up Kubernetes landscape for deploying {eic}.
 

adoc/SAP-Rancher-RKE2-Installation.adoc

@@ -38,7 +38,7 @@ image::SAP-Rancher-Create-Register.png[title=Rancher create registration,scaledw
 Now, in a first step, select the roles your node(s) should receive.
 A common high availability setup holds:
 
-* 3 x etcd / controll plane nodes
+* 3 x etcd / control plane nodes
 * 3 x worker nodes
 
 The next step is to copy the registration command to the target machines' shell and execute it.
@@ -67,7 +67,7 @@ image::SAP-Rancher-Create-Harvester-Landing.png[title=Rancher create harvester l
 Configure the cluster according to your requirements.
 For a highly available setup, we recommend using at least:
 
-* 3 x etcd / controll plane nodes
+* 3 x etcd / control plane nodes
 * 3 x worker nodes
 
 To do this, configure one pool of machines with a *Machine Count* of 3 and select only *etcd* and *Control Plane* for the roles.