Remove hard sentence breaks, and some other cleanup along the way.

1 files changed, 13 insertions, 8 deletions

diff --git a/sbin/mount_umap/mount_umap.8 b/sbin/mount_umap/mount_umap.8
index 3addee5c29e..2aacd29122d 100644
--- a/sbin/mount_umap/mount_umap.8
+++ b/sbin/mount_umap/mount_umap.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: mount_umap.8,v 1.13 2000/03/04 22:19:30 aaron Exp $
+.\"	$OpenBSD: mount_umap.8,v 1.14 2000/03/18 22:56:01 aaron Exp $
 .\"	$NetBSD: mount_umap.8,v 1.4 1996/03/05 02:36:42 thorpej Exp $
 .\"
 .\" Copyright (c) 1992, 1993, 1994
@@ -77,9 +77,11 @@ The
 .Nm
 command uses a set of files provided by the user to make correspondences
 between UIDs and GIDs in the subtree's original environment and
-some other set of IDs in the local environment.  For instance, user
+some other set of IDs in the local environment.
+For instance, user
 smith might have UID 1000 in the original environment, while having
-UID 2000 in the local environment.  The
+UID 2000 in the local environment.
+The
 .Nm
 command allows the subtree from smith's original environment to be
 mapped in such a way that all files with owner UID 1000 look like
@@ -97,7 +99,8 @@ and
 describe the mappings to be made between identifiers.
 Briefly, the format of these files is a count of the number of
 mappings on the first line, with each subsequent line containing
-a single mapping.  Each of these mappings consists of an ID from
+a single mapping.
+Each of these mappings consists of an ID from
 the original environment and the corresponding ID in the local environment,
 separated by whitespace.
 .Em uid-mapfile
@@ -111,21 +114,23 @@ will be treated as user NOBODY,
 and any GIDs not mapped in
 .Em gid-mapfile
 will be treated as group
-NULLGROUP.  At most 64 UIDs can be mapped for a given subtree, and
+NULLGROUP.
+At most 64 UIDs can be mapped for a given subtree, and
 at most 16 groups can be mapped by a given subtree.
 .Pp
 The mapfiles can be located anywhere in the file hierarchy, but they
 must be owned by root, and they must be writable only by root.
 .Nm
 will refuse to map the subtree if the ownership or permissions on
-these files are improper.  It will also balk if the count of mappings
+these files are improper.
+It will also balk if the count of mappings
 in the first line of the map files is not correct.
 .Pp
 The layer created by the
 .Nm
 command is meant to serve as a simple example of file system layering.
-It is not meant for production use.  The implementation is not very
-sophisticated.
+It is not meant for production use.
+The implementation is not very sophisticated.
 .Sh SEE ALSO
 .Xr mount 8 ,
 .Xr mount_null 8