53515: tests: correct ztst documentation error

2 files changed, 11 insertions, 9 deletions

diff --git a/ChangeLog b/ChangeLog
index c718bb110..57050830f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,13 +1,15 @@
+2025-04-27  dana  <dana@dana.is>
+
+	* 53515: Test/B01cd.ztst: correct ztst documentation error
+
 2025-04-20  Eric Cook  <illua@users.sourceforge.net>
 
 	* unposted: Config/version.mk, Etc/FAQ.yo, NEWS, README: Test
 	release: zsh-5.9.0.2-test.
 
-
 	* 53463: Completion/Unix/Type/_hosts: allow overriding the default
 	matching control
 
-
 2025-04-19  dana  <dana@dana.is>
 
 	* 53483: Doc/Zsh/mod_zutil.yo, Src/Modules/zutil.c,
diff --git a/Test/B01cd.ztst b/Test/B01cd.ztst
index bc6757549..e31341478 100644
--- a/Test/B01cd.ztst
+++ b/Test/B01cd.ztst
@@ -57,13 +57,13 @@
 # subsequent whitespace being significant; lines are not subject to any
 # substitution unless the `q' flag (see below) is set.
 #
-# Each line of a '>' and '?' chunk may be preceded by a '*', so the line
-# starts '*>' or '*?'.  This signifies that for any line with '*' in front
-# the actual output should be pattern matched against the corresponding
-# lines in the test output.  Each line following '>' or '?' must be a
-# valid pattern, so characters special to patterns such as parentheses
-# must be quoted with a backslash.  The EXTENDED_GLOB option is used for
-# all such patterns.
+# If any '>' or '?' line in a chunk is preceded by a '*', all lines in
+# that chunk with the same symbol are pattern matched against the
+# corresponding lines in the test output.  For example, a '*>' anywhere
+# in the chunk causes all other '>' lines to use pattern matching.
+# Each line following '>' or '?' must be a valid pattern, so characters
+# special to patterns such as parentheses must be quoted with a
+# backslash.  The EXTENDED_GLOB option is used for all such patterns.
 #
 # Each chunk of indented code is to be evaluated in one go and is to
 # be followed by a line starting (in the first column) with