summaryrefslogtreecommitdiff
path: root/src/Codec/Pesto/Lint.lhs
diff options
context:
space:
mode:
Diffstat (limited to 'src/Codec/Pesto/Lint.lhs')
-rw-r--r--src/Codec/Pesto/Lint.lhs6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/Codec/Pesto/Lint.lhs b/src/Codec/Pesto/Lint.lhs
index 1cce87c..0d1c848 100644
--- a/src/Codec/Pesto/Lint.lhs
+++ b/src/Codec/Pesto/Lint.lhs
@@ -14,7 +14,7 @@ Linting
> import Codec.Pesto.Parse hiding (test)
Not every graph generated in the previous section is a useful recipe, since
-some combinations of operations just do not make sense. The linting test in
+some combinations of instructions just do not make sense. The linting test in
this section can detect common errors. Failing any of these tests does not
render a recipe invalid, but *useless*. Thus implementations must not create
such recipes. They may be accepted the user though.
@@ -33,7 +33,7 @@ The graph must have exactly one root node (i.e. a node with incoming edges
only) and it must be a result. The result’s object name is the recipe’s title.
This also requires all results and alternatives to be referenced somewhere.
Directives are either consumed when parsing, generating a graph and linting.
-Otherwise they are dangling as well. Unknown operations are always dangling.
+Otherwise they are dangling as well. Unknown instructions are always dangling.
> rootIsResult nodes edges = case walkRoot nodes edges of
> [] -> [LintResult NoRootNode []]
@@ -51,7 +51,7 @@ This recipe’s title is “Pesto”.
> , cmpLint "+foobar >Pesto" []
-Directives and unknown operations are dangling and thus root nodes.
+Directives and unknown instructions are dangling and thus root nodes.
> , cmpLint "invalid %invalid +foo >bar" [LintResult MoreThanOneRootNode [0,1,3]]
> ]