summaryrefslogtreecommitdiff
path: root/src/shred.c
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2001-04-29 11:22:48 +0000
committerJim Meyering <jim@meyering.net>2001-04-29 11:22:48 +0000
commitc8de6584bb911fa239522b3bedffb27bc24fcf1d (patch)
treee5483611bedfcce89980894ba3ca93ebfebebc86 /src/shred.c
parentd463885c2485eeb954e582c73cc3dfc8af4fc36e (diff)
downloadcoreutils-c8de6584bb911fa239522b3bedffb27bc24fcf1d.tar.xz
--help:
downcase bulleted items remove some periods
Diffstat (limited to 'src/shred.c')
-rw-r--r--src/shred.c16
1 files changed, 8 insertions, 8 deletions
diff --git a/src/shred.c b/src/shred.c
index 152c303ab..82fbaca24 100644
--- a/src/shred.c
+++ b/src/shred.c
@@ -489,18 +489,18 @@ way to do things, but many modern filesystem designs do not satisfy this\n\
assumption. The following are examples of filesystems on which shred is\n\
not effective:\n\
\n\
-* Log-structured or journaled filesystems, such as those supplied with\n\
- AIX and Solaris (and JFS, ReiserFS, XFS, etc.).\n\
+* log-structured or journaled filesystems, such as those supplied with\n\
+ AIX and Solaris (and JFS, ReiserFS, XFS, etc.)\n\
\n\
-* Filesystems that write redundant data and carry on even if some writes\n\
- fail, such as RAID-based filesystems.\n\
+* filesystems that write redundant data and carry on even if some writes\n\
+ fail, such as RAID-based filesystems\n\
\n\
-* Filesystems that make snapshots, such as Network Appliance's NFS server.\n\
+* filesystems that make snapshots, such as Network Appliance's NFS server\n\
\n\
-* Filesystems that cache in temporary locations, such as NFS\n\
- version 3 clients.\n\
+* filesystems that cache in temporary locations, such as NFS\n\
+ version 3 clients\n\
\n\
-* Compressed filesystems.\n\
+* compressed filesystems\n\
"), DEFAULT_PASSES);
puts (_("\nReport bugs to <bug-fileutils@gnu.org>."));
}