* man/chmod.x: Correct the description of the sticky bit. Reported

by Chris Moore via Ian Jackson in <http://bugs.debian.org/376745>.

2 files changed, 8 insertions, 5 deletions

diff --git a/ChangeLog b/ChangeLog
index a319030ff..4b1252fd1 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,8 @@
 2006-07-05  Jim Meyering  <jim@meyering.net>
 
+	* man/chmod.x: Correct the description of the sticky bit.  Reported
+	by Chris Moore via Ian Jackson in <http://bugs.debian.org/376745>.
+
 	* src/copy.c (copy_internal): Don't work around old NFS clients like
 	SunOS-4.1.4 and Irix 5.3 that set errno to values like EIO and
 	ENOTEMPTY upon failed rename.  Otherwise, we risk misinterpreting
diff --git a/man/chmod.x b/man/chmod.x
index 497206667..ab5c88492 100644
--- a/man/chmod.x
+++ b/man/chmod.x
@@ -61,11 +61,11 @@ systems, and the Linux kernel ignores the sticky bit on files.  Other
 kernels may use the sticky bit on files for system-defined purposes.
 On some systems, only the superuser can set the sticky bit on files.
 .SH STICKY DIRECTORIES
-When the sticky bit is set on a directory, files in that directory may
-be unlinked or renamed only by root or their owner.  Without the
-sticky bit, anyone able to write to the directory can delete or rename
-files.  The sticky bit is commonly found on directories, such as /tmp,
-that are world-writable.
+When the sticky bit is set on a directory, a file in that directory may
+be unlinked or renamed only by the directory owner, the file owner, or root.
+Without the sticky bit, anyone able to write to the
+directory can delete or rename files.  The sticky bit is commonly found
+on directories, such as /tmp, that are world-writable.
 .SH OPTIONS
 [SEE ALSO]
 chmod(2)