Fix typos

tower-batch/src/lib.rs

@@ -62,7 +62,7 @@
 //!
 //! ## Batch processing middleware
 //!
-//! Tower's [`Service`](tower::Service) interface is an an attractive choice for
+//! Tower's [`Service`](tower::Service) interface is an attractive choice for
 //! implementing this model for two reasons. First, it makes it easy to express
 //! generic bounds on [`Service`](tower::Service)s, allowing higher-level
 //! verification services to be written generically with respect to the

zebra-chain/src/block/header.rs

@@ -48,7 +48,7 @@ pub struct BlockHeader {
     /// hash must be less than or equal to, in the same nBits format
     /// used by Bitcoin.
     ///
-    /// For a block at block height height, bits MUST be equal to
+    /// For a block at block height, bits MUST be equal to
     /// ThresholdBits(height).
     ///
     /// [Bitcoin-nBits](https://bitcoin.org/en/developer-reference#target-nbits)

zebra-chain/src/note_commitment_tree.rs

@@ -52,7 +52,7 @@ impl From<SaplingNoteCommitmentTree> for SaplingNoteTreeRootHash {
         // let mut hash_writer = Sha256dWriter::default();
         // sapling_note_commitment_tree
         //     .zcash_serialize(&mut hash_writer)
-        //     .expect("A Sapling note committment tree must serialize.");
+        //     .expect("A Sapling note commitment tree must serialize.");
         // Self(hash_writer.finish())
 
         unimplemented!();

zebra-chain/src/nullifier.rs

@@ -1,4 +1,4 @@
-//! Nullifier set types for sproud and sapling
+//! Nullifier set types for sprout and sapling
 
 pub mod sapling;
 pub mod sprout;

zebra-network/src/constants.rs

@@ -27,7 +27,7 @@ pub const HEARTBEAT_INTERVAL: Duration = Duration::from_secs(60);
 
 /// Truncate timestamps in outbound address messages to this time interval.
 ///
-/// This is intended to prevent a peer from learning exactly when we recieved
+/// This is intended to prevent a peer from learning exactly when we received
 /// messages from each of our peers.
 pub const TIMESTAMP_TRUNCATION_SECONDS: i64 = 30 * 60;
 

zebra-network/src/peer_set/initialize.rs

@@ -106,7 +106,7 @@ where
     // 3. Outgoing peers we connect to in response to load.
     let mut candidates = CandidateSet::new(address_book.clone(), peer_set.clone());
 
-    // We need to await candidates.update() here, because Zcashd only sends one
+    // We need to await candidates.update() here, because zcashd only sends one
     // `addr` message per connection, and if we only have one initial peer we
     // need to ensure that its `addr` message is used by the crawler.
     // XXX this should go in CandidateSet::new, but we need init() -> Result<_,_>

zebra-network/src/protocol/external/message.rs

@@ -308,7 +308,7 @@ where
 
             reason: e.source().unwrap().to_string(),
 
-            // Allow this to be overriden but not populated by default, methinks.
+            // Allow this to be overridden but not populated by default, methinks.
             data: None,
         }
     }

zebrad/src/commands/start.rs

@@ -6,7 +6,7 @@
 //!
 //!  * Network Service
 //!    * primary interface to the node
-//!    * handles all external network requests for the zcash protocol
+//!    * handles all external network requests for the Zcash protocol
 //!      * via zebra_network::Message and zebra_network::Response
 //!    * provides an interface to the rest of the network for other services and
 //!    tasks running within this node
@@ -16,7 +16,7 @@
 //!    * verifies blocks using zebra-chain and zebra-script, then stores verified
 //!    blocks in zebra-state
 //!  * Sync Task
-//!    * This task runs in the background and continouously queries the network for
+//!    * This task runs in the background and continuously queries the network for
 //!    new blocks to be verified and added to the local state
 use crate::config::ZebradConfig;
 use crate::{components::tokio::TokioComponent, prelude::*};