Merge pull request #38410 from leo8a/patch-1

Fix some nits on psap-configuring-node-feature-discovery.adoc

Author: ahardin-rh

modules/psap-configuring-node-feature-discovery.adoc

@@ -287,9 +287,9 @@ sources:
 
 [discrete]
 [id="configuring-node-feature-discovery-operator-sources-pci-deviceClassWhitelist_{context}"]
-=== soures.pci.deviceClassWhitelist
+=== sources.pci.deviceClassWhitelist
 
-`soures.pci.deviceClassWhitelist` is a list of link:https://pci-ids.ucw.cz/read/PD[PCI device class IDs] for which to publish a label. It can be specified as a main class only (for example, `03`) or full class-subclass combination (for example `0300`). The former implies that all
+`sources.pci.deviceClassWhitelist` is a list of link:https://pci-ids.ucw.cz/read/PD[PCI device class IDs] for which to publish a label. It can be specified as a main class only (for example, `03`) or full class-subclass combination (for example `0300`). The former implies that all
 subclasses are accepted.  The format of the labels can be further configured with `deviceLabelFields`.
 
 Default: `["03", "0b40", "12"]`
@@ -304,9 +304,9 @@ sources:
 
 [discrete]
 [id="configuring-node-feature-discovery-operator-sources-pci-deviceLabelFields_{context}"]
-=== soures.pci.deviceLabelFields
+=== sources.pci.deviceLabelFields
 
-`soures.pci.deviceLabelFields` is the set of PCI ID fields to use when constructing the name of the feature label. Valid fields are `class`, `vendor`, `device`, `subsystem_vendor` and `subsystem_device`.
+`sources.pci.deviceLabelFields` is the set of PCI ID fields to use when constructing the name of the feature label. Valid fields are `class`, `vendor`, `device`, `subsystem_vendor` and `subsystem_device`.
 
 Default: `[class, vendor]`
 
@@ -322,9 +322,9 @@ With the example config above, NFD would publish labels such as `feature.node.ku
 
 [discrete]
 [id="configuring-node-feature-discovery-operator-sources-usb-deviceClassWhitelist_{context}"]
-=== soures.usb.deviceClassWhitelist
+=== sources.usb.deviceClassWhitelist
 
-`soures.usb.deviceClassWhitelist` is a list of USB link:https://www.usb.org/defined-class-codes[device class] IDs for
+`sources.usb.deviceClassWhitelist` is a list of USB link:https://www.usb.org/defined-class-codes[device class] IDs for
 which to publish a feature label. The format of the labels can be further
 configured with `deviceLabelFields`.
 
@@ -340,9 +340,9 @@ sources:
 
 [discrete]
 [id="configuring-node-feature-discovery-operator-sources-usb-deviceLabelFields_{context}"]
-=== soures.usb.deviceLabelFields
+=== sources.usb.deviceLabelFields
 
-`soures.usb.deviceLabelFields` is the set of USB ID fields from which to compose the name of the feature label. Valid fields are `class`, `vendor`, and `device`.
+`sources.usb.deviceLabelFields` is the set of USB ID fields from which to compose the name of the feature label. Valid fields are `class`, `vendor`, and `device`.
 
 Default: `[class, vendor, device]`
 
@@ -358,9 +358,9 @@ With the example config above, NFD would publish labels like: `feature.node.kube
 
 [discrete]
 [id="configuring-node-feature-discovery-operator-sources-custom_{context}"]
-=== soures.custom
+=== sources.custom
 
-`soures.custom` is the list of rules to process in the custom feature source to create user-specific labels.
+`sources.custom` is the list of rules to process in the custom feature source to create user-specific labels.
 
 Default: *empty*