Mechanically kill hard sentence breaks and double whitespaces.

1 files changed, 38 insertions, 19 deletions

diff --git a/share/man/man4/sppp.4 b/share/man/man4/sppp.4
index 64a993e..32acec1 100644
--- a/share/man/man4/sppp.4
+++ b/share/man/man4/sppp.4
@@ -39,22 +39,27 @@ The
 network layer implements the state machine and the Link Control
 Protocol (LCP) of the
 .Em point to point protocol (PPP)
-as described in RFC 1661.  Note that this layer does not provide
+as described in RFC 1661.
+Note that this layer does not provide
 network interfaces of its own, it is rather intended to be layered on
 top of drivers providing a synchronous point-to-point connection that
-wish to run a PPP stack over it.  The corresponding network interfaces
+wish to run a PPP stack over it.
+The corresponding network interfaces
 have to be provided by these hardware drivers.
 .Pp
 The
 .Nm
-layer provides three basic modes of operation.  The default mode,
+layer provides three basic modes of operation.
+The default mode,
 with no special flags to be set, is to create the PPP connection
 (administrative
 .Em Open
 event to the LCP layer) as soon as the interface is taken up with the
 .Xr ifconfig 8
-command.  Taking the interface down again will terminate the LCP layer
-and thus all other layers on top.  The link will also terminate itself as
+command.
+Taking the interface down again will terminate the LCP layer
+and thus all other layers on top.
+The link will also terminate itself as
 soon as no Network Control Protocol (NCP) is open anymore, indicating
 that the lower layers are no longer needed.
 .Pp
@@ -64,7 +69,8 @@ with
 .Xr ifconfig 8
 will cause the respective network interface to go into
 .Em passive
-mode.  This means, the administrative
+mode.
+This means, the administrative
 .Em Open
 event to the LCP layer will be delayed until after the lower layers
 signals an
@@ -83,14 +89,17 @@ Finally, setting the flag
 .Em link1
 will cause the interface to operate in
 .Em dial-on-demand
-mode.  This is also only useful if the lower layer supports the notion
-of a carrier (like with an ISDN line).  Upon configuring the
+mode.
+This is also only useful if the lower layer supports the notion
+of a carrier (like with an ISDN line).
+Upon configuring the
 respective interface, it will delay the administrative
 .Em Open
 event to the LCP layer until either an outbound network packet
 arrives, or until the lower layer signals an
 .Em Up
-event, indicating an inbound connection.  As with passive mode, receipt
+event, indicating an inbound connection.
+As with passive mode, receipt
 of a
 .Em Down
 event (loss of carrier) will not automatically take the interface down,
@@ -107,14 +116,17 @@ exchanged as well as the option negotiation between both ends of the
 link will be logged at level
 .Dv LOG_DEBUG .
 This can be helpful to examine configuration problems during the first
-attempts to set up a new configuration.  Without this flag being set,
+attempts to set up a new configuration.
+Without this flag being set,
 only the major phase transitions will be logged at level
 .Dv LOG_INFO .
 .Pp
 It is possible to leave the local interface IP address open for
-negotiation by setting it to 0.0.0.0.  This requires that the remote
+negotiation by setting it to 0.0.0.0.
+This requires that the remote
 peer can correctly supply a value for it based on the identity of the
-caller, or on the remote address supplied by this side.  Due to the
+caller, or on the remote address supplied by this side.
+Due to the
 way the IPCP option negotiation works, this address is being supplied
 late during the negotiation, which might cause the remote peer to make
 wrong assumptions.
@@ -125,28 +137,33 @@ value
 which means that we don't care what address the remote
 side will use, as long as it is not 0.0.0.0.
 This is useful if your ISP has several dial-in
-servers.  You can of course
+servers.
+You can of course
 .Nm route Cm add Ar something_or_other 0.0.0. Ns Em *
 and it will do exactly what you would want it to.
 .Pp
 The PAP and CHAP authentication protocols as described in RFC 1334,
-and RFC 1994 resp., are also implemented.  Their parameters are being
+and RFC 1994 resp., are also implemented.
+Their parameters are being
 controlled by the
 .Xr spppcontrol 8
 utility.
 .Pp
-VJ header compression is implemented, and enabled by default.  It can be
+VJ header compression is implemented, and enabled by default.
+It can be
 disabled using
 .Xr spppcontrol 8 .
 .Sh DIAGNOSTICS
 .Bl -diag
 .It <ifname><ifnum>: <proto> illegal <event> in state <statename>
 An event happened that should not happen for the current state
-the respective control protocol is in.  See RFC 1661 for a description
+the respective control protocol is in.
+See RFC 1661 for a description
 of the state automaton.
 .It <ifname><ifnum>: loopback
 The state automaton detected a line loopback (that is, it was talking
-with itself).  The interface will be temporarily disabled.
+with itself).
+The interface will be temporarily disabled.
 .It <ifname><ifnum>: up
 The LCP layer is running again, after a line loopback had previously
 been detected.
@@ -192,7 +209,8 @@ was written in 1994 at Cronyx Ltd., Moscow by
 .Aq joerg_wunsch@uriah.heep.sax.de
 rewrote a large part in 1997 in order
 to fully implement the state machine as described in RFC 1661, so it
-could also be used for dialup lines.  He also wrote this man page.
+could also be used for dialup lines.
+He also wrote this man page.
 Serge later on wrote a basic implementation for PAP and CHAP, which
 served as the base for the current implementation, done again by
 .An J\(:org Wunsch .
@@ -207,7 +225,8 @@ network protocol is supported.
 More NCPs should be implemented, as well as other control protocols
 for authentication and link quality reporting.
 .Pp
-Negotiation loop avoidance is not fully implemented.  If the negotiation
+Negotiation loop avoidance is not fully implemented.
+If the negotiation
 doesn't converge, this can cause an endless loop.
 .Pp
 The various parameters that should be adjustable per RFC 1661 are