summaryrefslogtreecommitdiffstats
path: root/bin/rm
diff options
context:
space:
mode:
authoruqs <uqs@FreeBSD.org>2010-10-31 19:16:54 +0000
committeruqs <uqs@FreeBSD.org>2010-10-31 19:16:54 +0000
commit4d0f9c6e02adc2e1977f5473ceb66b24f371b266 (patch)
tree69cbbdd4c947902f3b67f9fc20834261cd447fca /bin/rm
parent1c7f5153549167afe33a35ba8b7a3d556c47c0ba (diff)
downloadFreeBSD-src-4d0f9c6e02adc2e1977f5473ceb66b24f371b266.zip
FreeBSD-src-4d0f9c6e02adc2e1977f5473ceb66b24f371b266.tar.gz
Fix typo and grammar nit
Submitted by: arundel MFC after: 7 days (or when the bikeshed has abated)
Diffstat (limited to 'bin/rm')
-rw-r--r--bin/rm/rm.14
1 files changed, 2 insertions, 2 deletions
diff --git a/bin/rm/rm.1 b/bin/rm/rm.1
index 4e4f240..ad81066 100644
--- a/bin/rm/rm.1
+++ b/bin/rm/rm.1
@@ -234,12 +234,12 @@ command appeared in
.Sh BUGS
The
.Fl P
-option assumes that the underlying storage overwrites file block
+option assumes that the underlying storage overwrites file blocks
when data is written to an existing offset.
Several factors including the file system and its backing store could defeat
this assumption.
This includes, but is not limited to file systems that use a
Copy-On-Write strategy (e.g. ZFS or UFS when snapshots are being used), Flash
-media that is using a wear leveling algorithm, or when the backing datastore
+media that are using a wear leveling algorithm, or when the backing datastore
does journaling, etc.
In addition, only regular files are overwritten, other types of files are not.
OpenPOWER on IntegriCloud