summaryrefslogtreecommitdiff
path: root/share/man/man4/wb.4
diff options
context:
space:
mode:
authorJason McIntyre <jmc@cvs.openbsd.org>2003-04-11 04:32:29 +0000
committerJason McIntyre <jmc@cvs.openbsd.org>2003-04-11 04:32:29 +0000
commitc341e62e40dcf89b30d4a2bcf64d515b776dee81 (patch)
treedd2a9c726fb98b2afc7489db2110c149d2add573 /share/man/man4/wb.4
parentf24ceb1e6c7ff64cfd585e68ef0913af97974acf (diff)
typos;
wscons(4): ok miod@
Diffstat (limited to 'share/man/man4/wb.4')
-rw-r--r--share/man/man4/wb.414
1 files changed, 7 insertions, 7 deletions
diff --git a/share/man/man4/wb.4 b/share/man/man4/wb.4
index e122f2e81f2..4e06166a259 100644
--- a/share/man/man4/wb.4
+++ b/share/man/man4/wb.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: wb.4,v 1.10 2002/09/26 22:09:53 miod Exp $
+.\" $OpenBSD: wb.4,v 1.11 2003/04/11 04:32:28 jmc Exp $
.\"
.\" Copyright (c) 1997, 1998
.\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
@@ -98,7 +98,7 @@ driver supports the following media options:
.Pp
.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
.It full-duplex
-Force full duplex operation
+Force full duplex operation.
.It half-duplex
Force half duplex operation.
.El
@@ -132,13 +132,13 @@ to configure it correctly.
The driver tries to detect this condition and bring
the adapter back to the D0 (full power) state, but this may not be
enough to return the driver to a fully operational condition.
-If you see this message at boot time and the driver fails to attach
-the device as a network interface, you will have to perform second
-warm boot to have the device properly configured.
+If this message appears at boot time and the driver fails to attach
+the device as a network interface, a second warm boot will have to be
+performed to have the device properly configured.
.Pp
Note that this condition only occurs when warm booting from another
operating system.
-If you power down your system prior to booting
+If the system is powered down prior to booting
.Ox ,
the card should be configured correctly.
.El
@@ -166,7 +166,7 @@ driver was written by
.Sh BUGS
The Winbond chip seems to behave strangely in some cases when the
link partner switches modes.
-If for example both sides are set to 10Mbps half-duplex, and the other end
+If, for example, both sides are set to 10Mbps half-duplex, and the other end
is changed to 100Mbps full-duplex, the Winbond's receiver suddenly starts
writing trash all over the RX descriptors.
The