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

---
 src/processor/update_difficulty.rs | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/processor/update_difficulty.rs b/src/processor/update_difficulty.rs
index b05eb66..0a0a2c1 100644
--- a/src/processor/update_difficulty.rs
+++ b/src/processor/update_difficulty.rs
@@ -22,10 +22,10 @@ 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 today processes well below 1 million real TPS or 
-///   (60 * 1,000,000) = 60,000,000 transactions per minute. Even if ever transaction on Solana
+///   (60 * 1,000,000) = 60,000,000 transactions per minute. Even if every 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. 
+///   to reach its network saturation point long before Ore ever hits its theoretical limits. 
 pub fn process_update_difficulty<'a, 'info>(
     _program_id: &Pubkey,
     accounts: &'a [AccountInfo<'info>],