~jan0sch/darcs-book

Showing details for patch 86781dfb2e2c94b14cae658000789ac67237d915.
2018-06-28 (Thu), 7:15 AM - - 86781dfb2e2c94b14cae658000789ac67237d915

fix typos in chapter 3

Summary of changes
1 files modified with 2 lines added and 2 lines removed
  • en/03-working-locally.md with 2 added and 2 removed lines
diff -rN -u old-darcs-book/en/03-working-locally.md new-darcs-book/en/03-working-locally.md
--- old-darcs-book/en/03-working-locally.md	2024-11-24 04:26:42.941465682 +0000
+++ new-darcs-book/en/03-working-locally.md	2024-11-24 04:26:42.941465682 +0000
@@ -64,7 +64,7 @@
 ```
 
 What `darcs` does here is that it compares the state of your working directory
-against the state of the repository (recall that the state of the respository is
+against the state of the repository (recall that the state of the repository is
 a set of changes). In our current repository there are no recorded changes so
 adding something to our working directory surely should constitute a change
 shouldn't it?
@@ -382,7 +382,7 @@
 ```
 
 The patch with the hash `81fac56462c274f8a507f9e5497c22e8d418cae9` looks
-interesting and I want to dril down further. I can use the `-h' flag to specify
+interesting and I want to drill down further. I can use the `-h' flag to specify
 a patch hash. I don't need to specify the entire hash but only a unique prefix.
 `darcs log` will display the first patch where the hash matches the given
 prefix.