Mostly punctuation fixes.

src/lib/libc/crypt/arc4random.3

@@ -1,4 +1,5 @@
-.\" $OpenBSD: arc4random.3,v 1.12 2000/04/02 17:59:04 millert Exp $
+.\" $OpenBSD: arc4random.3,v 1.13 2000/04/15 02:15:22 aaron Exp $
+.\"
 .\" Copyright 1997 Niels Provos <provos@physnet.uni-hamburg.de>
 .\" All rights reserved.
 .\"
@@ -33,8 +34,8 @@
 .Dt ARC4RANDOM 3
 .Os
 .Sh NAME
-.Nm arc4random,
-.Nm arc4random_stir,
+.Nm arc4random ,
+.Nm arc4random_stir ,
 .Nm arc4random_addrandom
 .Nd arc4 random number generator
 .Sh SYNOPSIS

src/lib/libc/crypt/blowfish.3

@@ -1,4 +1,5 @@
-.\" $OpenBSD: blowfish.3,v 1.7 2000/03/14 21:31:44 aaron Exp $
+.\" $OpenBSD: blowfish.3,v 1.8 2000/04/15 02:15:22 aaron Exp $
+.\"
 .\" Copyright 1997 Niels Provos <provos@physnet.uni-hamburg.de>
 .\" All rights reserved.
 .\"
@@ -33,8 +34,8 @@
 .Dt BLOWFISH 3
 .Os
 .Sh NAME
-.Nm blf_key,
-.Nm blf_enc,
+.Nm blf_key ,
+.Nm blf_enc ,
 .Nm blf_dec
 .Nd Blowfish encryption
 .Sh SYNOPSIS

src/lib/libc/crypt/crypt.3

@@ -1,4 +1,4 @@
-.\" $OpenBSD: crypt.3,v 1.14 2000/01/22 02:17:55 aaron Exp $
+.\" $OpenBSD: crypt.3,v 1.15 2000/04/15 02:15:22 aaron Exp $
 .\"
 .\" FreeSec: libcrypt
 .\"
@@ -234,8 +234,7 @@ iterations of
 and stores the 64-bit result in the 8 characters at
 .Fa out
 (which may be the same as
-.Fa in
-).
+.Fa in ) .
 The
 .Fa salt
 specifies perturbations to the

src/lib/libutil/login_fbtab.3

@@ -23,7 +23,7 @@ If errors occur a null string is returned.
 Problems are reported via the
 .Xr syslogd 8
 daemon with the severity of
-.Dv LOG_ERR.
+.Dv LOG_ERR .
 .Sh FILES
 .Bl -tag -width /etc/fbtab -compact
 .It Pa /etc/fbtab

src/lib/libutil/scsi.3

@@ -1,4 +1,4 @@
-.\"	$OpenBSD: scsi.3,v 1.4 2000/03/04 22:19:32 aaron Exp $
+.\"	$OpenBSD: scsi.3,v 1.5 2000/04/15 02:15:28 aaron Exp $
 .\" Copyright (c) 1994 HD Associates (hd@world.std.com)
 .\" All rights reserved.
 .\"
@@ -164,8 +164,8 @@ are the flags defined in
 Only two of these flags are supported in this release of the software:
 .Fr SCCMD_READ
 indicates a data in phase (a transfer into the user buffer at
-.Ar scsireg->databuf
-), and
+.Ar scsireg->databuf ) ,
+and
 .Fr SCCMD_WRITE
 indicates a data out phase (a transfer out of the user buffer).
 .Pp
@@ -244,7 +244,7 @@ The decoding is similar to
 the command specifier processing of
 .Fn scsireq_build
 except that the data is extracted from the data pointed to by
-.Fr scsireq->databuf.
+.Fr scsireq->databuf .
 The stdarg list should be pointers to integers instead of integer
 values.
 A seek field type and a suppression modifier are added.

src/lib/libutil/uucplock.3

@@ -1,4 +1,4 @@
-.\" $OpenBSD: uucplock.3,v 1.8 2000/03/28 22:41:42 deraadt Exp $
+.\" $OpenBSD: uucplock.3,v 1.9 2000/04/15 02:15:29 aaron Exp $
 .\"
 .\" All rights reserved.
 .\"
@@ -85,33 +85,33 @@ returns 0 on success and \-1 on failure.
 .Fn uu_lock
 may return any of the following values:
 .Pp
-.Dv UU_LOCK_INUSE:
+.Dv UU_LOCK_INUSE :
 The lock is in use by another process.
 .Pp
-.Dv UU_LOCK_OK:
+.Dv UU_LOCK_OK :
 The lock was successfully created.
 .Pp
-.Dv UU_LOCK_OPEN_ERR:
+.Dv UU_LOCK_OPEN_ERR :
 The lock file could not be opened via
 .Xr open 2 .
 .Pp
-.Dv UU_LOCK_READ_ERR:
+.Dv UU_LOCK_READ_ERR :
 The lock file could not be read via
 .Xr read 2 .
 .Pp
-.Dv UU_LOCK_CREAT_ERR:
+.Dv UU_LOCK_CREAT_ERR :
 Can't create temporary lock file via
 .Xr creat 2 .
 .Pp
-.Dv UU_LOCK_WRITE_ERR:
+.Dv UU_LOCK_WRITE_ERR :
 The current process ID could not be written to the lock file via a call to
 .Xr write 2 .
 .Pp
-.Dv UU_LOCK_LINK_ERR:
+.Dv UU_LOCK_LINK_ERR :
 Can't link temporary lock file via
 .Xr link 2 .
 .Pp
-.Dv UU_LOCK_TRY_ERR:
+.Dv UU_LOCK_TRY_ERR :
 Locking attempts are failed after 5 tries.
 .Pp
 If a value of
@@ -134,14 +134,14 @@ and
 .Fn uu_lock_txfr
 may return any of the following values:
 .Pp
-.Dv UU_LOCK_OK:
+.Dv UU_LOCK_OK :
 The transfer was successful.  The specified process now holds the device
 lock.
 .Pp
-.Dv UU_LOCK_OWNER_ERR:
+.Dv UU_LOCK_OWNER_ERR :
 The current process does not already own a lock on the specified device.
 .Pp
-.Dv UU_LOCK_WRITE_ERR:
+.Dv UU_LOCK_WRITE_ERR :
 The new process ID could not be written to the lock file via a call to
 .Xr write 2 .
 .Sh ERRORS