Minor fixup for module ids

Author: jab-rh

modules/machine-config-overview.adoc

@@ -4,7 +4,7 @@
 // * machine_configuration/index.adoc
 
 :_mod-docs-content-type: CONCEPT
-[id="machine-config-overview-{context}"]
+[id="machine-config-overview_{context}"]
 = Machine config overview
 
 The Machine Config Operator (MCO) manages updates to systemd, CRI-O and Kubelet, the kernel, Network Manager and other system features. It also offers a `MachineConfig` CRD that can write configuration files onto the host (see link:https://github.com/openshift/machine-config-operator#machine-config-operator[machine-config-operator]). Understanding what MCO does and how it interacts with other components is critical to making advanced, system-level changes to an {product-title} cluster. Here are some things you should know about MCO, machine configs, and how they are used:

modules/nw-audit-configuration.adoc

@@ -3,7 +3,7 @@
 // * networking/openshift_network_security/logging-network-security.adoc
 
 :_mod-docs-content-type: CONCEPT
-[id="network-policy-audit-configuration-{context}"]
+[id="network-policy-audit-configuration_{context}"]
 = Audit configuration
 
 The configuration for audit logging is specified as part of the OVN-Kubernetes cluster network provider configuration. The following YAML illustrates the default values for the audit logging:

modules/serverless-create-kafka-namespaced-broker.adoc

@@ -3,7 +3,7 @@
 // * serverless/eventing/brokers/kafka-broker.adoc
 
 :_mod-docs-content-type: PROCEDURE
-[id="serverless-create-kafka-namespaced-broker-{context}"]
+[id="serverless-create-kafka-namespaced-broker_{context}"]
 = Creating a Knative broker for Apache Kafka that uses an isolated data plane
 
 :FeatureName: The Knative Broker implementation for Apache Kafka with isolated data plane