aboutsummaryrefslogtreecommitdiff
path: root/chapters/pseudocode.adoc
diff options
context:
space:
mode:
authorEric Kunze <eric.kunze@arm.com>2021-12-13 15:40:04 -0800
committerEric Kunze <eric.kunze@arm.com>2022-01-07 14:28:31 -0800
commita3eded0843874a78e69e4b985cb2a492bfab78f3 (patch)
tree18a71120e14ff64cf2acbe4463dea78cff910c5a /chapters/pseudocode.adoc
parentf734f1b1c81d401f7e1891c763824038501b4969 (diff)
downloadspecification-a3eded0843874a78e69e4b985cb2a492bfab78f3.tar.gz
Add rudimentary spell check for specification
We can't easily spell check the entire specification, the pseudocode and operator tables make it unworkable. This adds a simple python script that tries to extract just the description of the operators for checking. It also does a check over the entire license. A custom dictionary is used to contain specification custom words. Change-Id: I74558c03af1506e2970f20b3246d920c2753ca44 Signed-off-by: Eric Kunze <eric.kunze@arm.com>
Diffstat (limited to 'chapters/pseudocode.adoc')
-rw-r--r--chapters/pseudocode.adoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/chapters/pseudocode.adoc b/chapters/pseudocode.adoc
index d5f05db..71cc14d 100644
--- a/chapters/pseudocode.adoc
+++ b/chapters/pseudocode.adoc
@@ -27,8 +27,8 @@ This condition is captured in the ERROR_IF function.
*Implementation Notes*
-* An implementation is not required to detect unpredictable behaviour. If tosa_execute_graph() returns tosa_unpredictable then the tosa_test_compliance() function does not require any specific output from an implementation.
-* An implementation is required to detect errors in a graph that does not have unpredictable behaviour (see tosa_test_compliance).
+* An implementation is not required to detect unpredictable behavior. If tosa_execute_graph() returns tosa_unpredictable then the tosa_test_compliance() function does not require any specific output from an implementation.
+* An implementation is required to detect errors in a graph that does not have unpredictable behavior (see tosa_test_compliance).
* An acceptable implementation is to stop and report an error on the first ERROR_IF condition that occurs. This satifies tosa_test_compliance() even if the tosa_execute_graph() was tosa_unpredictable.
* If the tosa_execute_graphs() result is tosa_unpredictable or tosa_error, then there is no requirement on the implementation to execute any portion of the TOSA graph.