Merge pull request #44020 from sjhala-ccs/BZ2043440

BZ2043440: Fixing inaccuracies in assembly

Author: sjhala-ccs

modules/virt-creating-bridge-nad-cli.adoc

@@ -10,8 +10,6 @@ As a network administrator, you can configure a network attachment definition of
 
 .Prerequisites
 
-* The network attachment definition must be in the same namespace as the pod or virtual machine.
-
 * The node must support nftables and the `nft` binary must be deployed to enable MAC spoof check.
 
 .Procedure

modules/virt-creating-bridge-nad-web.adoc

@@ -8,11 +8,7 @@
 [id="virt-creating-bridge-nad-web_{context}"]
 = Creating a Linux bridge network attachment definition in the web console
 
-The network attachment definition is a custom resource that exposes layer-2 devices
-to a specific namespace in your {VirtProductName} cluster.
-
-Network administrators can create network attachment definitions
-to provide existing layer-2 networking to pods and virtual machines.
+Network administrators can create network attachment definitions to provide layer-2 networking to pods and virtual machines.
 
 .Procedure
 

virt/virtual_machines/vm_networking/virt-attaching-vm-multiple-networks.adoc

@@ -12,6 +12,11 @@ You can also import virtual machines with existing workloads that depend on acce
 To attach a virtual machine to an additional network:
 
 . Configure a bridge network attachment definition for a namespace in the web console or CLI.
++
+[NOTE]
+====
+The network attachment definition must be in the same namespace as the pod or virtual machine.
+====
 . Attach the virtual machine to the network attachment definition by using either the web console or the CLI:
 ** In the web console, create a NIC for a new or existing virtual machine.
 ** In the CLI, include the network information in the virtual machine configuration.