lib:fuzzing: Fix code spelling

Best reviewed with: `git show --word-diff`.

Signed-off-by: Andreas Schneider <asn@samba.org>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>

3 files changed, 5 insertions, 5 deletions

diff --git a/lib/fuzzing/fuzz_ndr_X.c b/lib/fuzzing/fuzz_ndr_X.c
index a3fb984451f..3c0fe062d96 100644
--- a/lib/fuzzing/fuzz_ndr_X.c
+++ b/lib/fuzzing/fuzz_ndr_X.c
@@ -49,7 +49,7 @@ enum {
 
 /*
  * We want an even number here to ensure 4-byte alignment later
- * not just for efficieny but because the fuzzers are known to guess
+ * not just for efficiency but because the fuzzers are known to guess
  * that numbers will be 4-byte aligned
  */
 #define HEADER_SIZE 4
diff --git a/lib/fuzzing/oss-fuzz/check_build.sh b/lib/fuzzing/oss-fuzz/check_build.sh
index 6523bf32ace..487addfe80a 100755
--- a/lib/fuzzing/oss-fuzz/check_build.sh
+++ b/lib/fuzzing/oss-fuzz/check_build.sh
@@ -3,7 +3,7 @@
 # A very simple check script to confirm we still provide binaries
 # that look like the targets oss-fuzz wants.
 #
-# A much stronger check is availble in oss-fuzz via
+# A much stronger check is available in oss-fuzz via
 # infra/helper.py check_build samba
 #
 
diff --git a/lib/fuzzing/oss-fuzz/do_build.sh b/lib/fuzzing/oss-fuzz/do_build.sh
index 3b2fdd0da94..b23f6cd4e3e 100755
--- a/lib/fuzzing/oss-fuzz/do_build.sh
+++ b/lib/fuzzing/oss-fuzz/do_build.sh
@@ -109,7 +109,7 @@ mkdir -p $OUT/lib
 # but not for our hack.
 #
 # If we use RUNPATH, we can get an error like this:
-# Step #6: Error occured while running fuzz_nmblib_parse_packet:
+# Step #6: Error occurred while running fuzz_nmblib_parse_packet:
 # Step #6: /workspace/out/coverage/fuzz_nmblib_parse_packet: error while loading shared libraries: libavahi-common.so.3: cannot open shared object file: No such file or directory
 #
 # This is because the full contents of $OUT are copied to yet another
@@ -274,11 +274,11 @@ done
 # will cause the dynamic linker to search in the runpath, and not in $OUT/lib,
 # and there's no way it will be found in the fuzzing env.
 #
-# So how is the indirect depedency found in $OUT/lib? Well, suppose the fuzzer binary
+# So how is the indirect dependency found in $OUT/lib? Well, suppose the fuzzer binary
 # links library A which links library B. During linking, both A and B as listed in the
 # executable file's runtime dependencies (This was pioneered in Fedora 13 in 2010, but
 # is common behavior now). So we have the fuzzer binary with RPATH set to $OUT/lib, and
-# a dependency on library B, and it will therefor find library B in $OUT/lib. On the
+# a dependency on library B, and it will therefore find library B in $OUT/lib. On the
 # hand, if we keep the RUNPATH in library A, and load A first, it will try loading
 # library B as a dependency of A from the wrong place.
 chrpath -d $OUT/lib/*