Signed-off-by: Jakub Wilk <jw...@jwilk.net> --- lib/tap-driver.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lib/tap-driver.sh b/lib/tap-driver.sh index 616c09a..da6f463 100755 --- a/lib/tap-driver.sh +++ b/lib/tap-driver.sh @@ -369,7 +369,7 @@ function setup_result_obj(line) sub("^(not )?ok[ \t]*", "", line) # If the result has an explicit number, get it and strip it; otherwise, - # automatically assing the next progresive number to it. + # automatically assign the next progressive number to it. if (line ~ /^[0-9]+$/ || line ~ /^[0-9]+[^a-zA-Z0-9_]/) { match(line, "^[0-9]+") @@ -463,7 +463,7 @@ function get_test_exit_message(status) # shells, when a child process die due to signal number n, can leave # in $? an exit status of 256+n instead of the more standard 128+n. # Apparently, both behaviours are allowed by POSIX (2008), so be - # prepared to handle them both. See also Austing Group report ID + # prepared to handle them both. See also Austin Group report ID # 0000051 <http://www.austingroupbugs.net/view.php?id=51> exit_details = sprintf(" (terminated by signal %d?)", status - 256) else @@ -592,7 +592,7 @@ while (1) bailout_message = bailout_message " " $0 testsuite_error(bailout_message) } - # Maybe we have too look for dianogtic comments too. + # Maybe we have too look for diagnostic comments too. else if (comments != 0) { comment = extract_tap_comment($0); -- 2.7.0