Cont. (#2836)

modules/client-configuration/pages/autoinst-owngpgkey.adoc

@@ -10,7 +10,7 @@ A safer alternative is to provide your own GPG key.
 This technique applies to {suse} clients only.
 ====
 
-.Procedure: Include your own GPG key
+.Procedure: Include Your Own GPG Key
 . Create a GPG key.
 . Use it to sign the package's metadata.
 . Add it to the initial RAM disk of your installation media.
@@ -35,8 +35,6 @@ For already onboarded clients that use those repositories, the workaround is to
 The initial RAM disk ([path]``initrd``) used by PXE boot process normally contains {suse}'s GPG key only.
 You must add our own key to this file, so it can be used to check the packages.
 
-
-
 .Procedure: Add a GPG key to the initial RAM disk
 . Create a directory with a path identical to the one that is used during the boot process to find the GPG key:
 +
@@ -58,13 +56,11 @@ find . | cpio -o -H newc | xz --check=crc32 -c >> /path/to/initrd
 
 
 [[gpg-key-cdrom]]
-== Own GPG key in a CD-ROM
+== Own GPG Key in a CD-ROM
 
 You can modify an installation image with the [command]``mksusecd`` utility.
 This utility is contained in the Development Tools module.
 
-
-
 .Procedure: Add a GPG key to an Installation ISO image
 . Create a directory with a path identical to the one that is used during the boot process to find the GPG key:
 +

modules/client-configuration/pages/autoinst-profiles.adoc

@@ -134,7 +134,7 @@ For information about Yomi, see xref:specialized-guides:salt/salt-yomi.adoc[Inst
 
 
 [[kickstart]]
-== Kickstart profiles
+== Kickstart Profiles
 
 {kickstart} profiles offer a large number of configuration options.
 To create these profiles, you can upload them, or use a dedicated wizard.
@@ -144,7 +144,7 @@ If you have many custom configuration files located on a client you want to rein
 
 
 
-.Procedure: Creating a file preservation list
+.Procedure: Creating a File Preservation List
 
 . In the {productname} {webui}, navigate to menu:Systems[Autoinstallation > File Preservation] and click btn:[Create File Preservation List].
 
@@ -168,7 +168,7 @@ For more information about Kickstart, see the Red Hat documentation.
 
 
 [[templates-syntax]]
-== Templates syntax
+== Templates Syntax
 
 Parts of your installation file are replaced during the installation.
 Variables are replaced with single values, and code snippets are replaced with whole sections of text.
@@ -217,7 +217,7 @@ System variables take precedence over profile variables, which in turn take prec
 
 
 [[code-snippets]]
-=== Code snippets
+=== Code Snippets
 
 {productname} comes with a large number of predefined code snippets.
 Navigate to menu:Systems[Autoinstallation > Autoinstallation Snippets] to see the list of existing snippets.

modules/client-configuration/pages/autoinst-unattended.adoc

@@ -18,8 +18,6 @@ For information about declaring systems with the API, see xref:client-configurat
 When you have the bare metal provisioning option enabled, any client connected to the {productname} network is automatically added to the organization as soon as it is powered on.
 When this operation is complete, the client is shut down, and it appears in the [guimenu]``Systems`` list, ready to be installed.
 
-
-
 .Procedure: Enable the Bare Metal Functionality
 . In the {productname} {webui}, navigate to menu:Admin[Manager Configuration > Bare-metal systems].
 . Click btn:[Enable adding to this organization].
@@ -36,9 +34,7 @@ This also applies to mixed sets that include systems registered that way.
 All features become available to the set when all the clients in the set have been provisioned.
 For more information on SSM, see xref:client-configuration:system-set-manager.adoc[].
 
-
-
-.Procedure: Provision "Bootstrap" Type clients
+.Procedure: Provision "Bootstrap" Type Clients
 . In the {productname} {webui}, navigate to [guimenu]``Systems``, select the client to provision, and go to the menu:Provisioning[Autoinstallation] tab.
 . Select the {ay} profile to use, and click btn:[Create PXE installation configuration].
   This option creates a system entry at {cobbler}.
@@ -53,8 +49,6 @@ The server uses TFTP to provision the new client, so the appropriate port and ne
 You can use an API call to declare an association between a client identified by its MAC address and an autoinstallation profile.
 Next time the system reboots, it starts the installation based on the specified profile.
 
-
-
 .Procedure: Reinstallation From a Manually Declared Profile
 
 . On the {productname} Server, at the command prompt, use the [systemitem]``system.createSystemRecord`` API call.

modules/client-configuration/pages/vhm-aws.adoc

@@ -1,5 +1,5 @@
 [[vhm-aws]]
-= VHM and Amazon Web Services
+= Virtual Host Manager and Amazon Web Services
 
 You can use a virtual host manager (VHM) to gather instances from Amazon Web Services (AWS).
 

modules/client-configuration/pages/vhm-azure.adoc

@@ -1,5 +1,5 @@
 [[vhm-azure]]
-= VHM and Azure
+= Virtual Host Manager and Azure
 
 You can use a virtual host manager (VHM) to gather instances from Microsoft Azure.
 

modules/client-configuration/pages/vhm-gce.adoc

@@ -1,5 +1,5 @@
 [[vhm-hce]]
-= VHM and Google Compute Engine
+= Virtual Host Manager and Google Compute Engine
 
 You can use a virtual host manager (VHM) to gather instances from Google Compute Engine (GCE).
 

modules/client-configuration/pages/virt-xenkvm.adoc

@@ -22,7 +22,7 @@ The [systemitem]``Virtualization Host`` formula will help you with initializing
 For more information, see xref:client-configuration:virt-xenkvm.adoc#virt-xenkvm-host-formula[].
 
 
-=== Background information
+=== Background Information
 
 {productname} uses [systemitem]``libvirt`` to install and manage guests.
 You must have the [package]``libvirt-daemon`` package installed on your host.
@@ -62,25 +62,20 @@ systemctl restart salt-minion
 
 
 
-
 [[virt-xenkvm-autoinst]]
 == Autoinstall VM Guests
 
 You can use {ay} or {kickstart} to automatically install and register Xen and KVM guests.
 
 You need an activation key for the VM host you want to register the guests to, and for each guest.
 The activation key must have the [systemitem]``provisioning`` and [systemitem]``Virtualization Platform`` entitlements.
-// FIXME: Does Salt require sth special?
 For more information about creating activation keys, see xref:client-configuration:activation-keys.adoc[].
 
 If you want to automatically register the guests with {productname} after installation, you need to create a bootstrap script.
 For more information about creating a bootstrap script, see xref:client-configuration:registration-bootstrap.adoc[].
 
 
 
-
-
-
 === Create an Autoinstallable Distribution
 
 You need to create an autoinstallable distribution on the VM host to be able to autoinstall clients from {productname}.
@@ -91,11 +86,11 @@ The packages for a {rhel} installation are fetched from the associated base chan
 Packages for installing {suse} systems are fetched from the autoinstallable distribution.
 Therefore, for {suse} systems, the autoinstallable distribution must be a complete installation source.
 
-.Paths for autoinstallable distributions
+.Paths for Autoinstallable Distributions
 [cols="1,1,1", options="header"]
 |===
 
-| Operating System Type | Kernel Location | initrd Location
+| Operating System Type | Kernel Location | [literal]``initrd`` Location
 | {rhel} | [path]``images/pxeboot/vmlinuz``    | [path]``images/pxeboot/initrd.img``
 | {suse} | [path]``boot/<arch>/loader/initrd`` | [path]``boot/<arch>/loader/linux``
 |===

modules/client-configuration/pages/virtualization.adoc

@@ -68,7 +68,7 @@ You can add virtual guests to your virtualization hosts within the {productname}
 
 You can add virtual guests on a pacemaker cluster within the {productname} {webui}, too.
 
-.Procedure: Creating a cluster managed Virtual Guest
+.Procedure: Creating a Cluster Managed Virtual Guest
 . Follow the ``Creating a Virtual Guest`` procedure on one of the nodes of the cluster with the following additions:
 +
 * Ensure the [guimenu]``Define as a cluster resource`` field is checked.