aboutsummaryrefslogtreecommitdiff
path: root/shell/ash_test/ash-signals
diff options
context:
space:
mode:
authorDenys Vlasenko <vda.linux@googlemail.com>2016-10-26 13:15:35 +0200
committerDenys Vlasenko <vda.linux@googlemail.com>2016-10-26 13:15:35 +0200
commit4135a75ab05f2546f4f9e9b3e69d71f477efc1e8 (patch)
tree5ac8fd35f89d2901a736046a15a1772e62ea68ee /shell/ash_test/ash-signals
parenta513bf3c3ce0756c991b21c0ca271e24fedcdb51 (diff)
downloadbusybox-4135a75ab05f2546f4f9e9b3e69d71f477efc1e8.tar.gz
typo fixes
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'shell/ash_test/ash-signals')
-rwxr-xr-xshell/ash_test/ash-signals/return_in_trap1.tests4
1 files changed, 2 insertions, 2 deletions
diff --git a/shell/ash_test/ash-signals/return_in_trap1.tests b/shell/ash_test/ash-signals/return_in_trap1.tests
index f2498024f..4c0d53bde 100755
--- a/shell/ash_test/ash-signals/return_in_trap1.tests
+++ b/shell/ash_test/ash-signals/return_in_trap1.tests
@@ -11,8 +11,8 @@ a
echo d:$?
# It's debatable what is the correct value above.
-# Does 'return' in trap sees $? == 2 or $? == 3?
+# Does 'return' in trap see $? == 2 or $? == 3?
# IOW: after (kill..), does shell first wait for its completion
# and sets $?, then checks pending signals and runs a trap handler,
-# or does it first checks pending signals and runs handler?
+# or does it first check pending signals and runs handler?
# hush does the former, and prints 3.