Powered by @mantoya.

o) fix bogus .Xr usage;

millert@ ok.

1 files changed, 4 insertions, 4 deletions

diff --git a/share/man/man4/vlan.4 b/share/man/man4/vlan.4
index 26b0a088c3a..02bd44c9c9e 100644
--- a/share/man/man4/vlan.4
+++ b/share/man/man4/vlan.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: vlan.4,v 1.12 2001/08/03 23:21:20 chris Exp $
+.\" $OpenBSD: vlan.4,v 1.13 2001/08/20 05:57:55 mpech Exp $
 .\"
 .Dd January 9, 2000
 .Dt VLAN 4
@@ -84,18 +84,18 @@ If the IFCAP_VLAN_MTU capability is set on a vlan parent,
 assumes that Ethernet chip on the parent can handle
 oversized frames.
 Either the chip allows 1518 byte frames by default (such as
-.Xr rl 4 ),
+.Xr rl 4 ) ,
 the driver has instructed the chip to do so (such as
 .Xr fxp 4 
 and
-.Xr dc 4 ),
+.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
 .Ox
 (such as
 .Xr txp 4
 and
-.Xr ti 4 .)
+.Xr ti 4 ) .
 .Sh SEE ALSO
 .Xr bridge 4 ,
 .Xr inet 4 ,