Remove further mentioning of HW VLAN stripping.

1 files changed, 6 insertions, 7 deletions

diff --git a/share/man/man4/vlan.4 b/share/man/man4/vlan.4
index 44306e6b9b7..16894e1bdcb 100644
--- a/share/man/man4/vlan.4
+++ b/share/man/man4/vlan.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: vlan.4,v 1.29 2007/05/31 19:19:53 jmc Exp $
+.\" $OpenBSD: vlan.4,v 1.30 2008/06/01 16:18:49 brad Exp $
 .\"
 .\" Copyright (c) 2000 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -34,7 +34,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: June 1 2008 $
 .Dt VLAN 4
 .Os
 .Sh NAME
@@ -140,7 +140,7 @@ the driver has instructed the chip to do so (such as
 and
 .Xr dc 4 ) ,
 or the driver also takes advantage of a hardware tagging capability,
-and thus oversized frames are never actually sent or received by
+and thus oversized frames are never actually sent by
 .Ox
 (such as
 .Xr txp 4
@@ -167,12 +167,11 @@ This driver only supports such operation with Ethernet devices.
 .Pp
 When the IFCAP_VLAN_HWTAGGING capability is set on the parent interface,
 .Nm
-does not participate in the actual tagging or untagging of Ethernet frames.
-It simply passes the vlan ID on to the parent interface for tagging on transmit,
-and gets a vlan ID for each packet on receive.
+does not participate in the actual tagging of Ethernet frames.
+It simply passes the vlan ID on to the parent interface for tagging on transmit.
 The vlan tagged packet is not actually visible to
 .Ox .
 Thus,
 .Xr bpf 4
 will show untagged packets on the parent interface, although frames
-are actually being transmitted and received with tags on the wire.
+are actually being transmitted with tags on the wire.