Say what happens instead of making files do things

A file is written to; it does not write, score or name anything. Five comments
and doc lines said otherwise, two of them older than today.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RoGtneMQaz4M9w7Kk49AVD

docs/unfinished.md

@@ -137,15 +137,15 @@ What still differs, and why:
   like it was never scored. The rules here follow the class: 5 points for a
   portable station, 2 for one in Region 1 at home and 3 from outside it.
 - **SA 10 and OK/OM DX on SSB** are not written in code at all: both are
-  published as `.udc` files, and the files score the station's logs to the
-  contact. N1MM's OK/OM DX class is the CW running only and says so; the SSB
+  published as `.udc` files, and with those files in the user-defined contests
+  folder the station's logs score to the contact. N1MM's OK/OM DX class is the CW running only and says so; the SSB
   running has different rules and its own pair of files, one for each side of
   the contest.
 - **A `.udc` section multiplier** is counted for any exchange that is not all
-  digits. N1MM checks it against the section list the file names in
-  `MultWindowType`, and those lists are not held here, so a US state sent into
-  an OK/OM DX log counts here and not in N1MM. Three contacts across the two
-  logs.
+  digits. N1MM checks it against the section list given in the file's
+  `MultWindowType` setting, and those lists are not held here, so a US state
+  sent into an OK/OM DX log counts as a multiplier here and not in N1MM. Three
+  contacts across the two logs.
 - **The BARTG Sprint** stores the time of the contact in the exchange column,
   which N1MM fills in by itself. Nothing here fills it in yet, so a log written
   here carries the serial number alone.