Update doc from previous commit.

Make it clear it's commands whose names begin with a /
that aren't hashed.  Obviously commands whose paths
begin with a / are OK, duh.

2 files changed, 5 insertions, 3 deletions

diff --git a/ChangeLog b/ChangeLog
index d478b3307..a55eae61c 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2019-03-19  Peter Stephenson  <p.stephenson@samsung.com>
 
+	* unposted: Make the doc change in the foregoing clearer.
+
 	* Charles Blake: 44132: Src/exec.c, Doc/Zsh/builtins.yo: don't
 	hash commands beginning with a '/'.
 
diff --git a/Doc/Zsh/builtins.yo b/Doc/Zsh/builtins.yo
index a926395ad..d7b6e88fa 100644
--- a/Doc/Zsh/builtins.yo
+++ b/Doc/Zsh/builtins.yo
@@ -988,9 +988,9 @@ The choice of hash table to work on is determined by the tt(-d) option;
 without the option the command hash table is used, and with the option the
 named directory hash table is used.
 
-Command paths starting with a tt(/) are never hashed, whether by explicit
-use of the tt(hash) command or otherwise, but are always found
-by direct look up in the file system.
+A command var(name) starting with a tt(/) is never hashed, whether by
+explicit use of the tt(hash) command or otherwise.  Such a command
+is always found by direct look up in the file system.
 
 Given no arguments, and neither the tt(-r) or tt(-f) options,
 the selected hash table will be listed in full.