summaryrefslogtreecommitdiff
path: root/doc/concepts/cache-pragma.org
diff options
context:
space:
mode:
Diffstat (limited to 'doc/concepts/cache-pragma.org')
-rw-r--r--doc/concepts/cache-pragma.org4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/concepts/cache-pragma.org b/doc/concepts/cache-pragma.org
index 3d445257..11953702 100644
--- a/doc/concepts/cache-pragma.org
+++ b/doc/concepts/cache-pragma.org
@@ -49,7 +49,7 @@ To make everybody aware of their special nature, they are clearly
marked as such: tainted targets not generated by a tainted rule (e.g.,
a test rule) have to explicitly state their taintedness in their
attributes. This declaration also gives a natural way to mark targets
-that are techincally pure, but still should be used only in test,
+that are technically pure, but still should be used only in test,
e.g., a mock version of a larger library.
Besides being for tests only, there might be other reasons why a
@@ -79,7 +79,7 @@ report the set of strings the target is tainted with.
*** ~"may_fail"~ and ~"no_cache"~ properties of ~"ACTION"~
-The ~"ACTION"~ function in the definining expression of a rule
+The ~"ACTION"~ function in the defining expression of a rule
have two additional (besides inputs, etc) parameters ~"may_fail"~
and ~"no_cache"~. Those are not evaluated and have to be lists
of strings (with empty assumed if the respective parameter is not