diff --git a/EIPS/eip-6672.md b/EIPS/eip-6672.md
index 74afff70e1620c..10d4d6093cd1b9 100644
--- a/EIPS/eip-6672.md
+++ b/EIPS/eip-6672.md
@@ -159,7 +159,7 @@ The combination of `_operator`, `_tokenId`, and `_redemptionId` is chosen as the
 
 - Operator wallet address, i.e. `_operator`
 
-    It's possible that there are more than one party who would like to use the same NFT for redemption. For example, MisterPunks NFTs are eligible to be redemeed for both Event-X and Event-Y tickets, and each event's ticket redemption is handled by a different operator.
+    It's possible that there are more than one party who would like to use the same NFT for redemption. For example, MisterPunks NFTs are eligible to be redeemed for both Event-X and Event-Y tickets, and each event's ticket redemption is handled by a different operator.
 
 - Token identifier, i.e. `_tokenId`
 
@@ -167,7 +167,7 @@ The combination of `_operator`, `_tokenId`, and `_redemptionId` is chosen as the
 
 - Redemption identifier, i.e. `_redemptionId`
 
-    Using `_redemptionId` as one of the keys enables NFT holders to redeem the same NFT to the same operator in multiple campaigns. For example, Operator-X has 2 campaigns, i.e. campaign A and campaign B, and both campaigns allow for MisterPunks NFTs to be redemeed for physical action figures. Holder of MisterPunk #7 is eligible for redemption in both campaigns and each redemption is recorded with the same `_operator` and `_tokenId`, but with different `_redemptionId`.
+    Using `_redemptionId` as one of the keys enables NFT holders to redeem the same NFT to the same operator in multiple campaigns. For example, Operator-X has 2 campaigns, i.e. campaign A and campaign B, and both campaigns allow for MisterPunks NFTs to be redeemed for physical action figures. Holder of MisterPunk #7 is eligible for redemption in both campaigns and each redemption is recorded with the same `_operator` and `_tokenId`, but with different `_redemptionId`.
 
 ## Backwards Compatibility