First doc review: fixing format, wording, page breaks

According to documentation style guide, fixed several format issues,
wording, style.
Forced page breaks are okay after a chapter, but should not be added inside a chapters for sub-chapters at level 2 and below.

Author: chabowski

adoc/SAP-EIC-General.adoc

@@ -16,15 +16,14 @@ $ means that the command can be run by any user.
 
 
 # tag::disclaimer-production-versions[]
-IMPORTANT: If you want to use different versions of {slm}, {rancher}, {rke} or {lh}, make sure to check the support matrix for the related solutions you want to use:
+IMPORTANT: If you want to use different versions of {slem} or {slm}, {rancher}, {rke} or {lh}, make sure to check the support matrix for the related solutions you want to use:
 https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/ +
-For {redis} and {pg}, make sure to pick versions compatible to {eic}, which can be found in https://me.sap.com/notes/3247839 . +
-Other versions of {metallb} or {cm} can be used but may have not been tested. 
+For {redis} and {pg}, make sure to pick versions compatible to {eic}, which can be found at https://me.sap.com/notes/3247839 . +
+Other versions of {metallb} or {cm} can be used, but they may not have been tested. 
 
 # end::disclaimer-production-versions[]
 
 
-
 # tag::self-signed-certificates[]
 
 [#selfSignedCertificates]
@@ -40,7 +39,7 @@ The following excerpt provides an example of how to create one with a passphrase
 $ openssl req -x509 -sha256 -days 1825 -newkey rsa:2048 -keyout rootCA.key -out rootCA.crt -passout pass:<ca-passphrase> -subj "/C=DE/ST=BW/L=Nuremberg/O=SUSE"
 ----
 
-This will give you the files `rootCA.key` and `rootCA.crt`.
+This will give you the files _rootCA.key_ and _rootCA.crt_.
 The server certificate requires a certificate signing request (hereinafter referred to as CSR).
 The following excerpt shows how to create such a CSR:
 

adoc/SAP-EIC-Harvester-main.adoc

@@ -73,7 +73,7 @@ include::SAP-EIC-General.adoc[tags=disclaimer-production-versions]
 ** {rancher4SAP} *
 ** {sle_ha} **
 
-+++*+++ The {rancher4SAP} subscription holds support for all required components like {slm}, {rancher} and {harvester}.
++++*+++ The {rancher4SAP} subscription includes support for all required components like {slm}, {rancher} and {harvester}.
 
 +++**+++ Only needed if you want to set up {rancher} in a high availability setup without the  {harvester} Load Balancer feature.
 
@@ -100,12 +100,12 @@ Additionally,
 
 == Landscape Overview
 
-To run {eic} in a production-ready and supported way, you need to set up multiple Kubernetes clusters and their nodes.
-Those comprise a Kubernetes cluster where you will install {rancher} to set up and manage the production and non-production clusters.
+To run {eic} in a production-ready and supported way, you need to set up multiple Kubernetes clusters and their respective nodes.
+These include a Kubernetes cluster where {rancher} is installed to set up and manage both production and non-production clusters.
 For this {rancher} cluster, we recommend using three Kubernetes nodes and a Load Balancer.
 
-When using {harvester} you can provision all virtual machines needed within our example landscape.
-While the VMs for the {rancher} cluster have to be created in {harvester} itself, the Kubernetes clusters and the related virtual machines can be created through {rancher}.
+When using {harvester}, you can provision all virtual machines required for the example landscape.
+While the VMs for the {rancher} cluster must be created directly in {harvester}, the Kubernetes clusters and the related virtual machines can be created through {rancher}.
 
 The {eic} will need to run in a dedicated Kubernetes cluster.
 For an HA setup of this cluster, we recommend using three Kubernetes control planes and three Kubernetes worker nodes.

adoc/SAP-EIC-Harvester.adoc

@@ -3,17 +3,20 @@
 
 // {harvester} is SUSE's hyper converged infrastructure solution //TODO
 # tag::harvester-intro[]
-{harvester} is an open-source hyperconverged infrastructure (HCI) software that simplifies the management of virtual machines (VMs) and containerized workloads on bare metal servers. This cloud-native virtualization platform leverages core open-source technologies like Linux, KVM (Kernel-based Virtual Machine), Kubernetes, KubeVirt, and Longhorn, offering a flexible and cost-effective alternative to traditional virtualization.
+{harvester} is an open-source hyperconverged infrastructure (HCI) software that simplifies the management of 
+virtual machines (VMs) and containerized workloads on bare metal servers. This cloud native virtualization platform leverages 
+core open source technologies like Linux, KVM (Kernel-based Virtual Machine), Kubernetes, KubeVirt, and Longhorn, 
+offering a flexible and cost-effective alternative to traditional virtualization.
 
 # end::harvester-intro[]
 
 
 # tag::harvester-setup[]
 === Setting up {harvester}
 
-Please follow the instructions on:
+Follow the instructions at the:
 link:https://docs.harvesterhci.io/v1.4/[official website for {harvester}]
-to get more information how to setup {harvester}.
+to get more information how to set up {harvester}.
 
 NOTE: Make sure you meet the hardware requirements specified in 
 https://docs.harvesterhci.io/v1.4/install/requirements
@@ -26,11 +29,11 @@ to set up your {harvester} environments.
 
 === Integrating {harvester} into {rancher}
 
-IMPORTANT: Make sure you checked the support matrix at and use a supported {rancher} version:
+IMPORTANT: Make sure you checked the support matrix and use a supported {rancher} version:
 https://www.suse.com/suse-harvester/support-matrix/all-supported-versions/harvester-v1-4-x/
 
 To benefit from the synergies {rancher} and {harvester} can create, you need to import your {harvester} in the {rancher} UI.
-To do so, follow the steps described at:
+To do so, follow the steps described here:
 link:https://docs.harvesterhci.io/v1.4/rancher/virtualization-management[Importing Harvester cluster]
 
 # end::harvester-rancher-integration[]
@@ -50,7 +53,7 @@ https://docs.harvesterhci.io/v1.4/vm/index
 
 === Uploading images to {harvester}
 
-To find information how to upload images to {harvester} that will be used to spin up virtual machines, please refer to:
+To find information how to upload images to {harvester} that will be used to spin up virtual machines, refer to:
 
 https://docs.harvesterhci.io/v1.4/image/upload-image
 
@@ -63,17 +66,17 @@ You can get an overview of the currently supported images at https://docs.harves
 # tag::harvester-kubernetes-storage[]
 
 A benefit of using {harvester} is the provisioning of storage to your Kubernetes clusters.
-If you create a cluster as described in xref:SAP-Rancher-RKE2-Installation.adoc#installRKE2Harvester[the previous chapter], a storageClass will automatically be created within your Kubernetes cluster.
+If you create a cluster as described in xref:SAP-Rancher-RKE2-Installation.adoc#installRKE2Harvester[the previous chapter], a _storageClass_ will automatically be created within your Kubernetes cluster.
 
 # end::harvester-kubernetes-storage[]
 
 
 # tag::harvester-lb[]
 
-You can use {harvester} to create a guest Kubernetes cluster load balancer as also described at 
+You can use {harvester} to create a guest Kubernetes cluster load balancer, as also described at 
 https://docs.harvesterhci.io/v1.4/networking/loadbalancer#guest-kubernetes-cluster-load-balancer
 and
-https://docs.harvesterhci.io/v1.4/rancher/cloud-provider/#load-balancer-support .
+https://docs.harvesterhci.io/v1.4/rancher/cloud-provider/#load-balancer-support.
 
 
 # end::harvester-lb[]
@@ -82,22 +85,20 @@ https://docs.harvesterhci.io/v1.4/rancher/cloud-provider/#load-balancer-support
 
 == Creating an IP Pool in {harvester}
 
-To create an IP Pool, login to your {harvester} instance and go to *Networks -> IP Pools*.
-Click on *Create* in the upper right corner to create a new IP Pool:
+To create an IP Pool, log in to your {harvester} instance and go to *Networks -> IP Pools*.
+Click *Create* in the upper right corner to create a new IP Pool:
 
-image::SAP-EIC-Harvester-IPPool-Empty.png[scaledwidth=99%,opts=inline,Embedded]
+image::SAP-EIC-Harvester-IPPool-Empty.png[titel=Create a new IP Pool,scaledwidth=99%,opts=inline,Embedded]
 
-++++
-<?pdfpagebreak?>
-++++
 
-On the next screen, you should see a menu like this:
 
-image::SAP-EIC-Harvester-IPPool-Create.png[scaledwidth=99%,opts=inline,Embedded]
+On the next screen, you should see a menu similar to this:
 
-Click on *Edit as YAML* and adjust the IP Pool to your needs.
+image::SAP-EIC-Harvester-IPPool-Create.png[Create IP Pool Menu,scaledwidth=99%,opts=inline,Embedded]
 
-Here's an example for such an IP Pool:
+Click *Edit as YAML* and adjust the IP Pool to your needs.
+
+Find an example for an IP Pool below:
 
 [source, yaml]
 ----
@@ -120,17 +121,14 @@ spec:
       type: range
 ----
 
-When you're done, click the *Create* button at the bottom right.
+When you are done, click the *Create* button at the bottom right.
 
-image::SAP-EIC-Harvester-IPPool-Example.png[scaledwidth=99%,opts=inline,Embedded]
+image::SAP-EIC-Harvester-IPPool-Example.png[title=IP Pool Example,scaledwidth=99%,opts=inline,Embedded]
 
-++++
-<?pdfpagebreak?>
-++++
 
-At this point your IP Pool should have been created and show up in list of IP Pools:
+At this stage, your IP Pool should have been created and appear in the list of IP Pools.
 
-image::SAP-EIC-Harvester-IPPool.png[scaledwidth=99%,opts=inline,Embedded]
+image::SAP-EIC-Harvester-IPPool.png[title=List of IP Pools,scaledwidth=99%,opts=inline,Embedded]
 
 # end::harvester-ippool[]
 
@@ -148,29 +146,24 @@ If your management network is not managed by a DHCP, your first step would be to
 
 # tag::rancher-harvester-lb-config[]
 
-To create a Load Balancer, login to your {harvester} instance and go to *Networks -> Load Balancers*.
-Click on *Create* in the upper right corner to create a new Load Balancer:
+To create a Load Balancer, log in to your {harvester} instance and go to *Networks -> Load Balancers*.
+Click *Create* in the upper right corner to create a new Load Balancer:
 
-image::SAP-EIC-Harvester-LB-Empty.png[scaledwidth=99%,opts=inline,Embedded]
+image::SAP-EIC-Harvester-LB-Empty.png[title=Create New Load Balancer,scaledwidth=99%,opts=inline,Embedded]
 
-++++
-<?pdfpagebreak?>
-++++
 
-On the next screen, you should see a menu like this:
+On the next screen, you should see a menu similar to this:
 
-image::SAP-EIC-Harvester-LB-Create.png[scaledwidth=99%,opts=inline,Embedded]
+image::SAP-EIC-Harvester-LB-Create.png[title=CreateLoad Balancer Menu,scaledwidth=99%,opts=inline,Embedded]
 
 Select the IPAM method you want to use - either DHCP or Pool.
 
 // TODO image
 
-++++
-<?pdfpagebreak?>
-++++
 
-Next configure the *Listeners*. The *Port* is the port on which the Load Balancer will listen for requests. The *Backend Port* will be the port of the target virtual machine the traffic is forwarded to.
-If you want to use this Load Balancer to forward traffic to a {rancher} management cluster, you'd need to configure two listeners:
+Next, configure the *Listeners*. The *Port* is the port on which the Load Balancer will listen for requests. 
+The *Backend Port* is the port of the target virtual machine the traffic is forwarded to.
+If you want to use this Load Balancer to forward traffic to a {rancher} management cluster, you need to configure two listeners:
 
 [options="header"]
 |===
@@ -179,18 +172,14 @@ If you want to use this Load Balancer to forward traffic to a {rancher} manageme
 |https|TCP|443|443
 |===
 
-image::SAP-EIC-Harvester-LB-Listeners.png[scaledwidth=99%,opts=inline,Embedded]
-
+image::SAP-EIC-Harvester-LB-Listeners.png[title=Configuring Load Balancer Listeners,scaledwidth=99%,opts=inline,Embedded]
 
-++++
-<?pdfpagebreak?>
-++++
 
 The next step is to configure the *Backend Server Selector*.
-Here you'll configure which virtual machines are getting addressed by the Load Balancer.
+Here you will specify which virtual machines the Load Balancer will target.
 Therefore the *Key* and *Value* must match the *Instance Labels* of the target virtual machines.
 
-image::SAP-EIC-Harvester-LB-Selector.png[scaledwidth=99%,opts=inline,Embedded]
+image::SAP-EIC-Harvester-LB-Selector.png[title=Load Balancer Backend Server Selector,scaledwidth=99%,opts=inline,Embedded]
 
 
 

adoc/SAP-EIC-Main.adoc

@@ -28,7 +28,7 @@ include::SAP-EIC-General.adoc[tags=disclaimer-EIC-sizing;disclaimer-annotation]
 
 == Supported and used versions
 
-The support matrix below shows which versions of the given software we'll use in this guide.
+The support matrix below shows which versions of the given software we will use in this guide.
 
 [cols="1,1"]
 |===
@@ -91,7 +91,7 @@ For an HA setup of this cluster, we recommend using three Kubernetes control pla
 
 For a graphical overview of what is needed, take a look at the landscape overview:
 
-image::SAP-EIC-Architecture.svg[scaledwidth=99%,opts=inline,Embedded]
+image::SAP-EIC-Architecture.svg[title=Architecture Overview,scaledwidth=99%,opts=inline,Embedded]
 
 * The dark blue rectangles represent Kubernetes clusters.
 * The olive rectangles represent Kubernetes nodes that hold the roles of Control Plane and Worker combined.
@@ -122,7 +122,7 @@ By now you should have installed the operating system on every Kubernetes node.
 You are now ready to install a {rancher} cluster.
 Taking a look again on the landscape overview, this means, we will now cover how to set up the upper part of the given graphic:
 
-image::SAP-EIC-Architecture-Rancher.svg[scaledwidth=99%,opts=inline,Embedded]
+image::SAP-EIC-Architecture-Rancher.svg[title=Architecture SUSE Rancher Prime,scaledwidth=99%,opts=inline,Embedded]
 
 include::SAP-K8s-HA.adoc[tags=**]
 
@@ -139,18 +139,12 @@ SAP recommends to set up not only a production landscape, but to have  QA / Dev
 How to do this is covered in this chapter.
 Looking at the landscape overview again, we will now deal with setting up the lower part of the given graphic:
 
-image::SAP-EIC-Architecture-RKE2.svg[scaledwidth=99%,opts=inline,Embedded]
-
-++++
-<?pdfpagebreak?>
-++++
+image::SAP-EIC-Architecture-RKE2.svg[title=Architecture Overview RKE2,scaledwidth=99%,opts=inline,Embedded]
 
 
 include::SAP-Rancher-RKE2-Installation.adoc[tags=!install-rke2-harvester]
 
-++++
-<?pdfpagebreak?>
-++++
+
 
 include::SAPDI3-Longhorn.adoc[]
 
@@ -171,7 +165,7 @@ The easiest way to do so is to use the built-in shell in {rancher}. To access it
 
 image::EIC-Rancher-Kubectl-Button.png[title=Rancher Shell Access,scaledwidth=99%]
 
-A shell will open as shown in the image:
+A shell will open as shown in the image below:
 
 image::EIC-Rancher-Kubectl-Shell.png[title=Rancher Shell Overview,scaledwidth=99%]
 
@@ -183,18 +177,13 @@ You must log in to {rac}. This can be done as follows:
 $ helm registry login dp.apps.rancher.io/charts -u <yourUser> -p <your-token>
 ----
 
-++++
-<?pdfpagebreak?>
-++++
 
 === Installing {metallb}
 
 This chapter is intended to guide you through installing and configuring {metallb} on your Kubernetes cluster used for {eic}.
 
 include::SAP-EIC-Metallb.adoc[Metallb, leveloffset=2]
-++++
-<?pdfpagebreak?>
-++++
+
 
 === Installing {redis}
 
@@ -210,9 +199,6 @@ https://redis.io/docs/management/persistence/.
 
 include::SAP-EIC-Redis.adoc[leveloffset=2]
 
-++++
-<?pdfpagebreak?>
-++++
 
 === Installing {pg}
 
@@ -242,9 +228,8 @@ to install {eic} in your prepared environments.
 == Appendix
 
 include::SAP-EIC-ImagePullSecrets.adoc[leveloffset=+2]
-++++
-<?pdfpagebreak?>
-++++
+
+
 include::SAP-EIC-LoginRegistryApplicationCollection.adoc[tags=general-login;eic-reference,leveloffset=+2]
 
 === Using self-signed certificates

adoc/SAP-EIC-Redis.adoc

@@ -6,7 +6,7 @@
 
 IMPORTANT::
 SUSE does not offer database support for {redis}.
-For support requests contact link:https://redis.com/[Redis Ltd.].
+For support requests, contact link:https://redis.com/[Redis Ltd.].
 
 
 IMPORTANT::
@@ -21,10 +21,6 @@ instead of link:https://redis.io/docs/management/scaling/[{redis} Cluster].
 Although {redis} is available for deployment using the {rancher} Apps, we recommend using the {rac}.
 The {redis} chart can be found at https://apps.rancher.io/applications/redis.
 
-++++
-<?pdfpagebreak?>
-++++
-
 
 === Deploying the chart
 

adoc/SAP-K8s-HA.adoc

@@ -1,6 +1,6 @@
 # tag::rancher-haproxy-preps[]
 === Preparation
-To have a highly available {rancher} setup, you need a load balancer for your {rancher} nodes.
+To provide a highly available {rancher} setup, you need a load balancer for your {rancher} nodes.
 If you already have a load balancer, you can use that to make {rancher} highly available.
 
 If you do not plan to set up a highly available {rancher} cluster, you can skip this section.