Give the datatype item the reason that holds, and rewrap a line

README.md

@@ -176,8 +176,9 @@ than selected in.
 `misc.httpmethod` is the nine methods the HTTP core specification defines; the
 register's other entries, WebDAV and DeltaV among them, do not ship. Its `safe` and
 `idempotent` are `true` or `false`, so a Go `bool` reads them, though `--format json`
-and `sql` write them as text, a table column carrying no datatype. `misc.protocol` carries a `number` and a `name`,
-the keyword itself where the register spells none out, and selects by either spelling.
+and `sql` write them as text, a table column carrying no datatype. `misc.protocol`
+carries a `number` and a `name`, the keyword itself where the register spells none out,
+and selects by either spelling.
 `misc.port` is the TCP assignments, rendering the number a port field holds with the
 IANA `service` beside it, and selecting by number alone. A draw spans the whole
 register, so pin `misc.port[443]` where a fixture needs a port a reader recognises;

todo.md

@@ -112,7 +112,8 @@ by a `data-import/` script, as README goal 10 asks.
 - Let a table column carry a `datatype`, so `--format json` writes
   `"safe": true` and `--format sql` a boolean rather than the text `'true'`. Today only
   a JSON field takes one, so `misc.httpmethod`'s booleans are typed in Go and text
-  everywhere else. It reserves a field name, so it is a fence and a major.
+  everywhere else. Typing a shipped column changes what `json` and `sql` write, so the
+  capability is a minor and applying it to `misc.httpmethod` is a major.
 
 ### Open questions to settle