diff --git a/CHANGELOG.org b/CHANGELOG.org
index c988900..0676f56 100644
--- a/CHANGELOG.org
+++ b/CHANGELOG.org
@@ -21,6 +21,7 @@
 
 ** Fixed
 Fixed behavior of R@ thanks to reepca
+Updated changed checksums for stage2 FORTH
 
 ** Removed
 
diff --git a/bootstrapping Steps.org b/bootstrapping Steps.org
index 98331cf..cfc491a 100644
--- a/bootstrapping Steps.org	
+++ b/bootstrapping Steps.org	
@@ -174,7 +174,7 @@ Then we use our M0 Line macro assembler to convert our assembly into hex2 format
 Then we need to assemble that hex into our desired program:
 ./bin/vm --rom roms/stage1_assembler-2 --tape_01 temp2 --tape_02 roms/forth --memory 48K
 
-roms/forth should with the sha256sum of d7967248be71937d4fa1f38319a5a8473a842b1f6806b977e5fb184565bde0a4
+roms/forth should with the sha256sum of b3a910f18c6bc0ef4aa7a53cb3f0216a9f143319da67ed2a02210fe88b1e1131
 
 Our forth will first attempt to evaluate any code in tape_01 and then evaluate any code that the user types in
 (Otherwise there is no way for a forth fan to have a chance against the lisp in terms of being able to bootstrap something cool)
diff --git a/test/SHA256SUMS b/test/SHA256SUMS
index 399749d..58a810b 100644
--- a/test/SHA256SUMS
+++ b/test/SHA256SUMS
@@ -1,6 +1,6 @@
 8f465d3ec1cba00a7d024a1964e74bb6d241f86a73c77d95d8ceb10d09c8f7b9  roms/CAT
 59f0502748af32e3096e026a95e77216179cccfe803a05803317414643e2fcec  roms/DEHEX
-d7967248be71937d4fa1f38319a5a8473a842b1f6806b977e5fb184565bde0a4  roms/forth
+b3a910f18c6bc0ef4aa7a53cb3f0216a9f143319da67ed2a02210fe88b1e1131  roms/forth
 7c3887f791999aa9c1b8415d8e5be93afcf916b505296d9da7bd7a22531a84b5  roms/lisp
 2b9727381aec15a504c0898189fbc2344209d8e04451e3fa5d743e08e38f64cf  roms/M0
 24a4d74eb2eb7a82e68335643855658b27b5a6c3b13db473539f3e08d6f26ceb  roms/SET