OSDOCS#17381: Adding blank lines after includes

2026-02-05 03:47:04 +01:00 · 2025-11-18 17:48:49 -05:00
parent ab55857750
commit 22ecbb3d18
273 changed files with 1089 additions and 0 deletions
--- a/applications/application-health.adoc
+++ b/applications/application-health.adoc
@@ -24,6 +24,7 @@ include::modules/odc-monitoring-application-health-using-developer-perspective.a
 // cannot add health checks in web console
 ifdef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 include::modules/odc-adding-health-checks.adoc[leveloffset=+1]
+
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]

 include::modules/odc-editing-health-checks.adoc[leveloffset=+1]
--- a/applications/connecting_applications_to_services/binding-workloads-using-sbo.adoc
+++ b/applications/connecting_applications_to_services/binding-workloads-using-sbo.adoc
@@ -37,8 +37,11 @@ spec:
 As shown in the previous example, you can also directly use a `ConfigMap` or a `Secret` itself as a service resource to be used as a source of binding data.

 include::modules/sbo-naming-strategies.adoc[leveloffset=+1]
+
 include::modules/sbo-advanced-binding-options.adoc[leveloffset=+1]
+
 include::modules/sbo-binding-workloads-that-are-not-compliant-with-PodSpec.adoc[leveloffset=+1]
+
 include::modules/sbo-unbinding-workloads-from-a-backing-service.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/applications/connecting_applications_to_services/exposing-binding-data-from-a-service.adoc
+++ b/applications/connecting_applications_to_services/exposing-binding-data-from-a-service.adoc
@@ -13,9 +13,13 @@ Application developers need access to backing services to build and connect work
 The {servicebinding-title} enables application developers to easily bind workloads together with operator-managed backing services, without any manual procedures to configure the binding connection. For the {servicebinding-title} to provide the binding data, as an Operator provider or user who creates backing services, you must expose the binding data to be automatically detected by the {servicebinding-title}. Then, the {servicebinding-title} automatically collects the binding data from the backing service and shares it with a workload to provide a consistent and predictable experience.

 include::modules/sbo-methods-of-exposing-binding-data.adoc[leveloffset=+1]
+
 include::modules/sbo-data-model.adoc[leveloffset=+1]
+
 include::modules/sbo-setting-annotations-mapping-optional.adoc[leveloffset=+1]
+
 include::modules/sbo-rbac-requirements.adoc[leveloffset=+1]
+
 include::modules/sbo-categories-of-exposable-binding-data.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/applications/connecting_applications_to_services/projecting-binding-data.adoc
+++ b/applications/connecting_applications_to_services/projecting-binding-data.adoc
@@ -17,6 +17,7 @@ After the backing service exposes the binding data, for a workload to access and
 . As environment variables, after you configure the `.spec.bindAsFiles` parameter from the `ServiceBinding` resource.

 include::modules/sbo-configuration-of-directory-path-to-project-binding-data.adoc[leveloffset=+1]
+
 include::modules/sbo-projecting-the-binding-data.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/applications/connecting_applications_to_services/understanding-service-binding-operator.adoc
+++ b/applications/connecting_applications_to_services/understanding-service-binding-operator.adoc
@@ -13,8 +13,11 @@ Application developers need access to backing services to build and connect work
 The {servicebinding-title} enables application developers to easily bind workloads together with Operator-managed backing services, without any manual procedures to configure the binding connection.

 include::modules/sbo-service-binding-terminology.adoc[leveloffset=+1]
+
 include::modules/sbo-about-service-binding-operator.adoc[leveloffset=+1]
+
 include::modules/sbo-key-features.adoc[leveloffset=+1]
+
 include::modules/sbo-api-differences.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/applications/deployments/deployment-strategies.adoc
+++ b/applications/deployments/deployment-strategies.adoc
@@ -27,12 +27,16 @@ A deployment strategy uses readiness checks to determine if a new pod is ready f

 // Rolling strategies
 include::modules/deployments-rolling-strategy.adoc[leveloffset=+1]
+
 include::modules/deployments-canary-deployments.adoc[leveloffset=+2]
+
 // Creating rolling deployments
 include::modules/creating-rolling-deployments-CLI.adoc[leveloffset=+2]
+
 // Editing a deployment
 :context: rolling-strategy
 include::modules/odc-editing-deployments.adoc[leveloffset=+2]
+
 // Starting a deployment
 include::modules/odc-starting-rolling-deployment.adoc[leveloffset=+2]

@@ -43,9 +47,11 @@ include::modules/odc-starting-rolling-deployment.adoc[leveloffset=+2]

 // Recreate strategies
 include::modules/deployments-recreate-strategy.adoc[leveloffset=+1]
+
 // Editing a deployment
 :context: recreate-strategy
 include::modules/odc-editing-deployments.adoc[leveloffset=+2]
+
 // Starting a deployment
 include::modules/odc-starting-recreate-deployment.adoc[leveloffset=+2]

@@ -56,6 +62,7 @@ include::modules/odc-starting-recreate-deployment.adoc[leveloffset=+2]

 // Custom strategies
 include::modules/deployments-custom-strategy.adoc[leveloffset=+1]
+
 // Editing a deployment
 :context: custom-strategy
 include::modules/odc-editing-deployments.adoc[leveloffset=+2]
--- a/applications/deployments/managing-deployment-processes.adoc
+++ b/applications/deployments/managing-deployment-processes.adoc
@@ -14,13 +14,21 @@ include::snippets/deployment-config-deprecated.adoc[]
 `DeploymentConfig` objects can be managed from the {product-title} web console's *Workloads* page or using the `oc` CLI. The following procedures show CLI usage unless otherwise stated.

 include::modules/deployments-starting-deployment.adoc[leveloffset=+2]
+
 include::modules/deployments-viewing-deployment.adoc[leveloffset=+2]
+
 include::modules/deployments-retrying-deployment.adoc[leveloffset=+2]
+
 include::modules/deployments-rolling-back.adoc[leveloffset=+2]
+
 include::modules/deployments-exec-cmd-in-container.adoc[leveloffset=+2]
+
 include::modules/deployments-viewing-logs.adoc[leveloffset=+2]
+
 include::modules/deployments-triggers.adoc[leveloffset=+2]
+
 include::modules/deployments-setting-triggers.adoc[leveloffset=+3]
+
 include::modules/deployments-setting-resources.adoc[leveloffset=+2]

 // When the Nodes book is added to ROSA/OSD, check if this link is valid.
@@ -32,14 +40,17 @@ ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]

 include::modules/deployments-scaling-manually.adoc[leveloffset=+2]
+
 include::modules/deployments-accessing-private-repos.adoc[leveloffset=+2]

 ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
 include::modules/deployments-assigning-pods-to-nodes.adoc[leveloffset=+2]
+
 endif::[]

 ifndef::openshift-online[]
 include::modules/deployments-running-pod-svc-acct.adoc[leveloffset=+2]
+
 endif::[]

 ////
--- a/applications/deployments/rosa-config-custom-domains-applications.adoc
+++ b/applications/deployments/rosa-config-custom-domains-applications.adoc
@@ -14,4 +14,5 @@ Starting with {product-title} 4.14, the Custom Domain Operator is deprecated. To
 You can configure a custom domain for your applications. Custom domains are specific wildcard domains that can be used with {product-title} applications. 

 include::modules/rosa-applications-config-custom-domains.adoc[leveloffset=+1]
+
 include::modules/rosa-applications-renew-custom-domains.adoc[leveloffset=+1]
--- a/applications/deployments/route-based-deployment-strategies.adoc
+++ b/applications/deployments/route-based-deployment-strategies.adoc
@@ -28,10 +28,15 @@ A canary deployment tests the new version but when a problem is detected it quic
 The route-based deployment strategies do not scale the number of pods in the services. To maintain desired performance characteristics the deployment configurations might have to be scaled.

 include::modules/deployments-proxy-shards.adoc[leveloffset=+1]
+
 include::modules/deployments-n1-compatibility.adoc[leveloffset=+1]
+
 include::modules/deployments-graceful-termination.adoc[leveloffset=+1]
+
 include::modules/deployments-blue-green.adoc[leveloffset=+1]
+
 include::modules/deployments-ab-testing.adoc[leveloffset=+1]
+
 include::modules/deployments-ab-testing-lb.adoc[leveloffset=+2]

 ifndef::openshift-rosa-hcp[]
--- a/applications/deployments/what-deployments-are.adoc
+++ b/applications/deployments/what-deployments-are.adoc
@@ -45,13 +45,17 @@ If the existing deployment strategies are not suited for your use case and you m
 The following sections provide further details on these objects.

 include::modules/deployments-replicasets.adoc[leveloffset=+2]
+
 include::modules/deployments-replicationcontrollers.adoc[leveloffset=+2]

 include::modules/deployments-kube-deployments.adoc[leveloffset=+1]
+
 include::modules/deployments-deploymentconfigs.adoc[leveloffset=+1]

 include::modules/deployments-comparing-deploymentconfigs.adoc[leveloffset=+1]
+
 include::modules/deployment-specific-features.adoc[leveloffset=+2]
+
 include::modules/deploymentconfig-object-specific-features.adoc[leveloffset=+2]

 ////
--- a/applications/idling-applications.adoc
+++ b/applications/idling-applications.adoc
@@ -13,4 +13,5 @@ If any scalable resources are not in use, {product-title} discovers and idles th
 Applications are made of services, as well as other scalable resources, such as deployment configs. The action of idling an application involves idling all associated resources.

 include::modules/idle-idling-applications.adoc[leveloffset=+1]
+
 include::modules/idle-unidling-applications.adoc[leveloffset=+1]
--- a/applications/projects/configuring-project-creation.adoc
+++ b/applications/projects/configuring-project-creation.adoc
@@ -16,6 +16,9 @@ a cluster administrator, you can allow and configure how developers and service
 accounts can create, or _self-provision_, their own projects.

 include::modules/about-project-creation.adoc[leveloffset=+1]
+
 include::modules/modifying-template-for-new-projects.adoc[leveloffset=+1]
+
 include::modules/disabling-project-self-provisioning.adoc[leveloffset=+1]
+
 include::modules/customizing-project-request-message.adoc[leveloffset=+1]
--- a/applications/projects/working-with-projects.adoc
+++ b/applications/projects/working-with-projects.adoc
@@ -29,6 +29,7 @@ endif::openshift-dedicated[]

 ifndef::openshift-dedicated[]
 include::snippets/default-projects.adoc[]
+
 endif::openshift-dedicated[]
 ifdef::openshift-dedicated[]
 [NOTE]
--- a/applications/pruning-objects.adoc
+++ b/applications/pruning-objects.adoc
@@ -24,8 +24,11 @@ space.
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]

 include::modules/pruning-basic-operations.adoc[leveloffset=+1]
+
 include::modules/pruning-groups.adoc[leveloffset=+1]
+
 include::modules/pruning-deployments.adoc[leveloffset=+1]
+
 include::modules/pruning-builds.adoc[leveloffset=+1]

 ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
@@ -35,15 +38,21 @@ ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]

 include::modules/pruning-images.adoc[leveloffset=+1]
+
 //cannot create resource "serviceaccounts". cannot create resource "cronjobs"

 ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 include::modules/pruning-images-manual.adoc[leveloffset=+1]
+
 //include::modules/pruning-images-job-cronjob.adoc[leveloffset=+2]
 include::modules/pruning-images-conditions.adoc[leveloffset=+2]
+
 include::modules/pruning-images-running-operation.adoc[leveloffset=+2]
+
 include::modules/pruning-images-secure-insecure.adoc[leveloffset=+2]
+
 include::modules/pruning-images-options.adoc[leveloffset=+2]
+
 include::modules/pruning-images-troubleshooting.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -60,6 +69,7 @@ endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]

 ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 include::modules/pruning-hard-pruning-registry.adoc[leveloffset=+1]
+
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]

 include::modules/pruning-cronjobs.adoc[leveloffset=+1]
--- a/applications/quotas/quotas-setting-across-multiple-projects.adoc
+++ b/applications/quotas/quotas-setting-across-multiple-projects.adoc
@@ -13,5 +13,7 @@ This guide describes how cluster administrators can set and manage resource quot
 include::snippets/default-projects.adoc[]

 include::modules/quotas-selecting-projects.adoc[leveloffset=+1]
+
 include::modules/quotas-viewing-clusterresourcequotas.adoc[leveloffset=+1]
+
 include::modules/quotas-selection-granularity.adoc[leveloffset=+1]
--- a/applications/quotas/quotas-setting-per-project.adoc
+++ b/applications/quotas/quotas-setting-per-project.adoc
@@ -11,12 +11,21 @@ A _resource quota_, defined by a `ResourceQuota` object, provides constraints th
 This guide describes how resource quotas work, how cluster administrators can set and manage resource quotas on a per project basis, and how developers and cluster administrators can view them.

 include::modules/quotas-resources-managed.adoc[leveloffset=+1]
+
 include::modules/quotas-scopes.adoc[leveloffset=+1]
+
 include::modules/quotas-enforcement.adoc[leveloffset=+1]
+
 include::modules/quotas-requests-vs-limits.adoc[leveloffset=+1]
+
 include::modules/quotas-sample-resource-quotas-def.adoc[leveloffset=+1]
+
 include::modules/quotas-creating-a-quota.adoc[leveloffset=+1]
+
 include::modules/quotas-creating-object-count-quotas.adoc[leveloffset=+2]
+
 include::modules/setting-resource-quota-for-extended-resources.adoc[leveloffset=+2]
+
 include::modules/quotas-viewing-quotas.adoc[leveloffset=+1]
+
 include::modules/quotas-requiring-explicit-quota.adoc[leveloffset=+1]
--- a/applications/working-with-quotas.adoc
+++ b/applications/working-with-quotas.adoc
@@ -20,7 +20,11 @@ This guide describes how resource quotas work and how developers can work with
 and view them.

 include::modules/quotas-viewing-quotas.adoc[leveloffset=+1]
+
 include::modules/quotas-resources-managed.adoc[leveloffset=+1]
+
 include::modules/quotas-scopes.adoc[leveloffset=+1]
+
 include::modules/quotas-enforcement.adoc[leveloffset=+1]
+
 include::modules/quotas-requests-vs-limits.adoc[leveloffset=+1]
--- a/applications/working_with_helm_charts/configuring-custom-helm-chart-repositories.adoc
+++ b/applications/working_with_helm_charts/configuring-custom-helm-chart-repositories.adoc
@@ -31,6 +31,7 @@ In the *Developer* perspective of the web console, you can use the *Helm* page t
 // clusterroles.rbac.authorization.k8s.io is forbidden: user (groups=["dedicated-admins" "system:authenticated:oauth" "system:authenticated"]) is attempting to grant RBAC permissions not currently held:
 ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 include::modules/helm-installing-a-helm-chart-on-an-openshift-cluster.adoc[leveloffset=+1]
+
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]

 include::modules/odc-creating-helm-releases-using-developer-perspective.adoc[leveloffset=+1]
@@ -50,18 +51,23 @@ include::modules/helm-creating-a-custom-helm-chart-on-openshift.adoc[leveloffset
 //cannot create resource "helmchartrepositories" in API group "helm.openshift.io"
 ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 include::modules/helm-adding-helm-chart-repositories.adoc[leveloffset=+1]
+
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 //projecthelmchartrepositories.helm.openshift.io "azure-sample-repo" is forbidden: User cannot get resource "projecthelmchartrepositories" in API group "helm.openshift.io"
 ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 include::modules/helm-adding-namespace-scoped-helm-chart-repositories.adoc[leveloffset=+1]
+
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 //cannot create resource "helmchartrepositories" in API group "helm.openshift.io"
 ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 include::modules/helm-creating-credentials-and-certificates-to-add-helm-repositories.adoc[leveloffset=+1]
+
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]

 include::modules/helm-filtering-helm-charts-by-certification-level.adoc[leveloffset=+1]
+
 ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 //cannot patch resource "helmchartrepositories" in API group "helm.openshift.io"
 include::modules/helm-disabling-helm-chart-repositories.adoc[leveloffset=+1]
+
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
--- a/architecture/admission-plug-ins.adoc
+++ b/architecture/admission-plug-ins.adoc
@@ -21,6 +21,7 @@ include::modules/admission-webhook-types.adoc[leveloffset=+1]
 ifndef::openshift-rosa,openshift-dedicated[]
 // Procedure module
 include::modules/configuring-dynamic-admission.adoc[leveloffset=+1]
+
 endif::openshift-rosa,openshift-dedicated[]

 [role="_additional-resources"]
--- a/architecture/architecture-rhcos.adoc
+++ b/architecture/architecture-rhcos.adoc
@@ -7,5 +7,7 @@ include::_attributes/common-attributes.adoc[]
 toc::[]

 include::modules/rhcos-about.adoc[leveloffset=+1]
+
 include::modules/ignition-config-viewing.adoc[leveloffset=+1]
+
 include::modules/digging-into-machine-config.adoc[leveloffset=+1]
--- a/architecture/architecture.adoc
+++ b/architecture/architecture.adoc
@@ -19,6 +19,7 @@ include::modules/architecture-kubernetes-introduction.adoc[leveloffset=+2]
 include::modules/architecture-container-application-benefits.adoc[leveloffset=+2]

 include::modules/architecture-platform-benefits.adoc[leveloffset=+2]
+
 ////
 == User facing components
 * Workloads (Deployments, Jobs, ReplicaSets, etc)
@@ -43,4 +44,5 @@ notification when an image is updated with a new version.

 ifndef::openshift-dedicated,openshift-rosa[]
 include::modules/cluster-entitlements.adoc[leveloffset=+2]
+
 endif::openshift-dedicated,openshift-rosa[]
--- a/architecture/control-plane.adoc
+++ b/architecture/control-plane.adoc
@@ -18,11 +18,13 @@ and a set of individual Operators.
 ifdef::openshift-rosa[]
 :FeatureName: This control plane architecture
 include::snippets/rosa-classic-support.adoc[]
+
 endif::openshift-rosa[]

 // This module does not apply to OSD/ROSA
 ifndef::openshift-dedicated,openshift-rosa[]
 include::modules/architecture-machine-config-pools.adoc[leveloffset=+1]
+
 endif::openshift-dedicated,openshift-rosa[]

 ifndef::openshift-dedicated,openshift-rosa[]
@@ -62,7 +64,9 @@ include::modules/etcd-overview.adoc[leveloffset=+1]
 // These modules only apply to ROSA/OSD
 ifdef::openshift-dedicated,openshift-rosa[]
 include::modules/cpmso-feat-auto-update.adoc[leveloffset=+1]
+
 include::modules/cpmso-control-plane-recovery.adoc[leveloffset=+1]
+
 endif::openshift-dedicated,openshift-rosa[]

 // These xrefs do not apply to OSD/ROSA
--- a/architecture/index.adoc
+++ b/architecture/index.adoc
@@ -32,6 +32,7 @@ endif::openshift-dedicated,openshift-rosa[]

 ifdef::openshift-dedicated,openshift-rosa[]
 include::modules/sd-vs-ocp.adoc[leveloffset=+1]
+
 endif::openshift-dedicated,openshift-rosa[]

 ifndef::openshift-dedicated,openshift-rosa[]
--- a/architecture/nvidia-gpu-architecture-overview.adoc
+++ b/architecture/nvidia-gpu-architecture-overview.adoc
@@ -24,26 +24,31 @@ ifndef::openshift-dedicated,openshift-rosa[]
 include::modules/nvidia-gpu-enablement.adoc[leveloffset=+1]

 include::modules/nvidia-gpu-bare-metal.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.nvidia.com/ai-enterprise/deployment-guide-openshift-on-bare-metal/0.1.0/on-bare-metal.html[Red Hat OpenShift on Bare Metal Stack]

 include::modules/nvidia-gpu-virtualization.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/openshift/openshift-virtualization.html[NVIDIA GPU Operator with OpenShift Virtualization]

 include::modules/nvidia-gpu-vsphere.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/openshift/nvaie-with-ocp.html#openshift-container-platform-on-vmware-vsphere-with-nvidia-vgpus[OpenShift Container Platform on VMware vSphere with NVIDIA vGPUs]

 include::modules/nvidia-gpu-kvm.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://computingforgeeks.com/how-to-deploy-openshift-container-platform-on-kvm/[How To Deploy OpenShift Container Platform 4.13 on KVM]

 include::modules/nvidia-gpu-csps.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.nvidia.com/ai-enterprise/deployment-guide-cloud/0.1.0/aws-redhat-openshift.html[Red Hat Openshift in the Cloud]
@@ -52,6 +57,7 @@ endif::openshift-dedicated,openshift-rosa[]
 // Include this module at a higher leveloffset for OSD/ROSA.
 ifdef::openshift-dedicated,openshift-rosa[]
 include::modules/nvidia-gpu-csps.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.nvidia.com/ai-enterprise/deployment-guide-cloud/0.1.0/aws-redhat-openshift.html[Red Hat Openshift in the Cloud]
@@ -59,6 +65,7 @@ endif::openshift-dedicated,openshift-rosa[]

 ifndef::openshift-dedicated,openshift-rosa[]
 include::modules/nvidia-gpu-red-hat-device-edge.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://cloud.redhat.com/blog/how-to-accelerate-workloads-with-nvidia-gpus-on-red-hat-device-edge[How to accelerate workloads with NVIDIA GPUs on Red Hat Device Edge]
@@ -66,28 +73,34 @@ endif::openshift-dedicated,openshift-rosa[]

 // TELCODOCS-1092 GPU sharing methods
 include::modules/nvidia-gpu-sharing-methods.adoc[leveloffset=+1]
+
 .Additional resources
 * link:https://developer.nvidia.com/blog/improving-gpu-utilization-in-kubernetes/[Improving GPU Utilization]

 include::modules/nvidia-gpu-cuda-streams.adoc[leveloffset=+2]
+
 .Additional resources
 * link:https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#asynchronous-concurrent-execution[Asynchronous Concurrent Execution]

 include::modules/nvidia-gpu-time-slicing.adoc[leveloffset=+2]

 include::modules/nvidia-gpu-cuda-mps.adoc[leveloffset=+2]
+
 .Additional resources
 * link:https://docs.nvidia.com/deploy/mps/index.html[CUDA MPS]

 include::modules/nvidia-gpu-mig-gpu.adoc[leveloffset=+2]
+
 .Additional resources
 * link:https://docs.nvidia.com/datacenter/tesla/mig-user-guide/[NVIDIA Multi-Instance GPU User Guide]

 include::modules/nvidia-gpu-virtualization-with-gpu.adoc[leveloffset=+2]
+
 .Additional resources
 * link:https://www.nvidia.com/en-us/data-center/virtual-solutions/[Virtual GPUs]

 include::modules/nvidia-gpu-features.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources

--- a/architecture/ocm-overview-ocp.adoc
+++ b/architecture/ocm-overview-ocp.adoc
@@ -44,11 +44,17 @@ Selecting an active, installed cluster shows tabs associated with that cluster.
 * Settings

 include::modules/ocm-overview-tab.adoc[leveloffset=+2]
+
 include::modules/ocm-accesscontrol-tab.adoc[leveloffset=+2]
+
 include::modules/ocm-addons-tab.adoc[leveloffset=+2]
+
 include::modules/ocm-insightsadvisor-tab.adoc[leveloffset=+2]
+
 include::modules/ocm-machinepools-tab.adoc[leveloffset=+2]
+
 include::modules/ocm-support-tab.adoc[leveloffset=+2]
+
 include::modules/ocm-settings-tab.adoc[leveloffset=+2]

 [id="ocm-additional-resources-ocp"]
--- a/authentication/assuming-an-aws-iam-role-for-a-service-account.adoc
+++ b/authentication/assuming-an-aws-iam-role-for-a-service-account.adoc
@@ -17,12 +17,19 @@ endif::openshift-rosa,openshift-rosa-hcp[]
 You can use the pod identity webhook to project service account tokens to assume an AWS Identity and Access Management (IAM) role for your own workloads. If the assumed IAM role has the required AWS permissions, the pods can run AWS SDK operations by using temporary STS credentials.

 include::modules/how-service-accounts-assume-aws-iam-roles-in-sre-owned-projects.adoc[leveloffset=+1]
+
 include::modules/understanding-pod-identity-webhook-workflow-in-user-defined-projects.adoc[leveloffset=+1]
+
 include::modules/assuming-an-aws-iam-role-in-your-own-pods.adoc[leveloffset=+1]
+
 include::modules/setting-up-an-aws-iam-role-a-service-account.adoc[leveloffset=+2]
+
 include::modules/creating-a-service-account-in-your-project.adoc[leveloffset=+2]
+
 include::modules/creating-an-example-aws-sdk-container-image.adoc[leveloffset=+2]
+
 include::modules/deploying-a-pod-that-includes-an-aws-sdk.adoc[leveloffset=+2]
+
 include::modules/verifying-the-assumed-iam-role-in-your-pod.adoc[leveloffset=+2]

 [role="_additional-resources"]
--- a/authentication/identity_providers/configuring-github-identity-provider.adoc
+++ b/authentication/identity_providers/configuring-github-identity-provider.adoc
@@ -17,6 +17,7 @@ The following steps apply to both GitHub and GitHub Enterprise unless noted.

 ifdef::openshift-origin,openshift-enterprise,openshift-webscale[]
 include::modules/identity-provider-overview.adoc[leveloffset=+1]
+
 endif::openshift-origin,openshift-enterprise,openshift-webscale[]

 include::modules/identity-provider-github-about.adoc[leveloffset=+1]
@@ -37,4 +38,5 @@ include::modules/identity-provider-github-CR.adoc[leveloffset=+1]
 * See xref:../../authentication/understanding-identity-provider.adoc#identity-provider-parameters_understanding-identity-provider[Identity provider parameters] for information on parameters, such as `mappingMethod`, that are common to all identity providers.

 include::modules/identity-provider-add.adoc[leveloffset=+1]
+
 endif::[]
--- a/authentication/identity_providers/configuring-gitlab-identity-provider.adoc
+++ b/authentication/identity_providers/configuring-gitlab-identity-provider.adoc
@@ -10,6 +10,7 @@ Configure the `gitlab` identity provider using link:https://gitlab.com/[GitLab.c

 ifdef::openshift-origin,openshift-enterprise,openshift-webscale[]
 include::modules/identity-provider-overview.adoc[leveloffset=+1]
+
 endif::openshift-origin,openshift-enterprise,openshift-webscale[]

 include::modules/identity-provider-gitlab-about.adoc[leveloffset=+1]
--- a/authentication/identity_providers/configuring-google-identity-provider.adoc
+++ b/authentication/identity_providers/configuring-google-identity-provider.adoc
@@ -10,6 +10,7 @@ Configure the `google` identity provider using the link:https://developers.googl

 ifdef::openshift-origin,openshift-enterprise,openshift-webscale[]
 include::modules/identity-provider-overview.adoc[leveloffset=+1]
+
 endif::openshift-origin,openshift-enterprise,openshift-webscale[]

 include::modules/identity-provider-google-about.adoc[leveloffset=+1]
@@ -26,4 +27,5 @@ include::modules/identity-provider-google-CR.adoc[leveloffset=+1]
 * See xref:../../authentication/understanding-identity-provider.adoc#identity-provider-parameters_understanding-identity-provider[Identity provider parameters] for information on parameters, such as `mappingMethod`, that are common to all identity providers.

 include::modules/identity-provider-add.adoc[leveloffset=+1]
+
 endif::[]
--- a/authentication/identity_providers/configuring-htpasswd-identity-provider.adoc
+++ b/authentication/identity_providers/configuring-htpasswd-identity-provider.adoc
@@ -19,6 +19,7 @@ the default OAuth configuration to add the identity provider.

 ifdef::openshift-origin,openshift-enterprise,openshift-webscale[]
 include::modules/identity-provider-overview.adoc[leveloffset=+1]
+
 endif::openshift-origin,openshift-enterprise,openshift-webscale[]

 include::modules/identity-provider-htpasswd-about.adoc[leveloffset=+1]
--- a/authentication/identity_providers/configuring-ldap-identity-provider.adoc
+++ b/authentication/identity_providers/configuring-ldap-identity-provider.adoc
@@ -10,6 +10,7 @@ Configure the `ldap` identity provider to validate user names and passwords agai

 ifdef::openshift-origin,openshift-enterprise,openshift-webscale[]
 include::modules/identity-provider-overview.adoc[leveloffset=+1]
+
 endif::openshift-origin,openshift-enterprise,openshift-webscale[]

 include::modules/identity-provider-about-ldap.adoc[leveloffset=+1]
@@ -28,4 +29,5 @@ include::modules/identity-provider-ldap-CR.adoc[leveloffset=+1]
 * See xref:../../authentication/understanding-identity-provider.adoc#identity-provider-parameters_understanding-identity-provider[Identity provider parameters] for information on parameters, such as `mappingMethod`, that are common to all identity providers.

 include::modules/identity-provider-add.adoc[leveloffset=+1]
+
 endif::[]
--- a/authentication/identity_providers/configuring-oidc-identity-provider.adoc
+++ b/authentication/identity_providers/configuring-oidc-identity-provider.adoc
@@ -10,12 +10,14 @@ Configure the `oidc` identity provider to integrate with an OpenID Connect ident

 ifdef::openshift-origin,openshift-enterprise,openshift-webscale[]
 include::modules/identity-provider-overview.adoc[leveloffset=+1]
+
 endif::openshift-origin,openshift-enterprise,openshift-webscale[]

 include::modules/identity-provider-oidc-about.adoc[leveloffset=+1]

 ifdef::openshift-enterprise[]
 include::modules/identity-provider-oidc-supported.adoc[leveloffset=+1]
+
 endif::openshift-enterprise[]

 ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
@@ -34,4 +36,5 @@ include::modules/identity-provider-oidc-CR.adoc[leveloffset=+1]
 include::modules/identity-provider-add.adoc[leveloffset=+1]

 include::modules/identity-provider-configuring-using-web-console.adoc[leveloffset=+1]
+
 endif::[]
--- a/authentication/ldap-syncing.adoc
+++ b/authentication/ldap-syncing.adoc
@@ -44,13 +44,21 @@ You must have `dedicated-admin` privileges to sync groups.
 endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]

 include::modules/ldap-syncing-about.adoc[leveloffset=+1]
+
 include::modules/ldap-syncing-config-rfc2307.adoc[leveloffset=+2]
+
 include::modules/ldap-syncing-config-activedir.adoc[leveloffset=+2]
+
 include::modules/ldap-syncing-config-augmented-activedir.adoc[leveloffset=+2]
+
 include::modules/ldap-syncing-running.adoc[leveloffset=+1]
+
 include::modules/ldap-syncing-running-all-ldap.adoc[leveloffset=+2]
+
 include::modules/ldap-syncing-running-openshift.adoc[leveloffset=+2]
+
 include::modules/ldap-syncing-running-subset.adoc[leveloffset=+2]
+
 include::modules/ldap-syncing-pruning.adoc[leveloffset=+1]

 // OSD and ROSA dedicated-admins cannot create the cluster roles and cluster role bindings required for this procedure.
@@ -66,10 +74,17 @@ include::modules/ldap-auto-syncing.adoc[leveloffset=+1]
 endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]

 include::modules/ldap-syncing-examples.adoc[leveloffset=+1]
+
 include::modules/ldap-syncing-rfc2307.adoc[leveloffset=+2]
+
 include::modules/ldap-syncing-rfc2307-user-defined.adoc[leveloffset=+2]
+
 include::modules/ldap-syncing-rfc2307-user-defined-error.adoc[leveloffset=+2]
+
 include::modules/ldap-syncing-activedir.adoc[leveloffset=+2]
+
 include::modules/ldap-syncing-augmented-activedir.adoc[leveloffset=+2]
+
 include::modules/ldap-syncing-nesting.adoc[leveloffset=+2]
+
 include::modules/ldap-syncing-spec.adoc[leveloffset=+1]
--- a/authentication/managing-security-context-constraints.adoc
+++ b/authentication/managing-security-context-constraints.adoc
@@ -34,13 +34,18 @@ In {product-title} deployments, you can create your own SCCs only for clusters t
 endif::openshift-dedicated[]

 include::modules/security-context-constraints-about.adoc[leveloffset=+1]
+
 include::modules/security-context-constraints-pre-allocated-values.adoc[leveloffset=+1]
+
 include::modules/security-context-constraints-example.adoc[leveloffset=+1]
+
 include::modules/security-context-constraints-creating.adoc[leveloffset=+1]

 //  Configuring a workload to require a specific SCC
 include::modules/security-context-constraints-requiring.adoc[leveloffset=+1]
+
 include::modules/security-context-constraints-rbac.adoc[leveloffset=+1]
+
 include::modules/security-context-constraints-command-reference.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/authentication/understanding-and-managing-pod-security-admission.adoc
+++ b/authentication/understanding-and-managing-pod-security-admission.adoc
@@ -37,6 +37,7 @@ include::modules/security-context-constraints-psa-rectifying.adoc[leveloffset=+1
 ifndef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
 // Identifying pod security violations
 include::modules/security-context-constraints-psa-alert-eval.adoc[leveloffset=+2]
+
 endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]

 [role="_additional-resources"]
--- a/authentication/understanding-authentication.adoc
+++ b/authentication/understanding-authentication.adoc
@@ -29,4 +29,5 @@ ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
 include::modules/authentication-api-impersonation.adoc[leveloffset=+3]

 include::modules/authentication-prometheus-system-metrics.adoc[leveloffset=+3]
+
 endif::[]
--- a/authentication/using-rbac.adoc
+++ b/authentication/using-rbac.adoc
@@ -22,25 +22,31 @@ ifdef::openshift-enterprise,openshift-webscale,openshift-origin,openshift-dedica
 include::modules/rbac-creating-local-role.adoc[leveloffset=+1]

 include::modules/rbac-creating-cluster-role.adoc[leveloffset=+1]
+
 endif::[]

 include::modules/rbac-local-role-binding-commands.adoc[leveloffset=+1]

 ifdef::openshift-enterprise,openshift-webscale,openshift-origin,openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
 include::modules/rbac-cluster-role-binding-commands.adoc[leveloffset=+1]
+
 endif::[]

 ifndef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
 include::modules/rbac-creating-cluster-admin.adoc[leveloffset=+1]
+
 endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]

 ifdef::openshift-rosa,openshift-rosa-hcp[]
 include::modules/rosa-create-cluster-admins.adoc[leveloffset=+1]
+
 include::modules/rosa-create-dedicated-cluster-admins.adoc[leveloffset=+1]
+
 endif::openshift-rosa,openshift-rosa-hcp[]

 ifdef::openshift-dedicated[]
 include::modules/osd-grant-admin-privileges.adoc[leveloffset=+1]
+
 endif::openshift-dedicated[]

 include::modules/unauthenticated-users-cluster-role-binding-con.adoc[leveloffset=+1]
--- a/backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc
+++ b/backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.adoc
@@ -33,5 +33,7 @@ include::modules/backup-etcd.adoc[leveloffset=+1]

 // Creating automated etcd backups
 include::modules/etcd-creating-automated-backups.adoc[leveloffset=+1]
+
 include::modules/creating-single-etcd-backup.adoc[leveloffset=+2]
+
 include::modules/creating-recurring-etcd-backups.adoc[leveloffset=+2]
--- a/backup_and_restore/control_plane_backup_and_restore/disaster_recovery/about-disaster-recovery.adoc
+++ b/backup_and_restore/control_plane_backup_and_restore/disaster_recovery/about-disaster-recovery.adoc
@@ -51,6 +51,7 @@ expired control plane certificates.

 // Testing restore procedures
 include::modules/dr-testing-restore-procedures.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources
 * xref:../../../backup_and_restore/control_plane_backup_and_restore/disaster_recovery/scenario-2-restoring-cluster-state.adoc#dr-restoring-cluster-state[Restoring to a previous cluster state]
--- a/backup_and_restore/control_plane_backup_and_restore/replacing-unhealthy-etcd-member.adoc
+++ b/backup_and_restore/control_plane_backup_and_restore/replacing-unhealthy-etcd-member.adoc
@@ -44,6 +44,7 @@ Depending on the state of your unhealthy etcd member, use one of the following p

 // Replacing an unhealthy etcd member whose machine is not running or whose node is not ready
 include::modules/restore-replace-stopped-etcd-member.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * xref:../../machine_management/control_plane_machine_management/cpmso-troubleshooting.adoc#cpmso-ts-etcd-degraded_cpmso-troubleshooting[Recovering a degraded etcd Operator]
--- a/cli_reference/openshift_cli/getting-started-cli.adoc
+++ b/cli_reference/openshift_cli/getting-started-cli.adoc
@@ -33,6 +33,7 @@ include::modules/cli-installing-cli-web-console-macos.adoc[leveloffset=+3]
 ifndef::openshift-origin[]
 // Installing the CLI by using an RPM
 include::modules/cli-installing-cli-rpm.adoc[leveloffset=+2]
+
 endif::[]

 // Installing the CLI by using Homebrew
--- a/cli_reference/opm/cli-opm-install.adoc
+++ b/cli_reference/opm/cli-opm-install.adoc
@@ -17,6 +17,7 @@ ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]

 include::modules/olm-installing-opm.adoc[leveloffset=+1]
+
 ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 [role="_additional-resources"]
 [id="opm-addtl-resources"]
--- a/cli_reference/opm/cli-opm-ref.adoc
+++ b/cli_reference/opm/cli-opm-ref.adoc
@@ -36,6 +36,7 @@ The `opm` CLI is not forward compatible. The version of the `opm` CLI used to ge
 include::snippets/deprecated-feature.adoc[]

 include::modules/opm-cli-ref-generate.adoc[leveloffset=+1]
+
 include::modules/opm-cli-ref-index.adoc[leveloffset=+1]

 ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
@@ -48,7 +49,11 @@ ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
 endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]

 include::modules/opm-cli-ref-init.adoc[leveloffset=+1]
+
 include::modules/opm-cli-ref-migrate.adoc[leveloffset=+1]
+
 include::modules/opm-cli-ref-render.adoc[leveloffset=+1]
+
 include::modules/opm-cli-ref-serve.adoc[leveloffset=+1]
+
 include::modules/opm-cli-ref-validate.adoc[leveloffset=+1]
--- a/cli_reference/tkn_cli/installing-tkn.adoc
+++ b/cli_reference/tkn_cli/installing-tkn.adoc
@@ -32,6 +32,7 @@ endif::openshift-rosa,openshift-dedicated[]
 ifndef::openshift-rosa,openshift-dedicated[]
 :FeatureName: Running {pipelines-title} with the `opc` CLI tool
 include::snippets/technology-preview.adoc[]
+
 endif::openshift-rosa,openshift-dedicated[]
 // Install tkn on Linux
 include::modules/op-installing-tkn-on-linux.adoc[leveloffset=+1]
--- a/disconnected/about-installing-oc-mirror-v2.adoc
+++ b/disconnected/about-installing-oc-mirror-v2.adoc
@@ -59,7 +59,9 @@ include::modules/oc-mirror-workflows-partially-disconnected-v2.adoc[leveloffset=

 //Mirroring an image set in a fully disconnected environment:
 include::modules/oc-mirror-workflows-fully-disconnected-v2.adoc[leveloffset=+2]
+
 include::modules/oc-mirror-mirror-to-disk-v2.adoc[leveloffset=+2]
+
 include::modules/oc-mirror-disk-to-mirror-v2.adoc[leveloffset=+2]

 // About custom resources generated by oc-mirror plugin v2
@@ -126,7 +128,9 @@ include::modules/oc-mirror-proxy-support.adoc[leveloffset=+1]

 //signature mirroring
 include::modules/oc-mirror-signature-mirroring.adoc[leveloffset=+1]
+
 include::modules/oc-mirror-signature-mirroring-procedure.adoc[leveloffset=+2]
+
 include::modules/oc-mirror-signature-verification.adoc[leveloffset=+2]

 // Operator catalog filtering
@@ -137,7 +141,9 @@ include::modules/oc-mirror-imageset-config-parameters-v2.adoc[leveloffset=+1]

 // Command reference for oc-mirror v2
 include::modules/oc-mirror-command-reference-v2.adoc[leveloffset=+1]
+
 include::modules/oc-mirror-command-reference-v2-delete.adoc[leveloffset=+2]
+
 include::modules/oc-mirror-about-cache-and-workspace-dirs.adoc[leveloffset=+2]

 [role="_additional-resources"]
--- a/disconnected/connected-to-disconnected.adoc
+++ b/disconnected/connected-to-disconnected.adoc
@@ -41,6 +41,7 @@ If you have a subscription to Red{nbsp}Hat Quay, see the documentation on deploy
 * Access to the internet to obtain the necessary container images.

 include::modules/connected-to-disconnected-prepare-mirror.adoc[leveloffset=+1]
+
 include::modules/connected-to-disconnected-mirror-images.adoc[leveloffset=+1]

 [role="_additional-resources"]
@@ -50,7 +51,9 @@ include::modules/connected-to-disconnected-mirror-images.adoc[leveloffset=+1]
 * For more information about the `oc adm catalog mirror` command, see the xref:../cli_reference/openshift_cli/administrator-cli-commands.adoc#oc-adm-catalog-mirror[OpenShift CLI administrator command reference].

 include::modules/connected-to-disconnected-config-registry.adoc[leveloffset=+1]
+
 include::modules/connected-to-disconnected-verify.adoc[leveloffset=+1]
+
 include::modules/connected-to-disconnected-disconnect.adoc[leveloffset=+1]

 [NOTE]
@@ -59,4 +62,5 @@ The {insights-operator} is degraded when the cluster loses its Internet connecti
 ====

 include::modules/connected-to-disconnected-restore-insights.adoc[leveloffset=+1]
+
 include::modules/connected-to-disconnected-restore.adoc[leveloffset=+1]
--- a/disconnected/installing-mirroring-creating-registry.adoc
+++ b/disconnected/installing-mirroring-creating-registry.adoc
@@ -34,18 +34,31 @@ The _mirror registry for Red{nbsp}Hat OpenShift_ is not intended to be a substit
 ====

 include::modules/mirror-registry-introduction.adoc[leveloffset=+1]
+
 include::modules/mirror-registry-localhost.adoc[leveloffset=+1]
+
 include::modules/mirror-registry-localhost-update.adoc[leveloffset=+1]
+
 include::modules/mirror-registry-remote.adoc[leveloffset=+1]
+
 include::modules/mirror-registry-remote-host-update.adoc[leveloffset=+1]
+
 include::modules/mirror-registry-ssl-cert-replace.adoc[leveloffset=+1]
+
 include::modules/mirror-registry-uninstall.adoc[leveloffset=+1]
+
 include::modules/mirror-registry-flags.adoc[leveloffset=+1]
+
 include::modules/mirror-registry-release-notes.adoc[leveloffset=+1]
+
 include::modules/mirror-registry-release-notes-2-0.adoc[leveloffset=+2]
+
 include::modules/mirror-registry-release-notes-1-3.adoc[leveloffset=+2]
+
 include::modules/mirror-registry-release-notes-1-2.adoc[leveloffset=+2]
+
 include::modules/mirror-registry-release-notes-1-1.adoc[leveloffset=+2]
+
 include::modules/mirror-registry-troubleshooting.adoc[leveloffset=+1]

 [id="additional-resources_installing-mirroring-creating-registry"]
--- a/disconnected/installing-mirroring-installation-images.adoc
+++ b/disconnected/installing-mirroring-installation-images.adoc
@@ -117,11 +117,13 @@ $ REG_CREDS=${XDG_RUNTIME_DIR}/containers/auth.json
 ----

 include::modules/olm-mirroring-catalog-extracting.adoc[leveloffset=+2]
+
 include::modules/olm-mirroring-catalog-colocated.adoc[leveloffset=+3]

 include::modules/olm-mirroring-catalog-airgapped.adoc[leveloffset=+3]

 include::modules/olm-mirroring-catalog-manifests.adoc[leveloffset=+2]
+
 include::modules/olm-mirroring-catalog-post.adoc[leveloffset=+2]

 [role="_additional-resources"]
--- a/etcd/etcd-backup-restore/etcd-backup.adoc
+++ b/etcd/etcd-backup-restore/etcd-backup.adoc
@@ -32,5 +32,7 @@ include::modules/backup-etcd.adoc[leveloffset=+1]

 // Creating automated etcd backups
 include::modules/etcd-creating-automated-backups.adoc[leveloffset=+1]
+
 include::modules/creating-single-etcd-backup.adoc[leveloffset=+2]
+
 include::modules/creating-recurring-etcd-backups.adoc[leveloffset=+2]
--- a/extensions/arch/catalogd.adoc
+++ b/extensions/arch/catalogd.adoc
@@ -9,6 +9,7 @@ toc::[]
 {olmv1-first} uses the catalogd component and its resources to manage Operator and extension catalogs.

 include::modules/olmv1-about-catalogs.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources
 * xref:../../extensions/catalogs/fbc.adoc#fbc[File-based catalogs]
--- a/extensions/arch/operator-controller.adoc
+++ b/extensions/arch/operator-controller.adoc
@@ -9,6 +9,7 @@ toc::[]
 Operator Controller is the central component of {olmv1-first} and consumes the other {olmv1} component, catalogd. It extends Kubernetes with an API through which users can install Operators and extensions.

 include::modules/olmv1-clusterextension-api.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources

--- a/extensions/catalogs/fbc.adoc
+++ b/extensions/catalogs/fbc.adoc
@@ -13,17 +13,24 @@ include::modules/olm-fb-catalogs.adoc[leveloffset=+1]
 include::modules/olm-fb-catalogs-structure.adoc[leveloffset=+1]

 include::modules/olm-fb-catalogs-schemas.adoc[leveloffset=+1]
+
 include::modules/olm-package-schema.adoc[leveloffset=+2]
+
 include::modules/olm-channel-schema.adoc[leveloffset=+2]
+
 include::modules/olm-bundle-schema.adoc[leveloffset=+2]
+
 include::modules/olm-deprecations-schema.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources

 * xref:../../operators/admin/olm-managing-custom-catalogs.adoc#olm-filtering-fbc_olm-managing-custom-catalogs[Updating or filtering a file-based catalog image]

 include::modules/olm-fb-catalogs-prop.adoc[leveloffset=+1]
+
 include::modules/olm-fb-catalogs-example.adoc[leveloffset=+1]
+
 include::modules/olm-fb-catalogs-guidelines.adoc[leveloffset=+1]

 [id="olm-fb-catalogs-cli"]
--- a/extensions/catalogs/managing-catalogs.adoc
+++ b/extensions/catalogs/managing-catalogs.adoc
@@ -24,6 +24,9 @@ include::modules/olmv1-about-catalogs.adoc[leveloffset=+1]
 * xref:../../extensions/catalogs/fbc.adoc#fbc[File-based catalogs]

 include::modules/olmv1-red-hat-catalogs.adoc[leveloffset=+1]
+
 include::modules/olmv1-adding-a-catalog.adoc[leveloffset=+1]
+
 include::modules/olmv1-deleting-catalog.adoc[leveloffset=+1]
+
 include::modules/olmv1-disabling-a-default-catalog.adoc[leveloffset=+1]
--- a/extensions/ce/crd-upgrade-safety.adoc
+++ b/extensions/ce/crd-upgrade-safety.adoc
@@ -13,6 +13,9 @@ When you update a custom resource definition (CRD) that is provided by a cluster
 * xref:../../extensions/ce/managing-ce.adoc#olmv1-updating-an-operator_managing-ce[Updating a cluster extension]

 include::modules/prohibited-crd-upgrades.adoc[leveloffset=+1]
+
 include::modules/allowed-crd-upgrades.adoc[leveloffset=+1]
+
 include::modules/disabling-crd-preflight.adoc[leveloffset=+1]
+
 include::modules/examples-unsafe-crd-upgrades.adoc[leveloffset=+1]
--- a/extensions/ce/update-paths.adoc
+++ b/extensions/ce/update-paths.adoc
@@ -41,7 +41,9 @@ If `1.0.0` is installed, {olmv1} behavior differs in the following ways:
 include::modules/olmv1-version-range-support.adoc[leveloffset=+1]

 include::modules/olmv1-version-range-comparisons.adoc[leveloffset=+1]
+
 include::modules/olmv1-about-target-versions.adoc[leveloffset=+1]
+
 include::modules/olmv1-forcing-an-update-or-rollback.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/extensions/ce/user-access-resources.adoc
+++ b/extensions/ce/user-access-resources.adoc
@@ -26,7 +26,9 @@ include::modules/olmv1-default-cluster-roles-users.adoc[leveloffset=+1]
 * link:https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles[User-facing roles] (Kubernetes documentation)

 include::modules/olmv1-finding-ce-resources.adoc[leveloffset=+1]
+
 include::modules/olmv1-granting-user-access-binding.adoc[leveloffset=+1]
+
 include::modules/olmv1-granting-user-access-aggregated.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/hardware_accelerators/das-about-dynamic-accelerator-slicer-operator.adoc
+++ b/hardware_accelerators/das-about-dynamic-accelerator-slicer-operator.adoc
@@ -38,6 +38,7 @@ include::modules/das-operator-installing.adoc[leveloffset=+1]

 //Installing the Dynamic Accelerator Slicer Operator using the web console
 include::modules/das-operator-installing-web-console.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 ** xref:../security/cert_manager_operator/cert-manager-operator-install.adoc#cert-manager-operator-install[{cert-manager-operator}]
@@ -48,6 +49,7 @@ include::modules/das-operator-installing-web-console.adoc[leveloffset=+2]

 //Installing the Dynamic Accelerator Slicer Operator using the CLI
 include::modules/das-operator-installing-cli.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * xref:../security/cert_manager_operator/cert-manager-operator-install.adoc#cert-manager-operator-install[{cert-manager-operator}]
--- a/hardware_accelerators/nvidia-gpu-architecture.adoc
+++ b/hardware_accelerators/nvidia-gpu-architecture.adoc
@@ -24,17 +24,21 @@ include::modules/nvidia-gpu-prerequisites.adoc[leveloffset=+1]
 // New enablement modules
 ifndef::openshift-dedicated,openshift-rosa[]
 include::modules/nvidia-gpu-enablement.adoc[leveloffset=+1]
+
 include::modules/nvidia-gpu-bare-metal.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.nvidia.com/ai-enterprise/deployment-guide-openshift-on-bare-metal/0.1.0/on-bare-metal.html[Red Hat OpenShift on Bare Metal Stack]

 include::modules/nvidia-gpu-virtualization.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/openshift/openshift-virtualization.html[NVIDIA GPU Operator with OpenShift Virtualization]

 include::modules/nvidia-gpu-vsphere.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/openshift/nvaie-with-ocp.html#openshift-container-platform-on-vmware-vsphere-with-nvidia-vgpus[OpenShift Container Platform on VMware vSphere with NVIDIA vGPUs]
@@ -43,6 +47,7 @@ include::modules/nvidia-gpu-vsphere.adoc[leveloffset=+2]
 include::modules/nvidia-gpu-kvm.adoc[leveloffset=+2]

 include::modules/nvidia-gpu-csps.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.nvidia.com/ai-enterprise/deployment-guide-cloud/0.1.0/aws-redhat-openshift.html[Red Hat Openshift in the Cloud]
@@ -51,6 +56,7 @@ endif::openshift-dedicated,openshift-rosa[]
 // Include this module at a higher leveloffset for OSD/ROSA.
 ifdef::openshift-dedicated,openshift-rosa[]
 include::modules/nvidia-gpu-csps.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.nvidia.com/ai-enterprise/deployment-guide-cloud/0.1.0/aws-redhat-openshift.html[Red Hat Openshift in the Cloud]
@@ -58,6 +64,7 @@ endif::openshift-dedicated,openshift-rosa[]

 ifndef::openshift-dedicated,openshift-rosa[]
 include::modules/nvidia-gpu-red-hat-device-edge.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://cloud.redhat.com/blog/how-to-accelerate-workloads-with-nvidia-gpus-on-red-hat-device-edge[How to accelerate workloads with NVIDIA GPUs on Red Hat Device Edge]
@@ -65,28 +72,34 @@ endif::openshift-dedicated,openshift-rosa[]

 // TELCODOCS-1092 GPU sharing methods
 include::modules/nvidia-gpu-sharing-methods.adoc[leveloffset=+1]
+
 .Additional resources
 * link:https://developer.nvidia.com/blog/improving-gpu-utilization-in-kubernetes/[Improving GPU Utilization]

 include::modules/nvidia-gpu-cuda-streams.adoc[leveloffset=+2]
+
 .Additional resources
 * link:https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#asynchronous-concurrent-execution[Asynchronous Concurrent Execution]

 include::modules/nvidia-gpu-time-slicing.adoc[leveloffset=+2]

 include::modules/nvidia-gpu-cuda-mps.adoc[leveloffset=+2]
+
 .Additional resources
 * link:https://docs.nvidia.com/deploy/mps/index.html[CUDA MPS]

 include::modules/nvidia-gpu-mig-gpu.adoc[leveloffset=+2]
+
 .Additional resources
 * link:https://docs.nvidia.com/datacenter/tesla/mig-user-guide/[NVIDIA Multi-Instance GPU User Guide]

 include::modules/nvidia-gpu-virtualization-with-gpu.adoc[leveloffset=+2]
+
 .Additional resources
 * link:https://www.nvidia.com/en-us/data-center/virtual-solutions/[Virtual GPUs]

 include::modules/nvidia-gpu-features.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources

--- a/hardware_enablement/kmm-kernel-module-management.adoc
+++ b/hardware_enablement/kmm-kernel-module-management.adoc
@@ -11,20 +11,27 @@ Learn about the Kernel Module Management (KMM) Operator and how you can use it t
 :FeatureName: Kernel Module Management Operator

 include::modules/kmm-about-kmm.adoc[leveloffset=+1]
+
 include::modules/kmm-installation.adoc[leveloffset=+1]
+
 include::modules/kmm-installing-using-web-console.adoc[leveloffset=+2]
+
 include::modules/kmm-installing-using-cli.adoc[leveloffset=+2]
+
 include::modules/kmm-installing-older-versions.adoc[leveloffset=+2]

 // Added for TELCODOCS-1823
 include::modules/kmm-configuring-kmmo.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources

 * For more information, see xref:../hardware_enablement/kmm-kernel-module-management.adoc#kmm-install_kernel-module-management-operator[Installing the Kernel Module Management Operator].

 include::modules/kmm-unloading-kernel-module.adoc[leveloffset=+2]
+
 include::modules/kmm-setting-kernel-firmware-search-path.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources

@@ -32,14 +39,18 @@ include::modules/kmm-setting-kernel-firmware-search-path.adoc[leveloffset=+2]

 // Added for TELCODOCS-1309
 include::modules/kmm-uninstalling-kmm.adoc[leveloffset=+1]
+
 include::modules/kmm-uninstalling-kmmo-red-hat-catalog.adoc[leveloffset=+2]
+
 include::modules/kmm-uninstalling-kmmo-cli.adoc[leveloffset=+2]

 include::modules/kmm-deploying-modules.adoc[leveloffset=+1]
+
 include::modules/kmm-creating-module-cr.adoc[leveloffset=+2]

 // Added for TELCODOCS-1280
 include::modules/kmm-setting-soft-dependencies-between-kernel-modules.adoc[leveloffset=+2]
+
 include::modules/kmm-security.adoc[leveloffset=+1]

 [role="_additional-resources"]
@@ -54,6 +65,7 @@ include::modules/kmm-replacing-in-tree-modules-with-out-of-tree-modules.adoc[lev
 * link:https://fastbitlab.com/building-a-linux-kernel-module/[Building a linux kernel module]

 include::modules/kmm-example-module-cr.adoc[leveloffset=+2]
+
 // Added for MGMT-16631
 [role="_additional-resources"]
 .Additional resources
@@ -66,6 +78,7 @@ include::modules/kmm-using-intree-modules.adoc[leveloffset=+1]
 include::modules/kmm-symbolic-links-for-in-tree-dependencies.adoc[leveloffset=+1]

 include::modules/kmm-creating-kmod-image.adoc[leveloffset=+1]
+
 include::modules/kmm-running-depmod.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -99,10 +112,15 @@ include::modules/kmm-using-driver-toolkit.adoc[leveloffset=+2]

 // Added for TELCODOCS-1065
 include::modules/kmm-using-signing-with-kmm.adoc[leveloffset=+1]
+
 include::modules/kmm-adding-the-keys-for-secureboot.adoc[leveloffset=+1]
+
 include::modules/kmm-checking-the-keys.adoc[leveloffset=+2]
+
 include::modules/kmm-signing-kmods-in-a-prebuilt-image.adoc[leveloffset=+1]
+
 include::modules/kmm-building-and-signing-a-kmod-image.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources

@@ -110,31 +128,38 @@ include::modules/kmm-building-and-signing-a-kmod-image.adoc[leveloffset=+1]

 // Added for TELCODOCS-2197
 include::modules/kmm-using-tolerations-for-kernel-module-scheduling.adoc[leveloffset=+1]
+
 include::modules/kmm-applying-tolerations-to-kernel-module-pods.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://docs.openshift.com/container-platform/4.17/nodes/scheduling/nodes-scheduler-taints-tolerations.html#nodes-scheduler-taints-tolerations-about_nodes-scheduler-taints-tolerations[Understanding taints and tolerations]

 // Added for TELCODOCS-1109
 include::modules/kmm-hub-hub-and-spoke.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://www.redhat.com/en/technologies/management/advanced-cluster-management[Red{nbsp}Hat Advanced Cluster Management (RHACM)]

 include::modules/kmm-hub-kmm-hub.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://openshift-kmm.netlify.app/documentation/install/[Installing KMM]

 include::modules/kmm-hub-installing-kmm-hub.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * link:https://catalog.redhat.com/software/containers/kmm/kernel-module-management-hub-operator-bundle/63d84cc33862da54bb19b8c6?architecture=amd64&image=654273ac86f7e537ae452f6ehttps://catalog.redhat.com/software/containers/kmm/kernel-module-management-hub-operator-bundle/63d84cc33862da54bb19b8c6?architecture=amd64&image=654273ac86f7e537ae452f6e[KMM Operator bundle]

 include::modules/kmm-hub-installing-kmm-hub-olm.adoc[leveloffset=+3]
+
 include::modules/kmm-hub-installing-kmm-hub-creating-resources.adoc[leveloffset=+3]

 include::modules/kmm-hub-using-the-managedclustermodule.adoc[leveloffset=+2]
+
 include::modules/kmm-hub-running-kmm-on-the-spoke.adoc[leveloffset=+2]

 // Added for TELCODOCS-1277
@@ -142,19 +167,25 @@ include::modules/kmm-customizing-upgrades-for-kernel-modules.adoc[leveloffset=+1

 // Added for TELCODOCS-1278
 include::modules/kmm-day1-kernel-module-loading.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources
 * xref:../machine_configuration/index.adoc#machine-config-index[Machine Config Operator]

 include::modules/kmm-day1-supported-use-cases.adoc[leveloffset=+2]
+
 include::modules/kmm-day1-oot-kernel-module-loading-flow.adoc[leveloffset=+2]
+
 include::modules/kmm-day1-kernel-module-image.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * xref:../hardware_enablement/psap-driver-toolkit.adoc#driver-toolkit[Driver Toolkit]

 include::modules/kmm-day1-in-tree-module-replacement.adoc[leveloffset=+2]
+
 include::modules/kmm-day1-mco-yaml-creation.adoc[leveloffset=+2]
+
 include::modules/kmm-day1-machineconfigpool.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -165,31 +196,40 @@ include::modules/kmm-debugging-and-troubleshooting.adoc[leveloffset=+1]

 // Added for TELCODOCS-1067
 include::modules/kmm-firmware-support.adoc[leveloffset=+1]
+
 [role="_additional-resources"]

 include::modules/kmm-configuring-the-lookup-path-on-nodes.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * xref:../machine_configuration/index.adoc#machine-config-operator_machine-config-overview[Machine Config Operator].

 include::modules/kmm-building-a-kmod-image.adoc[leveloffset=+2]
+
 include::modules/kmm-tuning-the-module-resource.adoc[leveloffset=+2]

 // Added for TELCODOCS-1826
 include::modules/kmm-day0-day2-installation.adoc[leveloffset=+1]
+
 include::modules/kmm-layering-background.adoc[leveloffset=+2]
+
 include::modules/kmm-day0-day2-lifecycle-management.adoc[leveloffset=+2]

 // Added for TELCODOCS-1059
 include::modules/kmm-troubleshooting.adoc[leveloffset=+1]
+
 // Added for TELCODOCS-1820
 include::modules/kmm-reading-operator-logs.adoc[leveloffset=+2]
+
 include::modules/kmm-observing-events.adoc[leveloffset=+2]

 include::modules/kmm-must-gather-tool.adoc[leveloffset=+2]
+
 [role="_additional-resources"]
 .Additional resources
 * xref:../support/gathering-cluster-data.adoc#about-must-gather_gathering-cluster-data[About the must-gather tool]

 include::modules/kmm-gathering-data-for-kmm.adoc[leveloffset=+3]
+
 include::modules/kmm-gathering-data-for-kmm-hub.adoc[leveloffset=+3]
--- a/hardware_enablement/psap-node-feature-discovery-operator.adoc
+++ b/hardware_enablement/psap-node-feature-discovery-operator.adoc
@@ -26,7 +26,9 @@ Starting with version 4.12, the `operand.image` field in the `NodeFeatureDiscove
 ====

 include::modules/creating-nfd-cr-cli.adoc[leveloffset=+2]
+
 include::modules/creating-nfd-cr-cli-disconnected.adoc[leveloffset=+2]
+
 include::modules/creating-nfd-cr-web-console.adoc[leveloffset=+2]

 include::modules/psap-configuring-node-feature-discovery.adoc[leveloffset=+1]
--- a/hosted_control_planes/hcp-authentication-authorization.adoc
+++ b/hosted_control_planes/hcp-authentication-authorization.adoc
@@ -28,6 +28,7 @@ The CCO supports a manual mode only for hosted clusters on {aws-short}. By defau
 ====

 include::modules/hcp-cco-verify-aws-sts.adoc[leveloffset=+1]
+
 include::modules/osdk-cco-aws-sts-enabling.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/hosted_control_planes/hcp-deploy/hcp-deploy-aws.adoc
+++ b/hosted_control_planes/hcp-deploy/hcp-deploy-aws.adoc
@@ -11,7 +11,9 @@ A _hosted cluster_ is an {product-title} cluster with its API endpoint and contr
 You can use the {mce-short} console or the hosted control plane command-line interface (CLI), `hcp`, to create a hosted cluster. The hosted cluster is automatically imported as a managed cluster. However, you can xref:../../hosted_control_planes/hcp-import.adoc#hcp-import-disable_hcp-import[disable this automatic import feature into {mce-short}].

 include::modules/hcp-aws-prepare.adoc[leveloffset=+1]
+
 include::modules/hcp-aws-prereqs.adoc[leveloffset=+2]
+
 include::modules/hcp-access-hc-aws-hcpcli.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc
+++ b/hosted_control_planes/hcp-deploy/hcp-deploy-ibmz.adoc
@@ -41,6 +41,7 @@ include::modules/hcp-ibm-z-infra-reqs.adoc[leveloffset=+1]
 * xref:../../hosted_control_planes/hcp-prepare/hcp-enable-disable.adoc[Enabling or disabling the {hcp} feature]

 include::modules/hcp-ibm-z-dns.adoc[leveloffset=+1]
+
 include::modules/hcp-custom-dns.adoc[leveloffset=+2]

 include::modules/hcp-bm-hc.adoc[leveloffset=+1]
@@ -61,6 +62,7 @@ To attach compute nodes to a hosted control plane, create agents that help you t
 Unless stated otherwise, these procedures apply to both z/VM and RHEL KVM installations on {ibm-z-title} and {ibm-linuxone-title}.

 include::modules/hcp-ibm-z-kvm-agents.adoc[leveloffset=+2]
+
 include::modules/hcp-ibm-z-lpar-agents.adoc[leveloffset=+2]

 [role="_additional-resources"]
--- a/hosted_control_planes/hcp-deploy/hcp-deploy-virt.adoc
+++ b/hosted_control_planes/hcp-deploy/hcp-deploy-virt.adoc
@@ -53,7 +53,9 @@ include::modules/hcp-virt-live-migration.adoc[leveloffset=+1]
 With {product-title} 4.14 and later, you can create a cluster with KubeVirt, to include creating with an external infrastructure.

 include::modules/hcp-virt-create-hc-cli.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-create-hc-ext-infra.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-create-hc-console.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -64,6 +66,7 @@ include::modules/hcp-virt-create-hc-console.adoc[leveloffset=+2]
 * xref:../../hosted_control_planes/hcp-manage/hcp-manage-virt.adoc#hcp-virt-access_hcp-manage-virt[Accessing the hosted cluster]

 include::modules/hcp-virt-ingress-dns.adoc[leveloffset=+1]
+
 include::modules/hcp-custom-dns.adoc[leveloffset=+2]

 [id="hcp-virt-ingress-dns-custom"]
@@ -72,7 +75,9 @@ include::modules/hcp-custom-dns.adoc[leveloffset=+2]
 If you do not want to use the default ingress and DNS behavior, you can configure a KubeVirt hosted cluster with a unique base domain at creation time. This option requires manual configuration steps during creation and involves three main steps: cluster creation, load balancer creation, and wildcard DNS configuration.

 include::modules/hcp-virt-hc-base-domain.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-load-balancer.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-wildcard-dns.adoc[leveloffset=+2]

 include::modules/hcp-metallb.adoc[leveloffset=+1]
@@ -88,11 +93,15 @@ include::modules/hcp-metallb.adoc[leveloffset=+1]
 If you need to configure additional networks for node pools, request a guaranteed CPU access for Virtual Machines (VMs), or manage scheduling of KubeVirt VMs, see the following procedures.

 include::modules/hcp-virt-add-networks.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-addl-network.adoc[leveloffset=+3]
+
 include::modules/hcp-virt-guaranteed-cpus.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-sched-vms.adoc[leveloffset=+2]

 include::modules/hcp-virt-scale-nodepool.adoc[leveloffset=+1]
+
 include::modules/hcp-virt-add-node.adoc[leveloffset=+2]

 [role="_additional-resources"]
--- a/hosted_control_planes/hcp-destroy/hcp-destroy-bm.adoc
+++ b/hosted_control_planes/hcp-destroy/hcp-destroy-bm.adoc
@@ -9,4 +9,5 @@ toc::[]
 You can destroy hosted clusters on bare metal by using the command-line interface (CLI) or the {mce-short} web console.

 include::modules/destroy-hc-bm-cli.adoc[leveloffset=+1]
+
 include::modules/destroy-hc-bm-console.adoc[leveloffset=+1]
--- a/hosted_control_planes/hcp-disconnected/hcp-dc-monitor.adoc
+++ b/hosted_control_planes/hcp-disconnected/hcp-dc-monitor.adoc
@@ -9,5 +9,7 @@ toc::[]
 The `hypershift-addon` managed cluster add-on enables the `--enable-uwm-telemetry-remote-write` option in the HyperShift Operator. By enabling that option, you ensure that user workload monitoring is enabled and that it can remotely write telemetry metrics from control planes. 

 include::modules/hcp-dc-usr-wkld.adoc[leveloffset=+1]
+
 include::modules/hcp-dc-verify.adoc[leveloffset=+1]
+
 include::modules/hcp-dc-addon.adoc[leveloffset=+1]
--- a/hosted_control_planes/hcp-disconnected/hcp-deploy-dc-bm.adoc
+++ b/hosted_control_planes/hcp-disconnected/hcp-deploy-dc-bm.adoc
@@ -9,10 +9,15 @@ toc::[]
 When you provision {hcp} on bare metal, you use the Agent platform. The Agent platform and {mce} work together to enable disconnected deployments. The Agent platform uses the central infrastructure management service to add worker nodes to a hosted cluster. For an introduction to the central infrastructure management service, see link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/clusters/cluster_mce_overview#enable-cim[Enabling the central infrastructure management service].

 include::modules/hcp-dc-bm-arch.adoc[leveloffset=+1]
+
 include::modules/hcp-dc-bm-reqs.adoc[leveloffset=+1]
+
 include::modules/hcp-dc-extract.adoc[leveloffset=+1]
+
 include::modules/hcp-bm-dns.adoc[leveloffset=+1]
+
 include::modules/hcp-dc-registry.adoc[leveloffset=+1]
+
 include::modules/hcp-dc-mgmt-cluster.adoc[leveloffset=+1]

 [role="_additional-resources"]
@@ -22,6 +27,7 @@ include::modules/hcp-dc-mgmt-cluster.adoc[leveloffset=+1]
 * link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/clusters/cluster_mce_overview#mce-intro[About cluster lifecycle with multicluster engine operator]

 include::modules/hcp-dc-web-server.adoc[leveloffset=+1]
+
 include::modules/hcp-dc-image-mirror.adoc[leveloffset=+1]

 [role="_additional-resources"]
@@ -43,6 +49,7 @@ include::modules/hcp-agentserviceconfig.adoc[leveloffset=+1]
 To ensure proper function in a disconnected deployment, you need to configure the registry CA certificates in the management cluster and the worker nodes for the hosted cluster.

 include::modules/hcp-dc-tls-mgmt.adoc[leveloffset=+2]
+
 include::modules/hcp-dc-tls-hosted.adoc[leveloffset=+2]

 [id="hcp-dc-bm-hosted"]
@@ -51,8 +58,11 @@ include::modules/hcp-dc-tls-hosted.adoc[leveloffset=+2]
 A hosted cluster is an {product-title} cluster with its control plane and API endpoint hosted on a management cluster. The hosted cluster includes the control plane and its corresponding data plane.

 include::modules/hcp-hc-objects.adoc[leveloffset=+2]
+
 include::modules/hcp-nodepool-hc.adoc[leveloffset=+2]
+
 include::modules/hcp-dc-infraenv.adoc[leveloffset=+2]
+
 include::modules/hcp-bm-hosts.adoc[leveloffset=+2]

 [role="_additional-resources"]
--- a/hosted_control_planes/hcp-disconnected/hcp-deploy-dc-virt.adoc
+++ b/hosted_control_planes/hcp-disconnected/hcp-deploy-dc-virt.adoc
@@ -41,6 +41,7 @@ The {mce} plays a crucial role in deploying clusters across providers. If you do
 To ensure proper function in a disconnected deployment, you need to configure the registry CA certificates in the management cluster and the worker nodes for the hosted cluster.

 include::modules/hcp-dc-tls-mgmt.adoc[leveloffset=+2]
+
 include::modules/hcp-dc-tls-hosted.adoc[leveloffset=+2]

 [id="hcp-dc-virt-hosted"]
@@ -49,7 +50,9 @@ include::modules/hcp-dc-tls-hosted.adoc[leveloffset=+2]
 A hosted cluster is an {product-title} cluster with its control plane and API endpoint hosted on a management cluster. The hosted cluster includes the control plane and its corresponding data plane.

 include::modules/hcp-virt-reqs.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-create-hc-cli.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-ingress-dns.adoc[leveloffset=+2]

 [id="hcp-dc-virt-ingress-dns-custom"]
@@ -58,7 +61,9 @@ include::modules/hcp-virt-ingress-dns.adoc[leveloffset=+2]
 If you do not want to use the default ingress and DNS behavior, you can configure a KubeVirt hosted cluster with a unique base domain at creation time. This option requires manual configuration steps during creation and involves three main steps: cluster creation, load balancer creation, and wildcard DNS configuration.

 include::modules/hcp-virt-hc-base-domain.adoc[leveloffset=+3]
+
 include::modules/hcp-virt-load-balancer.adoc[leveloffset=+3]
+
 include::modules/hcp-virt-wildcard-dns.adoc[leveloffset=+3]

 [id="hcp-dc-finish"]
@@ -67,4 +72,5 @@ include::modules/hcp-virt-wildcard-dns.adoc[leveloffset=+3]
 You can monitor the deployment of a hosted cluster from two perspectives: the control plane and the data plane.

 include::modules/hcp-monitor-cp.adoc[leveloffset=+2]
+
 include::modules/hcp-monitor-dp.adoc[leveloffset=+2]
--- a/hosted_control_planes/hcp-import.adoc
+++ b/hosted_control_planes/hcp-import.adoc
@@ -18,5 +18,7 @@ include::modules/hcp-import-limitations.adoc[leveloffset=+1]
 * link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/clusters/cluster_mce_overview#discover-hosted-acm[Discovering {mce} hosted clusters in {rh-rhacm-title}]

 include::modules/hcp-import-manual.adoc[leveloffset=+1]
+
 include::modules/hcp-import-manual-aws.adoc[leveloffset=+1]
+
 include::modules/hcp-import-disable.adoc[leveloffset=+1]
--- a/hosted_control_planes/hcp-manage/hcp-manage-bm.adoc
+++ b/hosted_control_planes/hcp-manage/hcp-manage-bm.adoc
@@ -9,9 +9,13 @@ toc::[]
 After you deploy {hcp} on bare metal, you can manage a hosted cluster by completing the following tasks.

 include::modules/hcp-bm-access.adoc[leveloffset=+1]
+
 include::modules/hcp-bm-scale-np.adoc[leveloffset=+1]
+
 include::modules/hcp-bm-add-np.adoc[leveloffset=+2]
+
 include::modules/hcp-bm-autoscale.adoc[leveloffset=+2]
+
 include::modules/hcp-bm-autoscale-disable.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -27,6 +31,7 @@ include::modules/hcp-bm-ingress.adoc[leveloffset=+1]
 * xref:../../networking/networking_operators/metallb-operator/about-metallb.adoc#about-metallb_about-metallb[About MetalLB and the MetalLB Operator]

 include::modules/hcp-bm-machine-health.adoc[leveloffset=+1]
+
 include::modules/hcp-bm-machine-health-disable.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/hosted_control_planes/hcp-manage/hcp-manage-non-bm.adoc
+++ b/hosted_control_planes/hcp-manage/hcp-manage-non-bm.adoc
@@ -9,9 +9,13 @@ toc::[]
 After you deploy {hcp} on non-bare-metal agent machines, you can manage a hosted cluster by completing the following tasks.

 include::modules/hcp-bm-access.adoc[leveloffset=+1]
+
 include::modules/hcp-bm-scale-np.adoc[leveloffset=+1]
+
 include::modules/hcp-bm-add-np.adoc[leveloffset=+2]
+
 include::modules/hcp-bm-autoscale.adoc[leveloffset=+2]
+
 include::modules/hcp-bm-autoscale-disable.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -27,6 +31,7 @@ include::modules/hcp-bm-ingress.adoc[leveloffset=+1]
 * xref:../../networking/networking_operators/metallb-operator/about-metallb.adoc#about-metallb_about-metallb[About MetalLB and the MetalLB Operator]

 include::modules/hcp-bm-machine-health.adoc[leveloffset=+1]
+
 include::modules/hcp-bm-machine-health-disable.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/hosted_control_planes/hcp-manage/hcp-manage-virt.adoc
+++ b/hosted_control_planes/hcp-manage/hcp-manage-virt.adoc
@@ -9,6 +9,7 @@ toc::[]
 After you deploy a hosted cluster on {VirtProductName}, you can manage the cluster by completing the following procedures.

 include::modules/hcp-virt-access.adoc[leveloffset=+1]
+
 include::modules/hcp-bm-autoscale.adoc[leveloffset=+1]

 [id="hcp-virt-storage"]
@@ -43,10 +44,15 @@ a|
 ====

 include::modules/hcp-virt-map-storage.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-csi-snapshot.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-multiple-snapshots.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-root-volume.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-image-caching.adoc[leveloffset=+2]
+
 include::modules/hcp-virt-storage-security-isolation.adoc[leveloffset=+2]

 [role="_additional-resources"]
--- a/hosted_control_planes/hcp-networking.adoc
+++ b/hosted_control_planes/hcp-networking.adoc
@@ -12,12 +12,16 @@ For {hcp}, proxy support involves the following additional use cases.

 //cp workloads that need to use a proxy to access external services
 include::modules/hcp-proxy-cp-workloads.adoc[leveloffset=+1]
+
 //workers need a proxy to communicate with ignition endpoint
 include::modules/hcp-proxy-ignition.adoc[leveloffset=+1]
+
 //workers need proxy to communicate with cp
 include::modules/hcp-proxy-api.adoc[leveloffset=+1]
+
 //cp workloads that need access to external services and must use the proxy for the management cluster
 include::modules/hcp-proxy-mgmt-cluster.adoc[leveloffset=+1]
+
 //proxy configuration on the mgmt cluster when the hosted cluster has a secondary network and no default pod network
 include::modules/hcp-proxy-addl-network.adoc[leveloffset=+1]

--- a/hosted_control_planes/hcp-observability.adoc
+++ b/hosted_control_planes/hcp-observability.adoc
@@ -9,4 +9,5 @@ toc::[]
 You can gather metrics for {hcp} by configuring metrics sets. The HyperShift Operator can create or delete monitoring dashboards in the management cluster for each hosted cluster that it manages.

 include::modules/hosted-control-planes-metrics-sets.adoc[leveloffset=+1]
+
 include::modules/hosted-control-planes-monitoring-dashboard.adoc[leveloffset=+1]
--- a/hosted_control_planes/hcp-prepare/hcp-cli.adoc
+++ b/hosted_control_planes/hcp-prepare/hcp-cli.adoc
@@ -9,5 +9,7 @@ toc::[]
 The {hcp} command-line interface, `hcp`, is a tool that you can use to get started with {hcp}. For Day 2 operations, such as management and configuration, use GitOps or your own automation tool.

 include::modules/hcp-cli-terminal.adoc[leveloffset=+1]
+
 include::modules/hcp-cli-console.adoc[leveloffset=+1]
+
 include::modules/hcp-cli-gateway.adoc[leveloffset=+1]
--- a/hosted_control_planes/hcp-prepare/hcp-distribute-workloads.adoc
+++ b/hosted_control_planes/hcp-prepare/hcp-distribute-workloads.adoc
@@ -24,6 +24,9 @@ Do not use the management cluster for your workload. Workloads must not run on n
 ====

 include::modules/hcp-labels-taints.adoc[leveloffset=+1]
+
 include::modules/hcp-priority-classes.adoc[leveloffset=+1]
+
 include::modules/hcp-virt-taints-tolerations.adoc[leveloffset=+1]
+
 include::modules/hcp-isolation.adoc[leveloffset=+1]
--- a/hosted_control_planes/hcp-prepare/hcp-enable-disable.adoc
+++ b/hosted_control_planes/hcp-prepare/hcp-enable-disable.adoc
@@ -9,6 +9,7 @@ toc::[]
 The {hcp} feature, as well as the `hypershift-addon` managed cluster add-on, are enabled by default. If you want to disable the feature, or if you disabled it and want to manually enable it, see the following procedures.

 include::modules/hcp-enable-manual.adoc[leveloffset=+1]
+
 include::modules/hcp-enable-manual-addon.adoc[leveloffset=+2]

 [id="hcp-disable_{context}"]
@@ -17,4 +18,5 @@ include::modules/hcp-enable-manual-addon.adoc[leveloffset=+2]
 You can uninstall the HyperShift Operator and disable the {hcp} feature. When you disable the {hcp} feature, you must destroy the hosted cluster and the managed cluster resource on {mce-short}, as described in the _Managing hosted clusters_ topics.

 include::modules/hcp-uninstall-operator.adoc[leveloffset=+2]
+
 include::modules/hcp-disable-feature.adoc[leveloffset=+2]
--- a/hosted_control_planes/hcp-prepare/hcp-override-resource-util.adoc
+++ b/hosted_control_planes/hcp-prepare/hcp-override-resource-util.adoc
@@ -9,4 +9,5 @@ toc::[]
 The set of baseline measurements for resource utilization can vary in each hosted cluster.

 include::modules/hcp-override.adoc[leveloffset=+1]
+
 include::modules/hcp-disable-metrics.adoc[leveloffset=+1]
--- a/hosted_control_planes/hcp-prepare/hcp-requirements.adoc
+++ b/hosted_control_planes/hcp-prepare/hcp-requirements.adoc
@@ -23,6 +23,7 @@ The following requirements apply to {hcp}:
 * In Bare Metal Host (BMH) deployments, where the Bare Metal Operator starts machines, the hosted control plane must be able to reach baseboard management controllers (BMCs). If your security profile does not permit the Cluster Baremetal Operator to access the network where the BMHs have their BMCs in order to enable Redfish automation, you can use BYO ISO support. However, in BYO mode, {product-title} cannot automate the powering on of BMHs.

 include::modules/hcp-support-matrix.adoc[leveloffset=+1]
+
 include::modules/hcp-fips.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/hosted_control_planes/hcp-prepare/hcp-sizing-guidance.adoc
+++ b/hosted_control_planes/hcp-prepare/hcp-sizing-guidance.adoc
@@ -31,8 +31,11 @@ include::modules/hcp-pod-limits.adoc[leveloffset=+1]
 * xref:../../nodes/nodes/nodes-nodes-managing-max-pods.adoc#nodes-nodes-managing-max-pods-proc_nodes-nodes-managing-max-pods[Configuring the maximum number of pods per node]

 include::modules/hcp-resource-limit.adoc[leveloffset=+1]
+
 include::modules/hcp-load-based-limit.adoc[leveloffset=+1]
+
 include::modules/hcp-sizing-calculation.adoc[leveloffset=+1]
+
 include::modules/hcp-shared-infra.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/hosted_control_planes/hcp-troubleshooting.adoc
+++ b/hosted_control_planes/hcp-troubleshooting.adoc
@@ -20,6 +20,7 @@ include::modules/hosted-control-planes-troubleshooting.adoc[leveloffset=+1]
 You can gather {product-title} debugging information for a hosted cluster by using the {mce-short} web console or by using the CLI.

 include::modules/hcp-must-gather-cli.adoc[leveloffset=+2]
+
 include::modules/hcp-must-gather-console.adoc[leveloffset=+2]

 include::modules/hcp-must-gather-dc.adoc[leveloffset=+1]
@@ -34,6 +35,7 @@ include::modules/hcp-must-gather-dc.adoc[leveloffset=+1]
 When you troubleshoot a hosted cluster on {VirtProductName}, start with the top-level `HostedCluster` and `NodePool` resources and then work down the stack until you find the root cause. The following steps can help you discover the root cause of common issues.

 include::modules/hcp-ts-hc-stuck.adoc[leveloffset=+2]
+
 include::modules/hcp-ts-no-nodes-reg.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -41,11 +43,17 @@ include::modules/hcp-ts-no-nodes-reg.adoc[leveloffset=+2]
 * link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html/clusters/cluster_mce_overview#identifying-vm-console-logs[Identifying the problem: Access the VM console logs]

 include::modules/hcp-ts-nodes-stuck.adoc[leveloffset=+2]
+
 include::modules/hcp-ts-ingress-not-online.adoc[leveloffset=+2]
+
 include::modules/hcp-ts-load-balancer-svcs.adoc[leveloffset=+2]
+
 include::modules/hcp-ts-pvcs-not-avail.adoc[leveloffset=+2]
+
 include::modules/hcp-ts-vm-nodes.adoc[leveloffset=+2]
+
 include::modules/hcp-ts-rhcos.adoc[leveloffset=+2]
+
 include::modules/hcp-ts-non-bm.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -64,6 +72,9 @@ include::modules/hcp-ts-bm-nodes-not-added.adoc[leveloffset=+2]
 * link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html-single/clusters/index#on-prem-creating-your-cluster-with-the-cli-pull-secret[Add the pull secret to the namespace]

 include::modules/hosted-restart-hcp-components.adoc[leveloffset=+1]
+
 include::modules/hosted-control-planes-pause-reconciliation.adoc[leveloffset=+1]
+
 include::modules/scale-down-data-plane.adoc[leveloffset=+1]
+
 include::modules/agent-service-failure.adoc[leveloffset=+1]
--- a/hosted_control_planes/index.adoc
+++ b/hosted_control_planes/index.adoc
@@ -9,6 +9,7 @@ You can deploy {product-title} clusters by using two different control plane con
 toc::[]

 include::modules/hosted-control-planes-overview.adoc[leveloffset=+1]
+
 include::modules/hcp-ocp-differences.adoc[leveloffset=+1]

 [role="_additional-resources"]
@@ -16,7 +17,9 @@ include::modules/hcp-ocp-differences.adoc[leveloffset=+1]
 * xref:../etcd/etcd-encrypt.adoc#etcd-encrypt[Enabling etcd encryption]

 include::modules/hcp-mce-acm-relationship-intro.adoc[leveloffset=+1]
+
 include::modules/hcp-acm-discover.adoc[leveloffset=+2]
+
 include::modules/hosted-control-planes-version-support.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/installing/install_config/installing-customizing.adoc
+++ b/installing/install_config/installing-customizing.adoc
@@ -28,8 +28,11 @@ The following sections describe features that you might want to
 configure on your nodes in this way.

 include::modules/installation-special-config-butane.adoc[leveloffset=+1]
+
 include::modules/installation-special-config-butane-about.adoc[leveloffset=+2]
+
 include::modules/installation-special-config-butane-install.adoc[leveloffset=+2]
+
 include::modules/installation-special-config-butane-create.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -39,13 +42,19 @@ include::modules/installation-special-config-butane-create.adoc[leveloffset=+2]
 * xref:../../installing/install_config/installing-customizing.adoc#installation-special-config-storage_installing-customizing[Encrypting and mirroring disks during installation]

 include::modules/installation-special-config-kargs.adoc[leveloffset=+1]
+
 ifdef::openshift-webscale[]
 include::modules/installation-special-config-rtkernel.adoc[leveloffset=+1]
+
 endif::openshift-webscale[]
 include::modules/installation-special-config-kmod.adoc[leveloffset=+1]
+
 include::modules/installation-special-config-storage.adoc[leveloffset=+1]
+
 include::modules/installation-special-config-raid.adoc[leveloffset=+1]
+
 include::modules/installation-special-config-raid-intel-vroc.adoc[leveloffset=+1]
+
 include::modules/installation-special-config-chrony.adoc[leveloffset=+1]

 [role="_additional-resources"]
--- a/installing/installing_aws/aws-compute-edge-zone-tasks.adoc
+++ b/installing/installing_aws/aws-compute-edge-zone-tasks.adoc
@@ -31,9 +31,13 @@ include::modules/nw-cluster-mtu-change-about.adoc[leveloffset=+2]

 // Changing the cluster network MTU
 include::modules/nw-cluster-mtu-change.adoc[leveloffset=+2]
+
 include::modules/nw-cluster-mtu-checking.adoc[leveloffset=+3]
+
 include::modules/nw-cluster-mtu-migration.adoc[leveloffset=+3]
+
 include::modules/nw-cluster-mtu-verifying-configuration.adoc[leveloffset=+3]
+
 include::modules/nw-cluster-mtu-finalizing-migration.adoc[leveloffset=+3]

 // Opting in to AWS Local Zones or Wavelength Zones
--- a/installing/installing_aws/installing-aws-account.adoc
+++ b/installing/installing_aws/installing-aws-account.adoc
@@ -22,6 +22,7 @@ include::modules/installation-aws-iam-user.adoc[leveloffset=+1]
 include::modules/installation-aws-iam-policies-about.adoc[leveloffset=+1]

 include::modules/installation-aws-permissions-iam-roles.adoc[leveloffset=+2]
+
 include::modules/installation-aws-add-iam-roles.adoc[leveloffset=+2]

 [role="_additional-resources"]
--- a/installing/installing_aws/ipi/installing-aws-customizations.adoc
+++ b/installing/installing_aws/ipi/installing-aws-customizations.adoc
@@ -103,6 +103,7 @@ include::modules/cco-ccoctl-install-creating-manifests.adoc[leveloffset=+3]

 // Network Operator specific configuration
 include::modules/nw-operator-cr.adoc[leveloffset=+1]
+
 include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]

 [NOTE]
--- a/installing/installing_aws/ipi/installing-aws-outposts.adoc
+++ b/installing/installing_aws/ipi/installing-aws-outposts.adoc
@@ -15,6 +15,7 @@ For more information, see the link:https://docs.aws.amazon.com/outposts/[AWS Out

 //AWS Outposts on {product-title} requirements and limitations
 include::modules/aws-outposts-requirements-limitations.adoc[leveloffset=+1]
+
 [role="_additional-resources"]
 .Additional resources
 * xref:../../../installing/installing_aws/ipi/installing-aws-outposts.adoc#nw-aws-load-balancer-with-outposts_installing-aws-outposts[Using the AWS Load Balancer Operator in an AWS VPC cluster extended into an Outpost]
@@ -42,10 +43,15 @@ To extend your VPC cluster into an Outpost, you must complete the following netw

 //Changing the Cluster Network MTU to support AWS Outposts
 include::modules/nw-cluster-mtu-change.adoc[leveloffset=+2]
+
 include::modules/nw-cluster-mtu-checking.adoc[leveloffset=+3]
+
 include::modules/nw-cluster-mtu-migration.adoc[leveloffset=+3]
+
 include::modules/nw-cluster-mtu-verifying-configuration.adoc[leveloffset=+3]
+
 include::modules/nw-cluster-mtu-finalizing-migration.adoc[leveloffset=+3]
+
 [role="_additional-resources"]
 .Additional resources
 * xref:../../../networking/advanced_networking/changing-cluster-network-mtu.adoc#changing-cluster-network-mtu[Changing the MTU for the cluster network]
@@ -61,6 +67,7 @@ include::modules/aws-outposts-machine-set.adoc[leveloffset=+1]

 //Creating user workloads in an Outpost
 include::modules/create-user-workloads-aws-edge.adoc[leveloffset=+1]
+
 //To-do: reintegrate installation-extend-edge-nodes-aws-local-zones.adoc with create-user-workloads-aws-edge.adoc. Requires global repo update of any xrefs/includes.

 [id="aws-outposts-network-scheduling-workloads_{context}"]
--- a/installing/installing_aws/ipi/installing-aws-private.adoc
+++ b/installing/installing_aws/ipi/installing-aws-private.adoc
@@ -26,6 +26,7 @@ include::modules/private-clusters-default.adoc[leveloffset=+1]
 include::modules/private-clusters-about-aws.adoc[leveloffset=+2]

 include::modules/installation-custom-aws-vpc.adoc[leveloffset=+1]
+
 include::modules/installation-aws-security-groups.adoc[leveloffset=+2]

 include::modules/installation-initializing-manual.adoc[leveloffset=+1]
@@ -42,6 +43,7 @@ include::modules/installation-minimum-resource-requirements.adoc[leveloffset=+2]
 * xref:../../../scalability_and_performance/optimization/optimizing-storage.adoc#optimizing-storage[Optimizing storage]

 include::modules/installation-aws-tested-machine-types.adoc[leveloffset=+2]
+
 include::modules/installation-aws-arm-tested-machine-types.adoc[leveloffset=+2]

 include::modules/installation-aws-config-yaml-customizations.adoc[leveloffset=+2]
--- a/installing/installing_aws/ipi/installing-aws-specialized-region.adoc
+++ b/installing/installing_aws/ipi/installing-aws-specialized-region.adoc
@@ -60,6 +60,7 @@ If you have an AWS profile stored on your computer, it must not use a temporary
 ====

 include::modules/installation-aws-about-government-region.adoc[leveloffset=+1]
+
 include::modules/installation-aws-marketplace-government.adoc[leveloffset=+1]

 [role="_additional-resources"]
@@ -69,9 +70,11 @@ include::modules/installation-aws-marketplace-government.adoc[leveloffset=+1]
 include::modules/installation-aws-regions-with-no-ami.adoc[leveloffset=+1]

 include::modules/private-clusters-default.adoc[leveloffset=+1]
+
 include::modules/private-clusters-about-aws.adoc[leveloffset=+2]

 include::modules/installation-custom-aws-vpc.adoc[leveloffset=+1]
+
 include::modules/installation-aws-security-groups.adoc[leveloffset=+2]

 include::modules/installation-aws-upload-custom-rhcos-ami.adoc[leveloffset=+1]
@@ -97,6 +100,7 @@ include::modules/installation-minimum-resource-requirements.adoc[leveloffset=+2]
 * xref:../../../scalability_and_performance/optimization/optimizing-storage.adoc#optimizing-storage[Optimizing storage]

 include::modules/installation-aws-tested-machine-types.adoc[leveloffset=+2]
+
 include::modules/installation-aws-arm-tested-machine-types.adoc[leveloffset=+2]

 include::modules/installation-configure-proxy.adoc[leveloffset=+2]
--- a/installing/installing_aws/ipi/installing-aws-vpc.adoc
+++ b/installing/installing_aws/ipi/installing-aws-vpc.adoc
@@ -23,7 +23,9 @@ If you have an AWS profile stored on your computer, it must not use a temporary
 * If you use a firewall, you xref:../../../installing/install_config/configuring-firewall.adoc#configuring-firewall[configured it to allow the sites] that your cluster requires access to.

 include::modules/installation-custom-aws-vpc.adoc[leveloffset=+1]
+
 include::modules/installation-aws-security-groups.adoc[leveloffset=+2]
+
 include::modules/installation-aws-permissions-iam-shared-vpc.adoc[leveloffset=+2]

 include::modules/installation-initializing.adoc[leveloffset=+1]
@@ -40,6 +42,7 @@ include::modules/installation-minimum-resource-requirements.adoc[leveloffset=+2]
 * xref:../../../scalability_and_performance/optimization/optimizing-storage.adoc#optimizing-storage[Optimizing storage]

 include::modules/installation-aws-tested-machine-types.adoc[leveloffset=+2]
+
 include::modules/installation-aws-arm-tested-machine-types.adoc[leveloffset=+2]

 include::modules/installation-aws-config-yaml-customizations.adoc[leveloffset=+2]
--- a/installing/installing_aws/upi/upi-aws-installation-reqs.adoc
+++ b/installing/installing_aws/upi/upi-aws-installation-reqs.adoc
@@ -13,6 +13,7 @@ of the required machines.


 include::modules/installation-machine-requirements.adoc[leveloffset=+1]
+
 include::modules/installation-minimum-resource-requirements.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -21,6 +22,7 @@ include::modules/installation-minimum-resource-requirements.adoc[leveloffset=+2]
 * xref:../../../scalability_and_performance/optimization/optimizing-storage.adoc#optimizing-storage[Optimizing storage]

 include::modules/installation-aws-tested-machine-types.adoc[leveloffset=+2]
+
 include::modules/installation-aws-arm-tested-machine-types.adoc[leveloffset=+2]

 include::modules/csr-management.adoc[leveloffset=+1]
--- a/installing/installing_azure/ipi/installing-azure-government-region.adoc
+++ b/installing/installing_azure/ipi/installing-azure-government-region.adoc
@@ -44,6 +44,7 @@ include::modules/installation-minimum-resource-requirements.adoc[leveloffset=+2]
 include::modules/installation-azure-tested-machine-types.adoc[leveloffset=+2]

 include::modules/installation-azure-trusted-launch.adoc[leveloffset=+2]
+
 include::modules/installation-azure-confidential-vms.adoc[leveloffset=+2]

 include::modules/installation-azure-config-yaml.adoc[leveloffset=+2]
--- a/installing/installing_azure/ipi/installing-azure-private.adoc
+++ b/installing/installing_azure/ipi/installing-azure-private.adoc
@@ -41,6 +41,7 @@ include::modules/installation-azure-tested-machine-types.adoc[leveloffset=+2]
 include::modules/installation-azure-arm-tested-machine-types.adoc[leveloffset=+2]

 include::modules/installation-azure-trusted-launch.adoc[leveloffset=+2]
+
 include::modules/installation-azure-confidential-vms.adoc[leveloffset=+2]

 include::modules/installation-azure-config-yaml.adoc[leveloffset=+2]
--- a/installing/installing_azure/ipi/installing-azure-vnet.adoc
+++ b/installing/installing_azure/ipi/installing-azure-vnet.adoc
@@ -35,6 +35,7 @@ include::modules/installation-azure-tested-machine-types.adoc[leveloffset=+2]
 include::modules/installation-azure-arm-tested-machine-types.adoc[leveloffset=+2]

 include::modules/installation-azure-trusted-launch.adoc[leveloffset=+2]
+
 include::modules/installation-azure-confidential-vms.adoc[leveloffset=+2]

 include::modules/installation-azure-config-yaml.adoc[leveloffset=+2]
--- a/installing/installing_azure/ipi/installing-restricted-networks-azure-installer-provisioned.adoc
+++ b/installing/installing_azure/ipi/installing-restricted-networks-azure-installer-provisioned.adoc
@@ -52,6 +52,7 @@ include::modules/installation-azure-tested-machine-types.adoc[leveloffset=+2]
 include::modules/installation-azure-arm-tested-machine-types.adoc[leveloffset=+2]

 include::modules/installation-azure-trusted-launch.adoc[leveloffset=+2]
+
 include::modules/installation-azure-confidential-vms.adoc[leveloffset=+2]

 include::modules/installation-azure-dedicated-disks.adoc[leveloffset=+2]
--- a/installing/installing_azure/upi/installing-azure-user-infra.adoc
+++ b/installing/installing_azure/upi/installing-azure-user-infra.adoc
@@ -81,6 +81,7 @@ of the required machines.
 This section describes the requirements for deploying {product-title} on user-provisioned infrastructure.

 include::modules/installation-machine-requirements.adoc[leveloffset=+2]
+
 include::modules/installation-minimum-resource-requirements.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -89,6 +90,7 @@ include::modules/installation-minimum-resource-requirements.adoc[leveloffset=+2]
 * xref:../../../scalability_and_performance/optimization/optimizing-storage.adoc#optimizing-storage[Optimizing storage]

 include::modules/installation-azure-tested-machine-types.adoc[leveloffset=+2]
+
 include::modules/installation-azure-arm-tested-machine-types.adoc[leveloffset=+2]

 include::modules/installation-azure-marketplace-subscribe.adoc[leveloffset=+1]
@@ -98,11 +100,16 @@ include::modules/installation-obtaining-installer.adoc[leveloffset=+1]
 include::modules/ssh-agent-using.adoc[leveloffset=+1]

 include::modules/installation-user-infra-generate.adoc[leveloffset=+1]
+
 include::modules/installation-disk-partitioning-upi-templates.adoc[leveloffset=+2]
+
 include::modules/installation-initializing.adoc[leveloffset=+2]
+
 include::modules/installation-configure-proxy.adoc[leveloffset=+2]
+
 //include::modules/installation-three-node-cluster.adoc[leveloffset=+2]
 include::modules/installation-user-infra-exporting-common-variables-arm-templates.adoc[leveloffset=+2]
+
 include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[leveloffset=+2]

 include::modules/installation-azure-create-resource-group-and-identity.adoc[leveloffset=+1]
@@ -114,25 +121,31 @@ include::modules/installation-azure-create-dns-zones.adoc[leveloffset=+1]
 You can learn more about xref:installation-azure-network-config_{context}[configuring a public DNS zone in Azure] by visiting that section.

 include::modules/installation-creating-azure-vnet.adoc[leveloffset=+1]
+
 include::modules/installation-arm-vnet.adoc[leveloffset=+2]

 include::modules/installation-azure-user-infra-deploying-rhcos.adoc[leveloffset=+1]
+
 include::modules/installation-arm-image-storage.adoc[leveloffset=+2]

 include::modules/installation-network-user-infra.adoc[leveloffset=+1]

 include::modules/installation-creating-azure-dns.adoc[leveloffset=+1]
+
 include::modules/installation-arm-dns.adoc[leveloffset=+2]

 include::modules/installation-creating-azure-bootstrap.adoc[leveloffset=+1]
+
 include::modules/installation-arm-bootstrap.adoc[leveloffset=+2]

 include::modules/installation-creating-azure-control-plane.adoc[leveloffset=+1]
+
 include::modules/installation-arm-control-plane.adoc[leveloffset=+2]

 include::modules/installation-azure-user-infra-wait-for-bootstrap.adoc[leveloffset=+1]

 include::modules/installation-creating-azure-worker.adoc[leveloffset=+1]
+
 include::modules/installation-arm-worker.adoc[leveloffset=+2]

 include::modules/cli-installing-cli.adoc[leveloffset=+1]
--- a/installing/installing_azure/upi/installing-restricted-networks-azure-user-provisioned.adoc
+++ b/installing/installing_azure/upi/installing-restricted-networks-azure-user-provisioned.adoc
@@ -93,10 +93,15 @@ include::modules/installation-obtaining-installer.adoc[leveloffset=+2]
 include::modules/ssh-agent-using.adoc[leveloffset=+2]

 include::modules/installation-user-infra-generate.adoc[leveloffset=+1]
+
 include::modules/installation-disk-partitioning-upi-templates.adoc[leveloffset=+2]
+
 include::modules/installation-initializing.adoc[leveloffset=+2]
+
 include::modules/installation-configure-proxy.adoc[leveloffset=+2]
+
 include::modules/installation-user-infra-exporting-common-variables-arm-templates.adoc[leveloffset=+2]
+
 include::modules/installation-user-infra-generate-k8s-manifest-ignition.adoc[leveloffset=+2]

 include::modules/installation-azure-create-resource-group-and-identity.adoc[leveloffset=+1]
@@ -108,25 +113,31 @@ include::modules/installation-azure-create-dns-zones.adoc[leveloffset=+1]
 You can learn more about xref:installation-azure-network-config_{context}[configuring a public DNS zone in Azure] by visiting that section.

 include::modules/installation-creating-azure-vnet.adoc[leveloffset=+1]
+
 include::modules/installation-arm-vnet.adoc[leveloffset=+2]

 include::modules/installation-azure-user-infra-deploying-rhcos.adoc[leveloffset=+1]
+
 include::modules/installation-arm-image-storage.adoc[leveloffset=+2]

 include::modules/installation-network-user-infra.adoc[leveloffset=+1]

 include::modules/installation-creating-azure-dns.adoc[leveloffset=+1]
+
 include::modules/installation-arm-dns.adoc[leveloffset=+2]

 include::modules/installation-creating-azure-bootstrap.adoc[leveloffset=+1]
+
 include::modules/installation-arm-bootstrap.adoc[leveloffset=+2]

 include::modules/installation-creating-azure-control-plane.adoc[leveloffset=+1]
+
 include::modules/installation-arm-control-plane.adoc[leveloffset=+2]

 include::modules/installation-azure-user-infra-wait-for-bootstrap.adoc[leveloffset=+1]

 include::modules/installation-creating-azure-worker.adoc[leveloffset=+1]
+
 include::modules/installation-arm-worker.adoc[leveloffset=+2]

 include::modules/cli-installing-cli.adoc[leveloffset=+1]
--- a/installing/installing_azure_stack_hub/ipi/installing-azure-stack-hub-network-customizations.adoc
+++ b/installing/installing_azure_stack_hub/ipi/installing-azure-stack-hub-network-customizations.adoc
@@ -49,8 +49,11 @@ include::modules/azure-stack-hub-internal-ca.adoc[leveloffset=+1]

 // Network Operator specific configuration
 include::modules/nw-network-config.adoc[leveloffset=+1]
+
 include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]
+
 include::modules/nw-operator-cr.adoc[leveloffset=+1]
+
 include::modules/configuring-hybrid-ovnkubernetes.adoc[leveloffset=+1]

 ////
--- a/installing/installing_azure_stack_hub/upi/installing-azure-stack-hub-user-infra.adoc
+++ b/installing/installing_azure_stack_hub/upi/installing-azure-stack-hub-user-infra.adoc
@@ -54,6 +54,7 @@ You can view Azure's DNS solution by visiting this xref:installation-azure-creat
 include::modules/csr-management.adoc[leveloffset=+2]

 include::modules/installation-azure-stack-hub-permissions.adoc[leveloffset=+2]
+
 include::modules/installation-azure-service-principal.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -62,6 +63,7 @@ include::modules/installation-azure-service-principal.adoc[leveloffset=+2]
 * xref:../../../authentication/managing_cloud_provider_credentials/about-cloud-credential-operator.adoc#about-cloud-credential-operator-modes[About the Cloud Credential Operator]

 include::modules/installation-user-infra-generate.adoc[leveloffset=+1]
+
 include::modules/installation-initializing-manual.adoc[leveloffset=+2]

 [role="_additional-resources"]
@@ -71,6 +73,7 @@ include::modules/installation-initializing-manual.adoc[leveloffset=+2]
 include::modules/installation-azure-stack-hub-config-yaml.adoc[leveloffset=+2]

 include::modules/installation-configure-proxy.adoc[leveloffset=+2]
+
 include::modules/installation-user-infra-exporting-common-variables-arm-templates.adoc[leveloffset=+2]

 // Creating the Kubernetes manifest and Ignition config files
@@ -91,25 +94,31 @@ include::modules/installation-azure-create-dns-zones.adoc[leveloffset=+1]
 You can learn more about xref:installation-azure-stack-hub-network-config_{context}[configuring a DNS zone in Azure Stack Hub] by visiting that section.

 include::modules/installation-creating-azure-vnet.adoc[leveloffset=+1]
+
 include::modules/installation-arm-vnet.adoc[leveloffset=+2]

 include::modules/installation-azure-user-infra-deploying-rhcos.adoc[leveloffset=+1]
+
 include::modules/installation-arm-image-storage.adoc[leveloffset=+2]

 include::modules/installation-network-user-infra.adoc[leveloffset=+1]

 include::modules/installation-creating-azure-dns.adoc[leveloffset=+1]
+
 include::modules/installation-arm-dns.adoc[leveloffset=+2]

 include::modules/installation-creating-azure-bootstrap.adoc[leveloffset=+1]
+
 include::modules/installation-arm-bootstrap.adoc[leveloffset=+2]

 include::modules/installation-creating-azure-control-plane.adoc[leveloffset=+1]
+
 include::modules/installation-arm-control-plane.adoc[leveloffset=+2]

 include::modules/installation-azure-user-infra-wait-for-bootstrap.adoc[leveloffset=+1]

 include::modules/installation-creating-azure-worker.adoc[leveloffset=+1]
+
 include::modules/installation-arm-worker.adoc[leveloffset=+2]

 include::modules/cli-logging-in-kubeadmin.adoc[leveloffset=+1]
--- a/installing/installing_bare_metal/bare-metal-postinstallation-configuration.adoc
+++ b/installing/installing_bare_metal/bare-metal-postinstallation-configuration.adoc
@@ -54,45 +54,66 @@ include::modules/nw-osp-configuring-external-load-balancer.adoc[leveloffset=+2]

 // Using the Bare Metal Operator
 include::modules/bmo-config-using-bare-metal-operator.adoc[leveloffset=+1]
+
 // Bare Metal Operator architecture
 include::modules/bmo-bare-metal-operator-architecture.adoc[leveloffset=+2]
+
 // About the BareMetalHost resource
 include::modules/bmo-about-the-baremetalhost-resource.adoc[leveloffset=+2]
+
 // Getting the BareMetalHost resource
 include::modules/bmo-getting-the-baremetalhost-resource.adoc[leveloffset=+2]
+
 // Editing a BareMetalHost resource
 include::modules/bmo-editing-a-baremetalhost-resource.adoc[leveloffset=+2]
+
 // Troubleshooting latency.
 include::modules/bmo-troubleshooting-latency-when-deleting-a-baremetalhost-resource.adoc[leveloffset=+2]
+
 // Attaching a non-bootable ISO to a bare-metal node
 include::modules/bmo-attaching-a-non-bootable-iso-to-a-bare-metal-node.adoc[leveloffset=+2]
+
 // Configuring NC-SI and DisablePowerOff for shared NICs
 include::modules/bmo-configuring-ncsi-disable-poweroff.adoc[leveloffset=+2]
+
 // About the HostFirmwareSettings resource
 include::modules/bmo-about-the-hostfirmwaresettings-resource.adoc[leveloffset=+2]
+
 // Getting the HostFirmwareSettings resource
 include::modules/bmo-getting-the-hostfirmwaresettings-resource.adoc[leveloffset=+2]
+
 // Editing the HostFirmwareSettings resource
 include::modules/bmo-editing-the-hostfirmwaresettings-resource-of-a-provisioned-host.adoc[leveloffset=+2]
+
 // Patching the HostFirmawareSettings resource
 include::modules/bmo-performing-a-live-update-to-the-hostfirmwaresettings-resource.adoc[leveloffset=+2]
+
 // Verifying the HostFirmware Settings resource is valid
 include::modules/bmo-verifying-the-hostfirmware-settings-resource-is-valid.adoc[leveloffset=+2]
+
 // About the FirmwareSchema resource
 include::modules/bmo-about-the-firmwareschema-resource.adoc[leveloffset=+2]
+
 // Getting the FirmwareSchema resource
 include::modules/bmo-getting-the-firmwareschema-resource.adoc[leveloffset=+2]
+
 // About the HostFirmwareComponents resource
 include::modules/bmo-about-the-hostfirmwarecomponents-resource.adoc[leveloffset=+2]
+
 // Getting the HostFirmwareComponents resource
 include::modules/bmo-getting-the-hostfirmwarecomponents-resource.adoc[leveloffset=+2]
+
 // Editing the HostFirmwareComponents resource
 include::modules/bmo-editing-the-hostfirmwarecomponents-resource-of-a-provisioned-host.adoc[leveloffset=+2]
+
 // Patching the HostFirmawareComponents resource
 include::modules/bmo-performing-a-live-update-to-the-hostfirmwarecomponents-resource.adoc[leveloffset=+2]
+
 // Identifying the NICs `HostFirmwareComponents` resources you can update
 include::modules/bmo-getting-the-hostfirmwarecomponents-resource_nic.adoc[leveloffset=+2]
+
 // About the HostUpdatePolicy resource
 include::modules/bmo-about-the-hostupdatepolicy-resource.adoc[leveloffset=+2]
+
 // Setting the HostUpdatePolicy resource
 include::modules/bmo-setting-the-hostupdatepolicy-resource.adoc[leveloffset=+2]
--- a/Show More
+++ b/Show More