Fix attribute usage for Client OS (#4176)

maximiliankolb · web-flow · commit bf958bb5235d · 2025-08-21T08:08:28.000+02:00
* Use client-os attribute for generic Client OS
* Bump Client OS example major and minor versions
* Use EL in favor for RHEL for Foreman platform
* Use EL in favor for RHEL for example EL syncs
* Use RHEL in favor of EL for Satellite disconnected
* Rephrase registering Foreman server by sub-man to RH
* Use RHEL attribute in favor of RHEL
* Use sentence-case for link titles
* Reword if you use the Katello plugin
* Use EL in favor for RHEL for example
* Use SLES attribute in favor of SUSE Linux Enterprise Server
* Clarify example Client OS for Ansible Playbook
* Do not use attribute for RHEL to match Repo IDs
* Reword a Enterprise Linux
diff --git a/guides/common/attributes-base.adoc b/guides/common/attributes-base.adoc
@@ -176,9 +176,9 @@
 :client-os-family: Red Hat
 :client-os: {EL}
 :client-os-context: enterprise-linux
-:client-os-major: 8
-:client-os-minor: 8
-:client-os-minor-bumped: 9
+:client-os-major: 9
+:client-os-minor: 5
+:client-os-minor-bumped: 6
 :client-package-install-deb: apt install
 :client-package-install-el7: yum install
 :client-package-install-el8: dnf install
diff --git a/guides/common/modules/con_aws-requirements.adoc b/guides/common/modules/con_aws-requirements.adoc
@@ -37,7 +37,7 @@ ifdef::satellite[]
 .Red Hat Cloud prerequisites
 * Register with Red Hat Cloud Access.
 * Migrate any Red Hat subscriptions that you want to use.
-* Create an AWS instance and deploy a {RHEL} virtual machine to the instance.
+* Create an AWS instance and deploy a virtual machine running {RHEL} to the instance.
 For more information about deploying {RHEL} in AWS, see https://access.redhat.com/articles/2962171[How to Locate Red Hat Cloud Access Gold Images on AWS EC2].
 * Ensure that your subscriptions are eligible for transfer to Red Hat Cloud.
 For more information, see https://www.redhat.com/en/technologies/cloud-computing/cloud-access#program-details[Red Hat Cloud Access Program Details].
diff --git a/guides/common/modules/con_composite-content-views-overview.adoc b/guides/common/modules/con_composite-content-views-overview.adoc
@@ -21,7 +21,7 @@ The _example_application_ appears as:
 
 Example of four separate content views:
 
-* {RHEL} (Operating System)
+* {client-os} (Operating System)
 * PostgreSQL (Database)
 * MariaDB (Database)
 * _example_software_ (Application)
@@ -35,7 +35,7 @@ Example composite content view for a PostgreSQL database:
 
 | _example_software_ (Application)
 | PostgreSQL (Database)
-| {RHEL} (Operating System)
+| {client-os} (Operating System)
 |===
 
 Example composite content view for a MariaDB:
@@ -45,7 +45,7 @@ Example composite content view for a MariaDB:
 
 | _example_software_ (Application)
 | MariaDB (Database)
-| {RHEL} (Operating System)
+| {client-os} (Operating System)
 |===
 
 Each content view is then managed and published separately.
diff --git a/guides/common/modules/con_content-filter-examples.adoc b/guides/common/modules/con_content-filter-examples.adoc
@@ -12,8 +12,8 @@ For example, if a content view publish task completes in a few minutes without f
 ====
 
 .Example 1
-Create a repository with the base {RHEL} packages.
-This filter requires a {RHEL} repository added to the content view.
+Create a repository with the base {client-os} packages.
+This filter requires a {client-os} repository added to the content view.
 
 *Filter:*
 
@@ -24,7 +24,7 @@ This filter requires a {RHEL} repository added to the content view.
 .Example 2
 Create a repository that excludes all errata, except for security updates, after a certain date.
 This is useful if you want to perform system updates on a regular basis with the exception of critical security updates, which must be applied immediately.
-This filter requires a {RHEL} repository added to the content view.
+This filter requires a {client-os} repository added to the content view.
 
 *Filter:*
 
@@ -55,6 +55,7 @@ Set the *Date Type* to *Updated On*.
 Set the *Start Date* to the date you want to restrict errata.
 Leave the *End Date* blank to ensure any new non-security errata is filtered.
 
+ifdef::client-content-dnf[]
 .Example 4
 Filter a specific module stream in a content view.
 
@@ -71,6 +72,7 @@ Filter a specific module stream in a content view.
 * *Filter:* Add a rule to filter any non-modular packages that you want to exclude from the content view.
 If you do not filter the packages, the content view filter includes all non-modular packages associated with the module stream *ant*.
 Add a rule to exclude all `*` packages, or specify the package names that you want to exclude.
+endif::[]
 
 ifndef::orcharhino[]
 For another example of how content filters work, see the following article: https://access.redhat.com/solutions/1564953["How do content filters work in Satellite 6"].
diff --git a/guides/common/modules/con_managing-errata.adoc b/guides/common/modules/con_managing-errata.adoc
@@ -9,7 +9,7 @@ Red Hat compiles groups of related packages into an *erratum* along with an advi
 endif::[]
 ifndef::satellite[]
 {RHEL} users receive errata for each release of official Red Hat RPMs.
-SUSE Linux Enterprise Server users receive errata for each release of official SUSE RPMs.
+{SLES} users receive errata for each release of official SUSE RPMs.
 endif::[]
 ifdef::orcharhino[]
 Additionally, ATIX provides errata for hosts running Debian, CentOS 7, or Ubuntu.
@@ -31,7 +31,7 @@ ifdef::satellite[]
 endif::[]
 ifndef::satellite[]
 For {RHEL}, {Project} imports errata information when synchronizing repositories with Red Hat's Content Delivery Network (CDN).
-For SUSE Linux Enterprise Server, {Project} imports errata information when synchronizing repositories with SUSE Customer Center.
+For {SLES}, {Project} imports errata information when synchronizing repositories with SUSE Customer Center.
 For AlmaLinux and Rocky Linux, {Project} imports errata information when synchronizing repositories with upstream repositories.
 endif::[]
 {ProjectName} also provides tools to inspect and filter errata, allowing for precise update management.
diff --git a/guides/common/modules/con_provisioning-cloud-instances-on-microsoft-azure-resource-manager.adoc b/guides/common/modules/con_provisioning-cloud-instances-on-microsoft-azure-resource-manager.adoc
@@ -19,4 +19,4 @@ For more information, see https://docs.microsoft.com/en-us/azure/active-director
 * Based on your needs, associate a `finish` or `user_data` provisioning template with the operating system you want to use.
 For more information about provisioning templates, see {ProvisioningDocURL}provisioning-templates[Provisioning Templates].
 * Optional: If you want the virtual machine to use a static private IP address, create a subnet in {Project} with the *Network Address* field matching the Azure subnet address.
-* Before creating RHEL BYOS images, you must accept the image terms either in the Azure CLI or Portal so that the image can be used to create and manage virtual machines for your subscription.
+* Before creating {RHEL} BYOS images, you must accept the image terms either in the Azure CLI or Portal so that the image can be used to create and manage virtual machines for your subscription.
diff --git a/guides/common/modules/con_resolving-package-dependencies.adoc b/guides/common/modules/con_resolving-package-dependencies.adoc
@@ -53,7 +53,7 @@ To achieve this, you create filters to exclude most of the errata after the {RHE
 Then, you enable dependency solving.
 
 In this situation, dependency solving might include more packages than expected.
-As a result, the host diverges from being a {RHEL}{nbsp}8.3 machine.
+As a result, the host diverges from {RHEL}{nbsp}8.3 machines.
 
 If you do not need the extra errata and packages, do not configure content view filtering.
 Instead, enable and use the {RHEL}{nbsp}8.3 repository on the *Content* > *Red Hat Repositories* page in the {ProjectWebUI}.
@@ -64,7 +64,7 @@ ifeval::["{client-os-family}" == "Red Hat"]
 [id="Excluding_packages_and_dependency_solving_with_DNF_{context}"]
 .Excluding packages sometimes makes dependency solving impossible for DNF
 ====
-If you make a {RHEL}{nbsp}8.3 repository with a few excluded packages, `dnf upgrade` can sometimes fail.
+If you create {RHEL}{nbsp}8.3 repositories with a few excluded packages, `dnf upgrade` can sometimes fail.
 
 Do not enable dependency solving to resolve the problem.
 Instead, investigate the error from `dnf` and adjust the filters to stop excluding the missing dependency.
diff --git a/guides/common/modules/proc_applying-errata-to-multiple-hosts.adoc b/guides/common/modules/proc_applying-errata-to-multiple-hosts.adoc
@@ -3,7 +3,7 @@
 [id="Applying_Errata_to_Multiple_Hosts_{context}"]
 = Applying errata to multiple hosts
 
-Use these procedures to review and apply errata to multiple RHEL hosts.
+Use these procedures to review and apply errata to multiple {client-os} hosts.
 
 .Prerequisites
 * Synchronize {ProjectName} repositories with the latest errata available from Red{nbsp}Hat.
diff --git a/guides/common/modules/proc_configuring-a-finish-template-for-amazon-ec2.adoc b/guides/common/modules/proc_configuring-a-finish-template-for-amazon-ec2.adoc
@@ -33,7 +33,7 @@ _Template_ _Body_
 EOS
 ----
 +
-. Click the *Association* tab, and associate the template with a {RHEL} operating system that you want to use.
+. Click the *Association* tab, and associate the template with a {client-os} operating system that you want to use.
 . Click the *Locations* tab, and add the the location where the host resides.
 . Click the *Organizations* tab, and add the organization that the host belongs to.
 . Make any additional customizations or changes that you require, then click *Submit* to save your template.
diff --git a/guides/common/modules/proc_configuring-the-freeipa-authentication-source-on-projectserver.adoc b/guides/common/modules/proc_configuring-the-freeipa-authentication-source-on-projectserver.adoc
@@ -39,7 +39,7 @@ For example, to disable access to the {Project} API and Hammer CLI:
 ----
 # {foreman-installer} --reset-foreman-ipa-authentication-api
 ----
-. If your {ProjectServer} runs in an IPv6-only network and also runs on RHEL{nbsp}9.6 and earlier or RHEL{nbsp}10.0, set the `lookup_family_order` option in the `[domain/_{freeipaserver-example-com}_]` section of the `/etc/sssd/sssd.conf` file:
+. If your {ProjectServer} runs in an IPv6-only network and also runs on {EL}{nbsp}9.6 and earlier or {EL}{nbsp}10.0, set the `lookup_family_order` option in the `[domain/_{freeipaserver-example-com}_]` section of the `/etc/sssd/sssd.conf` file:
 +
 [source, ini, options="nowrap", subs="+quotes,verbatim,attributes"]
 ----
diff --git a/guides/common/modules/proc_creating-custom-rhel-images.adoc b/guides/common/modules/proc_creating-custom-rhel-images.adoc
@@ -5,12 +5,12 @@
 
 .Prerequisites
 * Use a Linux host machine to create an image.
-In this example, we use a {RHEL} 7 Workstation.
+This example uses {RHEL}{nbsp}7 Workstation.
 * Use `virt-manager` on your workstation to complete this procedure.
 If you create the image on a remote server, connect to the server from your workstation with `virt-manager`.
 * A {RHEL} 7 ISO file (see https://access.redhat.com/downloads/content/69/ver=/rhel---7/7.4/x86_64/product-software[{RHEL} 7.4 Binary DVD]).
 
-For more information about installing a {RHEL} Workstation, see the {RHELDocsBaseURL}7/html-single/installation_guide/index[_{RHEL}{nbsp}7 Installation Guide_].
+For more information about installing your {RHEL} Workstation, see the {RHELDocsBaseURL}7/html-single/installation_guide/index[_{RHEL}{nbsp}7 Installation Guide_].
 
 Before you can create custom images, install the following packages:
 
diff --git a/guides/common/modules/proc_editing-the-system-purpose-of-a-host.adoc b/guides/common/modules/proc_editing-the-system-purpose-of-a-host.adoc
@@ -3,7 +3,7 @@
 [id="Editing_the_System_Purpose_of_a_Host_{context}"]
 = Editing the system purpose of a host
 
-You can edit the system purpose attributes for a {RHEL} host.
+You can edit the system purpose attributes for your {RHEL} host.
 System purpose allows you to set the intended use of a system on your network and improves reporting accuracy in the Subscriptions service of the Red Hat Hybrid Cloud Console.
 ifndef::orcharhino[]
 For more information about system purpose, see {RHELDocsBaseURL}8/html/automatically_installing_rhel/proc_configuring-system-purpose-using-the-subscription-manager-command-line-tool_rhel-installer[Configuring System Purpose using the subscription-manager command-line tool] in _Automatically installing RHEL{nbsp}8_.
diff --git a/guides/common/modules/proc_exporting-a-content-view-version-incrementally.adoc b/guides/common/modules/proc_exporting-a-content-view-version-incrementally.adoc
@@ -7,7 +7,7 @@ Exporting complete content view versions can be a very expensive operation in te
 ifdef::orcharhino[]
 The size of the exported content view versions depends on the number of products.
 endif::[]
-Content view versions that have multiple {RHEL} trees can occupy several gigabytes of space on {ProjectServer}.
+Content view versions that have multiple {client-os} trees can occupy several gigabytes of space on {ProjectServer}.
 
 In such cases, you can create an incremental export which contains only pieces of content that have changed since the last export.
 Incremental exports typically result in smaller archive files than the full exports.
diff --git a/guides/common/modules/proc_exporting-a-repository-incrementally-in-a-syncable-format.adoc b/guides/common/modules/proc_exporting-a-repository-incrementally-in-a-syncable-format.adoc
@@ -4,7 +4,7 @@
 = Exporting a repository incrementally in a syncable format
 
 Exporting a repository can be a very expensive operation in terms of system resources.
-A typical {RHEL} tree may occupy several gigabytes of space on {ProjectServer}.
+A typical {client-os} tree may occupy several gigabytes of space on {ProjectServer}.
 
 In such cases, you can use *Incremental Export* to export only pieces of content that changed since the previous export.
 Incremental exports typically result in smaller archive files than full exports.
diff --git a/guides/common/modules/proc_exporting-a-repository-incrementally.adoc b/guides/common/modules/proc_exporting-a-repository-incrementally.adoc
@@ -4,7 +4,7 @@
 = Exporting a repository incrementally
 
 Exporting a repository can be a very expensive operation in terms of system resources.
-A typical {RHEL} tree may occupy several gigabytes of space on {ProjectServer}.
+A typical {client-os} tree may occupy several gigabytes of space on {ProjectServer}.
 
 In such cases, you can use *Incremental Export* to export only pieces of content that changed since the previous export.
 Incremental exports typically result in smaller archive files than the full exports.
diff --git a/guides/common/modules/proc_exporting-the-library-environment-incrementally.adoc b/guides/common/modules/proc_exporting-the-library-environment-incrementally.adoc
@@ -7,7 +7,7 @@ Exporting Library content can be a very expensive operation in terms of system r
 ifdef::orcharhino[]
 The size of the exported Library depends on the number of products.
 endif::[]
-Organizations that have multiple {RHEL} trees can occupy several gigabytes of space on {ProjectServer}.
+Organizations that have multiple {client-os} trees can occupy several gigabytes of space on {ProjectServer}.
 
 In such cases, you can create an incremental export which contains only pieces of content that have changed since the last export.
 Incremental exports typically result in smaller archive files than the full exports.
diff --git a/guides/common/modules/proc_preparing-a-synchronized-kickstart-repository.adoc b/guides/common/modules/proc_preparing-a-synchronized-kickstart-repository.adoc
@@ -4,7 +4,7 @@
 = Preparing a synchronized Kickstart repository
 
 {Project} contains a set of synchronized Kickstart repositories that you use to install the provisioned host's operating system.
-For more information about adding repositories, see {ContentManagementDocURL}Synchronizing_Repositories_content-management[Syncing Repositories] in _{ContentManagementDocTitle}_.
+For more information about adding repositories, see {ContentManagementDocURL}Synchronizing_Repositories_content-management[Synchronizing repositories] in _{ContentManagementDocTitle}_.
 
 Use this procedure to set up a Kickstart repository.
 
@@ -14,10 +14,10 @@ You must enable both *BaseOS* and *AppStream Kickstart* before provisioning.
 .Procedure
 . Add the synchronized Kickstart repository that you want to use to the existing content view, or create a new content view and add the Kickstart repository.
 +
-For {RHEL} 8, ensure that you add both *{RHEL} 8 for x86_64 - AppStream Kickstart x86_64 8* and *{RHEL} 8 for x86_64 - BaseOS Kickstart x86_64 8* repositories.
+For {EL} 8, ensure that you add both *{EL} 8 for x86_64 - AppStream Kickstart x86_64 8* and *{EL} 8 for x86_64 - BaseOS Kickstart x86_64 8* repositories.
 ifdef::satellite,orcharhino[]
 +
-If you use a disconnected environment, you must import the Kickstart repositories from a {RHEL} binary DVD.
+If you use a disconnected environment, you must import the Kickstart repositories from your {EL} binary DVD.
 endif::[]
 +
 . Publish a new version of the content view where the Kickstart repository is added and promote it to a required lifecycle environment.
diff --git a/guides/common/modules/proc_registering-to-red-hat-subscription-management.adoc b/guides/common/modules/proc_registering-to-red-hat-subscription-management.adoc
@@ -4,14 +4,15 @@
 = Registering to Red Hat Subscription Management
 
 ifdef::foreman-el,katello[]
-If you use a {RHEL}-based operating system, complete the following steps.
+If you run {Project} on {RHEL}, complete the following steps.
 endif::[]
 
 Registering the host to Red Hat Subscription Management enables the host to subscribe to and consume content for any subscriptions available to the user.
+ifdef::satellite[]
 This includes content such as {RHEL} and {ProjectName}.
+endif::[]
 
 .Procedure
-
 * Register your system with the Red Hat Content Delivery Network, entering your Customer Portal user name and password when prompted:
 +
 [options="nowrap"]
@@ -21,7 +22,7 @@ This includes content such as {RHEL} and {ProjectName}.
 +
 The command displays output similar to the following:
 +
-[options="nowrap"]
+[source, none, options="nowrap"]
 ----
 # subscription-manager register
 Username: user_name
diff --git a/guides/common/modules/proc_restricting-customrepoid-to-a-specific-operating-system-version-or-architecture-in-project.adoc b/guides/common/modules/proc_restricting-customrepoid-to-a-specific-operating-system-version-or-architecture-in-project.adoc
@@ -5,7 +5,7 @@
 
 You can configure {Project} to make a {customrepo} available only on hosts with a specific operating system version or architecture.
 ifdef::client-content-dnf[]
-For example, you can restrict a {customrepo} only to {RHEL}{nbsp}9 hosts.
+For example, you can restrict a {customrepo} only to {client-os}{nbsp}{client-os-major} hosts.
 endif::[]
 
 ifdef::satellite[]
diff --git a/guides/common/modules/proc_updating-disconnected-server-on-EL9.adoc b/guides/common/modules/proc_updating-disconnected-server-on-EL9.adoc
@@ -1,7 +1,7 @@
 :_mod-docs-content-type: PROCEDURE
 
 [id="Updating-Disconnected-{project-context}-on-EL9_{context}"]
-= Updating a disconnected {ProjectServer} on {EL} 9
+= Updating a disconnected {ProjectServer} on {RHEL} 9
 
 You can update your disconnected {Project} on {RHEL} 9 by synchronizing the required repositories on the connected {Project} and syncing the content to the disconnected {Project} using `reposync`.
 
diff --git a/guides/common/modules/proc_using-activation-keys-for-host-registration.adoc b/guides/common/modules/proc_using-activation-keys-for-host-registration.adoc
@@ -7,7 +7,7 @@ You can use activation keys to complete the following tasks:
 
 * Registering new hosts during provisioning through {ProjectName}.
 The Kickstart provisioning templates in {ProjectName} contain commands to register the host using an activation key that is defined when creating a host.
-* Registering existing {RHEL} hosts.
+* Registering existing {client-os} hosts.
 
 include::snip_host-registration-steps.adoc[]
 
diff --git a/guides/common/modules/ref_capsule-storage-requirements.adoc b/guides/common/modules/ref_capsule-storage-requirements.adoc
@@ -7,7 +7,7 @@ The following table details storage requirements for specific directories.
 These values are based on expected use case scenarios and can vary according to individual environments.
 
 ifdef::katello,satellite[]
-The runtime size was measured with {RHEL} 7, 8, and 9 repositories synchronized.
+The runtime size was measured with {EL} 7, 8, and 9 repositories synchronized.
 endif::[]
 
 .Storage requirements for {SmartProxyServer} installation
diff --git a/guides/common/modules/ref_playbook-example-enable-repositories-and-create-a-content-view.adoc b/guides/common/modules/ref_playbook-example-enable-repositories-and-create-a-content-view.adoc
@@ -8,7 +8,7 @@ This example playbook uses the following modules:
 * `{ansible-namespace}.repository_set`
 * `{ansible-namespace}.content_view`
 
-The playbook ensures repositories are enabled and a content view that contains these repositories exists.
+The playbook ensures RHEL 9 repositories are enabled and a content view that contains these repositories exists.
 
 Before you run this playbook, ensure that you have uploaded a manifest and can access the Red{nbsp}Hat CDN.
 
diff --git a/guides/common/modules/ref_playbook-example-synchronize-repositories-and-publish-a-content-view.adoc b/guides/common/modules/ref_playbook-example-synchronize-repositories-and-publish-a-content-view.adoc
@@ -15,7 +15,7 @@ For an example playbook that ensures this, see xref:playbook-example-enable-repo
 
 [options="nowrap" subs="+quotes,attributes"]
 ----
-- name: Ensure RHEL 9 repositories are synced and content view is published
+- name: Ensure {client-os} {client-os-major} repositories are synced and content view is published
   hosts: localhost
   vars_files:
     - _My_Vault.yml_
@@ -25,13 +25,13 @@ For an example playbook that ensures this, see xref:playbook-example-enable-repo
       password: "{{ _My_Password_ }}"
       server_url: "{{ _My_Server_URL_ }}"
   tasks:
-    - name: Sync RHEL repositories
+    - name: Sync {client-os} repositories
       {ansible-namespace}.repository_sync:
-        product: "Red Hat Enterprise Linux for x86_64"
+        product: "{client-os} for x86_64"
         organization: "Default Organization"
-    - name: Publish RHEL 9 content view
+    - name: Publish {client-os} {client-os-major} content view
       {ansible-namespace}.content_view_version:
-        content_view: "RHEL 9 content view"
+        content_view: "{client-os} {client-os-major} content view"
         organization: "Default Organization"
 ----
 
diff --git a/guides/common/modules/ref_storage-guidelines.adoc b/guides/common/modules/ref_storage-guidelines.adoc
@@ -64,7 +64,7 @@ Ensure that storage is available on the `/var` file system to prevent storage pr
 You cannot use symbolic links for `/var/lib/pulp/`.
 
 ifeval::["{mode}" == "connected"]
-.Synchronized RHEL ISO
-If you plan to synchronize RHEL content ISOs to {Project}, note that all minor versions of {RHEL} also synchronize.
+.Synchronized {client-os} ISO
+If you plan to synchronize {client-os} content ISOs to {Project}, note that all minor versions of {client-os} also synchronize.
 You must plan to have adequate storage on your {Project} to manage this.
 endif::[]
diff --git a/guides/common/modules/ref_storage-requirements.adoc b/guides/common/modules/ref_storage-requirements.adoc
@@ -7,7 +7,7 @@ The following table details storage requirements for specific directories.
 These values are based on expected use case scenarios and can vary according to individual environments.
 
 ifdef::katello,satellite[]
-The runtime size was measured with {RHEL} 7, 8, and 9 repositories synchronized.
+The runtime size was measured with {EL} 7, 8, and 9 repositories synchronized.
 endif::[]
 
 .Storage requirements for a {ProjectServer} installation
@@ -36,4 +36,4 @@ ifdef::foreman-el,katello,satellite[]
 For external database servers: `{postgresql-lib-dir}` with installation size of 100 MB and runtime size of 20 GB.
 
 For detailed information on partitioning and size, see {RHELDocsBaseURL}9/html/managing_storage_devices/disk-partitions_managing-storage-devices[Disk partitions] in _{RHEL}{nbsp}9 Managing storage devices_.
-endif::[]
+endif::[]
diff --git a/guides/common/modules/snip_prerequisites-common-compute-resource.adoc b/guides/common/modules/snip_prerequisites-common-compute-resource.adoc
diff --git a/guides/doc-Updating_Project/master.adoc b/guides/doc-Updating_Project/master.adoc

Original file line number	Diff line number	Diff line change
`@@ -33,7 +33,7 @@ _Template_ _Body_`
`33`	`33`	`EOS`
`34`	`34`	`----`
`35`	`35`	`+`
`36`		`-. Click the Association tab, and associate the template with a {RHEL} operating system that you want to use.`
	`36`	`+. Click the Association tab, and associate the template with a {client-os} operating system that you want to use.`
`37`	`37`	`. Click the Locations tab, and add the the location where the host resides.`
`38`	`38`	`. Click the Organizations tab, and add the organization that the host belongs to.`
`39`	`39`	`. Make any additional customizations or changes that you require, then click Submit to save your template.`
Original file line number	Diff line number	Diff line change
`@@ -39,7 +39,7 @@ For example, to disable access to the {Project} API and Hammer CLI:`
`39`	`39`	`----`
`40`	`40`	`# {foreman-installer} --reset-foreman-ipa-authentication-api`
`41`	`41`	`----`
`42`		-. If your {ProjectServer} runs in an IPv6-only network and also runs on RHEL{nbsp}9.6 and earlier or RHEL{nbsp}10.0, set the `lookup_family_order` option in the `[domain/_{freeipaserver-example-com}_]` section of the `/etc/sssd/sssd.conf` file:
	`42`	+. If your {ProjectServer} runs in an IPv6-only network and also runs on {EL}{nbsp}9.6 and earlier or {EL}{nbsp}10.0, set the `lookup_family_order` option in the `[domain/_{freeipaserver-example-com}_]` section of the `/etc/sssd/sssd.conf` file:
`43`	`43`	`+`
`44`	`44`	`[source, ini, options="nowrap", subs="+quotes,verbatim,attributes"]`
`45`	`45`	`----`