Use the .Tn macro for generic FreeBSD references. Other minor cleanup.

lib/libc/gen/sleep.3

@@ -85,7 +85,9 @@ is available.
 .Xr sigpause 2 ,
 .Xr usleep 3
 .Sh CAVEAT
-In practice the FreeBSD implementation will not be interrupted: it will
+In practice the
+.Tn FreeBSD
+implementation will not be interrupted: it will
 always return the original argument or zero. Code that depends on
 sleep being interrupted (using it as a timed pause, for example) needs
 to be recoded to use

lib/libc/stdlib/random.3

@@ -168,9 +168,9 @@ About 2/3 the speed of
 The historical implementation used to have a very weak seeding; the
 random sequence did not vary much with the seed.  For compatibility
 reasons, this implementation has been made available until the
-next FreeBSD release
-via the
-functions
+next
+.Tn FreeBSD
+release via the functions
 .Fn orandom ,
 .Fn osrandom ,
 .Fn oinitstate

lib/libc/sys/chmod.2

@@ -30,7 +30,7 @@
 .\" SUCH DAMAGE.
 .\"
 .\"     @(#)chmod.2	8.1 (Berkeley) 6/4/93
-.\"	$Id$
+.\"	$Id: chmod.2,v 1.8 1997/02/22 15:03:43 peter Exp $
 .\"
 .Dd June 4, 1993
 .Dt CHMOD 2
@@ -92,8 +92,10 @@ defined in
 #define S_ISVTX 0001000    /* sticky bit */
 .Ed
 .Pp
-The FreeBSD VM system totally ignores the sticky bit (
-.Dv ISVTX
+The
+.Tn FreeBSD
+VM system totally ignores the sticky bit
+.Pf ( Dv ISVTX
 ) for executables.
 .Pp
 If mode

lib/libc/sys/mmap.2

@@ -216,21 +216,26 @@ was specified and insufficient memory was available.
 .Xr munlock 2 ,
 .Xr munmap 2 ,
 .Xr getpagesize 3
-
 .Sh BUGS
 .Ar len
 is limited to 2GB.  Mmapping slightly more than 2GB doesn't work, but
 it is possible to map a window of size (filesize % 2GB) for file sizes 
 of slightly less than 2G, 4GB, 6GB and 8GB.
-
+.Pp
 The limit is imposed for a variety of reasons. Most of them have to do
-with FreeBSD not wanting to use 64 bit offsets in the VM system due to
-the extreme performance penalty. So FreeBSD uses 32bit page indexes and
-this gives FreeBSD a maximum of 8TB filesizes. It's actually bugs in
+with
+.Tn FreeBSD
+not wanting to use 64 bit offsets in the VM system due to
+the extreme performance penalty. So
+.Tn FreeBSD
+uses 32bit page indexes and
+this gives
+.Tn FreeBSD
+a maximum of 8TB filesizes. It's actually bugs in
 the filesystem code that causes the limit to be further restricted to
 1TB (loss of precision when doing blockno calculations).
-
+.Pp
 Another reason for the 2GB limit is that filesystem metadata can
 reside at negative offsets.
-
+.Pp
 We currently can only deal with page aligned file offsets.

lib/libc/sys/ptrace.2

@@ -1,4 +1,4 @@
-.\"	$Id$
+.\"	$Id: ptrace.2,v 1.9 1997/02/22 15:04:13 peter Exp $
 .\"	$NetBSD: ptrace.2,v 1.2 1995/02/27 12:35:37 cgd Exp $
 .\"
 .\" This file is in the public domain.
@@ -75,7 +75,9 @@ and data, which is why there are two requests: conceptually,
 .Dv PT_READ_I
 reads from the instruction space and
 .Dv PT_READ_D
-reads from the data space.  In the current FreeBSD implementation, these
+reads from the data space.  In the current
+.Tn FreeBSD
+implementation, these
 two requests are completely identical.  The
 .Fa addr
 argument specifies the address (in the traced process' virtual address

lib/libc/sys/rtprio.2

@@ -27,7 +27,7 @@
 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 .\" SUCH DAMAGE.
 .\" 
-.\" $Id$
+.\" $Id: rtprio.2,v 1.8 1997/02/22 15:04:17 peter Exp $
 .\"
 .Dd July 23, 1994
 .Dt RTPRIO 2
@@ -96,7 +96,9 @@ may only change the idle priority of the current process.
 The specified process was not found.
 .Sh AUTHOR
 The original author was Henrik Vestergaard Draboel - hvd@terry.ping.dk. This
-implementation in FreeBSD was substantially rewritten by David Greenman.
+implementation in
+.Tn FreeBSD
+was substantially rewritten by David Greenman.
 .Sh SEE ALSO
 .Xr nice 1 ,
 .Xr ps 1 ,