From f6aa4621fdedfa56e30080766807470b824ed6cb Mon Sep 17 00:00:00 2001
From: ru <ru@FreeBSD.org>
Date: Mon, 17 May 2004 08:35:43 +0000
Subject: Assorted markup, grammar, and spelling fixes.

---
 sbin/dump/dump.8 | 38 ++++++++++++++++++++++++--------------
 1 file changed, 24 insertions(+), 14 deletions(-)

(limited to 'sbin/dump')

diff --git a/sbin/dump/dump.8 b/sbin/dump/dump.8
index fedf9a6..ea35653 100644
--- a/sbin/dump/dump.8
+++ b/sbin/dump/dump.8
@@ -200,7 +200,7 @@ script string defined by
 for the output device of each volume.
 This child pipeline's
 .Dv stdin
-.Pa ( /dev/fd/0 )
+.Pq Pa /dev/fd/0
 is redirected from the
 .Nm
 output stream, and the environment variable
@@ -230,19 +230,25 @@ To obtain a consistent dump image,
 .Nm
 takes a snapshot of the file system in the
 .Pa .snap
-directory in the root of the filesystem being dumped and
+directory in the root of the file system being dumped and
 then does a dump of the snapshot.
 The snapshot is removed when the dump is complete.
-This option is ignored for unmounted or read-only filesystems.
+This option is ignored for unmounted or read-only file systems.
 If the
 .Pa .snap
-directory does not exist in the root of the filesystem being dumped,
-the dump will fail.
+directory does not exist in the root of the file system being dumped,
+the
+.Nm
+will fail.
 This problem can be corrected by creating a
 .Pa .snap
-directory in the root of the filesystem to be dumped;
-its owner should be root, its group should be operator,
-and its mode should be 0770.
+directory in the root of the file system to be dumped;
+its owner should be
+.Dq Li root ,
+its group should be
+.Dq Li operator ,
+and its mode should be
+.Dq Li 0770 .
 .It Fl n
 Whenever
 .Nm
@@ -439,7 +445,7 @@ Pathname of the remote
 .Xr rmt 8
 program.
 .It Ev RSH
-Pathname of remote shell program, if not
+Pathname of a remote shell program, if not
 .Xr rsh 1 .
 .El
 .Sh FILES
@@ -473,14 +479,18 @@ abnormal termination is indicated with an exit code of 3.
 Fewer than 32 read errors on the file system are ignored, though all
 errors will generate a warning message.
 This is a bit of a compromise.
-In practice it is possible to generate read errors when doing dumps
+In practice, it is possible to generate read errors when doing dumps
 on mounted partitions if the file system is being modified while the
-dump is running.
+.Nm
+is running.
 Since dumps are often done in an unattended fashion using
 .Xr cron 8
-jobs asking for Operator intervention would result in the dump dying.
-However there is nothing wrong with a dump tape written when this sort
-of read error occurs and there is no reason to terminate the dump.
+jobs asking for Operator intervention would result in the
+.Nm
+dying.
+However, there is nothing wrong with a dump tape written when this sort
+of read error occurs, and there is no reason to terminate the
+.Nm .
 .Pp
 Each reel requires a new process, so parent processes for
 reels already written just hang around until the entire tape
-- 
cgit v1.1