Merge pull request #91154 from jab-rh/OCPBUGS-33028

OCPBUGS-33028: Fix vlanID description for OVN-K8s 2ndary network

Author: jab-rh

modules/configuration-ovnk-network-plugin-json-object.adoc

@@ -21,10 +21,9 @@ The CNI specification version. The required value is `0.3.1`.
 |`name`
 |`string`
 |
-The name of the network. These networks are not namespaced. For example, you can have a network named
-`l2-network` referenced from two different `NetworkAttachmentDefinition` CRDs that exist on two different
-namespaces. This ensures that pods making use of the `NetworkAttachmentDefinition` CRD on their own different
-namespaces can communicate over the same secondary network. However, those two different `NetworkAttachmentDefinition` CRDs must also share the same network specific parameters such as `topology`, `subnets`, `mtu`, and `excludeSubnets`.
+The name of the network. These networks are not namespaced. For example, a network named `l2-network` can be referenced by `NetworkAttachmentDefinition` custom resources (CRs) that exist in different namespaces.
+This configuration allows pods that use the `NetworkAttachmentDefinition` CR in different namespaces to communicate over the same secondary network.
+However, the `NetworkAttachmentDefinition` CRs must share the same network-specific parameters, such as `topology`, `subnets`, `mtu`, `excludeSubnets`, and `vlanID`. The `vlanID` parameter applies only when the `topology` field is set to `localnet`.
 
 |`type`
 |`string`