diff --git a/tests/scripts/all.sh b/tests/scripts/all.sh
index c5c0c3a..3f1a32b 100755
--- a/tests/scripts/all.sh
+++ b/tests/scripts/all.sh
@@ -96,7 +96,7 @@
 KEEP_GOING=0
 RUN_ARMCC=1
 
-# Default commands, can be overriden by the environment
+# Default commands, can be overridden by the environment
 : ${OPENSSL:="openssl"}
 : ${OPENSSL_LEGACY:="$OPENSSL"}
 : ${OPENSSL_NEXT:="$OPENSSL"}
diff --git a/tests/scripts/test_zeroize.gdb b/tests/scripts/test_zeroize.gdb
index 77c812a..67ca2e8 100644
--- a/tests/scripts/test_zeroize.gdb
+++ b/tests/scripts/test_zeroize.gdb
@@ -17,7 +17,7 @@
 # seem to be a mechanism to reliably check whether the zeroize calls are being
 # eliminated by compiler optimizations from within the compiled program. The
 # problem is that a compiler would typically remove what it considers to be
-# "unecessary" assignments as part of redundant code elimination. To identify
+# "unnecessary" assignments as part of redundant code elimination. To identify
 # such code, the compilar will create some form dependency graph between
 # reads and writes to variables (among other situations). It will then use this
 # data structure to remove redundant code that does not have an impact on the