diff --git a/fuzz/cycle.sh b/fuzz/cycle.sh
index 0b59827a..7de15c82 100755
--- a/fuzz/cycle.sh
+++ b/fuzz/cycle.sh
@@ -1,6 +1,6 @@
 #!/usr/bin/env bash
 
-# Continuosly cycle over fuzz targets running each for 1 hour.
+# Continuously cycle over fuzz targets running each for 1 hour.
 # It uses chrt SCHED_IDLE so that other process takes priority.
 #
 # For hfuzz options see https://github.com/google/honggfuzz/blob/master/docs/USAGE.md
diff --git a/hashes/README.md b/hashes/README.md
index 433a9593..a6143d70 100644
--- a/hashes/README.md
+++ b/hashes/README.md
@@ -2,7 +2,7 @@
 
 This is a simple, no-dependency library which implements the hash functions
 needed by Bitcoin. These are SHA1, SHA256, SHA256d, SHA512, and RIPEMD160. As an
-ancilliary thing, it exposes hexadecimal serialization and deserialization,
+ancillary thing, it exposes hexadecimal serialization and deserialization,
 since these are needed to display hashes anway.
 
 [Documentation](https://docs.rs/bitcoin_hashes/)
diff --git a/hashes/src/sha256t.rs b/hashes/src/sha256t.rs
index 774dfdc8..1a613cd3 100644
--- a/hashes/src/sha256t.rs
+++ b/hashes/src/sha256t.rs
@@ -101,7 +101,7 @@ fn from_engine<T: Tag>(e: sha256::HashEngine) -> Hash<T> {
 /// says the midstate should be generated by hashing the supplied string in a way described in
 /// BIP-341. Alternatively, you can supply `hash_bytes` to hash raw bytes. If you have the midstate
 /// already pre-computed and prefer **compiler** performance to readability you may use
-/// `raw(MIDSTATE_BYTES, HASHED_BYTES_LENGHT)` instead.
+/// `raw(MIDSTATE_BYTES, HASHED_BYTES_LENGTH)` instead.
 ///
 /// Both visibility modifiers and attributes are optional and passed to inner structs (excluding
 /// `#[hash_newtype(...)]`). The attributes suffer same compiler performance limitations as in
diff --git a/hashes/src/sha512_256.rs b/hashes/src/sha512_256.rs
index c0d4529b..e5c36624 100644
--- a/hashes/src/sha512_256.rs
+++ b/hashes/src/sha512_256.rs
@@ -2,7 +2,7 @@
 
 //! SHA512_256 implementation.
 //!
-//! SHA512/256 is a hash function that uses the sha512 alogrithm but it truncates
+//! SHA512/256 is a hash function that uses the sha512 algorithm but it truncates
 //! the output to 256 bits. It has different initial constants than sha512 so it
 //! produces an entirely different hash compared to sha512. More information at
 //! <https://eprint.iacr.org/2010/548.pdf>.
@@ -16,7 +16,7 @@ use crate::{sha512, FromSliceError};
 crate::internal_macros::hash_type! {
     256,
     false,
-    "Output of the SHA512/256 hash function.\n\nSHA512/256 is a hash function that uses the sha512 alogrithm but it truncates the output to 256 bits. It has different initial constants than sha512 so it produces an entirely different hash compared to sha512. More information at <https://eprint.iacr.org/2010/548.pdf>."
+    "Output of the SHA512/256 hash function.\n\nSHA512/256 is a hash function that uses the sha512 algorithm but it truncates the output to 256 bits. It has different initial constants than sha512 so it produces an entirely different hash compared to sha512. More information at <https://eprint.iacr.org/2010/548.pdf>."
 }
 
 fn from_engine(e: HashEngine) -> Hash {
@@ -27,7 +27,7 @@ fn from_engine(e: HashEngine) -> Hash {
 
 /// Engine to compute SHA512/256 hash function.
 ///
-/// SHA512/256 is a hash function that uses the sha512 alogrithm but it truncates
+/// SHA512/256 is a hash function that uses the sha512 algorithm but it truncates
 /// the output to 256 bits. It has different initial constants than sha512 so it
 /// produces an entirely different hash compared to sha512. More information at
 /// <https://eprint.iacr.org/2010/548.pdf>.