~jan0sch/darcs-book

Showing details for patch 2304ec8fd8d59dd91bab1c4aa6717d004c4f5794.
2019-01-19 (Sat), 7:17 PM - blabber - 2304ec8fd8d59dd91bab1c4aa6717d004c4f5794

fix typos in chapter 8

Summary of changes
1 files modified with 2 lines added and 2 lines removed
  • en/08-rewriting-history.md with 2 added and 2 removed lines
diff -rN -u old-darcs-book/en/08-rewriting-history.md new-darcs-book/en/08-rewriting-history.md
--- old-darcs-book/en/08-rewriting-history.md	2024-11-23 17:35:55.285571074 +0000
+++ new-darcs-book/en/08-rewriting-history.md	2024-11-23 17:35:55.285571074 +0000
@@ -308,7 +308,7 @@
 OB-LIT-E-RATE!
 --------------
 
-Sometime we want to go even further than `unrecord`. For example when a feature
+Sometimes we want to go even further than `unrecord`. For example when a feature
 we are working on turns out to be completely broken and we think that we are
 better off to start from scratch. Of course we could just do an `unrecord`
 followed by a `revert` to make the patches disappear from our repository and
@@ -394,5 +394,5 @@
 as well as the related files in our working tree. Notice how `darcs` has kept
 all our changes regarding file `A` even though the changes to `A` and `B` where
 interleaved in our first `darcs log` output. But there is no relationship
-between those changes so `darcs` could get separate those two cleanly from one
+between those changes so `darcs` could separate those two cleanly from one
 another.