* doc/coreutils.texi (tee invocation): Fix typo. Add a little.

diff --git a/ChangeLog b/ChangeLog
index d025e231eea7b7c6127540b86bd3e7b92260765c..85d2ed260ebc0568b11086dcf822260fdc5f5137 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2007-10-20  Jim Meyering  <meyering@redhat.com>
 
+       * doc/coreutils.texi (tee invocation): Fix typo.  Add a little.
+
        Adjust tests to pass, now that Test.pm ones use check.mk.
        * tests/check.mk (vc_exe_in_TESTS): Adjust regexp not to match the
        "TESTS = $x-tests" line in each Test.pm-derived Makefile.am file.

diff --git a/doc/coreutils.texi b/doc/coreutils.texi
index 3aec8e58dfe881b8c00426a12afedb0b68230a22..c729b2265b657fd5889260350c4be0c2fefeae34 100644 (file)
--- a/doc/coreutils.texi
+++ b/doc/coreutils.texi
@@ -11056,7 +11056,7 @@ Ignore interrupt signals.
 
 @end table
 
-The @command{tee} is useful when you happen to be transferring a large
+The @command{tee} command is useful when you happen to be transferring a large
 amount of data and also want to summarize that data without reading
 it a second time.  For example, when you are downloading a DVD image,
 you often want to verify its signature or checksum right away.
@@ -11086,8 +11086,9 @@ checksum in a file named @file{dvd.sha1}.
 
 Note, however, that this example relies on a feature of modern shells
 called process substitution (the @samp{>(command)} syntax, above),
-so you can use @command{zsh}, @command{bash}, or @command{ksh}, but
-not a minimal @command{/bin/sh}.
+so it works with e.g., @command{zsh}, @command{bash}, or @command{ksh},
+but not with a minimal @command{/bin/sh}.  So if you use this technique
+in a shell script, be sure to start the script with @samp{#!/bin/bash}.
 
 You can extend this example to make @command{tee} write to two processes,
 computing MD5 and SHA1 checksums in parallel: