~jan0sch/darcs-book

Showing details for patch 1c68aee239785bc86c83116c6f74ae90eab38f70.
2018-07-24 (Tue), 4:25 PM - - 1c68aee239785bc86c83116c6f74ae90eab38f70

fix typo in chapter 5

Summary of changes
1 files modified with 3 lines added and 3 lines removed
  • en/05-a-little-help-from-my-friends.md with 3 added and 3 removed lines
diff -rN -u old-darcs-book/en/05-a-little-help-from-my-friends.md new-darcs-book/en/05-a-little-help-from-my-friends.md
--- old-darcs-book/en/05-a-little-help-from-my-friends.md	2024-11-23 17:56:10.968357165 +0000
+++ new-darcs-book/en/05-a-little-help-from-my-friends.md	2024-11-23 17:56:10.968357165 +0000
@@ -134,7 +134,7 @@
 `darcs` first figures out which patches are not present in the destination
 repository and prompts us for each one of them if we really want to push that
 patch. Once we are done it asks us if we really want to push these patches and
-after confirming all our selected patches are being transfered to the
+after confirming all our selected patches are being transferred to the
 destination repository.
 
 Let's take a quick look at the patches that are now inside our `new-project`
@@ -150,9 +150,9 @@
   * added some file
 ```
 
-Nice, as you can see our patch has been transfered from `new-project-work` to
+Nice, as you can see our patch has been transferred from `new-project-work` to
 the `new-project` repository. If you take a look at the working tree you will
-also find that all the changes contained in our transfered patches have been
+also find that all the changes contained in our transferred patches have been
 applied. Piece of cake!
 
 Keep in mind that the destination does not need to be just another folder on our