diff --git a/tests/scripts/all.sh b/tests/scripts/all.sh
index 53f2a93..de0bbcc 100755
--- a/tests/scripts/all.sh
+++ b/tests/scripts/all.sh
@@ -909,7 +909,7 @@
 
 for optimization_flag in -O2 -O3 -Ofast -Os; do
     for compiler in clang gcc; do
-        msg "test: $compiler $optimization_flag, mbedtls_zeroize()"
+        msg "test: $compiler $optimization_flag, mbedtls_platform_zeroize()"
         cleanup
         CC="$compiler" DEBUG=1 CFLAGS="$optimization_flag" make programs
         gdb -x tests/scripts/test_zeroize.gdb -nw -batch -nx
diff --git a/tests/scripts/test_zeroize.gdb b/tests/scripts/test_zeroize.gdb
index 11ea37f..617ab55 100644
--- a/tests/scripts/test_zeroize.gdb
+++ b/tests/scripts/test_zeroize.gdb
@@ -25,10 +25,10 @@
 # intelligent compiler could determine that this function clears a block of
 # memory that is not accessed later in the program, so removing the call to
 # mbedtls_platform_zeroize() does not have an observable behavior. However,
-# inserting a test after a call to mbedtls_zeroize() to check whether the block
-# of memory was correctly zeroed would force the compiler to not eliminate the
-# mbedtls_platform_zeroize() call. If this does not occur, then the compiler
-# potentially has a bug.
+# inserting a test after a call to mbedtls_platform_zeroize() to check whether
+# the block of memory was correctly zeroed would force the compiler to not
+# eliminate the mbedtls_platform_zeroize() call. If this does not occur, then
+# the compiler potentially has a bug.
 #
 # Note: This test requires that the test program is compiled with -g3.
 #