Remove single-space hard sentence breaks. These degrade the quality

of the typeset output, tend to make diffs harder to read and provide
bad examples for new-comers to mdoc.

19 files changed, 182 insertions, 91 deletions

diff --git a/share/man/man4/man4.i386/alpm.4 b/share/man/man4/man4.i386/alpm.4
index 9b4c18c..f8177e0 100644
--- a/share/man/man4/man4.i386/alpm.4
+++ b/share/man/man4/man4.i386/alpm.4
@@ -39,7 +39,8 @@ This driver provides access to the
 function is implemented.
 
 The embedded SMBus controller of the Aladdin chipset may give you access
-to the monitoring facilities of your mainboard. See
+to the monitoring facilities of your mainboard.
+See
 .Xr smb 4
 for writing user code to fetch voltages, temperature and so on from the
 monitoring chip of your mainboard.
diff --git a/share/man/man4/man4.i386/ar.4 b/share/man/man4/man4.i386/ar.4
index 0502e17..f6f6474 100644
--- a/share/man/man4/man4.i386/ar.4
+++ b/share/man/man4/man4.i386/ar.4
@@ -43,12 +43,15 @@ synchronous Digi/Arnet device driver.
 The
 .Nm ar
 driver supports the Digi/Arnet SYNC/570i ISA and PCI cards that is based on the
-HD64570 chip. Both the 2 and 4 port cards are supported and auto detected.
+HD64570 chip.
+Both the 2 and 4 port cards are supported and auto detected.
 .Pp
 The standard
 .Tn FreeBSD
-sppp code is used for the link level layer. The
-default protocol used is PPP. The Cisco HDLC protocol can be used by
+sppp code is used for the link level layer.
+The
+default protocol used is PPP.
+The Cisco HDLC protocol can be used by
 adding
 .Ar link2
 to
@@ -83,7 +86,8 @@ prepended, e.g.,
 .Sh DIAGNOSTICS
 .Bl -diag
 .It "ar%d: Warning illegal interrupt %d."
-The card cannot use the specified interrupt. Choose a different one.
+The card cannot use the specified interrupt.
+Choose a different one.
 .El
 .Sh FILES
 .Bl -tag -width /sys/i386/isa/ic/hd64570.h -compact
@@ -94,7 +98,8 @@ The card cannot use the specified interrupt. Choose a different one.
 .It Pa /sys/pci/if_ar_p.c
 .El
 .Sh BUGS
-At the moment only the V.35 and X.21 interfaces are tested. The others
+At the moment only the V.35 and X.21 interfaces are tested.
+The others
 may need tweaks to the clock selection code.
 .Pp
 The code can probably stand some optimizing.
diff --git a/share/man/man4/man4.i386/asc.4 b/share/man/man4/man4.i386/asc.4
index ad24fa1..18bfd37 100644
--- a/share/man/man4/man4.i386/asc.4
+++ b/share/man/man4/man4.i386/asc.4
@@ -48,7 +48,8 @@ It uses DMA and interrupts.
 Up to 50 lines of scanned input data are buffered in the driver.
 .Pp
 The device can operate at four different resolutions: 100, 200, 300
-and 400 dots per inch. It produces a simple bitmap with the most
+and 400 dots per inch.
+It produces a simple bitmap with the most
 significant bit at the left side.  The driver can optionally output
 the simple portable bitmap file format
 .Xr pbm 5 ;
@@ -100,7 +101,8 @@ Get the current height of the bitmap.
 .It Dv ASC_SBLEN
 .Pq Li int
 Set the length of the buffer used internally to do the DMA transfer.
-The buffer length is supplied in lines of the bitmap. Since the buffer
+The buffer length is supplied in lines of the bitmap.
+Since the buffer
 size limit is (currently) 0x3000 bytes, the maximum number of lines
 allowed will vary with the width of each line.  An
 .Er ENOMEM
@@ -110,7 +112,8 @@ error is returned if the requested length would exceed this limit.
 Get the current buffer length in lines.
 .It Dv ASC_SBTIME
 .Pq Li int
-Set the timeout for the completion of reading one buffer. Since a
+Set the timeout for the completion of reading one buffer.
+Since a
 handy scanner is a human/computer interface timeout values are usually
 higher than those of a flat scanner; the default is 15 seconds.  After
 timeout is reached the read operation will fail with 
diff --git a/share/man/man4/man4.i386/bktr.4 b/share/man/man4/man4.i386/bktr.4
index 1fb8661..01e857d 100644
--- a/share/man/man4/man4.i386/bktr.4
+++ b/share/man/man4/man4.i386/bktr.4
@@ -80,7 +80,8 @@ This means that there are (216*4096) bytes available for use.
 .br
 .Em options BROOKTREE_SYSTEM_DEFAULT=BROOKTREE_NTSC
 .br
-One of these options can be used to set the default video format for the driver. This fixed random hangs and lockups with the VideoLogic Captivator PCI card.
+One of these options can be used to set the default video format for the driver.
+This fixed random hangs and lockups with the VideoLogic Captivator PCI card.
 .br
 .Pp
 The following sysctls may be used to further configure the driver:
@@ -177,7 +178,8 @@ An FM Radio Tuner for cards which have an FM Radio tuner fitted. - requires that
 .Em The X Window System
 and
 .Em The Ports Collection
-also be installed. It also requires
+also be installed.
+It also requires
 .Em Motif
 or the
 .Em lesstif
diff --git a/share/man/man4/man4.i386/cs.4 b/share/man/man4/man4.i386/cs.4
index 10be006..9a0fe3b 100644
--- a/share/man/man4/man4.i386/cs.4
+++ b/share/man/man4/man4.i386/cs.4
@@ -77,7 +77,8 @@ The IRQ specified in the configuration entry is not valid for the adapter.
 .It "cs%d: Could not allocate memory for NIC"
 There is a critical memory shortage.  The adapter will not function.
 .It "cs%d: Adapter has no media"
-The adapter is not configured for a specific media type. The media type will have
+The adapter is not configured for a specific media type.
+The media type will have
 to be manually set.
 .It "This is a %s, but LDN %d is disabled"
 The PnP probe code found a recognised adapter, but the adapter is disabled.
diff --git a/share/man/man4/man4.i386/ie.4 b/share/man/man4/man4.i386/ie.4
index 9e7405c..88783ac 100644
--- a/share/man/man4/man4.i386/ie.4
+++ b/share/man/man4/man4.i386/ie.4
@@ -17,7 +17,8 @@ ethernet device driver
 The
 .Nm ie
 driver provides support for 8 and 16bit ISA ethernet cards that are based on
-the Intel i82586 chip. It supports the AT&T Starlan 10 and Starlan Fiber, 
+the Intel i82586 chip.
+It supports the AT&T Starlan 10 and Starlan Fiber, 
 the EN100, the Intel EtherExpress 16, the 3COM 3C507 and the RACAL Interlan 
 NI5210.
 .Pp
@@ -40,16 +41,20 @@ interrupt than the one specified in the kernel configuration file.
 .It "ie%d: reset"
 The Intel i82586 had to be reset by the driver.
 .It "ie%d: transceiver problem"
-The driver has detected a problem with the ethernet transceiver. This is
+The driver has detected a problem with the ethernet transceiver.
+This is
 usually due to a loose or broken transceiver cable when using an external
-transceiver. When you experience this problem with an on-card transceiver
+transceiver.
+When you experience this problem with an on-card transceiver
 your card may be incorrectly jumpered for to use an external transceiver.
 Worst case your on-board transceiver may be broken.
 .It "ie%d: TDR detected an open %d clocks away"
-The driver detected an open circuit in the ethernet cable. Check your
+The driver detected an open circuit in the ethernet cable.
+Check your
 coax cable and terminator resistors.
 .It "ie%d: TDR detected a short %d clocks away"
-The driver detected a short circuit in the ethernet cable. Check your 
+The driver detected a short circuit in the ethernet cable.
+Check your 
 coax cable and terminator resistors.
 .It "ie%d: TDR returned unknown status %x"
 The driver got an unknown status from the card during the ethernet cable
@@ -63,7 +68,8 @@ The programming of the Ethernet (MAC) address failed.
 .El
 .Sh CAVEATS
 The Racal Interlan NI5210 comes in variants with 8 and 16 kbytes of 
-shared memory. It is strongly advisable to use the 16 kbyte variant. 
+shared memory.
+It is strongly advisable to use the 16 kbyte variant. 
 You can upgrade your 8 kbyte card to 16 kbyte by adding an additional
 RAM chip. 
 .Pp
diff --git a/share/man/man4/man4.i386/joy.4 b/share/man/man4/man4.i386/joy.4
index 039542c..c04d8db 100644
--- a/share/man/man4/man4.i386/joy.4
+++ b/share/man/man4/man4.i386/joy.4
@@ -16,7 +16,8 @@ the PC joystick.
 This device may be opened by only one process at a time.
 .Pp
 The joystick status is read from a structure via a read()
-call. The structure is defined in the header file as follows:
+call.
+The structure is defined in the header file as follows:
 .Pp
 .Bd -literal -offset indent
 	struct joystick {
@@ -33,12 +34,14 @@ perl -e 'open(JOY,"/dev/joy0")||die;while(1)
 .br
 {sysread(JOY,$x,16);@j=unpack("iiii",$x);print "@j\\n";sleep(1);}'
 .Ss ioctl calls
-Several ioctl() calls are also available. They take an argument of
+Several ioctl() calls are also available.
+They take an argument of
 type int *
 .Bl -tag -width JOY_SET_X_OFFSET 
 .It Dv JOY_SETTIMEOUT Fa int *limit
 Set the time limit (in microseconds) for reading the joystick
-status. Setting a value
+status.
+Setting a value
 too small may prevent to get correct values for the positions (which
 are then set to -2147483648), however this can be useful if one is
 only interested by the buttons status. 
diff --git a/share/man/man4/man4.i386/lnc.4 b/share/man/man4/man4.i386/lnc.4
index 16e8d81..115dfa9 100644
--- a/share/man/man4/man4.i386/lnc.4
+++ b/share/man/man4/man4.i386/lnc.4
@@ -71,7 +71,8 @@ the lower 16Mb of physical memory.  The
 .Nm
 driver assumes the memory it allocates is within the lower 16Mb range.
 This is not a very valid assumption but there's nothing that can be done
-about it yet. For shared memory NICs this isn't relevant.
+about it yet.
+For shared memory NICs this isn't relevant.
 .It "lnc%d: Device timeout -- Resetting"
 The device has stopped responding to the network, or there is a problem with
 the network connection (cable).   Make sure the network connection in use
diff --git a/share/man/man4/man4.i386/meteor.4 b/share/man/man4/man4.i386/meteor.4
index 1e75294..63f23ec 100644
--- a/share/man/man4/man4.i386/meteor.4
+++ b/share/man/man4/man4.i386/meteor.4
@@ -16,7 +16,8 @@ The
 .Nm meteor
 driver provides support for a PCI
 .Em video
-capture. It allows the capture of 24 bit RGB, 16 bit RGB and 16 bit YUV 
+capture.
+It allows the capture of 24 bit RGB, 16 bit RGB and 16 bit YUV 
 output formats.
 .Pp
 .Sh Meteor Driver Installation
@@ -66,7 +67,8 @@ probed.  The default number of pages allocated by the kernel is 151.
 This means that there are (151*4096) bytes available for use.
 .Pp
 .Em options METEOR_DEALLOC_PAGES
-deallocate all pages when closing the device. Note, the chance of
+deallocate all pages when closing the device.
+Note, the chance of
 contiguously re-allocating new pages are very small.  The default
 behavior is to not deallocate pages.
 .Pp
@@ -88,7 +90,8 @@ The Meteor capture driver has three modes of capture operation.
 1) Conventional read(2) interface.
 .in +0.5i
 .Pp
-This mode is the easiest and slowest to use. This mode is great for
+This mode is the easiest and slowest to use.
+This mode is great for
 capturing a single field at little programming cost.
 .Pp
 In this mode, the user opens the device, set the capture mode
@@ -175,7 +178,8 @@ main()
 .Pp
 The single capture mode is designed for conferencing tools such as nv.
 These tools need to control the starting of the image capture and also
-need several frames a second. The continuous capture mode is designed
+need several frames a second.
+The continuous capture mode is designed
 for applications that want free-running data.
 .Pp
 In this mode, the user opens the device, set the capture mode
@@ -266,15 +270,18 @@ main()
 .Pp
 .in +0.5i
 This continuous capture mode is synchronized with the application that
-processes up to 32 frames. This gives the advantages of both single and
+processes up to 32 frames.
+This gives the advantages of both single and
 continuous capture modes. 
 .Pp
 The kernel notifies the application of a new data by raising an
-application defined signal. The driver also shares a structure with
+application defined signal.
+The driver also shares a structure with
 the application that allows them to communicate which frame has been
 written by the kernel and which frame has been read by the application.
 .Pp
-The shared structure starts on the first page after your data. The
+The shared structure starts on the first page after your data.
+The
 structure address can be found by calculation:
 .in +0.5i
 .Pp
@@ -287,25 +294,30 @@ structure address can be found by calculation:
 ((number_rows * number_columns * pixel_depth + 4095)/4096) * 4096
 .in -0.5i
 .Pp
-The shared structure is of type struct meteor_mem. The two most
+The shared structure is of type struct meteor_mem.
+The two most
 important fields are called active and num_active_buf. active
 is a bitmap of frames written by the kernel. num_active_bufs is
-a count of frames marked in the active field. When a frame is read
+a count of frames marked in the active field.
+When a frame is read
 in by the driver, the num_active_bufs count is tested, if this
 count is below the threshold of number of active frames (value
 in meteor_mem's hiwat variable), the bit representing frame
 number in the buffer is stored in the active variable, the
 num_active_bufs is incremented, the kernel then raises the specified
-signal to activate the user application. The user application's
+signal to activate the user application.
+The user application's
 responsibility when getting the signal is to check the active bitmap
 to determine the lowest active frame, use the data as the application
 desires, clear the bitmap entry for that frame, and decrement the
-num_active_bufs. If the threshold of number of active frames (hiwat)
+num_active_bufs.
+If the threshold of number of active frames (hiwat)
 has been exceeded, no new frames or signal from the kernel will occur
 until the num_active_bufs is less than or equal to lowat.
 .Pp
 The driver loads the frames in a round-robin fashion. it is expected
-that the user removes them in the same order. The driver does not
+that the user removes them in the same order.
+The driver does not
 check to see if the frame is already active.
 .Pp
 The frame_size and number of frames in the buffer are also provided
@@ -314,7 +326,8 @@ application will not change the operation of the driver.
 .Pp
 In programming for this mode, the user opens the device, sets the
 geometry, mmaps the data/common control structure, then starts the
-continuous capture mode. A special signal catcher is required to
+continuous capture mode.
+A special signal catcher is required to
 process the frames as they are read by the kernel.
 .Pp
 When specifying the geometry (See: ioctl METEORSETGEO), it
@@ -451,7 +464,8 @@ attributes.
 .Pp
 IT IS VERY IMPORTANT TO CHECK FOR ERRORS ON THESE RETURNING IOCTLs.
 Errors indicate that something is very wrong with the ioctl and the
-application should not attempt to proceed further with capturing. The
+application should not attempt to proceed further with capturing.
+The
 meteor capture driver still makes attempts to stop the next capture step if
 an error occurred in a previous step but was ignored by the application
 programmer.
@@ -470,12 +484,14 @@ number of rows (lines high) in output image
 .It Dv columns
 number of pixels in a row (width) in output image
 .It Dv frames
-number of frames in buffer. Should be 1, unless using
+number of frames in buffer.
+Should be 1, unless using
 the multi-framed synchronous capture mode (METEORCAPFRM)
 which REQUIRES frames to be larger than 1.
 .Pp
 Note: if rows, columns or frames is not changed, then
-the existing values are used. The system defaults
+the existing values are used.
+The system defaults
 is 640x480x1.
 .It Dv oformat
 you may choose one of the following output format:
@@ -499,12 +515,14 @@ rows * column / 4 bytes of odd  v)
 .El
 .Pp
 The METEORSETGEO ioctl will fail if more than one entry from a category
-is selected. It is highly recommended that a METEORSETGEO is done
+is selected.
+It is highly recommended that a METEORSETGEO is done
 before capturing data because you cannot guarantee the initial mode
 the card.
 .Pp
 The METEORSETGEO will also attempt to reallocate a new contiguous
-kernel buffer if the new geometry exceeds the old geometry. On
+kernel buffer if the new geometry exceeds the old geometry.
+On
 other hand, if the new geometry will fit in the existing buffer,
 the existing buffer is used. 
 .Pp
@@ -543,7 +561,8 @@ Autodetect.
 .in +0.5i
 .Pp
 METEORSINPUT and METEORGINPUT are used to set and read the camera
-input device. Using the DB9 connector on the Meteor card, 4 input
+input device.
+Using the DB9 connector on the Meteor card, 4 input
 devices can be connected and an input camera can be selected with this
 ioctl.
 .Pp
@@ -667,7 +686,8 @@ variables in the structure as inputs
 .El
 .It Dv signal
 signal to send to application when a new
-frame has been captured. This signal will
+frame has been captured.
+This signal will
 only be raised if the captured frame is saved.
 .It Dv lowat
 see below
@@ -715,7 +735,8 @@ invalid unsigned char pointer.
 8) ioctl requests METEORGHUE and METEORSHUE
 .in +0.5i
 .Pp
-METEORGHUE and METEORSHUE are used to get and set the hue. The
+METEORGHUE and METEORSHUE are used to get and set the hue.
+The
 signed character has legal values are from +127 which represent
 +178.6 degrees to -128 which represents -180 degrees.
 .Pp
@@ -733,7 +754,8 @@ invalid signed char pointer.
 .Pp
 METEORGCOUNT is used to get the count of frame errors, DMA errors and
 count of the number of frames captured that have occurred since
-the device was opened. METEORSCOUNT can be used to reinitialize the
+the device was opened.
+METEORSCOUNT can be used to reinitialize the
 counters.
 .Pp
 This ioctl routines use the meteor_counts structure that has the
@@ -758,11 +780,13 @@ invalid meteor_counts structure pointer.
 .Sh Known Bugs:
 .in +0.5i
 .Pp
-1) IIC register is difficult to set. We got around that by adding a long
+1) IIC register is difficult to set.
+We got around that by adding a long
 wait at each IIC register write.
 .Pp
 2) We had difficulties getting the Meteor capture card to work on systems
-that used NCR chipset SCSI cards. It is possible that the Meteor and NCR SCSI
+that used NCR chipset SCSI cards.
+It is possible that the Meteor and NCR SCSI
 could work together using the newer TRITON motherboards.
 .in -0.5i
 .Pp
diff --git a/share/man/man4/man4.i386/pcf.4 b/share/man/man4/man4.i386/pcf.4
index 8257f86..cbe573c 100644
--- a/share/man/man4/man4.i386/pcf.4
+++ b/share/man/man4/man4.i386/pcf.4
@@ -45,9 +45,12 @@ system.
 .Pp
 The PCF8584 is an integrated circuit designed in CMOS technology which serves
 as an interface between most standard parallel-bus 
-microcontrollers/microprocessors and the serial I2C-bus. The PCF8584 
-provides both master and slave functions. Communication with I2C-bus is
-carried out on a byte-wise basis using interrupt or polled handshake. It
+microcontrollers/microprocessors and the serial I2C-bus.
+The PCF8584 
+provides both master and slave functions.
+Communication with I2C-bus is
+carried out on a byte-wise basis using interrupt or polled handshake.
+It
 controls all the I2C-bus specific sequences, protocol, arbitration and timing.
 The PCF8584 allows parallel-bus systems to communicate bidirectionally with
 the I2C-bus.
diff --git a/share/man/man4/man4.i386/ppc.4 b/share/man/man4/man4.i386/ppc.4
index 64a9acc..d29eed7 100644
--- a/share/man/man4/man4.i386/ppc.4
+++ b/share/man/man4/man4.i386/ppc.4
@@ -118,7 +118,8 @@ ppb->ppb_avm field contains the available modes of the chipset.
 .Xr ppbus 4 ,
 .Xr ppi 4
 .Sh BUGS
-The chipset detection process may corrupt your chipset configuration. You may
+The chipset detection process may corrupt your chipset configuration.
+You may
 disable chipset specific detection by using the above flags.
 .Sh HISTORY
 The
diff --git a/share/man/man4/man4.i386/sb.4 b/share/man/man4/man4.i386/sb.4
index e086d81..5958793 100644
--- a/share/man/man4/man4.i386/sb.4
+++ b/share/man/man4/man4.i386/sb.4
@@ -42,7 +42,8 @@ To add SG NX Pro mixer support:
 .Cd "options __SGNXPRO__"
 .Pp
 The OPL-2/3 is used in the SoundBlaster, SoundBlaster Pro, SB 16, and the
-Pro Audio Spectrum. For Yamaha OPL-2/OPL-3 FM support:
+Pro Audio Spectrum.
+For Yamaha OPL-2/OPL-3 FM support:
 .Cd "device opl0  at isa? port 0x388"
 .Sh DESCRIPTION
 This driver covers the SoundBlaster family of cards including the
@@ -59,7 +60,8 @@ the kernel thinks there is a conflict.  This can be worked-around by
 using the "conflicts" keyword on the sb16's device line.
 .Pp
 Current version doesn't support mode changes without closing and reopening
-the device. Support for this feature may be implemented in a future
+the device.
+Support for this feature may be implemented in a future
 version of this driver.
 .Sh SEE ALSO
 .Xr cdcontrol 1 , 
diff --git a/share/man/man4/man4.i386/spkr.4 b/share/man/man4/man4.i386/spkr.4
index 9bc1b7e..71c24f0 100644
--- a/share/man/man4/man4.i386/spkr.4
+++ b/share/man/man4/man4.i386/spkr.4
@@ -22,12 +22,15 @@ Only one process may have this device open at any given time;
 .Xr open 2
 and
 .Xr close 2
-are used to lock and relinquish it. An attempt to open when
+are used to lock and relinquish it.
+An attempt to open when
 another process has the device locked will return -1 with an
 .Er EBUSY
 error
-indication. Writes to the device are interpreted as `play strings' in a
-simple ASCII melody notation. An 
+indication.
+Writes to the device are interpreted as `play strings' in a
+simple ASCII melody notation.
+An 
 .Xr ioctl 2
 request
 for tone generation at arbitrary
@@ -35,7 +38,8 @@ frequencies is also supported.
 .Pp
 Sound-generation does not monopolize the processor; in fact, the driver
 spends most of its time sleeping while the PC hardware is emitting
-tones. Other processes may emit beeps while the driver is running.
+tones.
+Other processes may emit beeps while the driver is running.
 .Pp
 Applications may call 
 .Xr ioctl 2
@@ -70,7 +74,8 @@ Advanced BASIC 2.0.  The
 and
 .Li X
 primitives of PLAY are not
-useful in a timesharing environment and are omitted. The `octave-tracking'
+useful in a timesharing environment and are omitted.
+The `octave-tracking'
 feature and the slur mark are new.
 .Pp
 There are 84 accessible notes numbered 1-84 in 7 octaves, each running from
@@ -79,7 +84,8 @@ with middle C.  By default, the play function emits half-second notes with the
 last 1/16th second being `rest time'.
 .Pp
 Play strings are interpreted left to right as a series of play command groups;
-letter case is ignored. Play command groups are as follows:
+letter case is ignored.
+Play command groups are as follows:
 .Bl -tag -width CDEFGABxx
 .It Li CDEFGAB
 Letters A through G cause the corresponding note to be played in the
@@ -101,7 +107,8 @@ or
 to enable or disable octave-tracking (it is disabled by default).
 When octave-tracking is on, interpretation of a pair of letter notes
 will change octaves if necessary in order to make the smallest
-possible jump between notes. Thus ``olbc'' will be played as
+possible jump between notes.
+Thus ``olbc'' will be played as
 ``olb>c'', and ``olcb'' as ``olc<b''.  Octave locking is disabled for
 one letter note following >, < and O[0123456].  (The octave-locking
 feature is not supported in 
@@ -120,7 +127,8 @@ May be followed by sustain dots.
 .It Ns Li L Sy n
 Sets the current time value for notes.  The default is 
 .Li L4 ,
-quarter or crotchet notes. The lowest possible value is 1; values up
+quarter or crotchet notes.
+The lowest possible value is 1; values up
 to 64 are accepted.
 .Li L1
 sets whole notes,
@@ -164,7 +172,8 @@ Set articulation.
 .Li MN
 .Ns No ( Li N
 for normal) is the default; the last 1/8th of
-the note's value is rest time. You can set
+the note's value is rest time.
+You can set
 .Li ML
 for legato (no rest space) or
 .Li MS
@@ -176,8 +185,10 @@ Notes (that is,
 or
 .Li N
 command character groups) may be followed by
-sustain dots. Each dot causes the note's value to be lengthened by one-half
-for each one. Thus, a note dotted once is held for 3/2 of its undotted value;
+sustain dots.
+Each dot causes the note's value to be lengthened by one-half
+for each one.
+Thus, a note dotted once is held for 3/2 of its undotted value;
 dotted twice, it is held 9/4, and three times would give 27/8. 
 .Pp
 A note and its sustain dots may also be followed by a slur mark (underscore).
@@ -191,7 +202,8 @@ melody sections.
 .Sh BUGS
 Due to roundoff in the pitch tables and slop in the tone-generation and timer
 hardware (neither of which was designed for precision), neither pitch accuracy
-nor timings will be mathematically exact. There is no volume control.
+nor timings will be mathematically exact.
+There is no volume control.
 .Pp
 The action of two or more sustain dots does not reflect standard musical
 notation, in which each dot adds half the value of the previous dot
diff --git a/share/man/man4/man4.i386/sr.4 b/share/man/man4/man4.i386/sr.4
index 6d8cdc6..12a3e03 100644
--- a/share/man/man4/man4.i386/sr.4
+++ b/share/man/man4/man4.i386/sr.4
@@ -49,8 +49,10 @@ that is based on the HD64570 chip.
 .Pp
 The standard
 .Tn FreeBSD
-sppp code is used for the link level layer. The
-default protocol used is PPP. The Cisco HDLC protocol can be used by
+sppp code is used for the link level layer.
+The
+default protocol used is PPP.
+The Cisco HDLC protocol can be used by
 adding
 .Em link2
 to
@@ -62,7 +64,8 @@ Alternately, the driver can be compiled to support
 .Pp
 The
 .Em flags
-field is optional. If it isn't specified, the driver will
+field is optional.
+If it isn't specified, the driver will
 assume the following:
 .Pp
 .Bl -hang -offset indent
@@ -111,7 +114,8 @@ prepended, e.g.,
 .Sh DIAGNOSTICS
 .Bl -diag
 .It "sr%d: Warning illegal interrupt %d."
-The card cannot use the specified interrupt. Choose a different one.
+The card cannot use the specified interrupt.
+Choose a different one.
 .El
 .Sh FILES
 .Bl -tag -width /sys/i386/isa/ic/hd64570.h -compact
@@ -122,7 +126,8 @@ The card cannot use the specified interrupt. Choose a different one.
 .It Pa /sys/pci/if_sr_p.c
 .El
 .Sh BUGS
-At the moment only the X.21 interface is tested. The others
+At the moment only the X.21 interface is tested.
+The others
 may need tweaks to the clock selection code.
 .Pp
 The code can probably stand some optimizing.
diff --git a/share/man/man4/man4.i386/sym.4 b/share/man/man4/man4.i386/sym.4
index 1f11fcc..99ca522 100644
--- a/share/man/man4/man4.i386/sym.4
+++ b/share/man/man4/man4.i386/sym.4
@@ -93,17 +93,21 @@ PCI-SCSI controllers.
 .Pp
 Driver features include support for wide SCSI busses, fast10, fast20,
 fast40 and fast80-dt synchronous data transfers depending on controller
-capabilities. It also provides generic SCSI features as tagged command
-queuing and auto-request sense. This driver is configured by default
+capabilities.
+It also provides generic SCSI features as tagged command
+queuing and auto-request sense.
+This driver is configured by default
 for a maximum of 446 outstanding commands per bus, 8 LUNs per target
-and 64 tagged tasks per LUN. These numbers are not so limited by design,
+and 64 tagged tasks per LUN.
+These numbers are not so limited by design,
 as have been considered reasonable values for current SCSI technology.
 These values can be increased by changing appropriate
 constants in driver header files (not recommended).
 .Pp
 This driver requires the PCI-SCSI chip to implement LOAD/STORE SCRIPTS
 instructions and therefore it does not provide support for 53C810 revid < 16,
-53C825 revid < 16 and all 53C815 revisions. The generic
+53C825 revid < 16 and all 53C815 revisions.
+The generic
 .Nm ncr
 driver can be used to support these early chips.
 .Pp
@@ -116,7 +120,8 @@ drivers are configured, the
 driver takes precedence over the
 .Nm ncr
 driver for all chips that are supported by
-both drivers. As result, the
+both drivers.
+As result, the
 .Nm ncr
 driver does only attach the 53C8XX
 chips that donnot support LOAD/STORE (i.e.: 53C810, 53C815 and 53C825).
@@ -143,13 +148,16 @@ driver will only
 attach the 53C1010 Ultra-3 controllers.
 .Pp
 HVD/LVD capable controllers (895, 895A, 896, 897 and 1010) report
-the actual bus mode from the STEST4 chip IO registers. This feature
+the actual bus mode from the STEST4 chip IO registers.
+This feature
 allows to safely probe against bus mode and to set up the chip
-accordingly. By default the driver only supports HVD for these chips.
+accordingly.
+By default the driver only supports HVD for these chips.
 For other chips that can support HVD but not LVD, the driver has to probe
 implementation dependent registers (GPIO) in order to detect HVD bus mode.
 Only HVD implementations that conform with Symbios Logic recommendation can
-be detected by the driver. When the
+be detected by the driver.
+When the
 .Ar SYM_SETUP_SCSI_DIFF
 kernel is provided
 as value 1, the driver will also probe against HVD for 825a, 875, 876 and
@@ -158,21 +166,27 @@ as value 1, the driver will also probe against HVD for 825a, 875, 876 and
 When supplied as 0, the
 .Ar SYM_SETUP_PCI_PARITY
 kernel configuration option
-indicates the driver not to enable PCI parity checking. PCI parity
+indicates the driver not to enable PCI parity checking.
+PCI parity
 checking should not be an option for PCI-SCSI controllers, but some
 systems have been reported to fail using 53C8XX chips due to spurious or
-permanent PCI parity errors detected. This option is supplied for
+permanent PCI parity errors detected.
+This option is supplied for
 convenience but it is not recommended nor supported.
 .Pp
 This driver offers other options that are not currently exported to user.
-They are defined and documented in the sym_conf.h driver file. It is not
-recommended to change these options unless absolute need. Some of these
+They are defined and documented in the sym_conf.h driver file.
+It is not
+recommended to change these options unless absolute need.
+Some of these
 options are planned to be exported through SYSCTL or equivalent mechanism
 in a further driver release and therefore, no compatibility is guaranteed.
 .Pp
 At initialization, the driver tries to detect and read user settings from
-controller NVRAM. The Symbios/Logic NVRAM layout and the Tekram NVRAM
-layout are currently supported. If the reading of the NVRAM succeeds, the
+controller NVRAM.
+The Symbios/Logic NVRAM layout and the Tekram NVRAM
+layout are currently supported.
+If the reading of the NVRAM succeeds, the
 following settings are taken into account and reported to CAM:
 .Pp
 .Bl -column "SCSI parity checking      " "Symbios     " "Tekram"
@@ -196,7 +210,8 @@ Scan LUN       	Y	N
 .El
 .Pp
 Devices that are configured as disabled for 'scan' in the NVRAM are not
-reported to CAM at system start-up. They can be discovered later using
+reported to CAM at system start-up.
+They can be discovered later using
 the
 .Nm camcontrol rescan
 command.
diff --git a/share/man/man4/man4.i386/tx.4 b/share/man/man4/man4.i386/tx.4
index 3d1bcb6..9496be4 100644
--- a/share/man/man4/man4.i386/tx.4
+++ b/share/man/man4/man4.i386/tx.4
@@ -66,14 +66,18 @@ The old ``ifconfig tx0 linkN'' method of configuration is not supported.
 .Sh DIAGNOSTICS
 .Bl -diag
 .It "tx%d: device timeout %d packets"
-The device stops responding. Device and driver reset follows this error.
+The device stops responding.
+Device and driver reset follows this error.
 .It "tx%d: PCI fatal error occured (%s)"
 One of following errors occured: PCI Target Abort, PCI Master Abort, Data
-Parity Error or Address Parity Error. Device and driver reset follows this error.
+Parity Error or Address Parity Error.
+Device and driver reset follows this error.
 .It "tx%d: WARNING! no link established"
-No media connected. Displayed at startup only.
+No media connected.
+Displayed at startup only.
 .It "tx%d: cannot allocate mbuf header/cluster"
-Cannot allocate memory for received packet. Packet thrown away.
+Cannot allocate memory for received packet.
+Packet thrown away.
 .It "tx%d: can't stop %s DMA"
 While reseting, driver failed to stop device correctly. 
 .El
diff --git a/share/man/man4/man4.i386/wd.4 b/share/man/man4/man4.i386/wd.4
index fa38680..88a4b63 100644
--- a/share/man/man4/man4.i386/wd.4
+++ b/share/man/man4/man4.i386/wd.4
@@ -39,7 +39,8 @@ Generic WD100x/IDE disk controller driver
 .Cd "device wd1 at wdc0 drive 1" Op flags Ar flags
 .Sh DESCRIPTION
 This driver provides access to disks connected to controllers that emulate
-the Western Digital WD100x series. This range of controllers includes WD1003
+the Western Digital WD100x series.
+This range of controllers includes WD1003
 type ST412 controllers, WD1007 ESDI controllers and also the generic IDE 
 controllers found on most motherboards.
 .Pp
diff --git a/share/man/man4/man4.i386/wfd.4 b/share/man/man4/man4.i386/wfd.4
index 7bb15bb..66fe28b 100644
--- a/share/man/man4/man4.i386/wfd.4
+++ b/share/man/man4/man4.i386/wfd.4
@@ -49,7 +49,8 @@ In general the interfaces are similar to those described by
 .Pp
 As the IDE controllers are probed during boot, the 
 .Em IDE
-buses are scanned for devices. Any devices found which answered as
+buses are scanned for devices.
+Any devices found which answered as
 .Sq Em Floppy
 and
 .Sq Em removable
diff --git a/share/man/man4/man4.i386/wl.4 b/share/man/man4/man4.i386/wl.4
index 86b3e27..9ec25e9 100644
--- a/share/man/man4/man4.i386/wl.4
+++ b/share/man/man4/man4.i386/wl.4
@@ -111,7 +111,8 @@ sender MAC address.
 There are two sysctls that change how it filters packets.  Both are on
 by default.
 .It machdep.wl_wlcache_mcastonly <0 | 1> 
-By default this switch is on. It forces the cache to filter out
+By default this switch is on.
+It forces the cache to filter out
 unicast packets.  Only broadcast or multicast packets are accepted.
 .It machdep.wl_wlcache_iponly <0 | 1>
 By default this switch is on.  It forces the driver to discard non-IP