openshift · JoeAldinger · Aug 3, 2026
diff --git a/hardware_enablement/kmm-kernel-module-management.adoc b/hardware_enablement/kmm-kernel-module-management.adoc
@@ -26,7 +26,7 @@ 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].
+* 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]
 
@@ -35,7 +35,7 @@ include::modules/kmm-setting-kernel-firmware-search-path.adoc[leveloffset=+2]
 [role="_additional-resources"]
 .Additional resources
 
-* For more information about the `worker.setFirmwareClassPath` path, see xref:../hardware_enablement/kmm-kernel-module-management.adoc#kmm-configuring-kmmo_kernel-module-management-operator[Configuring the Kernel Module Management Operator].
+* xref:../hardware_enablement/kmm-kernel-module-management.adoc#kmm-configuring-kmmo_kernel-module-management-operator[Configuring the Kernel Module Management Operator]
 
 // Added for TELCODOCS-1309
 include::modules/kmm-uninstalling-kmm.adoc[leveloffset=+1]
@@ -212,7 +212,7 @@ 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].
+* xref:../machine_configuration/index.adoc#machine-config-operator_machine-config-overview[Machine Config Operator]
 
 include::modules/kmm-building-a-kmod-image.adoc[leveloffset=+2]
 

diff --git a/modules/kmm-hub-installing-kmm-hub-olm.adoc b/modules/kmm-hub-installing-kmm-hub-olm.adoc
@@ -6,4 +6,6 @@
 [id="kmm-hub-installing-kmm-hub-olm_{context}"]
 = Installing KMM-Hub using the Operator Lifecycle Manager
 
-Use the *Operators* section of the OpenShift console to install KMM-Hub.
+.Procedure
+
+* Use the *Operators* section of the OpenShift console to install KMM-Hub.
diff --git a/modules/kmm-hub-installing-kmm-hub.adoc b/modules/kmm-hub-installing-kmm-hub.adoc
@@ -2,7 +2,7 @@
 //
 // * hardware_enablement/kmm-kernel-module-management.adoc
 
-:_mod-docs-content-type: PROCEDURE
+:_mod-docs-content-type: CONCEPT
 [id="kmm-hub-installing-kmm-hub_{context}"]
 = Installing KMM-Hub
 

diff --git a/modules/kmm-hub-using-the-managedclustermodule.adoc b/modules/kmm-hub-using-the-managedclustermodule.adoc
@@ -2,7 +2,7 @@
 //
 // * hardware_enablement/kmm-kernel-module-management.adoc
 
-:_mod-docs-content-type: PROCEDURE
+:_mod-docs-content-type: REFERENCE
 [id="kmm-hub-using-the-managedclustermodule_{context}"]
 = Using the `ManagedClusterModule` CRD
 

diff --git a/modules/kmm-must-gather-tool.adoc b/modules/kmm-must-gather-tool.adoc
@@ -2,7 +2,7 @@
 //
 // * hardware_enablement/kmm-kernel-module-management.adoc
 
-:_mod-docs-content-type: PROCEDURE
+:_mod-docs-content-type: CONCEPT
 [id="kmm-must-gather-tool_{context}"]
 = Using the must-gather tool
 

diff --git a/modules/kmm-running-depmod.adoc b/modules/kmm-running-depmod.adoc
@@ -23,11 +23,12 @@ You must have a Red Hat subscription to download the `kernel-devel` package.
 $ depmod -b /opt ${KERNEL_FULL_VERSION}+`.
 ----
 +
-.Example Dockerfile
 If you are building your image on {product-title}, consider using the Driver Toolkit (DTK).
 +
 For further information, see link:https://cloud.redhat.com/blog/how-to-use-entitled-image-builds-to-build-drivercontainers-with-ubi-on-openshift[using an entitled build].
 +
+The following example Dockerfile shows how to run `depmod` at the end of the build:
++
 [source,yaml]
 ----
 apiVersion: v1

diff --git a/modules/kmm-using-signing-with-kmm.adoc b/modules/kmm-using-signing-with-kmm.adoc
@@ -8,11 +8,16 @@
 
 On a Secure Boot enabled system, all kernel modules (kmods) must be signed with a public/private key-pair enrolled into the Machine Owner's Key (MOK) database. Drivers distributed as part of a distribution should already be signed by the distribution's private key, but for kernel modules build out-of-tree, KMM supports signing kernel modules using the `sign` section of the kernel mapping.
 
-For more details on using Secure Boot, see link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_monitoring_and_updating_the_kernel/signing-a-kernel-and-modules-for-secure-boot_managing-monitoring-and-updating-the-kernel#generating-a-public-and-private-key-pair_signing-a-kernel-and-modules-for-secure-boot[Generating a public and private key pair]
+For more details on using Secure Boot, see "Generating a public and private key pair".
 
 [id="kmm-using-signing-with-kmm-prerequisites_{context}"]
 == Prerequisites
 
 * A public private key pair in the correct (DER) format.
 * At least one secure-boot enabled node with the public key enrolled in its MOK database.
 * Either a pre-built driver container image, or the source code and Dockerfile needed to build one in-cluster.
+
+[role="_additional-resources"]
+.Additional resources
+
+* link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/managing_monitoring_and_updating_the_kernel/signing-a-kernel-and-modules-for-secure-boot_managing-monitoring-and-updating-the-kernel#generating-a-public-and-private-key-pair_signing-a-kernel-and-modules-for-secure-boot[Generating a public and private key pair]