[libvirt PATCH 14/23] docs: remove use of the term 'enslaved' wrt tap & bridge devices

[Daniel P. Berrangé <berrange@xxxxxxxxxx>]

Network interfaces are simply attached to a bridge device.

Signed-off-by: Daniel P. Berrangé <berrange@xxxxxxxxxx>
---
 docs/firewall.html.in     | 4 ++--
 docs/formatdomain.html.in | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/firewall.html.in b/docs/firewall.html.in
index bfb5a47b1c..2d55021d9b 100644
--- a/docs/firewall.html.in
+++ b/docs/firewall.html.in
@@ -12,7 +12,7 @@
       <li>The virtual network driver
           <br /><br />
           This provides an isolated bridge device (ie no physical NICs
-          enslaved). Guest TAP devices are attached to this bridge.
+          attached). Guest TAP devices are attached to this bridge.
           Guests can talk to each other and the host, and optionally the
           wider world.
           <br /><br />
@@ -46,7 +46,7 @@
     </p>
     <p>Thus the virtual network driver in libvirt was invented. This takes
        the form of an isolated bridge device (ie one with no physical NICs
-       enslaved). The TAP devices associated with the guest NICs are attached
+       attached). The TAP devices associated with the guest NICs are attached
        to the bridge device. This immediately allows guests on a single host
        to talk to each other and to the host OS (modulo host IPtables rules).
     </p>
diff --git a/docs/formatdomain.html.in b/docs/formatdomain.html.in
index 07d0fa5c70..3f4d633909 100644
--- a/docs/formatdomain.html.in
+++ b/docs/formatdomain.html.in
@@ -5785,11 +5785,11 @@
     <p>
       Provides a bridge from the VM directly to the LAN. This assumes
       there is a bridge device on the host which has one or more of the hosts
-      physical NICs enslaved. The guest VM will have an associated tun device
+      physical NICs attached. The guest VM will have an associated tun device
       created with a name of vnetN, which can also be overridden with the
       &lt;target&gt; element (see
       <a href="#elementsNICSTargetOverride">overriding the target element</a>).
-      The tun device will be enslaved to the bridge. The IP range / network
+      The tun device will be attached to the bridge. The IP range / network
       configuration is whatever is used on the LAN. This provides the guest VM
       full incoming &amp; outgoing net access just like a physical machine.
     </p>
-- 
2.24.1