Updates misleading example on ONVK additional network config

Author: Steven Smith

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

@@ -15,7 +15,10 @@ The following table describes the configuration parameters for the OVN-Kubernete
 
 |`name`
 |`string`
-|The name of the network. This value must be unique across all `NetworkAttachmentDefinitions`. Failure to make this attribute unique might result in the merging of two networks with the same name. Merging two networks by sharing similar names is unsupported.
+|The name of the network. These networks are not namespaced. For example, you can have a network named
+`l2-network` referenced from two different `NetworkAttachmentDefinitions` that exist on two different
+namespaces. This ensures that pods making use of the `NetworkAttachmentDefinition` on their own different
+namespaces can communicate over the same secondary network. However, those two different `NetworkAttachmentDefinitions` must also share the same network specific parameters such as `topology`, `subnets`, `mtu`, and `excludeSubnets`.
 
 |`type`
 |`string`
@@ -37,7 +40,8 @@ For `"topology":"layer2"` deployments, IPv6 (`2001:DBB::/64`) and dual-stack (`1
 
 |`netAttachDefName`
 |`string`
-| The namespace and the network attachment name. The value must match the values specified for `namespace` and `name` when defining the network attachment definition object. For example, `ns1/l2-network` refers to the `ns1` namespace and the `l2-network` network attachment definition name.
+|The metadata `namespace` and `name` of the network attachment definition object where this
+configuration is included. For example, if this configuration is defined in a `NetworkAttachmentDefinition` in namespace `ns1` named `l2-network`, this should be set to `ns1/l2-network`.
 
 |`excludeSubnets`
 |`string`

modules/configuring-layer-two-switched-topology.adoc

@@ -19,7 +19,7 @@ The following `NetworkAttachmentDefinition` custom resource definition (CRD) YAM
 ----
     {
             "cniVersion": "0.3.1",
-            "name": "ns1-l2-network",
+            "name": "l2-network",
             "type": "ovn-k8s-cni-overlay",
             "topology":"layer2",
             "subnets": "10.100.200.0/24",