diff --git a/guides/common/modules/con_dependency-solving-for-content-views.adoc b/guides/common/modules/con_dependency-solving-for-content-views.adoc
index 5aece44d100..247736d5b63 100644
--- a/guides/common/modules/con_dependency-solving-for-content-views.adoc
+++ b/guides/common/modules/con_dependency-solving-for-content-views.adoc
@@ -22,7 +22,7 @@ As an alternative, consider updating the content view.
 ====
 Dependency solving only considers packages within the repositories of the content view.
 It does not consider packages installed on clients.
-ifeval::["{client-os-family}" == "Red Hat"]
+ifdef::katello,satellite,almalinux,centos,oracle_linux,red_hat_enterprise_linux,rocky_linux[]
 For example, if a content view includes only AppStream, dependency solving does not include dependent BaseOS content at publish time.
 endif::[]
 
@@ -45,7 +45,7 @@ For example, if you create a filter for security purposes but enable dependency
 To mitigate this problem, carefully test filtering rules to determine the required dependencies.
 If dependency solving includes unwanted packages, manually identify the core basic dependencies that the extra packages and errata need.
 
-ifeval::["{client-os}" == "{RHEL}"]
+ifdef::katello,satellite,red_hat_enterprise_linux[]
 [id="Combining_exclusion_filters_with_dependency_solving_{context}"]
 .Combining exclusion filters with dependency solving
 ====
@@ -59,9 +59,7 @@ As a result, the host diverges from {client-os}{nbsp}9.3 machines.
 If you do not need the extra errata and packages, do not configure content view filtering.
 Instead, enable and use the {client-os}{nbsp}9.3 repository on the *Content* > *Red Hat Repositories* page in the {ProjectWebUI}.
 ====
-endif::[]
 
-ifeval::["{client-os}" == "{RHEL}"]
 [id="Excluding_packages_and_dependency_solving_with_DNF_{context}"]
 .Excluding packages sometimes makes dependency solving impossible for DNF
 ====
diff --git a/guides/common/modules/con_host-substatus-overview.adoc b/guides/common/modules/con_host-substatus-overview.adoc
index d10b5b7c685..6faf7703ce3 100644
--- a/guides/common/modules/con_host-substatus-overview.adoc
+++ b/guides/common/modules/con_host-substatus-overview.adoc
@@ -143,7 +143,7 @@ Possible values:
 | Needed security errata | Error | 3
 |===
 
-ifeval::["{client-os}" == "{RHEL}"]
+ifdef::katello,satellite,red_hat_enterprise_linux[]
 RHEL Lifecycle::
 Indicates the current state of the {RHEL} operating system installed on the host.
 +
diff --git a/guides/common/modules/proc_configuring-smart-proxy-to-provision-secure-boot-enabled-hosts.adoc b/guides/common/modules/proc_configuring-smart-proxy-to-provision-secure-boot-enabled-hosts.adoc
index e92ad9aaad6..2da42585cb5 100644
--- a/guides/common/modules/proc_configuring-smart-proxy-to-provision-secure-boot-enabled-hosts.adoc
+++ b/guides/common/modules/proc_configuring-smart-proxy-to-provision-secure-boot-enabled-hosts.adoc
@@ -20,10 +20,10 @@ endif::[]
 You have to perform the following configuration steps on each TFTP {SmartProxy} for a subnet to provision Secure Boot enabled hosts on that subnet.
 ====
 
-ifeval::["{client-os-context}" == "rhel"]
+ifdef::satellite[]
 {client-os} supports Secure Boot on x86_64 architecture only.
 endif::[]
-ifeval::["{client-os-context}" != "rhel"]
+ifndef::satellite[]
 The following example works for {client-os} on x86_64 architecture.
 endif::[]