[src/trunk]: src/share/man/man4 Fix several typos and improve english.

[rumble <rumble%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/0b48a21dd13c
branches:  trunk
changeset: 586815:0b48a21dd13c
user:      rumble <rumble%NetBSD.org@localhost>
date:      Tue Jan 03 01:22:51 2006 +0000

description:
Fix several typos and improve english.

diffstat:

 share/man/man4/awi.4 |  66 ++++++++++++++++++++++++++-------------------------
 1 files changed, 34 insertions(+), 32 deletions(-)

diffs (131 lines):

diff -r 9a19d3254036 -r 0b48a21dd13c share/man/man4/awi.4
--- a/share/man/man4/awi.4      Tue Jan 03 01:15:47 2006 +0000
+++ b/share/man/man4/awi.4      Tue Jan 03 01:22:51 2006 +0000
@@ -1,4 +1,4 @@
-.\"     $NetBSD: awi.4,v 1.24 2004/11/22 12:23:31 wiz Exp $
+.\"     $NetBSD: awi.4,v 1.25 2006/01/03 01:22:51 rumble Exp $
 .\"
 .\" Copyright (c) 1999,2000,2001 The NetBSD Foundation, Inc.
 .\" All rights reserved.
@@ -33,7 +33,7 @@
 .\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
 .\" POSSIBILITY OF SUCH DAMAGE.
-.Dd November 22, 2004
+.Dd January 2, 2006
 .Dt AWI 4
 .Os
 .Sh NAME
@@ -46,40 +46,41 @@
 The
 .Nm
 driver supports various IEEE 802.11 wireless cards
-which run AMD PCnetMobile firmware based on AMD 79c930 controller
-with Intersil (formerly Harris) PRISM radio chipset.
+that run AMD PCnetMobile firmware based on the AMD 79c930 controller
+with the Intersil (formerly Harris) PRISM radio chipset.
 It provides access to 32kb of memory shared between the controller
 and the host.
-All host/device interaction is via this shared memory, which can be
-accessed either via PCMCIA memory space or I/O space.
+All host/device interaction is accomplished via this shared memory, which
+can be accessed either via PCMCIA or I/O memory spaces.
 The
 .Nm
-driver encapsulates all IP and ARP traffic as 802.11 frames.
+driver encapsulates all IP and ARP traffic in 802.11 frames.
 .Pp
 The driver works both in infrastructure mode and in ad-hoc (independent
 BSS) mode.
 .Pp
-In infrastructure mode, it communicates with an Access Point
-which serves as a link-layer bridge between an Ethernet and
-the wireless network.  An access point also provides roaming capability
-which allows wireless node to move between access points.
+In infrastructure mode, it communicates with an Access Point,
+which serves as a link-layer bridge between an Ethernet segment and
+the wireless network.  An access point also provides roaming capability,
+which allows a wireless node to move between access points.
 .Pp
-In ad-hoc mode, it communicates peer to peer.
-Though it is more efficient to communicate between wireless nodes,
-the coverage is limited spatially due to lack of roaming capability.
+In ad-hoc mode, the device communicates peer to peer.
+Although it is more efficient to communicate between wireless nodes,
+the coverage is limited spatially due to the lack of roaming capability.
 .Pp
-In addition to these two mode in IEEE 802.11 specification, the
+In addition to these two modes in the IEEE 802.11 specification, the
 .Nm
-driver also supports a variant of ad-hoc mode out of spec for DS radio cards,
-which makes possible to communicate with WaveLAN ad-hoc mode of
+driver also supports a variant of ad-hoc mode outside of the spec for
+DS radio cards.
+This makes it possible to communicate with the WaveLAN ad-hoc mode of
 .Xr wi 4
-driver.  The NWID doesn't affect in this mode.
+driver.  The NWID has no effect in this mode.
 .Pp
 Another mode added to the
 .Nm
-driver can be used with old Melco access point with 2Mbps card,
-which actually use IEEE 802.11 ad-hoc mode with encapsulation of
-raw Ethernet packet including header in 802.11 frames.
+driver can be used with old Melco access points with 2Mbps cards.
+This mode actually uses the IEEE 802.11 ad-hoc mode with encapsulation of
+raw Ethernet packets (including headers) in 802.11 frames.
 .Pp
 For more information on configuring this device, see
 .Xr ifconfig 8
@@ -125,16 +126,16 @@
 .Em DS1
 and
 .Em DS2
-media types, while the FH cards support
+media types, while the FH cards support the
 .Em FH1
-media type.  For each media type,
+media type.  For each media type, the
 .Em adhoc
-mediaopt can be used to indicate the driver to operate in ad-hoc mode.
+mediaopt can be used to indicate to the driver to operate in ad-hoc mode.
 The
 .Em flag0
 mediaopt
-should be used only with old access point which operates in IBSS mode.
-For DS radio cards,
+should be used only with old access points, which operate in IBSS mode.
+For DS radio cards, the
 .Em adhoc,flag0
 mediaopt can be used for
 .Xr wi 4
@@ -142,12 +143,15 @@
 .Sh DIAGNOSTICS
 .Bl -diag
 .It "awi0: no suitable CIS info found"
-The device cannot be mapped due to conflict of the resource.
+The device cannot be mapped due to a resource conflict.
 Or, the device failed to initialize its firmware.
 .It "awi0: failed to complete selftest (%s)"
 The device failed to complete its self test.
 In some circumstances, resetting device after power on fails.
-Re-inserting the card or down-then-up interface may be helpful.
+Re-inserting the card or setting the interface up and then down again
+(using 
+.Xr ifconfig 8 )
+may also be helpful.
 .It "awi0: transmit timeout"
 The device failed to generate an interrupt to acknowledge a
 transmitted packet.
@@ -180,9 +184,7 @@
 driver was written by
 .An Bill Sommerfeld
 .Aq sommerfeld%NetBSD.org@localhost .
-Then the
-.Nm
-driver module completely rewritten to support cards with DS phy and
-to support ad-hoc mode by
+It was then completely rewritten to support cards with the DS phy and
+ad-hoc mode by
 .An Atsushi Onoe
 .Aq onoe%NetBSD.org@localhost .