var_bash4.tests: better wording in comment

Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>

diff --git a/shell/ash_test/ash-vars/var_bash4.tests b/shell/ash_test/ash-vars/var_bash4.tests
index 01a0def51b194053351acd7a95a2fbf4160a30be..a6e98fd86388f461ded2a6ea43f6dbd18cf808a7 100755 (executable)
--- a/shell/ash_test/ash-vars/var_bash4.tests
+++ b/shell/ash_test/ash-vars/var_bash4.tests
@@ -1,12 +1,12 @@
 # This testcase demonstrates that backslashes are treated differently
 # in 1st and 2nd parts of ${var/search/repl}:
-# if quoted: "${var/search/repl}", and repl contains \a (a non-special char),
-# the backslash in repl stays; if unquoted, backslash: removed
+# if quoted ("${var/search/repl}"), and repl contains \a (a non-special char),
+# the backslash in repl stays; if unquoted, backslash is removed.
 # But search part does not act like that: \a is always converted to just a,
 # even in quotes.
 #
-# bash4 (and probably bash3 too) result: "Quoted:" results are different -
-# they have extra backslash before z.
+# bash4 (and probably bash3 too): "Quoted:" results are different from
+# unquoted and assignment expansions - they have a backslash before z.
 
 v='a*b\*c'
 echo 'Source:       ' "$v"