diff --git a/examples/fieldtest/rbx_1_float_window_stats.ail b/examples/fieldtest/rbx_1_float_window_stats.ail
index 8845d6b..b96f743 100644
--- a/examples/fieldtest/rbx_1_float_window_stats.ail
+++ b/examples/fieldtest/rbx_1_float_window_stats.ail
@@ -30,12 +30,13 @@
 
 (module rbx_1_float_window_stats
 
-  ; NOTE (field test): the ledger's §Series substrate form writes the
-  ; storage field as `(own (RawBuf a))`. That does NOT parse here — `own`
-  ; in a ctor field position is rejected (surface-parse-error). And the
-  ; bare `(con RawBuf (con Float))` field gives a type-mismatch
-  ; (expected RawBuf<Float>, got raw_buf.RawBuf<Float>). The only form
-  ; that checks is the fully-qualified `raw_buf.RawBuf`. See findings.
+  ; NOTE (field test): a ctor-field storage type carries no mode — the
+  ; `(own (RawBuf a))` form does NOT parse (`own` in a ctor field is a
+  ; surface-parse-error; modes live on fn params/ret only). The element
+  ; type itself is plain type position, so both the kernel-auto-imported
+  ; bare `(con RawBuf (con Float))` and the fully-qualified
+  ; `(con raw_buf.RawBuf (con Float))` check — they denote the same type.
+  ; (The qualified form is kept here as the explicit spelling.)
   (data Window
     (ctor W (con raw_buf.RawBuf (con Float)) (con Int)))