~jan0sch/darcs-book

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

fix typos in chapter 7

Summary of changes
1 files modified with 1 lines added and 1 lines removed
  • en/07-dependencies-and-good-patches.md with 1 added and 1 removed lines
diff -rN -u old-darcs-book/en/07-dependencies-and-good-patches.md new-darcs-book/en/07-dependencies-and-good-patches.md
--- old-darcs-book/en/07-dependencies-and-good-patches.md	2024-11-23 18:00:20.160989056 +0000
+++ new-darcs-book/en/07-dependencies-and-good-patches.md	2024-11-23 18:00:20.160989056 +0000
@@ -213,7 +213,7 @@
 
 So here you can see a repository where were are tracking the development of 3
 different features `A`, `B` and `C`. Since `darcs` knows about dependencies we
-can work on each of these features separately without interfering the others. I
+can work on each of these features separately without interfering the others. If
 someone else chooses to work on feature `A` and we are working on feature `B` we
 can do that in a single repository without getting in each others way. Not many
 version control systems can do that without changing the identity of the patches