From: Andre Noll <maan@tuebingen.mpg.de>
Date: Sat, 14 Oct 2023 13:59:26 +0000 (+0200)
Subject: Networking: Slightly reword veth paragraph.
X-Git-Url: http://git.tue.mpg.de/?a=commitdiff_plain;h=c8dbbdc20bbcf726672198332ecbda1b3ae642e8;p=aple.git

Networking: Slightly reword veth paragraph.

Don't imply that eth0 is always a physical interface and fix a
typo/braino: one instance of pair needs to be peer.
---

diff --git a/Networking.m4 b/Networking.m4
index a3a5d65..6acf215 100644
--- a/Networking.m4
+++ b/Networking.m4
@@ -156,15 +156,15 @@ section aim to get the reader started with both tools. </p>
 
 SUBSECTION(«Virtual Ethernet Interfaces»)
 
-<p> A bridge can accommodate physical devices like <code> eth0 </code>
-as well as virtual devices. On Linux systems the common approach
-to equip virtual machines with network interfaces employs the <em>
-virtual ethernet </em> (veth) device driver. This driver provides
-virtual pairs of devices where each pair represents an ethernet
-tunnel. Ethernet frames received by one end appear on its pair. To
-set up the network interface for a virtual machine, one end of the
-pair is added to a bridge on the host system while the other end
-represents the ethernet device of the virtual machine. </p>
+<p> A bridge can accommodate physical devices as well as virtual
+devices. On Linux systems the common approach to equip virtual machines
+with network interfaces employs the <em>virtual ethernet</em> device
+driver, veth. This driver provides virtual pairs of devices where
+each pair represents an ethernet tunnel. Ethernet frames received
+by one end appear on its peer. To set up the network interface for
+a virtual machine, one end of the pair is added to a bridge on the
+host system while the other end represents the ethernet device of
+the virtual machine. </p>
 
 EXERCISES()
 <ul>