tweak previous;

1 files changed, 10 insertions, 9 deletions

diff --git a/share/man/man4/bpe.4 b/share/man/man4/bpe.4
index 21eb58b597f..5d852f62c89 100644
--- a/share/man/man4/bpe.4
+++ b/share/man/man4/bpe.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: bpe.4,v 1.2 2018/12/20 23:16:47 dlg Exp $
+.\" $OpenBSD: bpe.4,v 1.3 2018/12/20 23:57:06 jmc Exp $
 .\"
 .\" Copyright (c) 2018 David Gwynne <dlg@openbsd.org>
 .\"
@@ -25,8 +25,8 @@
 .Sh DESCRIPTION
 The
 .Nm bpe
-driver allows construction of IEEE 802.1Q Provider Backbone Bridge
-(PBB) networks by acting as a Backbone Edge Bridge (BEB).
+driver creates IEEE 802.1Q Provider Backbone Bridge (PBB) networks
+by acting as a Backbone Edge Bridge (BEB).
 PBB, also known as mac-in-mac, was originally specified in
 IEEE 802.1ah-2008 and became part of IEEE 802.1Q-2011.
 .Pp
@@ -38,7 +38,7 @@ packets for different networks but retain the Ethernet addresses
 of encapsulated traffic, PBB completely encapsulates Ethernet packets
 for transmission between BEBs on a PBBN.
 This removes the need for intermediate BCB devices on the backbone
-network  to learn the Ethernet addresses of devices on the encapsulated
+network to learn the Ethernet addresses of devices on the encapsulated
 network, but requires each BEB to maintain a mapping of addresses
 on the encapsulated network to peer BEBs.
 .Pp
@@ -49,7 +49,7 @@ encapsulated Ethernet frame.
 The I-TAG contains a 24-bit Backbone Service Instance Identifiier
 (I-SID) to differentiate different PBBNs on the same backbone network
 .Pp
-IEEE 802.1Q describes Customer VLANs being encapsulated by PBB,
+IEEE 802.1Q describes customer VLANs being encapsulated by PBB,
 which in turn uses an S-VLAN service.
 This can be implemented with
 .Xr vlan 4
@@ -71,18 +71,19 @@ driver implements a learning bridge on each interface.
 The driver will learn the mapping of BEPs to encapsulated Ethernet
 address based on traffic received from other devices on the backbone
 network.
-Traffic sent to broadcast, multicast, or unknown unicast Etherent
+Traffic sent to broadcast, multicast, or unknown unicast Ethernet
 addresses will be flooded to a multicast address on the backbone network.
 The multicast address used for each PBB Service Instance
 will begin with 01:1e:83 as the first three octets, with the I-SID
-as the last three octets, e.g., a
+as the last three octets.
+For example, a
 .Nm bpe
 interface with a vnetid of 1024 (0x400 in hex) will have a multicast
 group address of 01:1e:83:00:04:00.
 The address learning in
 .Nm bpe
-only uses the Ethernet addresses of encapsulated traffic for it's
-forwarding decisions, it does not use VLAN or S-VLAN tags to
+only uses the Ethernet addresses of encapsulated traffic for its
+forwarding decisions; it does not use VLAN or S-VLAN tags to
 differentiate services.
 .Pp
 .Nm bpe