Scheduled mdoc(7) sweep.

2 files changed, 11 insertions, 10 deletions

diff --git a/usr.sbin/bluetooth/l2ping/l2ping.8 b/usr.sbin/bluetooth/l2ping/l2ping.8
index da2b22c..c033892 100644
--- a/usr.sbin/bluetooth/l2ping/l2ping.8
+++ b/usr.sbin/bluetooth/l2ping/l2ping.8
@@ -44,7 +44,7 @@ The
 .Nm
 utility uses L2CAP
 .Dv ECHO_REQUEST
-datagram to elicit a L2CAP
+datagram to elicit an L2CAP
 .Dv ECHO_RESPONSE
 datagram from a remote device.
 .Pp
@@ -77,7 +77,7 @@ This option is ignored if
 has been specified.
 .It Fl n
 Numeric output only.
-No attempt will be made to lookup symbolic names for host addresses.
+No attempt will be made to look up symbolic names for host addresses.
 .It Fl S Ar source
 Specify the local device which should be used to send L2CAP
 .Dv ECHO_REQUEST
@@ -92,7 +92,8 @@ Specify the number of payload bytes to be sent.
 The default size is 44 bytes.
 It is calculated as minimum L2CAP MTU (48 bytes) minus the size of the L2CAP
 signalling command header (4 bytes).
-The maximum size is 65531 bytes. Is is calculated as maximum L2CAP MTU
+The maximum size is 65531 bytes.
+Is is calculated as maximum L2CAP MTU
 (65535 bytes) minus four bytes of payload reserved for
 .Nm
 internal use.
diff --git a/usr.sbin/bluetooth/rfcomm_pppd/rfcomm_pppd.8 b/usr.sbin/bluetooth/rfcomm_pppd/rfcomm_pppd.8
index bba4016..d9b8777 100644
--- a/usr.sbin/bluetooth/rfcomm_pppd/rfcomm_pppd.8
+++ b/usr.sbin/bluetooth/rfcomm_pppd/rfcomm_pppd.8
@@ -132,16 +132,16 @@ In both client and server modes, this required option specifies which
 .Xr ppp 8
 label will be used.
 .It Fl S
-In the server mode register the Serial Port (SP) service in addition to the
+In the server mode, register the Serial Port (SP) service in addition to the
 LAN Access Using PPP (LAN) service.
-It appears that some cell phones are using so called
-.Dq callback mechanism .
-In this scenario the user is trying to connect his cell phone to the Internet,
-and, user's host computer is acting as the gateway server.
+It appears that some cell phones are using the so-called
+.Dq "callback mechanism" .
+In this scenario, the user is trying to connect his cell phone to the Internet,
+and user's host computer is acting as the gateway server.
 It seems that it is not possible to tell the phone to just connect and start
 using the LAN service.
-Instead the user's host computer must
-.Dq jump start
+Instead, the user's host computer must
+.Dq "jump start"
 the phone by connecting to the phone's SP service.
 What happens next is the phone kills the existing connection and opens another
 connection back to the user's host computer.