summaryrefslogtreecommitdiff
path: root/doc/sed-in.texi
diff options
context:
space:
mode:
authorJim Meyering <meyering@fb.com>2015-04-27 08:19:47 -0700
committerJim Meyering <meyering@fb.com>2015-05-01 18:09:51 -0700
commit857ed5c3b95f5737020d57b30f202588fe023fde (patch)
tree55d2a3af576a208980f5a95c451c1b25424a48ca /doc/sed-in.texi
parent312c75163a67986a4da33516b22e865aa3ca65ce (diff)
downloadsed-857ed5c3b95f5737020d57b30f202588fe023fde.tar.gz
maint: enable sc_file_system
* cfg.mk (local-checks-to-skip): Remove its exemption. * BUGS (characters): s/filesystem/file system/ * ChangeLog-2014 (setup_jump): Likewise. * doc/sed-in.texi: Likewise. * doc/sed.texi: Likewise.
Diffstat (limited to 'doc/sed-in.texi')
-rw-r--r--doc/sed-in.texi2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/sed-in.texi b/doc/sed-in.texi
index 03f525f..0e10cde 100644
--- a/doc/sed-in.texi
+++ b/doc/sed-in.texi
@@ -2786,7 +2786,7 @@ In short, @samp{sed -i} will let you delete the contents of
a read-only file, and in general the @option{-i} option
(@pxref{Invoking sed, , Invocation}) lets you clobber
protected files. This is not a bug, but rather a consequence
-of how the Unix filesystem works.
+of how the Unix file system works.
The permissions on a file say what can happen to the data
in that file, while the permissions on a directory say what can