Mdoc Janitor:

* cleanup hard sentence breaks.

	* sprinle some .Dq macros.

share/man/man4/ddb.4

@@ -312,7 +312,8 @@ Setting a break
 point at the low-level code paths may also cause strange behavior.
 .It Cm delete Ar addr
 .It Cm delete Li \&# Ns Ar number
-Delete the break point.  The target break point can be specified by a
+Delete the break point.
+The target break point can be specified by a
 break point number with
 .Li # ,
 or by using the same
@@ -520,7 +521,10 @@ Addresses are printed as 'symbol'+offset unless offset is greater than maxoff.
 .It Li maxwidth
 The width of the displayed line.
 .It Li lines
-The number of lines.  It is used by "more" feature.
+The number of lines.
+It is used by
+.Dq more
+feature.
 .It Li tabstops
 Tab stop width.
 .It Li work Ns Ar xx
@@ -583,7 +587,8 @@ and modifiers as described above.
 a binary operator which rounds up the left hand side to the next
 multiple of right hand side.
 .It Li \&* Ns Em expr
-indirection.  It may be followed by a
+indirection.
+It may be followed by a
 .Sq Li :
 and modifiers as described above.
 .El

share/man/man4/inet.4

@@ -297,7 +297,8 @@ which initiates dynamic adaptation (default 128).
 .Re
 .Sh CAVEAT
 The Internet protocol support is subject to change as
-the Internet protocols develop.  Users should not depend
+the Internet protocols develop.
+Users should not depend
 on details of the current implementation, but rather
 the services exported.
 .Sh HISTORY

share/man/man4/intro.4

@@ -149,8 +149,8 @@ See
 .Xr config 8
 for a detailed description of the files involved.
 The individual manual pages in this section provide a sample line for the
-configuration file in their synopsis portion.  See also the sample
-config file
+configuration file in their synopsis portion.
+See also the sample config file
 .Pa /sys/i386/conf/LINT
 (for the
 .Em i386

share/man/man4/man4.i386/lnc.4

@@ -68,20 +68,24 @@ Diamond HomeFree
 .Sh DIAGNOSTICS
 .Bl -diag
 .It "lnc%d: Framing error"
-A framing error occurred.  This means a CRC error also occurred.
+A framing error occurred.
+This means a CRC error also occurred.
 This caused the driver to drop the packet that contained the framing error.
 .It "lnc%d: Receive CRC error
 The received Ethernet frame failed the CRC checksum.
 This caused the driver to drop the packet that failed the checksum.
 .It "lnc%d: Packet dropped, no mbufs"
-The driver ran out of mbuf's.  This may suggest a resource problem.
+The driver ran out of mbuf's.
+This may suggest a resource problem.
 .It "lnc%d: Couldn't allocate memory for NIC"
-This is a fatal error.  The driver will not attach to the card under this
+This is a fatal error.
+The driver will not attach to the card under this
 circumstance.
 .It "lnc%d: Memory allocated above 16Mb limit"
 ISA and ESIA cards require bounce buffers for DMA transfers above 16mb.
 The Am7990 and Am79C960 only have 24 address lines and so can only access
-the lower 16Mb of physical memory.  The
+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
@@ -89,7 +93,8 @@ 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
+the network connection (cable).
+Make sure the network connection in use
 is the same one the card is configured for.
 .It "lnc%d: Transmit late collision  -- Net error?"
 .It "lnc%d: Loss of carrier during transmit -- Net error?"

share/man/man4/man4.i386/svr4.4

@@ -141,7 +141,9 @@ or
 .Pa /compat/svr4/dev .
 Internally, the
 .Xr streams 4
-driver produces a socket descriptor and "tags" it with additional STREAMS
+driver produces a socket descriptor and
+.Dq tags
+it with additional STREAMS
 state information before returning it to the client application.
 The
 .Nm
@@ -177,9 +179,11 @@ archives containing pre-populated trees can be obtained from
 .Pp
 Extensive testing has only really been carried out with Solaris 2.x binaries,
 with anecdotal reports of limited success coming from testers with
-early-revision SCO media.  In theory, the basic SVR4 ABI should be constant
+early-revision SCO media.
+In theory, the basic SVR4 ABI should be constant
 across the set of vendors who produce SVR4 operating systems, but in
-practice that's probably not the case.  If necessary, future work can
+practice that's probably not the case.
+If necessary, future work can
 either implement additional
 .Xr kld 4
 modules which produce functionality which contains OS-dependent
@@ -187,7 +191,9 @@ departures from the behaviour which has been implemented in this
 ABI implementation.
 Alternatively,
 .Xr sysctl 8
-variables could set the "personality" the environment should present to
+variables could set the
+.Dq personality
+the environment should present to
 client applications.
 .Sh FILES
 .Bl -tag -width /sys/compat/svr4/syscalls.master -compact