From f11cacf513778d44a0061f06f8b653a631b76f29 Mon Sep 17 00:00:00 2001 From: Tony Garnock-Jones Date: Fri, 25 Feb 2022 14:47:27 +0100 Subject: [PATCH] Tweak --- src/operation/scripting.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/src/operation/scripting.md b/src/operation/scripting.md index 56ab1e6..03da25b 100644 --- a/src/operation/scripting.md +++ b/src/operation/scripting.md @@ -108,9 +108,9 @@ compiled and executed in order. NB: to publish a sequence of values, use the `+= *RetargetInstruction* = `$`*var* -The target can be set with a plain variable reference. After compiling such an instruction, the -active target register will contain the variable name *var*. NB: to publish the contents of a -variable, use the `+=` form of *AssertionInstruction*. +The target is set with a variable reference standing alone. After compiling such an +instruction, the active target register will contain the variable name *var*. NB: to publish +the contents of a variable, use the `+=` form of *AssertionInstruction*. ### Publishing an assertion @@ -124,9 +124,8 @@ The most general form of *AssertionInstruction* is "`+= `*ValueExpr*". When eval result of evaluating *ValueExpr* will be published (asserted) at the entity denoted by the active target register. -As a convenient shorthand, the compiler also interprets every plain Preserves record or -dictionary in *Instruction* position as denoting a *ValueExpr* to be used to produce a value to -be asserted. +As a convenient shorthand, the compiler also interprets every Preserves record or dictionary in +*Instruction* position as denoting a *ValueExpr* to be used to produce a value to be asserted. ### Sending a message