diff --git a/modules/virt-creating-linux-bridge-nad-cli.adoc b/modules/virt-creating-linux-bridge-nad-cli.adoc
index c1377b9806b3..48a05abc9948 100644
--- a/modules/virt-creating-linux-bridge-nad-cli.adoc
+++ b/modules/virt-creating-linux-bridge-nad-cli.adoc
@@ -59,11 +59,6 @@ OSA interfaces on {ibm-z-name} do not support VLAN filtering and VLAN-tagged tra
 ====
 
 <8> Optional: Indicates whether the VM connects to the bridge through the default VLAN. The default value is `true`.
-+
-[NOTE]
-====
-A Linux bridge network attachment definition is the most efficient method for connecting a virtual machine to a VLAN.
-====
 --
 
 . Optional: If you want to connect a VM to the native network, configure the Linux bridge `NetworkAttachmentDefinition` manifest without specifying any VLAN:
diff --git a/modules/virt-creating-linux-bridge-nad-web.adoc b/modules/virt-creating-linux-bridge-nad-web.adoc
index b6cf77c945c4..e68174cb7d28 100644
--- a/modules/virt-creating-linux-bridge-nad-web.adoc
+++ b/modules/virt-creating-linux-bridge-nad-web.adoc
@@ -10,8 +10,6 @@
 
 You can create a network attachment definition (NAD) to provide layer-2 networking to pods and virtual machines by using the {product-title} web console.
 
-A Linux bridge network attachment definition is the most efficient method for connecting a virtual machine to a VLAN.
-
 [WARNING]
 ====
 Configuring IP address management (IPAM) in a network attachment definition for virtual machines is not supported.