docs(cctv): tighten the Bosch MIC record notes

DATA_SOURCES.md

@@ -256,12 +256,12 @@ The CCTV layer's hardware-model specs are a small extract (v2.26.0, plus the Bos
 records from v2.29.0) of the
 [CCTV Camera Database](https://github.com/ch-bas/cctv-camera-database), an open dataset of
 camera models transcribed from manufacturer datasheets, dedicated to the public domain under
-**CC0-1.0**. Only the records for hardware named by the integrated public catalogs (King
-County, Sarasota County and Sioux Falls), plus the City of Amsterdam register proposed
-in [#251](https://github.com/bilawalsidhu/gods-eye-view/pull/251), are bundled, compiled into the module. Nothing is
-fetched at runtime. The MIC specification fields are unchanged; product titles are shortened
-to model codes and colour aliases are added locally. The records describe camera products (optics, resolution, night vision)
-only, never endpoints, stream paths or access data. CC0 requires no attribution; the CCTV HUD
+**CC0-1.0**. Only records for hardware named by the integrated public catalogs (King County,
+Sarasota County and Sioux Falls) or by the City of Amsterdam register proposed in
+[#251](https://github.com/bilawalsidhu/gods-eye-view/pull/251) are bundled, compiled into the
+module. Nothing is fetched at runtime. The MIC records keep their specification fields; their
+titles are shortened to model codes and colour aliases are added. The records describe camera
+products (optics, resolution, night vision) only, never endpoints, stream paths or access data. CC0 requires no attribution; the CCTV HUD
 credits it anyway as `SPECS: CCTV-DATABASE.COM` beside any spec line it renders.
 
 ### Bundled OpenStreetMap data

docs/CURRENT-STATE.md

@@ -5160,10 +5160,10 @@ silently demoting every later lookup for the session.
   multi-sensor datasheets publish a capability range, not the lens's current zoom, so those
   cameras keep their estimate and show `SPEC FOV min–max° (CAPABILITY)` beside it. Public
   camera state carries `fovSource`, `specFovMinDeg`, `specFovMaxDeg` and `spec` (#452).
-  The table also includes Bosch MIC-7130, MIC-7502 and MIC-7522 records for the Amsterdam
-  register proposed in #251, including its `x` colour aliases (#1319). Their axis-less
-  datasheet FOV does not supply a horizontal capability range or replace the estimated
-  FOV. Adding these records does not enable the proposed source pack.
+  The table also has Bosch MIC-7130, MIC-7502 and MIC-7522 records for the Amsterdam
+  register proposed in #251, with its `x` colour aliases (#1319). Their datasheet FOV names
+  no axis, so it neither gives a capability range nor replaces the estimate. The records
+  alone do not enable that source pack.
 - **FIRMS**: no ground clamping (zero 3D-tiles height sampling), ≤18 screen-decluttered ambient labels, click-to-inspect detail card, 2.5k/3k sprite budgets viewport-clipped by FRP. Fire-power labels share display rounding before localization: one decimal below the rounded 10 MW boundary, then whole megawatts (for example, 9.96 MW reads 10 MW).
 - **CCTV v2 foundation:** a pitched
   frustum wireframe (4 corner rays + far-cap rectangle) with a monitor plane at the frustum's

src/layers/cctv/modelSpecs.js

@@ -27,14 +27,12 @@
  */
 
 /**
- * Records from the dataset's model-enrichment extract (v2.26.0; the Bosch MIC
- * records from v2.29.0). MIC specification fields are unchanged; product
- * titles are shortened to model codes and colour aliases are added locally.
- * Bosch MIC order codes end in a colour letter (B black, G grey, W white)
- * on one shared datasheet; those siblings,
- * and the `x` wildcard registries write for the colour letter, are listed as
- * aliases of the one vendored record. Its `model` leaves the colour out, so
- * the HUD never names a variant the source did not.
+ * Records from the dataset's model-enrichment extract: v2.26.0, plus the Bosch
+ * MIC records from v2.29.0 with titles shortened to model codes.
+ * A Bosch MIC order code ends in a colour letter (B, G, W; registries write
+ * `x`) on one shared datasheet. The colours are aliases of one record whose
+ * `model` leaves the letter out, so the HUD never names a variant the source
+ * did not.
  */
 const RECORDS = [
   {