Documentation: fix some typos

2 files changed, 4 insertions, 4 deletions

diff --git a/doc/concepts/overview.md b/doc/concepts/overview.md
index 18552f87..79dc301f 100644
--- a/doc/concepts/overview.md
+++ b/doc/concepts/overview.md
@@ -21,7 +21,7 @@ actual library file and its public headers) as well as information on
 how to use the target (linking arguments, transitive header files, etc).
 For a consumer of a target, the definition of this collection of files
 as well as the additionally provided information is what defines the
-target as a dependency, respectively of where the target is coming from
+target as a dependency, irrespectively of where the target is coming from
 (i.e., targets coinciding here are indistinguishable for other targets).
 
 Of course, to actually build a single target from its dependencies, many
@@ -78,8 +78,8 @@ Repository data
 
 A repository uses a (logical) directory for several purposes: to obtain
 source files, to read definitions of targets, to read rules, and to read
-expressions that can be used by rules. While all those directories can
-(and often are) be the same, this does not have to be the case. For each
+expressions that can be used by rules. While all those directories can be
+(and often are) the same, this does not have to be the case. For each
 of those purposes, a different logical directory (also called "root")
 can be used. In this way, one can, e.g., add target definitions to a
 source tree originally written for a different build tool without
diff --git a/doc/tutorial/computed.md b/doc/tutorial/computed.md
index f746236d..96e27dbe 100644
--- a/doc/tutorial/computed.md
+++ b/doc/tutorial/computed.md
@@ -310,7 +310,7 @@ $ touch src/baz/baz.cpp
 $ echo 'bar' > src/baz/deps
 ```
 
-As this affects the target structure with commit those changes.
+As this affects the target structure, we commit those changes.
 
 ```shell
 $ git add . && git commit -m 'New library baz'