Answer prose round 2: one wording for what a binding binds, the calc exception scoped in the decision, and rewrapped lines

2026-10-05 10:05:14 +02:00
parent f89ffd1b73
commit bf81c38315
5 changed files with 18 additions and 17 deletions
@@ -16,9 +16,9 @@ replacement, and each removed path, column or flag.
  `{w} {uppercase(w)}` and `{/person.first} {/person.last}` are two draws each, which
  `{p as q}{q.a} {q.b}` and `{/person as n}{n.first} {n.last}` make one.
  `{/misc.territory as t}` binds one row of `misc.territory` to `t` and prints nothing;
-  `{t}`, `{t.capital}` and `{lowercase(t.name)}` read that one row. A name binds a
-  reference, a sibling field or a path into one, lives in the category binding it, and
-  picks again on every iteration of a `repeat` binding it. A struct's tags share its
+  `{t}`, `{t.capital}` and `{lowercase(t.name)}` read that one row. `{x as n}` binds a
+  reference, a sibling field or a path into one; a name lives in the category binding it,
+  and picks again on every iteration of a `repeat` binding it. A struct's tags share its
  names, `{/sv_SE.person as p}{p.first}` beside `{p.sex}`. A name is a `{calc()}`
  operand: `{/misc.coordinate.lat as lat}{calc(lat * 60)}`. What `New` refuses is listed
  under [Names](README.md#names).