From a57fd16b7cac9e9e28a0e07222c99ca4903772de Mon Sep 17 00:00:00 2001
From: Skylar Ray <137945430+sky-coderay@users.noreply.github.com>
Date: Wed, 27 Nov 2024 14:57:11 +0200
Subject: [PATCH] Update cat_pool.md

---
 specs/src/cat_pool.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/specs/src/cat_pool.md b/specs/src/cat_pool.md
index 22ad999aec..feaecf7319 100644
--- a/specs/src/cat_pool.md
+++ b/specs/src/cat_pool.md
@@ -53,7 +53,7 @@ A node in the protocol has two distinct modes: "broadcast" and "request/response
 A `SeenTx` is broadcasted to ALL nodes upon receiving a "new" transaction from a peer. The transaction pool does not need to track every unique inbound transaction, therefore "new" is identified as:
 
 - The node does not currently have the transaction
-- The node did not recently reject the transacton or has recently seen the same transaction committed (subject to the size of the cache)
+- The node did not recently reject the transaction or has recently seen the same transaction committed (subject to the size of the cache)
 - The node did not recently evict the transaction (subject to the size of the cache)
 
 Given this criteria, it is feasible, yet unlikely that a node receives two `SeenTx` messages from the same peer for the same transaction.