diff options
| author | Tom Rhodes <trhodes@FreeBSD.org> | 2002-05-16 02:19:14 +0000 |
|---|---|---|
| committer | Tom Rhodes <trhodes@FreeBSD.org> | 2002-05-16 02:19:14 +0000 |
| commit | 46c2a2cfa4db0a7969436da3293dedaadf750470 (patch) | |
| tree | 9e08fb6b9504917bf2eb917a2e6f067ec3218930 /usr.bin/sed | |
| parent | db4f576472b23c95fa8d8e50e425d45b264e9fd0 (diff) | |
Notes
Diffstat (limited to 'usr.bin/sed')
| -rw-r--r-- | usr.bin/sed/process.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/usr.bin/sed/process.c b/usr.bin/sed/process.c index a1e3ca72756c..aa44378b5ac9 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. */ |