From 04dcb00173baa5258b3a0b4557e41474f6708df0 Mon Sep 17 00:00:00 2001
From: Hardhat Chad <155858888+HardhatChad@users.noreply.github.com>
Date: Fri, 8 Mar 2024 08:59:33 -0600
Subject: [PATCH] Update update_difficulty.rs

---
 src/processor/update_difficulty.rs | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/processor/update_difficulty.rs b/src/processor/update_difficulty.rs
index d47e575..efac504 100644
--- a/src/processor/update_difficulty.rs
+++ b/src/processor/update_difficulty.rs
@@ -22,7 +22,7 @@ use crate::{
 ///   but it is the responsibility of the admin to adjust mining difficulty if needed to maintain
 ///   the 1 ORE / min target average.
 /// - It is worth noting that Solana processes well below 1 million real TPS or 
-///   (60 * 1,000,000) = 60,000,000 hash validations per epoch. Even if ever transaction on Solana
+///   (60 * 1,000,000) = 60,000,000 transactions per minute. Even if ever transaction on Solana
 ///   were a mine operation, this would still be two orders of magnitude below the boundary 
 ///   condition where Ore inflation targets would be challenged. So in practice, Solana is likely 
 ///   to reach its network saturation point long before Ore ever hits theoretical limits.