Fixed wording, punctuation, grammar

Small changes according to doc style guide.

Author: chabowski

adoc/SAP-EIC-General.adoc

@@ -16,7 +16,7 @@ $ means that the command can be run by any user.
 
 
 # tag::disclaimer-production-versions[]
-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:
+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 at https://me.sap.com/notes/3247839 . +
 Other versions of {metallb} or {cm} can be used, but they may not have been tested. 
@@ -32,14 +32,14 @@ Other versions of {metallb} or {cm} can be used, but they may not have been test
 WARNING: We strongly advise against using self-signed certificates in production environments.
 
 The first step is to create a certificate authority (hereinafter referred to as CA) with a key and certificate.
-The following excerpt provides an example of how to create one with a passphrase of your choice:
+The following excerpt provides an example of how to create a CA with a passphrase of your choice:
 
 [source, bash]
 ----
 $ 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 generate 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:
 
@@ -68,11 +68,11 @@ The example below shows how to do that by passing the extension file (here calle
 $ openssl x509 -req -CA rootCA.crt -CAkey rootCA.key -in domain.csr -out server.pem -days 365 -CAcreateserial -extfile domain.ext -passin pass:<ca-passphrase>
 ----
 
-This creates a file called _server.pem_ which is your certificate to be used for your application.
+This creates a file called _server.pem_, which is the certificate to be used for your application.
 
 
 Your _domain.key_ is still encrypted at this point, but the application requires an unencrypted server key.
-To decrypt, run the given command which will create the _server.key_.
+To decrypt it, run the provided command, which will generate the _server.key_.
 [source, bash]
 ----
 $ openssl rsa -passin pass:<csr-passphrase> -in domain.key -out server.key
@@ -91,7 +91,7 @@ $ cat server.pem rootCA.crt > chained.pem
 
 # tag::k8s-upload-certificates[]
 
-To use certificate files in Kubernetes, you need to save them as so-called *Secrets*.
+To use certificate files in Kubernetes, you need to save them as so-called *secrets*.
 For an example of uploading your certificates to Kubernetes, see the following excerpt:
 
 [source, bash]
@@ -106,7 +106,8 @@ NOTE: All applications are expecting to have the secret to be used in the same n
 
 # tag::use-cert-manager[]
 
-`cert-manager` needs to be available in your Downstream Cluster. To install `cert-manager` in your downstream cluster, you can use the same installation steps that are described in the Rancher Prime installation section.
+`cert-manager` needs to be available in your Downstream Cluster. To install `cert-manager` in your downstream cluster, 
+you can follow the same installation steps outlined in the Rancher Prime installation section.
 First,  create a _selfsigned-issuer.yaml_ file:
 
 [source,yaml]
@@ -180,6 +181,6 @@ $ kubectl apply -f application-name-certificate.yaml
 ----
 
 When you deploy your applications via Helm Charts, you can use the generated certificate. 
-In the Kubernetes Secret Certificate, three files are stored. These are the file _tls.crt_, _tls.key_ and _ca.crt_ which you cann use in the _values.yaml_ file of your application.
+In the Kubernetes Secret Certificate, three files are stored. These are the files _tls.crt_, _tls.key_ and _ca.crt_, which you can use in the _values.yaml_ file of your application.
 
 # end::use-cert-manager[]