Make a few content fixes/additions to tap(4) manual page.

PR:		36985
Submitted by:	Hiten Pandya <hiten@uk.FreeBSD.org>
MFC after:	4 days

1 files changed, 23 insertions, 16 deletions

diff --git a/share/man/man4/tap.4 b/share/man/man4/tap.4
index 9deb12f..7b8b415 100644
--- a/share/man/man4/tap.4
+++ b/share/man/man4/tap.4
@@ -231,7 +231,9 @@ On the last close of the data device, the interface is
 brought down
 (as if with
 .Dq ifconfig tap Ns Sy N No down )
-unless the devices is a VMnet device.
+unless the device is a 
+.Em VMnet 
+device.
 All queued frames are thrown away.
 If the interface is up when the data
 device is not open, output frames are thrown away rather than
@@ -239,32 +241,41 @@ letting them pile up.
 .Pp
 The
 .Nm
-device is also can be used with the VMware port as a replacement
-for the old VMnet device driver.
+device can also be used with the VMware port as a replacement
+for the old 
+.Em VMnet 
+device driver.
 The driver uses the minor number
 to select between
 .Nm
 and
 .Nm vmnet
 devices.
-VMnet minor numbers begin at
+.Em VMnet 
+minor numbers begin at
 .Va 0x800000
 +
-.Va N .
-Where
+.Va N ;
+where
 .Va N
-is a VMnet unit number.
-In this case control device is expected to be
+is a 
+.Em VMnet 
+unit number.
+In this case the control device is expected to be
 .Pa /dev/vmnet Ns Sy N ,
-and network interface will be
+and the network interface will be
 .Sy vmnet Ns Ar N .
-Additionally, VMnet devices do not ifconfig themselves down when the
+Additionally, 
+.Em VMnet 
+devices do not 
+.Xr ifconfig 8 
+themselves down when the
 control device is closed.
 Everything else is the same.
 .Pp
-In addition to mentioned above
+In addition to the above mentioned 
 .Xr ioctl 2
-there is one additional one for the VMware port.
+calls, there is an additional one for the VMware port.
 .Bl -tag -width VMIO_SIOCSETMACADDR
 .It Dv VMIO_SIOCSIFFLAGS
 VMware
@@ -273,7 +284,3 @@ VMware
 .Sh SEE ALSO
 .Xr inet 4 ,
 .Xr intro 4
-.\" .Sh BUGS
-.Sh AUTHORS
-This man page has been obtained from
-.Fx .