diff -rN -u old-darcs-book/en/01-introduction.md new-darcs-book/en/01-introduction.md
--- old-darcs-book/en/01-introduction.md	2024-11-23 18:13:12.186624680 +0000
+++ new-darcs-book/en/01-introduction.md	2024-11-23 18:13:12.186624680 +0000
@@ -6,13 +6,13 @@
 
 So, you want to learn version control, or more specifically, you want to learn
 `darcs`? That's great! I hope this book will give you an interesting perspective
-on how to manage your projects and enables you to work with other people all
+on how to manage your projects and enable you to work with other people all
 around the world. I want to encourage you to follow along with the examples I
 present in this book and play around with them a bit. Things sometimes happen to
 make a lot more sense when you type them yourself and see things happening right
 in front of you. If you haven't used any kind of version control before I hope
 this book empowers and equips you with new tools that help you to manage your
-projects and improve your collaborations. If you have using traditional
+projects and improve your collaborations. If you have been using traditional
 centralized version control systems as well as other distributed systems I hope
 this book gives you a new perspective on how things can be done differently
 since `darcs` tackles version control in a refreshingly unique way.
@@ -21,7 +21,7 @@
 operating system.
 
 Most of the examples in this book happen inside of a shell and the issued
-commands prefixed with a `$` symbol while its output isn't prefixed with
+commands are prefixed with a `$` symbol while its output isn't prefixed with
 anything. Here's an example command that only outputs the word `output`.
 
 ```
@@ -32,8 +32,8 @@
 What's version control?
 -----------------------
 
-Ever had to write an imported document over an extended period of time? Then you
-probably know how this works. You start with `important.txt` and a
+Ever had to write an important document over an extended period of time? Then
+you probably know how this works. You start with `important.txt` and after a
 couple of weeks you end up with a folder full of files like this:
 
 ```
@@ -77,7 +77,7 @@
 share those with you. Nifty huh? We say that every party has their own copy of
 the project's **repository**. That's not always the case, there are so called
 **centralized version control systems** like `svn` where you only have the most
-recent revision of the project our your machine. To access older ones you need
+recent revision of the project on your machine. To access older ones you need
 to be able to access a server.
 
 Why `darcs`?
@@ -252,7 +252,7 @@
 ```
 
 "But hey! You might now have the same patches but they are in reverse order?
-Doesn't that mean the mine an gimbar's repository are different?", I hear you
+Doesn't that mean that mine and gimbar's repository are different?", I hear you
 say. That's one of the beautiful things about `darcs` and what makes it so
 fundamentally different from other version control systems, even though the
 patches have been applied in reverse order, for `darcs` both of our repositories