Drop the chatty asides Sentences addressing the reader's likely mistakes, telling them what they usually want, or what to reach for. "This is the part that catches people", "that is usually what you want", "the one to reach for", "the first thing to check". Documentation states what the thing does. Eighteen sentences across nine pages, prose only. No table, example or claim changed; the generated blocks are untouched and every example still runs.
Templates and Aliases, and point the pages that needed it at it The wire language has template and alias verbs sitting beside new/set/ destroy, and nothing on the wiki mentioned them. Worse, ListView and ComboBox taught a workaround for a problem templates solve. A template's children are applied before any instance's properties, so template Sizes=listview children={...three items...} lv=new Sizes selected=2 selects the third row, while the same properties in one statement out of order silently select the first. ListView and ComboBox now lead with that and keep the manual ordering rule as the single-statement case. Panel gains a FormRow example, since a layout built more than once is what templates are for. The new page covers what running the code showed: instance properties override the template's, templates chain with the more specific winning, template children come first and instance children are appended to them, and keys inside a template body are namespaced under the instance key and surfaced with key=path. Also the D18 naming rule and every rejection it produces, each one run rather than assumed. Two examples were wrong before this landed. font_size=20 came from a session test that uses a mock factory accepting any property; against the real registry a button has no font_size, so a reader pasting it would get an error. And the appended-children example omitted its own template declaration. Both found by executing the examples rather than parsing them -- parsing had passed.