summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJim Meyering <jim@meyering.net>2001-05-11 07:53:44 +0000
committerJim Meyering <jim@meyering.net>2001-05-11 07:53:44 +0000
commite57fb62f7fd9bed96e49741c0404f2724d529689 (patch)
treed3eb3843f10d21f413d437e7615e995ef929a485 /doc
parent02465682052815751af0f360970b5d5b98116698 (diff)
downloadcoreutils-e57fb62f7fd9bed96e49741c0404f2724d529689.tar.xz
add a space after a period
(true invocation): fix a typo
Diffstat (limited to 'doc')
-rw-r--r--doc/omni-utils.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/omni-utils.texi b/doc/omni-utils.texi
index cdc69dcc1..7a9f32536 100644
--- a/doc/omni-utils.texi
+++ b/doc/omni-utils.texi
@@ -7010,7 +7010,7 @@ the times of last access and modification -- of a file, there is actually
a third one as well: the inode change time. This is often referred to
as a file's @code{ctime}.
The inode change time represents the time when the file's meta-information
-last changed. One common example of this is when the permissions of a
+last changed. One common example of this is when the permissions of a
file change. Changing the permissions doesn't access the file, so
the atime doesn't change, nor does it modify the file, so the mtime
doesn't change. Yet, something about the file itself has changed,
@@ -7714,7 +7714,7 @@ be used as a dummy shell for the purpose of disabling accounts.
@dfn{success}. It can be used as a place holder in shell scripts
where a successful command is needed, although the shell built-in
command @code{:} (colon) may do the same thing faster.
-In most modern shells, @code{true} is built-in command, so when
+In most modern shells, @code{true} is a built-in command, so when
you use @samp{true} in a script, you're probably using the built-in
command, not the one documented here.