BZ2077574 Remove SRO Using Templates

Author: James Brigman

hardware_enablement/psap-special-resource-operator.adoc

@@ -25,8 +25,6 @@ include::modules/psap-special-resource-operator-installing-using-web-console.ado
 
 include::modules/psap-special-resource-operator-using.adoc[leveloffset=+1]
 
-include::modules/psap-special-resource-operator-using-manifests.adoc[leveloffset=+2]
-
 include::modules/psap-special-resource-operator-using-configmaps.adoc[leveloffset=+2]
 
 

modules/psap-special-resource-operator-using.adoc

@@ -5,7 +5,6 @@
 [id="using-the-special-resource-operator_{context}"]
 = Using the Special Resource Operator
 
-The Special Resource Operator (SRO) is used to manage the build and deployment of a driver container. The objects required to build and deploy the container can be defined in a Helm chart. 
+The Special Resource Operator (SRO) is used to manage the build and deployment of a driver container. The objects required to build and deploy the container can be defined in a Helm chart.
 
-The examples in this section use the simple-kmod kernel module to demonstrate how to use the SRO to build and run a driver container.
-In the first example, the SRO image contains a local repository of Helm charts including the templates for deploying the simple-kmod kernel module. In this case, a `SpecialResource` manifest is used to deploy the driver container. In the second example, the simple-kmod `SpecialResource` object points to a `ConfigMap` object that is created to store the Helm charts.
+The example in this section uses the simple-kmod `SpecialResource` object to point to a `ConfigMap` object that is created to store the Helm charts.