docs: typo fixes in the usage guide

commit 89427c24824053434f410ce770162cc8d45b1d2e · parent f7d299ab19 · browse this tree
Ximianth, 2026-10-27 17:04:48 UTC

diff --git a/docs/userguide/USAGE.md b/docs/userguide/USAGE.md
index cae1f89..7f4b897 100644
--- a/docs/userguide/USAGE.md
+++ b/docs/userguide/USAGE.md
@@ -70,7 +70,7 @@ and one patch file per commit.
 
 ### the files
 
-Here's a quick peak into the files produced by the export:
+Here's a quick peek into the files produced by the export:
 
 First, here's `~/src/frob-patches/docs-polish/STACK`:
 
@@ -192,7 +192,7 @@ and checks it comes out exactly as it was recorded.
 
 Useful for the paranoid and cautious, effectively.
 But also can tell you if you've edited the patches manually (see more about this in the next section)
-and have forgotten to regenerated any of the logged hashes.
+and have forgotten to regenerate any of the logged hashes.
 
 One can also name specific branches to check just those.
 
@@ -300,7 +300,7 @@ verify: ok: refs/heads/topic/fancy reproduces recorded tip 57d05b16d9ad81fd92af1
 
 Note that `patchette verify` fails right after the manual edits:
 this makes sense, because if the patches have been changed, of course they no longer produce
-the exact same resulting history and content in git, so they expected tip hash has to be updated.
+the exact same resulting history and content in git, so the expected tip hash has to be updated.
 A `patchette import -f` and `patchette export` round trip will cause the tip hash to be freshly recorded
 and result in a happy verify again.