Fixed style, grammar, format

According to doc review and style guide, fixed sub-section titles,
grammar, typos and some wording.

Author: chabowski

adoc/SAP-EIC-SLEMicro.adoc

@@ -1,25 +1,26 @@
 [#SLEMicro]
 
-=== Installation
+=== Installing and configuring {slem}
 
 On each server in your environment for {eic} and {rancher}, install {slem} {slem_version} as the operating system.
-There are several methods to install {slem} {slem_version} on your hardware or virtual machine. A list of all possible solutions are available in our Documentation  https://documentation.suse.com/sle-micro/{slem_version}/[SLE Micro 6.0]. 
+There are several methods to install {slem} {slem_version} on your hardware or virtual machine. 
+A list of all possible solutions are available in our Documentation  https://documentation.suse.com/sle-micro/{slem_version}/[SLE Micro 6.0]. 
 
-At the end of the installation process in the summary windows you need to check if these Security Settings are configured:
+At the end of the installation process, in the summary window, you need to verify that the following security settings are configured:
 
    ** The firewall will be disabled.
    ** The SSH service will be enabled.
    ** SELinux will be set in permissive mode.
 
-Set SELinux into _permissive_ mode, because otherwise, some components of the Edge Integration Cell violate SELinux rules, and the application will not work. 
+Set SELinux to _permissive_ mode, because otherwise, some components of the Edge Integration Cell will violate SELinux rules, and the application will not work. 
 
 
 TIP: If you have already set up all machines and the operating system, skip this chapter.
 
 === Registering your system
 
 To get your system up-to-date, you need to register it with SUSE Manager, an RMT server, or directly with the SCC Portal. 
-Find the registration process with a direct connection to SCC describedin the instructions below. For more information, see the {slem} documentation.
+Find the registration process with a direct connection to SCC described in the instructions below. For more information, see the {slem} documentation.
 
 Registering the system is possible from the command line using the `transactional-update register` command. 
 For information that goes beyond the scope of this section, refer to the inline documentation with *SUSEConnect --help*. 
@@ -61,21 +62,23 @@ $ systemctl --now disable transactional-update.timer
 ----
 
 === Preparing for {lh}
-For {lh} you need to do some preparation steps. First, install some additional packages on all worker nodes. Then attach a second disk to the worker nodes, create a file system on top of it and mount it to the Longhorn default location. The size of the second disk depends on your use case. 
+For {lh},  some preparation steps are required. First, install some additional packages on all worker nodes. 
+Then, attach a second disk to the worker nodes, create a file system on top of it, and mount it to the default {lh} location. 
+The size of the second disk will depend on your use case. 
 
-Install some packages as a requirement for longhorn and Logical Volume Management for adding a file system to Longhorn.
+Install some packages as a requirement for {lh} and Logical Volume Management for adding a file system to {lh}.
 [source, bash]
 ----
 $ transactional-update pkg install lvm2 jq nfs-client cryptsetup open-iscsi
 ----
 
-After the needed packages are installed, you need to reboot your machine. 
+After the required packages are installed, you need to reboot your machine. 
 [source, bash]
 ----
 $ reboot
 ----
 
-Now you can enable the _iscsid_ server.
+Now you can enable the `iscsid` server.
 
 [source, bash]
 ----
@@ -86,7 +89,7 @@ $ systemctl enable iscsid  --now
 
 The next step is to create a new logical volume with the Logical Volume Management. 
 
-First, you need to create a new physical volume. In our case the second disk is called _vdb_. Use this as longhorn volume.
+First, you need to create a new physical volume. In our case, the second disk is called _vdb_. Use this as {lh} volume.
 [source, bash]
 ----
 $ pvcreate /dev/vdb