diff --git a/docs/build-on-morph/build-on-morph/3-bridge-between-morph-and-ethereum.md b/docs/build-on-morph/build-on-morph/3-bridge-between-morph-and-ethereum.md
index 517bd4a6..cdb5ce00 100644
--- a/docs/build-on-morph/build-on-morph/3-bridge-between-morph-and-ethereum.md
+++ b/docs/build-on-morph/build-on-morph/3-bridge-between-morph-and-ethereum.md
@@ -31,7 +31,7 @@ All Gateway contracts will form the message and send it to the `L1CrossDomainMes
 
 This means they can execute any function on L2 from a transaction made on L1 via the bridge. Although an application could directly pass messages to existing token contracts, the Gateway abstracts the specifics and simplifies making transfers and calls.
 
-When a new block gets created on L1, the Sequencer will detect the message on the `L1MessageQueue`, and submit the transaction to the L2 via the its L2 node. Finally, the L2 node will pass the transaction to the `L2CrossDomainMessenger` contract for execution on L2.
+When a new block gets created on L1, the Sequencer will detect the message on the `L1MessageQueue`, and submit the transaction to the L2 via its L2 node. Finally, the L2 node will pass the transaction to the `L2CrossDomainMessenger` contract for execution on L2.
 
 ## Withdraw ETH and ERC20 tokens from L2
 
diff --git a/docs/build-on-morph/build-on-morph/4-understand-transaction-cost-on-morph.md b/docs/build-on-morph/build-on-morph/4-understand-transaction-cost-on-morph.md
index f494b9fe..62b077da 100644
--- a/docs/build-on-morph/build-on-morph/4-understand-transaction-cost-on-morph.md
+++ b/docs/build-on-morph/build-on-morph/4-understand-transaction-cost-on-morph.md
@@ -31,7 +31,7 @@ The formula is straightforward:
 
 
 <!--
-We support [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) as a way to process L2 transaction fee.
+We support [EIP-1559](https://eips.ethereum.org/EIPS/eip-1559) as a way to process L2 transaction fees.
 
 In EIP-1559, the cost of a unit of gas is composed of two components:
 
@@ -172,4 +172,4 @@ See the section on [Responding to gas price updates](#responding-to-gas-price-up
 
 This is a custom RPC error that Morph returns when a transaction is rejected because the gas price is too high.
 We include this as a safety measure to prevent users from accidentally sending a transaction with an extremely high L2 gas price.
-See the section on [Responding to gas price updates](#responding-to-gas-price-updates) for more information.
\ No newline at end of file
+See the section on [Responding to gas price updates](#responding-to-gas-price-updates) for more information.
diff --git a/docs/build-on-morph/build-on-morph/5-verify-your-smart-contracts.md b/docs/build-on-morph/build-on-morph/5-verify-your-smart-contracts.md
index bdbcc63c..5ee080d5 100644
--- a/docs/build-on-morph/build-on-morph/5-verify-your-smart-contracts.md
+++ b/docs/build-on-morph/build-on-morph/5-verify-your-smart-contracts.md
@@ -17,7 +17,7 @@ Most smart contract tools have plugins for verifying contracts on Etherscan. Blo
 We provide a comprehensive example of deploying contracts on Morph using Hardhat and Foundry, which includes the verification process.
 
 
-Check [Deploy Conrtacts on Morph](../code-examples/1-deploy-contract-on-morph.md) for examples.
+Check [Deploy Contracts on Morph](../code-examples/1-deploy-contract-on-morph.md) for examples.
 
 ## Vefiry with Morph explorer