summaryrefslogtreecommitdiffstats
path: root/usr.bin/sed
diff options
context:
space:
mode:
authortrhodes <trhodes@FreeBSD.org>2002-05-16 02:19:14 +0000
committertrhodes <trhodes@FreeBSD.org>2002-05-16 02:19:14 +0000
commitfa6c7efe3f6fd797e86dc3c67a98949a5a5caac7 (patch)
tree9e08fb6b9504917bf2eb917a2e6f067ec3218930 /usr.bin/sed
parent004729ff8a0138980eca89fcf00c1434878eec9d (diff)
downloadFreeBSD-src-fa6c7efe3f6fd797e86dc3c67a98949a5a5caac7.zip
FreeBSD-src-fa6c7efe3f6fd797e86dc3c67a98949a5a5caac7.tar.gz
More consistancy. file system > filesystem
Diffstat (limited to 'usr.bin/sed')
-rw-r--r--usr.bin/sed/process.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/usr.bin/sed/process.c b/usr.bin/sed/process.c
index a1e3ca7..aa44378 100644
--- a/usr.bin/sed/process.c
+++ b/usr.bin/sed/process.c
@@ -444,7 +444,7 @@ flush_appends()
* Read files probably shouldn't be cached. Since
* it's not an error to read a non-existent file,
* it's possible that another program is interacting
- * with the sed script through the file system. It
+ * with the sed script through the filesystem. It
* would be truly bizarre, but possible. It's probably
* not that big a performance win, anyhow.
*/
OpenPOWER on IntegriCloud