Source-Changes-HG archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

[src/trunk]: src/sbin/resize_ffs Replace contractions.



details:   https://anonhg.NetBSD.org/src/rev/974092353d0a
branches:  trunk
changeset: 347715:974092353d0a
user:      sevan <sevan%NetBSD.org@localhost>
date:      Mon Sep 12 05:47:21 2016 +0000

description:
Replace contractions.

diffstat:

 sbin/resize_ffs/resize_ffs.8 |  8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diffs (33 lines):

diff -r 76a8758a7034 -r 974092353d0a sbin/resize_ffs/resize_ffs.8
--- a/sbin/resize_ffs/resize_ffs.8      Mon Sep 12 05:43:15 2016 +0000
+++ b/sbin/resize_ffs/resize_ffs.8      Mon Sep 12 05:47:21 2016 +0000
@@ -1,4 +1,4 @@
-.\"     $NetBSD: resize_ffs.8,v 1.16 2015/04/06 22:44:04 jmcneill Exp $
+.\"     $NetBSD: resize_ffs.8,v 1.17 2016/09/12 05:47:21 sevan Exp $
 .\"
 .\" As its sole author, I explicitly place this man page in the public
 .\" domain.  Anyone may use it in any way for any purpose (though I would
@@ -38,7 +38,7 @@
 has to copy anything that currently resides in the space being shrunk
 away; there must be enough space free on the file system for this to
 succeed.
-If there isn't,
+If there is not,
 .Nm
 will complain and exit; when this happens, it attempts to always leave
 the file system in a consistent state, but it is probably a good idea to
@@ -90,7 +90,7 @@
 .Nm
 may misbehave, anything from dumping core to completely curdling the
 data.
-It's probably wise to
+It is probably wise to
 .Xr fsck 8
 the file system before and after, just to be safe.
 You should be aware that just because
@@ -143,4 +143,4 @@
 Has no intelligence whatever when it comes to allocating blocks to copy
 data into when shrinking.
 .Pp
-Doesn't currently support shrinking FFSv2 file systems.
+Does not currently support shrinking FFSv2 file systems.



Home | Main Index | Thread Index | Old Index