diff --git a/hush-v3.pdf b/hush-v3.pdf
index c3bc173..88d7d7b 100644
Binary files a/hush-v3.pdf and b/hush-v3.pdf differ
diff --git a/hush-v3.tex b/hush-v3.tex
index ab22dec..5f57cd7 100644
--- a/hush-v3.tex
+++ b/hush-v3.tex
@@ -734,8 +734,8 @@ explorer such as :
 
 https://explorer.hush.zelcore.io
 
-Additionally, the orphaned block will not be in the main chain and only will
-exist as an orphaned block on nodes which originally saw that invalidated chain.
+Additionally, the orphaned blocks will not be in the main chain and only will
+exist as an orphaned blocks on nodes which originally saw that invalidated chain.
 
 Via blockchain analysis and detailed transaction logs from Cryptopia, who gave
 us details about which addresses the attacker was using, it was determined that
@@ -784,7 +784,7 @@ get to decide which chain goes forward.
 Let it be known that HUSH v2 mainnet is considered a Sprout Inflation bug
 playground, and there is a bounty of 500 HUSH for a script which makes it
 trivial to exploit the Sprout inflation bug and generate arbitrary amounts
-of funds insize of a Sprout zaddr.
+of funds inside of a Sprout zaddr.
 
 Developers and information security researchers are directed here for more
 info: