diff --git a/zebra-chain/src/addresses/transparent.rs b/zebra-chain/src/addresses/transparent.rs
index 394fcfba2..8317b38c6 100644
--- a/zebra-chain/src/addresses/transparent.rs
+++ b/zebra-chain/src/addresses/transparent.rs
@@ -35,7 +35,7 @@ mod magics {
 /// In Bitcoin a single byte is used for the version field identifying
 /// the address type. In Zcash two bytes are used. For addresses on
 /// the production network, this and the encoded length cause the first
-/// two characters of the Base58Check encoding to be xed as “t3” for
+/// two characters of the Base58Check encoding to be fixed as “t3” for
 /// P2SH addresses, and as “t1” for P2PKH addresses. (This does not
 /// imply that a transparent Zcash address can be parsed identically
 /// to a Bitcoin address just by removing the “t”.)
@@ -66,7 +66,7 @@ impl TransparentAddress {
     /// addresses.
     ///
     /// The resulting hash in both of these cases is always exactly 20
-    /// bytes. These are big-endian.
+    /// bytes.
     /// https://en.bitcoin.it/Base58Check_encoding#Encoding_a_Bitcoin_address
     fn hash_payload(bytes: &[u8]) -> [u8; 20] {
         let sha_hash = Sha256::digest(bytes);
diff --git a/zebra-chain/src/keys/sapling.rs b/zebra-chain/src/keys/sapling.rs
index 486dc8d0d..3c8d363e1 100644
--- a/zebra-chain/src/keys/sapling.rs
+++ b/zebra-chain/src/keys/sapling.rs
@@ -2,7 +2,7 @@
 //!
 //! "The spend authorizing key ask, proof authorizing key (ak, nsk),
 //! full viewing key (ak, nk, ovk), incoming viewing key ivk, and each
-//! diversied payment address addr_d = (d, pk_d ) are derived from sk,
+//! diversified payment address addr_d = (d, pk_d ) are derived from sk,
 //! as described in [Sapling Key Components][ps]."
 //!
 //! [ps]: https://zips.z.cash/protocol/protocol.pdf#saplingkeycomponents