13 files changed, 138 insertions, 141 deletions
diff --git a/share/man/man4/ac97.4 b/share/man/man4/ac97.4
index 299b4a5da1e..efdb637d6bc 100644
--- a/share/man/man4/ac97.4
+++ b/share/man/man4/ac97.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ac97.4,v 1.3 2000/05/30 17:10:18 mickey Exp $
+.\"	$OpenBSD: ac97.4,v 1.4 2000/10/13 18:56:48 aaron Exp $
 .Dd October 7, 1999
 .Dt AC97 4
 .Os
@@ -8,17 +8,19 @@
 generic AC-97 codec driver
 .Sh DESCRIPTION
 AC-97 codecs contain the analog-to-digital (A/D), digital-to-analog
-(D/A), and mixing circuitry of many modern sound cards. AC-97 codecs,
-for the most part, do not talk to host busses like the PCI bus
-directly. Instead, they communicate through an interface chip, called
-the host controller. The Ensoniq AudioPCI 97 (see
-.Xr eap 4
-) is an example of such a host controller.
+(D/A), and mixing circuitry of many modern sound cards.
+AC-97 codecs, for the most part, do not talk to host busses like the PCI bus
+directly.
+Instead, they communicate through an interface chip, called
+the host controller.
+The Ensoniq AudioPCI 97 (see
+.Xr eap 4 )
+is an example of such a host controller.
 .Pp
 Unlike many drivers, the
 .Nm
-driver does not appear in the configuration file. Instead, the driver
-is automatically attached by the drivers that require it.
+driver does not appear in the configuration file.
+Instead, the driver is automatically attached by the drivers that require it.
 .Sh SEE ALSO
 .Xr eap 4 ,
 .Xr ich 4 ,
diff --git a/share/man/man4/adv.4 b/share/man/man4/adv.4
index 4c212a58353..c97fa9e149a 100644
--- a/share/man/man4/adv.4
+++ b/share/man/man4/adv.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: adv.4,v 1.7 2000/09/17 00:53:35 aaron Exp $
+.\"	$OpenBSD: adv.4,v 1.8 2000/10/13 18:56:48 aaron Exp $
 .\"
 .\" Copyright (c) 1998, Jason Downs.  All rights reserved.
 .\"
@@ -65,8 +65,6 @@ This board has been sold by SIIG as the Fast SCSI Pro PCI.
 .It
 This board has been sold by Iomega as a Jaz Jet PCI adapter.
 .El
-.Sh BUGS
-Probably.
 .Pp
 .Sh SEE ALSO
 .Xr cd 4 ,
@@ -79,5 +77,5 @@ Probably.
 .Sh AUTHOR
 The
 .Nm
-drivers were written by Baldassare Dante Profeta and Advanced System Products,
-Inc.
+drivers were written by Baldassare Dante Profeta and
+Advanced System Products, Inc.
diff --git a/share/man/man4/aha.4 b/share/man/man4/aha.4
index 053950cbca4..503cd193ccb 100644
--- a/share/man/man4/aha.4
+++ b/share/man/man4/aha.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: aha.4,v 1.2 2000/09/09 17:15:55 deraadt Exp $
+.\"	$OpenBSD: aha.4,v 1.3 2000/10/13 18:56:48 aaron Exp $
 .\"
 .\" Copyright (c) 1994 James A. Jegers
 .\" All rights reserved.
@@ -48,6 +48,7 @@ driver provides support for the following SCSI adapters:
 .It Tekram DC-300B
 .It Tekram DC-320E
 .El
+.Pp
 This driver uses bounce buffers if the machine has more than 16
 megabytes of memory.
 .Sh SEE ALSO
diff --git a/share/man/man4/ahc.4 b/share/man/man4/ahc.4
index 2f0888b5adb..c32b5d60499 100644
--- a/share/man/man4/ahc.4
+++ b/share/man/man4/ahc.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ahc.4,v 1.12 2000/05/26 17:46:10 deraadt Exp $
+.\"	$OpenBSD: ahc.4,v 1.13 2000/10/13 18:56:48 aaron Exp $
 .\"	$NetBSD: ahc.4,v 1.1.2.1 1996/08/25 17:22:14 thorpej Exp $
 .\"
 .\" Copyright (c) 1995, 1996
@@ -28,8 +28,6 @@
 .\"
 .\"
 .Dd March 20, 2000
-.\".Dt AHC 4
-.\".Os FreeBSD
 .Dt AHC 4
 .Os
 .Sh NAME
@@ -140,23 +138,20 @@ is honored by this driver with the stipulation that the
 .Tn BIOS
 must be enabled for
 .Tn EISA
-adaptors.  This includes synchronous/asynchronous transfers,
-maximum synchronous negotiation rate,
-disconnection,
-the host adapter's SCSI ID,
-and,
+adaptors.
+This includes synchronous/asynchronous transfers, maximum synchronous
+negotiation rate, disconnection, the host adapter's SCSI ID, and,
 in the case of
 .Tn EISA
-Twin Channel controllers,
-the primary channel selection.
+Twin Channel controllers, the primary channel selection.
 .Pp
 Performance and feature sets vary throughout the aic7xxx product line.
-The following table provides a comparison of the different chips supported
-by the
+The following table provides a comparison of the different chips
+supported by the
 .Nm
-driver.  Note that wide and twin channel features, although always supported
-by a particular chip, may be disabled in a particular motherboard or card
-design.
+driver.
+Note that wide and twin channel features, although always supported by a
+particular chip, may be disabled in a particular motherboard or card design.
 .Pp
 .Bd -filled -offset indent
 .Bl -column "aic7770 " "10 " "EISA/VL  " "10MHz " "16bit " "SCBs " Features
@@ -199,13 +194,16 @@ sequencer.
 .Sh SCSI CONTROL BLOCKS (SCBs)
 Every transaction sent to a device on the SCSI bus is assigned a
 .Sq SCSI Control Block
-(SCB).  The SCB contains all of the information required by the
-controller to process a transaction.  The chip feature table lists
-the number of SCBs that can be stored in on chip memory.  All chips
-with model numbers greater than or equal to 7870 allow for the on chip
-SCB space to be augmented with external SRAM up to a maximum of 255 SCBs.
+(SCB).
+The SCB contains all of the information required by the
+controller to process a transaction.
+The chip feature table lists the number of SCBs that can be stored
+in on chip memory.
+All chips with model numbers greater than or equal to 7870 allow for the
+on-chip SCB space to be augmented with external SRAM up to a
+maximum of 255 SCBs.
 Very few Adaptec controller have external SRAM.
-
+.Pp
 If external SRAM is not available, SCBs are a limited resource and
 using them in a straight forward manner would only allow us to
 keep as many transactions as there are SCBs outstanding at a time.
@@ -213,46 +211,39 @@ This would not allow enough concurrency to fully utilize the SCSI
 bus and it's devices.
 The solution to this problem is
 .Em SCB Paging ,
-a concept similar to memory paging.  SCB paging takes advantage of
-the fact that devices usually disconnect from the SCSI bus for long
-periods of time without talking to the controller.  The SCBs
-for disconnected transactions are only of use to the controller
-when the transfer is resumed.  When the host queues another transaction
-for the controller to execute, the controller firmware will use a
-free SCB if one is available.  Otherwise, the state of the most recently
-disconnected (and therefor most likely to stay disconnected) SCB is
-saved, via dma, to host memory, and the local SCB reused to start
-the new transaction.  This allows the controller to queue up to
-255 transactions regardless of the amount of SCB space.  Since the
-local SCB space serves as a cache for disconnected transactions, the
-more SCB space available, the less host bus traffic consumed saving
+a concept similar to memory paging.
+SCB paging takes advantage of the fact that devices usually disconnect from
+the SCSI bus for long periods of time without talking to the controller.
+The SCBs for disconnected transactions are only of use to the controller
+when the transfer is resumed.
+When the host queues another transaction for the controller to execute,
+the controller firmware will use a free SCB if one is available.
+Otherwise, the state of the most recently disconnected (and therefore most
+likely to stay disconnected) SCB is saved, via DMA, to host memory,
+and the local SCB reused to start the new transaction.
+This allows the controller to queue up to 255 transactions regardless
+of the amount of SCB space.
+Since the local SCB space serves as a cache for disconnected transactions,
+the more SCB space available, the less host bus traffic consumed saving
 and restoring SCB data.
-.Sh BUGS
-Some Quantum drives (at least the Empire 2100 and 1080s) will not run on an
-.Tn AIC7870
-Rev B in synchronous mode at 10MHz.  Controllers with this problem have a
-42 MHz clock crystal on them and run slightly above 10MHz.  This confuses
-the drive and hangs the bus.  Setting a maximum synchronous negotiation rate
-of 8MHz in the
-.Tn SCSI-Select
-utility
-will allow normal operation.
-
 .Sh SEE ALSO
 .Xr aha 4 ,
 .Xr ahb 4
-.if 0 \{
-.Xr cd 4 ,
-.Xr scsi 4 ,
-.Xr sd 4 ,
-.Xr st 4
-\}
 .Sh AUTHOR
 The
 .Nm
 driver, the
 .Tn AIC7xxx
-sequencer-code assembler,
-and the firmware running on the aic7xxx chips was written by
+sequencer-code assembler, and the firmware running on the aic7xxx chips
+were written by
 .An Justin T. Gibbs .
-
+.Sh BUGS
+Some Quantum drives (at least the Empire 2100 and 1080s) will not run on an
+.Tn AIC7870
+Rev B in synchronous mode at 10MHz.
+Controllers with this problem have a 42 MHz clock crystal on them and
+run slightly above 10MHz.
+This confuses the drive and hangs the bus.
+Setting a maximum synchronous negotiation rate of 8MHz in the
+.Tn SCSI-Select
+utility will allow normal operation.
diff --git a/share/man/man4/aria.4 b/share/man/man4/aria.4
index cb1ec05fa8b..ac9fde5619c 100644
--- a/share/man/man4/aria.4
+++ b/share/man/man4/aria.4
@@ -1,5 +1,5 @@
-.\"	$OpenBSD: aria.4,v 1.3 2000/09/09 17:15:55 deraadt Exp $
-.\"	aria.4
+.\"	$OpenBSD: aria.4,v 1.4 2000/10/13 18:56:48 aaron Exp $
+.\"
 .\" Copyright (c) 1996 Roland C. Dowdeswell
 .\" All rights reserved.
 .\"
@@ -43,25 +43,33 @@ Aria 16 audio device driver
 The
 .Nm
 driver provides support for sound cards based on Sierra Semiconductor's
-Aria chipset.  Cards based on this chipset are capable of recording and
-playing 8- or 16-bit samples in mono or stereo up to 44.1KHz.  Some chipsets
-only play linear or ADCPM, but others will also play Mu-law and A-law
-sounds.  Three different mixer configurations are available.
+Aria chipset.
+Cards based on this chipset are capable of recording and playing
+8- or 16-bit samples in mono or stereo up to 44.1KHz.
+Some chipsets only play linear or ADCPM, but others will also play
+Mu-law and A-law sounds.
+Three different mixer configurations are available.
 .Pp
-The I/O Port Base is selected from 0x280, 0x290, 0x2a0 and 0x2b0. The
-selection method depends on the board. The Aria takes 8 ports.
+The I/O Port Base is selected from 0x280, 0x290, 0x2a0 and 0x2b0.
+The selection method depends on the board.
+The Aria takes 8 ports.
 .Pp
 The IRQ is selected from 10, 11, or 12.
 .Pp
 The DRQ line is chosen from 5 or 6, this driver will work with or without
-a DRQ.  If no DRQ is given, then the
-.Nm aria
+a DRQ.
+If no DRQ is given, then the
+.Nm
 driver will simply use Direct I/O.
 .Pp
 The flags currently supported are 0x1, for the Prometheus Aria 16/Aria 16se.
-This flag tells the driver to initialise the card.  It is a weird undocumented
-piece of horribleness, but the card will not respond until you twiddle with
-the joystick port...
+This flag tells the driver to initialise the card.
+It is a weird and undocumented piece of horribleness, but the card
+will not respond until you twiddle with the joystick port.
+.Sh SEE ALSO
+.Xr audio 4
+.Sh AUTHOR
+Roland C. Dowdeswell <roland@imrryr.org>
 .Sh BUGS
 The driver has only been tested on a Prometheus Aria 16.
 .Pp
@@ -69,14 +77,10 @@ No DMA support, yet, so don't bother setting a DRQ.
 .Pp
 The full-duplex features are horribly inconsistent (i.e., unusable).
 .Pp
-The card sometimes drops out, and needs to be reset.  This can be
-accomplished by opening and closing
+The card sometimes drops out, and needs to be reset.
+This can be accomplished by opening and closing
 .Pa /dev/audio ,
 e.g.,
 .Dq echo -n >/dev/audio
 .Pp
 The joystick and MIDI port interfaces are not supported.
-.Sh SEE ALSO
-.Xr audio 4
-.Sh AUTHOR
-Roland C. Dowdeswell <roland@imrryr.org>
diff --git a/share/man/man4/ast.4 b/share/man/man4/ast.4
index 8670a983b7f..c1a81adb8ae 100644
--- a/share/man/man4/ast.4
+++ b/share/man/man4/ast.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ast.4,v 1.3 2000/09/09 17:15:55 deraadt Exp $
+.\"	$OpenBSD: ast.4,v 1.4 2000/10/13 18:56:49 aaron Exp $
 .\"	$NetBSD: ast.4,v 1.7 1996/03/16 00:07:07 thorpej Exp $
 .\"
 .\" Copyright (c) 1990, 1991 The Regents of the University of California.
@@ -51,7 +51,7 @@ multiplexing serial communications interface
 .Cd "com* at ast? slave ?"
 .Sh DESCRIPTION
 The
-.Nm ast
+.Nm
 driver provides support for boards that multiplex together up to four
 .Tn EIA
 .Tn RS-232C
diff --git a/share/man/man4/atalk.4 b/share/man/man4/atalk.4
index 8c609dd0f96..74db9a12bb5 100644
--- a/share/man/man4/atalk.4
+++ b/share/man/man4/atalk.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: atalk.4,v 1.6 1999/09/23 04:12:04 alex Exp $
+.\"	$OpenBSD: atalk.4,v 1.7 2000/10/13 18:56:49 aaron Exp $
 .\"
 .\" This file is derived from the atalk.4 man page in the Netatlk 1.4b2
 .\" distribution. That distribution is covered by the following copyright:
@@ -50,18 +50,19 @@ Token Ring, and asynchronous serial connections (using either
 AppleTalk Remote Access
 .Pq Tn ARA
 or
-.Tn PPP
-).   Currently, this AppleTalk implementation supports only
-Ethernet.
+.Tn PPP ) .
+Currently, this AppleTalk implementation supports only Ethernet.
 .\" and Token Ring?
 .Pp
 AppleTalk packets are encapsulated on the ethernet using the EtherTalk
-Link Access Protocol (ELAP).   Local network address resolution is
-handled using the AppleTalk Address Resolution Protocol (AARP).
+Link Access Protocol (ELAP).
+Local network address resolution is handled using the
+AppleTalk Address Resolution Protocol (AARP).
 Neither of these protocols is exposed to user-mode applications.
 .Sh ADDRESSING
 AppleTalk addresses are three byte quantities, stored in network
-byte order. The include file
+byte order.
+The include file
 .Aq Pa netatalk/at.h
 defines the AppleTalk address format.
 
@@ -98,7 +99,7 @@ corresponds to the machine's ``primary'' address (the first
 configured).
 .\".Dv ATADDR_LATENET
 .\"causes the address in outgoing packets to be determined when a packet
-.\"is sent, i.e. determined late.
+.\"is sent, i.e., determined late.
 .\".Dv ATADDR_LATENET
 .\"is equivalent to opening one socket for each network interface.
 The port of a socket and
diff --git a/share/man/man4/audio.4 b/share/man/man4/audio.4
index a7b0f88e29a..b7828da6bf4 100644
--- a/share/man/man4/audio.4
+++ b/share/man/man4/audio.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: audio.4,v 1.12 2000/05/30 17:14:57 mickey Exp $
+.\"	$OpenBSD: audio.4,v 1.13 2000/10/13 18:56:49 aaron Exp $
 .\"	$NetBSD: audio.4,v 1.20 1998/05/28 17:27:15 augustss Exp $
 .\"
 .\" Copyright (c) 1996 The NetBSD Foundation, Inc.
@@ -157,7 +157,7 @@ and
 calls can be used.
 The playing and recording buffers are distinct and must be
 mapped separately if both are to be used.
-Only encodings that are not emulated (i.e. where
+Only encodings that are not emulated (i.e., where
 .Dv AUDIO_ENCODINGFLAG_EMULATED
 is not set) work properly for a mapped device.
 .Pp
@@ -318,7 +318,8 @@ is the maximum value and for
 sets the current audio blocksize.
 The generic audio driver layer and the hardware driver have the
 opportunity to adjust this block size to get it within
-implementation-required limits.  Upon return from an
+implementation-required limits.
+Upon return from an
 .Dv AUDIO_SETINFO
 call, the actual blocksize set is returned in this field.
 Normally the
@@ -571,8 +572,8 @@ commands.
 The
 .Va type
 field identifies the type of this mixer control.
-Enumeration types are typically used for on/off style controls (e.g. a
-mute control) or for input/output device selection (e.g. select
+Enumeration types are typically used for on/off style controls (e.g., a
+mute control) or for input/output device selection (e.g., select
 recording input source from CD, line in, or microphone).
 Set types are similar to enumeration types but any combination
 of the mask bits can be used.
@@ -585,8 +586,8 @@ For example, a mixer level controlling the input gain on the ``line
 in'' circuit would be a class that matches an input class device
 with the name ``Inputs'' (AudioCInputs).
 Mixer controls which control audio circuitry for a particular audio
-source (e.g. line-in, CD in, DAC output) are collected under the input class,
-while those which control all audio sources (e.g. master volume,
+source (e.g., line-in, CD in, DAC output) are collected under the input class,
+while those which control all audio sources (e.g., master volume,
 equalization controls) are under the output class.
 .Pp
 The
@@ -627,20 +628,19 @@ mixer controls because they use a name from one of the AudioC* string values.
 .El
 .Sh SEE ALSO
 .Xr audioctl 1 ,
-.Xr mixerctl 1 .
-.br
+.Xr mixerctl 1 ,
 .Xr ioctl 2 ,
-.Xr ossaudio 3 .
+.Xr ossaudio 3 ,
 .Xr ac97 4 ,
-.Xr audio 9 .
-.br
+.Xr audio 9
+.Pp
 For ports using the ISA bus:
 .Xr gus 4 ,
 .Xr pas 4 ,
 .Xr pss 4 ,
 .Xr sb 4 ,
 .Xr wss 4 .
-.br
+.Pp
 For ports using the PCI bus:
 .Xr cmpci 4 ,
 .Xr eap 4 ,
@@ -655,4 +655,3 @@ If the device is used in
 .Xr mmap 2
 it is currently always mapped for writing (playing) due to
 VM system weirdness.
-.Pp
diff --git a/share/man/man4/awi.4 b/share/man/man4/awi.4
index 5a750a49f6f..c61fb6110aa 100644
--- a/share/man/man4/awi.4
+++ b/share/man/man4/awi.4
@@ -1,8 +1,7 @@
 .\"     $NetBSD: awi.4,v 1.1 1999/11/04 19:36:01 sommerfeld Exp $
-.\"	$OpenBSD: awi.4,v 1.2 2000/07/20 08:48:17 deraadt Exp $
+.\"	$OpenBSD: awi.4,v 1.3 2000/10/13 18:56:49 aaron Exp $
 .\"
-.\"
-.\"	$Id: awi.4,v 1.2 2000/07/20 08:48:17 deraadt Exp $
+.\"	$Id: awi.4,v 1.3 2000/10/13 18:56:49 aaron Exp $
 .\"
 .Dd October 31, 1999
 .Dt AWI 4
@@ -12,7 +11,7 @@
 .Nd
 Bay Networks BayStack 650 IEEE 802.11FH PCMCIA driver
 .Sh SYNOPSIS
-.Cd "awi*     at pcmcia? function ?"
+.Cd "awi* at pcmcia? function ?"
 .Sh DESCRIPTION
 The
 .Nm
@@ -25,15 +24,16 @@ All host/device interaction is via this shared memory, which can be
 accessed either via PCMCIA memory space or I/O space.
 The
 .Nm
-driver encapsulates all IP and ARP traffic as 802.11 frames. Transmit
-speed is fixed at 1Mbps.
+driver encapsulates all IP and ARP traffic as 802.11 frames.
+Transmit speed is fixed at 1Mbps.
 .Pp
 The driver currently only works in infrastructure mode, communicating
 with an Access Point which serves as a link-layer bridge between an
 ethernet and the wireless network.
 .Pp
 This card seems to take between 5 and 20 seconds after it has been brought up
-to synchronize with an AP.  When using
+to synchronize with an AP.
+When using
 .Xr dhclient 8
 to automatically configure an address on this card, it may be
 advisable to delay the invocation of dhclient for about 10 seconds
@@ -48,7 +48,8 @@ For more information on configuring this device, see
 Indicates that the driver was not able to allocate 32kb of PCMCIA bus
 address space into which to map the device; the driver will use the
 (slightly slower) i/o-space only access methods to read and write to
-the shared memory.  This message is in some sense to be expected and
+the shared memory.
+This message is in some sense to be expected and
 should not be a cause for alarm.
 See
 .Xr pcmcia 4
@@ -79,9 +80,6 @@ Point recently, and is looking for a new access point.
 The access point the card was most recently associated with has
 forgotten about us.
 .El
-.Sh BUGS
-Doesn't support ad-hoc mode or WEP.
-Round trip times seem higher than what one might expect.
 .Sh SEE ALSO
 .Xr ray 4 ,
 .Xr arp 4 ,
@@ -107,3 +105,6 @@ and ported to
 .Ox
 by
 .An Angelos D. Keromytis Aq angelos@dsl.cis.upenn.edu
+.Sh BUGS
+Doesn't support ad-hoc mode or WEP.
+Round trip times seem higher than what one might expect.
diff --git a/share/man/man4/brgphy.4 b/share/man/man4/brgphy.4
index 3f50a17197a..9429e799847 100644
--- a/share/man/man4/brgphy.4
+++ b/share/man/man4/brgphy.4
@@ -1,6 +1,6 @@
-.\"	$OpenBSD: brgphy.4,v 1.1 2000/08/28 13:52:58 jason Exp $
+.\"	$OpenBSD: brgphy.4,v 1.2 2000/10/13 18:56:49 aaron Exp $
 .\"
-.\"Copyright (c) 2000 Jason L. Wright (jason@thought.net)
+.\" Copyright (c) 2000 Jason L. Wright (jason@thought.net)
 .\" All rights reserved.
 .\"
 .\" Redistribution and use in source and binary forms, with or without
diff --git a/share/man/man4/bridge.4 b/share/man/man4/bridge.4
index bb8c3023029..6cd3c6f3479 100644
--- a/share/man/man4/bridge.4
+++ b/share/man/man4/bridge.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: bridge.4,v 1.23 2000/08/03 05:04:18 jason Exp $
+.\"	$OpenBSD: bridge.4,v 1.24 2000/10/13 18:56:50 aaron Exp $
 .\"
 .\" Copyright (c) 1999, 2000 Jason L. Wright (jason@thought.net)
 .\" All rights reserved.
@@ -39,10 +39,10 @@
 .Cd pseudo-device bridge 2
 .Sh DESCRIPTION
 The
-.Nm bridge
+.Nm
 device creates a logical link between two or more Ethernet interfaces or
 encapsulation interfaces (see
-.Xr enc 4 ).
+.Xr enc 4 ) .
 This link between the interfaces selectively forwards frames from
 each interface on the bridge to every other interface on the bridge.
 A bridge can serve several services, including, isolation of traffic between
@@ -91,7 +91,7 @@ input rules for the source interface are checked with the datagram;
 output rules have no effect.
 .Sh IOCTLS
 A
-.Nm bridge
+.Nm
 interface responds to all of the
 .Xr ioctl 2
 calls specific to other interfaces listed in
@@ -99,7 +99,7 @@ calls specific to other interfaces listed in
 The following
 .Xr ioctl 2
 calls are specific to
-.Nm bridge
+.Nm
 devices.
 They are defined in
 .Aq Pa sys/sockio.h .
diff --git a/share/man/man4/bt.4 b/share/man/man4/bt.4
index 8d9da32b48a..e45891c21c2 100644
--- a/share/man/man4/bt.4
+++ b/share/man/man4/bt.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: bt.4,v 1.2 2000/09/09 17:15:55 deraadt Exp $
+.\"	$OpenBSD: bt.4,v 1.3 2000/10/13 18:56:50 aaron Exp $
 .\"
 .\" Copyright (c) 1994 James A. Jegers
 .\" All rights reserved.
@@ -46,9 +46,9 @@ The Buslogic BT-930 is not supported.
 .Pp
 The PCI versions of this card will require the Buslogic BIOS
 "Advanced Options" suboption called "Set ISA Compatible IO Port"
-to be set to the value "Primary" or "Alternate".  Some cards have
-an option called "Set host adapter IO port address as default" instead;
-for those boards you should set the value to "false".
+to be set to the value "Primary" or "Alternate".
+Some cards have an option called "Set host adapter IO port address as default"
+instead; for those boards you should set the value to "false".
 .Sh SEE ALSO
 .Xr cd 4 ,
 .Xr ch 4 ,
diff --git a/share/man/man4/ipsec.4 b/share/man/man4/ipsec.4
index a1a79bb8d19..0d4f46b3064 100644
--- a/share/man/man4/ipsec.4
+++ b/share/man/man4/ipsec.4
@@ -1,4 +1,4 @@
-.\" $OpenBSD: ipsec.4,v 1.33 2000/09/29 04:03:18 angelos Exp $
+.\" $OpenBSD: ipsec.4,v 1.34 2000/10/13 18:56:50 aaron Exp $
 .\" Copyright 1997 Niels Provos <provos@physnet.uni-hamburg.de>
 .\" All rights reserved.
 .\"
@@ -282,8 +282,8 @@ packets that have been or will be processed by
 .Tn IPsec.
 .Pp
 .Xr ipnat 8
-can also be applied to 
-.Nm enc# 
+can also be applied to
+.Nm enc#
 interfaces, but special care should be taken because of the interactions
 between NAT and the IPsec flow matching, especially on the packet output path.
 Inside the TCP/IP stack, packets go through the following stages:
@@ -292,12 +292,12 @@ UL/R -> [X] -> IPF/NAT(enc0) -> IPSec -> IPF/NAT(IF) -> IF
 UL/R <-------- IPF/NAT(enc0) <- IPSec -> IPF/NAT(IF) <- IF
 .Ed
 .Pp
-With 
+With
 .Tn IF
-being the real interface and 
+being the real interface and
 .Tn UL/R
-the Upper Layer or Routing code. 
-The 
+the Upper Layer or Routing code.
+The
 .Tn [X]
 Stage on the output path represents the point where the packet
 is matched against the IPsec flow database (SPD) to determine if and how