 "When quotations take named parameters using " { $link POSTPONE: [| } ", " { $link curry } " fills in the variable bindings from right to left. The following two snippets are equivalent:"
 { $code "3 [| a b | a b - ] curry" }
 { $code "[| a | a 3 - ]" }
-"Because of this, the behavior of " { $snippet "fry" } " changes when applied to such a quotation to ensure that fry conceptually behaves the same as with normal quotations, placing the fried values “underneath” the local variable bindings. Thus, the following snippets are no longer equivalent:"
+"Because of this, the behavior of " { $snippet "fry" } " changes when applied to such a quotation to ensure that fry conceptually behaves the same as with normal quotations, placing the fried values “underneath” the variable bindings. Thus, the following snippets are no longer equivalent:"
 { $code "'[ [| a | _ a - ] ]" }
 { $code "'[ [| a | a - ] curry ] call" }
 "Instead, the first line above expands into something like the following:"

"""2.0
-3.0"""
}
"If you wanted to perform the quadratic formula interactively from the listener, you could use " { $link POSTPONE: [let } " to provide a scope for the local variables:"
{ $example """USING: locals math math.functions kernel ;
IN: scratchpad
[let 1.0 :> a 1.0 :> b -6.0 :> c

    "locals-word-test locals-word-test eq? ."
    "t"
}
"However, literals with lexical variables in them actually construct a new object:"
{ $example
    "USING: locals splitting ;"
    "IN: scratchpad"
