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 23:35:17.500801588 +0000
+++ new-darcs-book/en/05-a-little-help-from-my-friends.md	2024-11-23 23:35:17.500801588 +0000
@@ -17,7 +17,7 @@
 
 Let's say you want to `clone` the source of this book, which is hosted on [darcs
 hub](https://hub.darcs.net/raichoo/darcs-book). To `clone` this repository you
-simply issue `darcs `clone` https://hub.darcs.net/raichoo/darcs-book` and
+simply issue `darcs clone https://hub.darcs.net/raichoo/darcs-book` and
 `darcs` will start copying the repository into a directory called `darcs-book`..
 
 ```
@@ -32,7 +32,7 @@
 the newest changes and pull in everything else on demand? No need to pull in the
 entire history of a project all at once. A lazy repository does just that, and
 this reduces cloning time drastically. Cloning the entire history is only useful
-if you might not be able to access the internet for some time and you really
+if you might not be able to access the Internet for some time and you really
 need to have access to the entire evolution of the project. So if you happen to
 get stuck on a particularly long `clone`, just hit `CTRL-C` and you are good to
 go, most of the time you will be interested in the current state of the