Answer stability round 1 and product-owner round 1: the Swedish address paragraph warns of a street under a neighbouring postort, the street row names the centre point, phone-exchange's rule gets its own sentence, and a level is a path prefix

README.md

@@ -162,8 +162,7 @@ Each locale carries `address`, `color`, `company`, `date`, `email`, `first-name`
 `ip`, `last-name`, `person`, `phone`, `price`, `sentence`, `sex`, `time`, `url`,
 `username`, `version` and `word`, formatted per locale; `sv_SE` adds `personnummer`
 and `samordningsnummer`, `en_US` adds `ssn`, `itin` and `phone-exchange` (the three
-digits after the area code, drawn evenly from the codes NANPA may assign: `200` to `999`,
-except `211`, `311` … `911`, `555`, `950`, `958`, `959` and `976`). `misc` carries `car`, `coordinate`, `creditcard`
+digits after the area code). `misc` carries `car`, `coordinate`, `creditcard`
 (Luhn-valid), `currency` (ISO 4217), `datetime` (RFC 3339), `emoji`, `httpmethod`,
 `httpstatus`, `language` (ISO 639-1, with its 639-2/T code), `loglevel` (syslog
 severity), `mac`, `mimetype`, `objectid`, `port`, `protocol`, `territory` (ISO
@@ -174,6 +173,9 @@ carry sub-fields — `misc.currency.symbol`, `misc.territory.alpha2`,
 `timezone`, `tld` and `useragent` are [tables](#table), so
 `misc.territory[SE].capital` and `misc.currency[Euro].symbol` select a row; `car` and
 `useragent` carry no key or name, so they are drawn from rather than selected in.
+`en_US.phone` draws its exchange from `en_US.phone-exchange`, which draws evenly from the
+codes NANPA may assign: `200` to `999`, except `211`, `311` … `911`, `555`, `950`, `958`,
+`959` and `976`.
 
 Where a script under [`data-import/`](data-import) reads a source, the facts come from
 that source, and the script drops a row only by a rule it states; elsewhere a small hand-written
@@ -261,7 +263,9 @@ one has no use for, and `sv_SE.title` has no `parent`, so it is selected as
 A `geo` folder holds one tree per country under its alpha-2 code: five
 [linked tables](#linked-tables) named alike, and an `address` record binding one locality
 and drawing its street and postal code inside it. The locale's `address` prints that
-record, and each of its columns describes the address printed.
+record, and each of its columns describes the address printed. Do not expect a check that a
+Swedish street lies in its postort to pass: a street may sit under a neighbouring postort,
+as the `street` row below says.
 
 | Table | `geo.SE` | `geo.US` | Weight |
 |-------|----------|----------|--------|
@@ -269,7 +273,7 @@ record, and each of its columns describes the address printed.
 | `municipality` | kommun, by code or name | county, by FIPS code or name | population |
 | `locality` | postort, by name; [`geo-se.py`](data-import/geo-se.py)'s `localities` picks which ship | incorporated place of 25,000 people or more with a postal code of its own, by GEOID or name; Hawaii has none | tätort population, the kommun's where the postort names it, else 200; place population |
 | `postal-code` | postnummer with street delivery, by code | ZCTA, by code | one; address ranges |
-| `street` | gatunamn, the ten with most road segments per postort, each segment counted toward the postort of the nearest postal code, so a street near a border may sit under the neighbouring postort | street name, the ten with most address ranges per place | segments; address ranges |
+| `street` | gatunamn, the ten with most road segments per postort, each segment counted toward the shipped postort whose postal code's centre point is nearest | street name, the ten with most address ranges per place | segments; address ranges |
 
 `geo.SE.region[Skåne län].municipality` draws a kommun in Skåne,
 `geo.SE.locality[Lund].street` a street in Lund, and