Review abstracts and headings in Managing hosts

guides/common/assembly_administering-hosts.adoc

@@ -1,10 +1,10 @@
 :_mod-docs-content-type: ASSEMBLY
 
-include::modules/con_administering-hosts.adoc[]
+include::modules/con_administering-hosts-in-project.adoc[]
 
-include::modules/con_browsing-hosts-in-web-ui.adoc[leveloffset=+1]
+include::modules/proc_browsing-hosts-in-web-ui.adoc[leveloffset=+1]
 
-include::modules/proc_cloning-hosts.adoc[leveloffset=+1]
+include::modules/proc_cloning-hosts-in-project.adoc[leveloffset=+1]
 
 include::modules/proc_associating-a-virtual-machine-from-a-hypervisor.adoc[leveloffset=+1]
 
@@ -42,7 +42,7 @@
 
 include::modules/proc_removing-a-host-from-server-by-using-cli.adoc[leveloffset=+1]
 
-include::modules/proc_disassociating-a-virtual-machine-without-removing-it-from-a-hypervisor.adoc[leveloffset=+1]
+include::modules/proc_disassociating-a-vm-from-project-without-removing-it-from-a-hypervisor.adoc[leveloffset=+1]
 
 ifndef::satellite[]
 include::modules/proc_installing-the-snapshot-management-plugin.adoc[leveloffset=+1]

guides/common/assembly_configuring-host-collections.adoc

@@ -32,7 +32,7 @@ include::modules/proc_removing-a-package-from-a-host.adoc[leveloffset=+2]
 
 include::modules/proc_adding-errata-to-a-host-collection.adoc[leveloffset=+2]
 
-include::modules/proc_adding-errata-to-a-host.adoc[leveloffset=+2]
+include::modules/proc_adding-errata-to-a-single-host.adoc[leveloffset=+2]
 
 include::modules/proc_applying-errata-to-hosts-by-using-web-ui.adoc[leveloffset=+2]
 

guides/common/assembly_managing-packages.adoc

@@ -1,6 +1,6 @@
 :_mod-docs-content-type: ASSEMBLY
 
-include::modules/con_managing-packages.adoc[]
+include::modules/con_managing-packages-in-project.adoc[]
 
 include::modules/proc_enabling-and-disabling-repositories-on-hosts.adoc[leveloffset=+1]
 

guides/common/assembly_monitoring-hosts-by-using-insights-in-project.adoc

@@ -19,9 +19,9 @@ include::modules/proc_examining-recommendations-for-hosts.adoc[leveloffset=+1]
 
 include::modules/proc_remediating-issues-based-on-insights-recommendations.adoc[leveloffset=+1]
 
-include::modules/proc_disabling-recommendations.adoc[leveloffset=+1]
+include::modules/proc_disabling-recommendations-in-project.adoc[leveloffset=+1]
 
-include::modules/proc_enabling-recommendations.adoc[leveloffset=+1]
+include::modules/proc_enabling-recommendations-in-project.adoc[leveloffset=+1]
 
 include::modules/proc_examining-vulnerability-of-hosts.adoc[leveloffset=+1]
 

guides/common/assembly_registering-hosts.adoc

@@ -5,7 +5,7 @@ include::modules/con_registering-hosts-and-setting-up-host-integration.adoc[]
 include::modules/ref_supported-clients-in-registration.adoc[leveloffset=+1]
 
 ifdef::satellite,orcharhino[]
-include::modules/ref_registration-methods.adoc[leveloffset=+1]
+include::modules/ref_host-registration-methods.adoc[leveloffset=+1]
 endif::[]
 
 // Global registration

guides/common/assembly_template-writing-reference.adoc

@@ -12,14 +12,14 @@ include::modules/ref_troubleshooting-erb-templates.adoc[leveloffset=+1]
 
 include::modules/ref_generic-project-specific-macros.adoc[leveloffset=+1]
 
-include::modules/ref_template-macros.adoc[leveloffset=+1]
+include::modules/ref_template-macros-reference.adoc[leveloffset=+1]
 
-include::modules/ref_host-specific-variables.adoc[leveloffset=+1]
+include::modules/ref_host-specific-variables-in-templates.adoc[leveloffset=+1]
 
 include::modules/ref_kickstart-specific-variables.adoc[leveloffset=+1]
 
-include::modules/ref_conditional-statements.adoc[leveloffset=+1]
+include::modules/ref_conditional-statements-in-erb.adoc[leveloffset=+1]
 
-include::modules/proc_parsing-arrays.adoc[leveloffset=+1]
+include::modules/proc_parsing-arrays-in-templates.adoc[leveloffset=+1]
 
 include::modules/ref_example-template-snippets.adoc[leveloffset=+1]

guides/common/assembly_using-kernelcare.adoc

@@ -5,7 +5,7 @@ include::modules/con_using-the-kernelcare-plugin.adoc[]
 include::modules/proc_installing-the-kernelcare-plugin.adoc[leveloffset=+1]
 
 ifdef::katello,orcharhino[]
-include::modules/con_kernelcare-client.adoc[leveloffset=+1]
+include::modules/con_kernelcare-client-overview.adoc[leveloffset=+1]
 
 include::modules/ref_kernelcare-client-repositories.adoc[leveloffset=+1]
 endif::[]

guides/common/modules/con_adding-content-to-a-host-collection.adoc

@@ -4,4 +4,4 @@
 = Adding content to a host collection
 
 [role="_abstract"]
-These steps show how to add content to host collections in {ProjectName}.
+You can add content to host collections in {Project} so that you can install packages, apply errata, or manage other content across all hosts in the collection.

guides/common/modules/con_administering-hosts-in-project.adoc

@@ -0,0 +1,7 @@
+:_mod-docs-content-type: CONCEPT
+
+[id="administering-hosts-in-{project-context}"]
+= Administering hosts in {Project}
+
+[role="_abstract"]
+Create, register, administer, and remove hosts in {Project} to manage your infrastructure from a single place.

guides/common/modules/con_configuring-host-collections.adoc

@@ -4,7 +4,6 @@
 = Configuring host collections
 
 [role="_abstract"]
-A host collection in {Project} is a group of hosts.
-With host collections, you can perform the same action on multiple hosts at once.
-These actions include installing, removing, and updating packages, applying errata, and assigning content view environments.
+You can use host collections in {Project} to group hosts and perform the same action on multiple hosts at once.
+Actions include installing, removing, and updating packages, applying errata, and assigning content view environments.
 For example, you can use host collections to group hosts by function, department, or business unit.

guides/common/modules/con_configuring-network-interfaces.adoc

@@ -5,7 +5,7 @@
 
 [role="_abstract"]
 {Project} supports specifying multiple network interfaces for a single host.
-You can configure these interfaces when creating a new host or when editing an existing host.
+This lets you add physical, virtual, bonded, bridge, or BMC interfaces as needed for your network layout.
 
 There are several types of network interfaces that you can attach to a host.
 When configuring an interface, select one of:

guides/common/modules/con_converting-hosts-to-rhel.adoc

@@ -4,4 +4,5 @@
 = Converting hosts to {RHEL}
 
 [role="_abstract"]
-You can convert {RHEL} derivative distributions into a supportable {RHEL} on a host while retaining installed applications and configurations.
+You can convert {RHEL} derivative distributions, such as CentOS or Oracle Linux, to supported {RHEL} on a host while retaining installed applications and configurations.
+This helps you move your hosts to {RHEL} without a full reinstall.

guides/common/modules/con_host-global-status-overview.adoc

@@ -4,11 +4,12 @@
 = Host global status overview
 
 [role="_abstract"]
-The global status represents the overall status of a particular host.
+You can use the host global status in {Project} to see at a glance whether a host is OK, needs attention (Warning), or has errors.
+The status appears on the Hosts Overview page and helps you prioritize which hosts to investigate.
 
-The status can have one of three possible values: *OK*, *Warning*, or *Error*.
+The host global status can have one of three possible values: *OK*, *Warning*, or *Error*.
 You can find global status on the Hosts Overview page.
-The status displays a small icon next to host name and has a color that corresponds with the status.
+The status displays a small icon next to the host name and has a color that corresponds with the status.
 Hovering over the icon renders a tooltip with sub-status information to quickly find out more details.
 To view the global status for a host, in the {ProjectWebUI}, navigate to *Hosts* > *All Hosts*.
 

guides/common/modules/con_host-groups-overview.adoc

@@ -4,7 +4,8 @@
 = Host groups overview
 
 [role="_abstract"]
-A host group acts as a template for common host settings.
+You can use host groups in {Project} as templates for common host settings.
+Define the settings once and apply them to multiple hosts instead of configuring each host individually.
 
 ifdef::katello,orcharhino,satellite[]
 With host groups, you can define many settings for hosts, such as lifecycle environment, content view, or Ansible roles that are available to the hosts.

guides/common/modules/con_host-management-and-monitoring-by-using-cockpit.adoc

@@ -4,7 +4,5 @@
 = Host management and monitoring by using {the-Cockpit}
 
 [role="_abstract"]
-You can use the {Cockpit} interactive web interface to perform actions and monitor {EL} hosts.
-You can enable a remote-execution feature to integrate {Project} with {the-Cockpit}.
-When you install {the-Cockpit} on a host that you manage with {Project}, you can view the {Cockpit} dashboards of that host from within the {ProjectWebUI}.
-You can also use the features that are integrated with {the-Cockpit}, for example, {LoraxCompose}.
+You can use the {Cockpit} web interface to perform actions and monitor {EL} hosts.
+Enable {Cockpit} integration in {Project} to view host dashboards and use {Cockpit} features, such as {LoraxCompose}, from within the {ProjectWebUI}.

guides/common/modules/con_host-substatus-overview.adoc

@@ -4,14 +4,15 @@
 = Host sub-status overview
 
 [role="_abstract"]
-A sub-status monitors only a part of a host's capabilities.
+You can use host sub-statuses in {Project} to see the status of specific areas of a host, such as configuration, build, or content.
+Sub-statuses feed into the global host status and help you pinpoint what needs attention.
 
 To view the sub-statuses of a host, in the {ProjectWebUI}, navigate to *Hosts* > *All Hosts* and click on the host whose full status you want to inspect.
 You can view the global host status next to the name of the host and the host sub-statuses on the *Host status* card.
 
 Each sub-status has its own set of possible values that are mapped to the three global status values.
 
-Below are listed sub-statuses that {Project} contains.
+The following sub-statuses are available in {Project}:
 ifdef::foreman-el,foreman-deb,katello[]
 There can be more sub-statuses depending on which plugins you add to your {Project}.
 endif::[]

guides/common/modules/con_job-template-examples-and-extensions.adoc

@@ -4,4 +4,4 @@
 = Job template examples and extensions
 
 [role="_abstract"]
-Use this section as a reference to help modify, customize, and extend your job templates to suit your requirements.
+You can use these examples to modify, customize, and extend job templates for tasks such as restoring SELinux context, combining templates, or adding power actions.

guides/common/modules/con_kernelcare-client.adoc → guides/common/modules/con_kernelcare-client-overview.adoc

@@ -1,7 +1,7 @@
 :_mod-docs-content-type: CONCEPT
 
-[id="KernelCare_Client_{context}"]
-= KernelCare client
+[id="kernelcare-client-overview"]
+= KernelCare client overview
 
 [role="_abstract"]
 After installing the KernelCare plugin, you must provide the KernelCare client to your hosts.

guides/common/modules/con_managing-packages-in-project.adoc

@@ -0,0 +1,8 @@
+:_mod-docs-content-type: CONCEPT
+
+[id="managing-packages-in-{project-context}"]
+= Managing packages in {Project}
+
+[role="_abstract"]
+You can use {Project} to install, upgrade, and remove packages and to enable or disable repositories on hosts.
+Package actions use remote execution so you can manage host software from a central place.

guides/common/modules/con_nested-host-groups.adoc

@@ -4,7 +4,7 @@
 = Nested host groups
 
 [role="_abstract"]
-You can create a hierarchy of host groups.
+You can create a hierarchy of host groups so that child host groups inherit and override settings from parent host groups.
 
 Aim to have one base level host group that represents all hosts in your organization and provides general settings, and then nested groups that provide specific settings.
 

guides/common/modules/con_overview-of-the-conversion-process.adoc

@@ -4,7 +4,8 @@
 = Overview of the conversion process
 
 [role="_abstract"]
-{Project} provides *Convert2RHEL* utilities to simplify the conversion process.
+You can use the Convert2RHEL utilities in {Project} to convert CentOS or Oracle Linux hosts to {RHEL}.
+The process replaces packages with {RHEL} equivalents while retaining applications and configurations.
 
 The conversion process is similar to a minor release upgrade of {RHEL} in which every RPM package on the system is replaced.
 Third-party packages and non-Red Hat packages that are not available in {RHEL} are retained.

guides/common/modules/con_registering-hosts-by-using-global-registration.adoc

@@ -5,6 +5,7 @@
 
 [role="_abstract"]
 You can register a host to {Project} by generating a `curl` or `wget` command on {Project} and running this command on hosts.
+
 This method uses two provisioning templates: *Global Registration* template and *Linux host_init_config default* template.
 That gives you complete control over the host registration process.
 

guides/common/modules/con_remote-execution-workflow.adoc

@@ -4,7 +4,8 @@
 = Remote execution workflow
 
 [role="_abstract"]
-When you run a remote job on hosts, for every host, {Project} performs a series of actions to find a remote execution {SmartProxy} to use.
+When you run a remote job on hosts, {Project} selects a remote execution {SmartProxy} for each host by checking the host interfaces and subnets and balancing load across {SmartProxies}.
+Understanding this workflow helps you troubleshoot job routing or plan where to enable remote execution.
 
 For custom Ansible roles that you create, or roles that you download, you must install the package containing the roles on your {SmartProxyServer}.
 Before you can use Ansible roles, you must import the roles into {Project} from the {SmartProxy} where they are installed.

guides/common/modules/con_template-writing-reference.adoc

@@ -5,7 +5,7 @@
 
 [role="_abstract"]
 Embedded Ruby (ERB) is a tool for generating text files based on templates that combine plain text with Ruby code.
-This section provides an overview of {Project}-specific macros and variables that can be used in ERB templates along with some usage examples.
+You can use the following {Project}-specific macros and variables in your ERB templates.
 
 When provisioning a host or running a remote job, the code in the ERB is executed and the variables are replaced with the host specific values.
 This process is referred to as *rendering*.

guides/common/modules/con_transport-modes-for-remote-execution.adoc

@@ -4,10 +4,9 @@
 = Transport modes for remote execution
 
 [role="_abstract"]
-You can configure your {Project} to use two different modes of transport for remote job execution.
-
-The following transport modes are available for remote execution.
-You can configure single {SmartProxy} to use either one mode or the other but not both.
+You can configure {Project} to use push-based (SSH) or pull-based (MQTT) transport for remote job execution.
+Each {SmartProxy} uses one mode.
+Choose push for direct SSH to hosts or pull when hosts receive jobs via MQTT and HTTPS.
 
 Push-based transport::
 On {SmartProxies} in `ssh` mode, remote execution uses the SSH service to transport job details.

guides/common/modules/con_working-with-host-groups.adoc

@@ -4,4 +4,5 @@
 = Working with host groups
 
 [role="_abstract"]
-With {Project}, you can use host groups as a template for common host settings to apply these settings to multiple hosts.
+You can use host groups in {Project} as templates for common host settings and apply those settings to multiple hosts at once.
+This reduces repeated configuration when you manage many similar hosts.

guides/common/modules/proc_accessing-the-template-writing-reference.adoc

@@ -4,7 +4,7 @@
 = Accessing the template writing reference in the {ProjectWebUI}
 
 [role="_abstract"]
-You can access the template writing reference document in the {ProjectWebUI}.
+You can open the template writing reference from the {ProjectWebUI} to look up ERB macros, variables, and syntax when writing or editing provisioning templates, job templates, or report templates.
 
 .Procedure
 . Log in to the {ProjectWebUI}.

guides/common/modules/proc_adding-a-host-to-a-host-collection-by-using-web-ui.adoc

@@ -4,7 +4,7 @@
 = Adding a host to a host collection by using {ProjectWebUI}
 
 [role="_abstract"]
-You can add a host to a host collection in the {ProjectWebUI}.
+You can add a host to a host collection from the {ProjectWebUI}.
 
 Note that if you add a host to a host collection, the {Project} auditing system does not log the change.
 

guides/common/modules/proc_adding-a-host-to-a-host-group.adoc

@@ -4,7 +4,7 @@
 = Adding a host to a host group
 
 [role="_abstract"]
-You can add a host to a host group in the {ProjectWebUI}.
+You can add a host to a host group from the {ProjectWebUI} so that the host inherits the settings of the host group.
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Hosts* > *All Hosts*.

guides/common/modules/proc_adding-errata-to-a-host-collection.adoc

@@ -4,10 +4,10 @@
 = Adding errata to a host collection
 
 [role="_abstract"]
-The following procedure shows how to add errata to host collections.
+You can add errata to a host collection so that the errata are applied to all hosts in the collection in one action.
 
 .Prerequisites
-* The errata to be added should be available in one of the existing repositories or added prior to this procedure.
+* The errata to be added should be available in one of the existing repositories or added before this procedure.
 * Errata should be promoted to the environment where the hosts are assigned.
 
 .Procedure

guides/common/modules/proc_adding-errata-to-a-host.adoc → guides/common/modules/proc_adding-errata-to-a-single-host.adoc

@@ -1,10 +1,10 @@
 :_mod-docs-content-type: PROCEDURE
 
-[id="Adding_errata_to_a_single_host_{context}"]
+[id="adding-errata-to-a-single-host"]
 = Adding errata to a single host
 
 [role="_abstract"]
-Use the following procedure to add errata to a host.
+You can add errata to a host so that the host is updated with the errata.
 
 .Procedure
 . In the {ProjectWebUI}, navigate to *Hosts* > *All Hosts*.

guides/common/modules/proc_adding-hosts-to-a-host-collection-in-bulk-by-using-cli.adoc

@@ -4,7 +4,7 @@
 = Adding hosts to a host collection in bulk by using Hammer CLI
 
 [role="_abstract"]
-You can add multiple hosts to a host collection by using Hammer CLI.
+You can add multiple hosts to a host collection at once by using Hammer CLI.
 
 Note that if you add a host to a host collection, the {Project} auditing system does not log the change.
 

guides/common/modules/proc_adding-hosts-to-a-host-collection-in-bulk-by-using-web-ui.adoc

@@ -4,7 +4,7 @@
 = Adding hosts to a host collection in bulk by using {ProjectWebUI}
 
 [role="_abstract"]
-You can add multiple hosts to a host collection from {ProjectWebUI}.
+You can add multiple hosts to a host collection at once from the {ProjectWebUI}.
 
 Note that if you add a host to a host collection, the {Project} auditing system does not log the change.
 

guides/common/modules/proc_adding-packages-to-a-host-collection.adoc

@@ -4,10 +4,10 @@
 = Adding packages to a host collection
 
 [role="_abstract"]
-The following procedure shows how to add packages to host collections.
+You can add packages to a host collection so that the packages are installed on all hosts in the collection in one action.
 
 .Prerequisites
-* The content to be added should be available in one of the existing repositories or added prior to this procedure.
+* The content to be added should be available in one of the existing repositories or added before this procedure.
 * Content should be promoted to the environment where the hosts are assigned.
 
 .Procedure

guides/common/modules/proc_altering-the-privilege-elevation-method.adoc

@@ -5,7 +5,6 @@
 
 [role="_abstract"]
 By default, push-based remote execution uses `sudo` to switch from the SSH user to the effective user that executes the script on your host.
-In some situations, you might require to use another method, such as `su` or `dzdo`.
 You can globally configure an alternative method in your {Project} settings.
 
 .Prerequisites

guides/common/modules/proc_applying-errata-to-hosts-by-using-cli.adoc

@@ -4,7 +4,7 @@
 = Applying errata to hosts by using CLI
 
 [role="_abstract"]
-You can use Hammer CLI to review and apply errata to hosts.
+You can use Hammer CLI to review and apply errata to hosts so that security and bugfix updates are installed on selected hosts.
 
 .Procedure
 . List all errata: