From 95a5f26024661cceaca96e432474b814ead87df3 Mon Sep 17 00:00:00 2001
From: Evan Su <48808396+HACKERALERT@users.noreply.github.com>
Date: Sun, 10 Apr 2022 13:44:27 -0400
Subject: [PATCH] Better words

---
 Internals.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Internals.md b/Internals.md
index 3dad328..4d51cd1 100644
--- a/Internals.md
+++ b/Internals.md
@@ -39,4 +39,4 @@ If "Require correct order" is not checked, Picocrypt will take the SHA3 hash of
 If "Require correct order" is checked, Picocrypt will concatenate the files together in the order they were dropped into the window and take the SHA3 hash of the combined keyfiles. If the order is not correct, the keyfiles, when appended to each other, will result in a different file, and therefore a different hash. Thus, the correct order of keyfiles is required to successfully decrypt the volume.
 
 # Reed-Solomon
-By default, all Picocrypt volume headers are encoded with Reed-Solomon to improve resiliency to bit rot, etc. The header uses N+2N encoding, where N is the size of a particular header field such as the version number or Argon2 salt. If Reed-Solomon is to be used with the input data itself, the data is encoded using 128+8 encoding, with the data being read in chunks of 1 MiB, and the final set padded to 128 bytes using PKCS#7.
+By default, all Picocrypt volume headers are encoded with Reed-Solomon to improve resiliency against bit rot, etc. The header uses N+2N encoding, where N is the size of a particular header field such as the version number or the Argon2 salt. If Reed-Solomon is to be used with the input data itself, the data will be encoded using 128+8 encoding, with the data being read in chunks of 1 MiB, and the final set padded to 128 bytes using PKCS#7.