From f35521a1fbf2a8a2cfe27baee5aa68317f860f3b Mon Sep 17 00:00:00 2001
From: wintercooled <wintercooled@users.noreply.github.com>
Date: Thu, 22 Mar 2018 17:43:03 +0000
Subject: [PATCH] Update 05_1_Watching_for_Stuck_Transactions.md

Fixed minor typo.
---
 05_1_Watching_for_Stuck_Transactions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/05_1_Watching_for_Stuck_Transactions.md b/05_1_Watching_for_Stuck_Transactions.md
index 263ca51..d9b79ec 100644
--- a/05_1_Watching_for_Stuck_Transactions.md
+++ b/05_1_Watching_for_Stuck_Transactions.md
@@ -38,7 +38,7 @@ $  bitcoin-cli -named gettransaction txid=0f618e38efe887028a5dd04d0e12241431978b
 ```
 A transaction can be considered stuck if it stays in this state for an extended amount of time. Not too many years ago, you could be sure that every transaction would go out _eventually_. But, that's no longer the case due to the increased usage of Bitcoin. Now, if a transaction is stuck too long, it will drop out of the mempool and then be lost from the Bitcoin network.
 
-_What is the mempool?_ The Bitcoin mempool (or Memory Pool) is the pool of all unconfirmed transactions. When a miner makes a block, he uses transactions from his mempool. Then, when a block is verified, all the miners remove the transactions it contains from their pools. As of Bitcoin 0.12, unconfirmed transactions can also expire from mempools if they're old enough: typically, 72 hours or more. Mining pools might have their mempool-management mechanisms. Though the mempool should be largely the same across the Bitcoin network, there will be variations on each machine: different transactions might have propogated to a specific node or (more notably) it might have different limits on how much it's willing to store. 
+_What is the mempool?_ The Bitcoin mempool (or Memory Pool) is the pool of all unconfirmed transactions. When a miner makes a block, he uses transactions from his mempool. Then, when a block is verified, all the miners remove the transactions it contains from their pools. As of Bitcoin 0.12, unconfirmed transactions can also expire from mempools if they're old enough: typically, 72 hours or more. Mining pools might have their own mempool-management mechanisms. Though the mempool should be largely the same across the Bitcoin network, there will be variations on each machine: different transactions might have propogated to a specific node or (more notably) it might have different limits on how much it's willing to store. 
 
 This list of all [unconfirmed transactions](https://blockchain.info/unconfirmed-transactions) might not match any individual machine's mempool, but it should (mostly) be a superset of them.