Signed-off-by: Stefano Lattarini <stefano.lattar...@gmail.com>
---
 t/ax/test-lib.sh | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/t/ax/test-lib.sh b/t/ax/test-lib.sh
index 81f9170..a3c16ee 100644
--- a/t/ax/test-lib.sh
+++ b/t/ax/test-lib.sh
@@ -258,7 +258,7 @@ am_set_exit_traps ()
   trap "fatal_ 'caught signal SIGINT'" 2
   trap "fatal_ 'caught signal SIGTERM'" 15
   # Various shells seems to just ignore SIGQUIT under some circumstances,
-  # even if the signal is not blocked; however, if the signal it trapped,
+  # even if the signal is not blocked; however, if the signal is trapped,
   # the trap gets correctly executed.  So we also trap SIGQUIT.
   # Here is a list of some shells that have been verified to exhibit the
   # problematic behavior with SIGQUIT:
-- 
1.8.1.1.662.gaa39828


Reply via email to