docs: Fix typos in general documentation

1 files changed, 3 insertions, 3 deletions

diff --git a/doc/concepts/built-in-rules.org b/doc/concepts/built-in-rules.org
index 117761fc..9463b10c 100644
--- a/doc/concepts/built-in-rules.org
+++ b/doc/concepts/built-in-rules.org
@@ -77,7 +77,7 @@ map. Any provided information of the dependencies is discarded.
 
 The ~"generic"~ rules allows to define artifacts as the output
 of an action. This is mainly useful for ad-hoc constructions; for
-anything occuring more often, a proper user-defined rule is usually
+anything occurring more often, a proper user-defined rule is usually
 the better choice.
 
 The ~"deps"~ argument is evaluated and has to evaluate to a list
@@ -132,7 +132,7 @@ and artifacts are overlayed in an artifacts-win fashion and
 the union of the resulting stages is taken; it is an error if conflicts
 arise in this way. The resulting stage is transformed into a tree.
 Both, artifacts and runfiles of the ~"tree"~ target are a singleton map
-with the key the result of evaluting ~"name"~ (which has to evalutate to
+with the key the result of evaluating ~"name"~ (which has to evaluate to
 a single string) and value that tree.
 
 
@@ -158,7 +158,7 @@ to the project. In any case, when using non-internal targets as
 dependencies (i.e., targets that a caller of the ~"configure"~
 potentially might use as well), care should be taken that those
 are only used in the initial configuration. Such preservation of
-the configuraiton is necessary to avoid conflicts, if the targets
+the configuration is necessary to avoid conflicts, if the targets
 depended upon are visible in the ~"configure"~ target itself, e.g.,
 as link dependency (which almost always happens when depending on a
 library). Even if a non-internal target depended upon is not visible