Fix typos

Author: kianmeng

README.md

@@ -188,12 +188,12 @@ For instance:
   * Avoid potential undeterministic behavior from racing threads.
   * ...
 * Never ever call `std::process::exit()`.
-* Disable logging and other unnecessary functionnalities.
+* Disable logging and other unnecessary functionalities.
 * Try to avoid modifying global state when possible.
 * Do not set up your own panic hook when run with `cfg(fuzzing)`
 
 
-When building with `cargo hfuzz`, the argument `--cfg fuzzing` is passed to `rustc` to allow you to condition the compilation of thoses adaptations thanks to the `cfg` macro like so:
+When building with `cargo hfuzz`, the argument `--cfg fuzzing` is passed to `rustc` to allow you to condition the compilation of those adaptations thanks to the `cfg` macro like so:
 
 ```rust
 #[cfg(fuzzing)]

build.rs

@@ -33,7 +33,7 @@ fn main() {
     let out_dir = env::var("OUT_DIR").unwrap(); // from cargo
     let crate_root = env::var("CRATE_ROOT").unwrap(); //from honggfuzz
 
-    // clean upsteam honggfuzz directory
+    // clean upstream honggfuzz directory
     let status = Command::new(GNU_MAKE)
         .args(&["-C", "honggfuzz", "clean"])
         .status()

example/test.sh

@@ -24,7 +24,7 @@ workspace="hfuzz_workspace/example"
 rm -rf $workspace
 mkdir -p $workspace/input
 
-# fuzz exemple
+# fuzz example
 cd subdirectory
 HFUZZ_RUN_ARGS="-v -N 10000000 --run_time 120 --exit_upon_crash" $CARGO_HFUZZ run example
 cd ..

src/lib.rs

@@ -160,7 +160,7 @@
 //! 
 //! Honggfuzz input files (also called "corpus"), defaults to `$HFUZZ_WORKSPACE/{TARGET}/input`.
 //! 
-//! ## Conditionnal compilation
+//! ## Conditional compilation
 //! 
 //! Sometimes, it is necessary to make some specific adaptation to your code to yield a better fuzzing efficiency.
 //! 
@@ -171,11 +171,11 @@
 //!   - Avoid potential undeterministic behavior from racing threads.
 //!   - ...
 //! - Never ever call `std::process::exit()`.
-//! - Disable logging and other unnecessary functionnalities.
+//! - Disable logging and other unnecessary functionalities.
 //! - Try to avoid modifying global state when possible.
 //! 
 //! 
-//! When building with `cargo hfuzz`, the argument `--cfg fuzzing` is passed to `rustc` to allow you to condition the compilation of thoses adaptations thanks to the `cfg` macro like so:
+//! When building with `cargo hfuzz`, the argument `--cfg fuzzing` is passed to `rustc` to allow you to condition the compilation of those adaptations thanks to the `cfg` macro like so:
 //! 
 //! ```rust
 //! # use rand::{self, Rng, SeedableRng};
@@ -247,7 +247,7 @@ pub fn fuzz<F>(closure: F) where F: FnOnce(&[u8]) {
 
 // Registers a panic hook that aborts the process before unwinding.
 // It is useful to abort before unwinding so that the fuzzer will then be
-// able to analyse the process stack frames to tell different bugs appart.
+// able to analyse the process stack frames to tell different bugs apart.
 #[cfg(all(fuzzing, not(fuzzing_debug)))]
 lazy_static::lazy_static! {
     static ref PANIC_HOOK: () = {
@@ -277,7 +277,7 @@ pub fn fuzz<F>(closure: F) where F: FnOnce(&[u8]) {
 
     // We still catch unwinding panics just in case the fuzzed code modifies
     // the panic hook.
-    // If so, the fuzzer will be unable to tell different bugs appart and you will
+    // If so, the fuzzer will be unable to tell different bugs apart and you will
     // only be able to find one bug at a time before fixing it to then find a new one.
     // The closure is assumed to be unwind-safe, which might be unsafe. For more info, check the
     // [`std::panic::UnwindSafe`] trait.