mdoc(7) police:

	* correctly place parenthisized sentences
	* remove hard sentence breaks
	* use .Vt instead of .Fn

6 files changed, 48 insertions, 25 deletions

diff --git a/share/man/man9/buf.9 b/share/man/man9/buf.9
index 137d150..c122c51 100644
--- a/share/man/man9/buf.9
+++ b/share/man/man9/buf.9
@@ -125,8 +125,11 @@ written to its backing store before it can actually be released.
 In the case
 where B_DELWRI is not set, the underlying dirty pages are still properly
 marked as dirty and the buffer can be completely freed without losing that
-clean/dirty state information.  ( XXX do we have to check other flags in
-regards to this situation ??? ).
+clean/dirty state information.
+.Po
+XXX do we have to check other flags in
+regards to this situation ???
+.Pc
 .Pp
 The kernel reserves a portion of its KVM space to hold VM Buffer's data
 maps.
diff --git a/share/man/man9/cd.9 b/share/man/man9/cd.9
index d52e47b..f86344b 100644
--- a/share/man/man9/cd.9
+++ b/share/man/man9/cd.9
@@ -90,9 +90,13 @@ The reason is that the driver does several things to attempt to
 determine whether the drive in question needs 10 byte commands.
 First, it
 issues a CAM Path Inquiry command to determine whether the protocol that
-the drive speaks typically only allows 10 byte commands.  (ATAPI and USB
+the drive speaks typically only allows 10 byte commands.
+.Po
+ATAPI and USB
 are two prominent examples of protocols where you generally only want to
-send 10 byte commands.)  Then, if it gets an ILLEGAL REQUEST error back
+send 10 byte commands.
+.Pc
+Then, if it gets an ILLEGAL REQUEST error back
 from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10
 byte version of the command instead.
 The only reason you would need a
diff --git a/share/man/man9/hexdump.9 b/share/man/man9/hexdump.9
index ea6cd41..2d42309 100644
--- a/share/man/man9/hexdump.9
+++ b/share/man/man9/hexdump.9
@@ -40,26 +40,29 @@
 .Fn hexdump "void *ptr" "int length" "const char *hdr" "int flags"
 .Sh DESCRIPTION
 Hexdump prints an array of bytes to the console in hexadecimal form, along with
-the ASCII representation of the bytes, if possible.  By default, each line of
+the ASCII representation of the bytes, if possible.
+By default, each line of
 output will start with an offset count, followed by 16 hexadecimal values,
 followed by 16 ASCII characters.
 .Bl -tag -width 6n
 .It Fa ptr
-Pointer to the array of bytes to print.  It does not need to be NULL-terminated.
+Pointer to the array of bytes to print.
+It does not need to be NULL-terminated.
 .It Fa length
 Number of bytes to print
 .It Fa hdr
 Pointer to a NULL-terminated character string that will be prepended to each
-line of output.  A value of NULL implies that no header will be printed.
+line of output.
+A value of NULL implies that no header will be printed.
 .It Fa flags
 Flags for controlling the formatting of the output
 .Bl -tag -width HD_OMIT_COUNT
 .It Fa Bits 0-7
-Integer value of the number of bytes to display on each line.  A value of 0
-implies that the default value of 16 will be used.
+Integer value of the number of bytes to display on each line.
+A value of 0 implies that the default value of 16 will be used.
 .It Fa Bits 8-15
-Character ASCII value to use as the separator for the hexadecimal output.  A
-value of 0 implies that the default value of 32 (ASCII space) will be used.
+Character ASCII value to use as the separator for the hexadecimal output.
+A value of 0 implies that the default value of 32 (ASCII space) will be used.
 .It Fa HD_OMIT_COUNT
 Don't print the offset column at the beginning of each line
 .It Fa HD_OMIT_HEX
diff --git a/share/man/man9/rtentry.9 b/share/man/man9/rtentry.9
index 6c2d517..cd47b5b 100644
--- a/share/man/man9/rtentry.9
+++ b/share/man/man9/rtentry.9
@@ -62,9 +62,9 @@ These members also include in
 their substructure the key (i.e., destination address) and mask used
 when the route was created.
 The
-.Fn rt_key \&rt
+.Vt rt_key \&rt
 and
-.Fn rt_mask \&rt
+.Vt rt_mask \&rt
 macros can be used to extract this information (in the form of a
 .Dq Li "struct sockaddr *" )
 given a
@@ -125,10 +125,13 @@ route is generated.
 When the
 .Dv RTF_LLINFO
 flag is set, this field contains information specific to the link
-layer represented by the named interface address.  (It is normally
-managed by the
-.Fn rt_ifa->ifa_rtrequest
-routine.)  Protocols such as
+layer represented by the named interface address.
+.Po
+It is normally managed by the
+.Vt rt_ifa->ifa_rtrequest
+routine.
+.Pc
+Protocols such as
 .Xr arp 4
 use this field to reference per-destination state internal to that
 protocol.
@@ -194,8 +197,11 @@ When this route is returned as a result of a lookup, send a report on
 the
 .Xr route 4
 interface requesting that an external process perform resolution for
-this route.  (Used in conjunction with
-.Dv RTF_CLONING . )
+this route.
+.Po
+Used in conjunction with
+.Dv RTF_CLONING .
+.Pc
 .It Dv RTF_LLINFO
 Indicates that this route represents information being managed by a
 link layer's adaptation layer (e.g.,
@@ -213,11 +219,14 @@ Protocol-specific.
 .It Dv RTF_PRCLONING
 Like
 .Dv RTF_CLONING ,
-only managed by an entire protocol.  (E.g.,
+only managed by an entire protocol.
+.Po
+E.g.,
 .Tn IP
 uses this flag to manage a per-host cache integrated with the routing
 table, for those destinations which do not have a link layer
-performing this function.)
+performing this function.
+.Pc
 .It Dv RTF_WASCLONED
 Indicates that this route was generated as a result of cloning
 requested by the
@@ -337,7 +346,7 @@ fields could be named better.
 There is some disagreement over whether it is legitimate for
 .Dv RTF_LLINFO
 to be set by any process other than
-.Fn rt_ifa->ifa_rtrequest .
+.Vt rt_ifa->ifa_rtrequest .
 .Sh AUTHORS
 This manual page was written by
 .An Garrett Wollman .
diff --git a/share/man/man9/time.9 b/share/man/man9/time.9
index 0c14d74..05560d5 100644
--- a/share/man/man9/time.9
+++ b/share/man/man9/time.9
@@ -92,9 +92,12 @@ variable is a monotonically increasing system clock.
 It is set
 from
 .Va time
-at boot, and is updated by the periodic timer interrupt.  (It is
+at boot, and is updated by the periodic timer interrupt.
+.Po
+It is
 not updated by
-.Xr settimeofday 2 . )
+.Xr settimeofday 2 .
+.Pc
 .Pp
 All of these variables contain times
 expressed in seconds and microseconds since midnight (0 hour),
diff --git a/share/man/man9/timeout.9 b/share/man/man9/timeout.9
index 078b60a..beb2553 100644
--- a/share/man/man9/timeout.9
+++ b/share/man/man9/timeout.9
@@ -203,7 +203,8 @@ The function
 is identical to
 .Fn callout_stop
 except that it will wait for the callout to be completed if it is
-already in progress.  This MUST NOT be called while holding any
+already in progress.
+This function MUST NOT be called while holding any
 locks on which the callout might block, or deadlock will result.
 .Pp
 The function