Name a port apart from its message in the node panel, two lines per port

The port name follows the message until it is typed by hand, and clearing
it follows again. The second line holds the message, so a list port's item
type no longer squeezes the name.

docs/reference/node-types.md

@@ -321,10 +321,10 @@ that is not wired to the node.
   `heat`, `boost` for heating; `media`, `music`, `tv`; `shutter`, `blind`,
   `cover`; `water`, `watering`, `sprinkler`
 
-A port naming anything else is refused when the flow is built. The editor
-names a port after its message, so there a target's message carries the name;
-binding a port to a message named otherwise, as `{"name": "setpoint", "port":
-"living_room_setpoint"}`, takes the flow API.
+A port naming anything else is refused when the flow is built. A port is
+named after its message unless it is given a name of its own, in the node
+panel's port name field or as `{"name": "setpoint", "port":
+"living_room_setpoint"}` through the flow API.
 
 Targets of one area and kind are one device to the model, and each takes what
 a call means for its type. A target's current value is the state the model