diff --git a/chain/chain/src/chain_update.rs b/chain/chain/src/chain_update.rs
index 42944b3e813..2e4173b87c9 100644
--- a/chain/chain/src/chain_update.rs
+++ b/chain/chain/src/chain_update.rs
@@ -195,7 +195,7 @@ impl<'a> ChainUpdate<'a> {
         Ok(())
     }
 
-    /// Extra sanity check for bandwdith scheduler - the scheduler state should be the same on all shards.
+    /// Extra sanity check for bandwidth scheduler - the scheduler state should be the same on all shards.
     fn bandwidth_scheduler_state_sanity_check(apply_results: &[ShardUpdateResult]) {
         let state_hashes: Vec<CryptoHash> = apply_results
             .iter()
diff --git a/docs/misc/contract_distribution.md b/docs/misc/contract_distribution.md
index c8faa14f630..4bacf778100 100644
--- a/docs/misc/contract_distribution.md
+++ b/docs/misc/contract_distribution.md
@@ -4,7 +4,7 @@ The current chunk state witness structure is inefficient due to a significant po
 
 In feature `ExcludeContractCodeFromStateWitness`, we optimize the state witness size by distributing the contract code separately from the witness, under the following observations:
 1. New contracts are deployed infrequently, so the function calls are often made to the same contract and we distribute the same contract code in the witness many times at different heights.
-2. Once deployed, a contract is compiled and stored in the compiled-contract cache. This cache is stored in the disk and persistent across epochs, until the VM configuration changes. The chunk application uses this cache to bypass the trie traversal and storage reads to fetch the uncompiled contract code from storage. The cache is maintaned with high hit rates by both chunk producers and chunk validators.
+2. Once deployed, a contract is compiled and stored in the compiled-contract cache. This cache is stored in the disk and persistent across epochs, until the VM configuration changes. The chunk application uses this cache to bypass the trie traversal and storage reads to fetch the uncompiled contract code from storage. The cache is maintained with high hit rates by both chunk producers and chunk validators.
 
 ## Deploying a contract to an account