Say in the docs that the RTTY QTC messages are there now

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

docs/unfinished.md

@@ -540,10 +540,16 @@ why it is one message rather than a button per line: the type-ahead buffer holds
 it and paces the engine, and the operator presses one button. This has been
 tested as text — what the message comes out as — and not on the air.
 
+The station taking traffic down has N1MM's messages too — RX Ready, All Agn,
+Agn n and Save, its `WAERXReadyText`, `WAEAllAgnText`, `WAEAGNText` and
+`WAESaveQTCText` — and so has the station reading it out: R U QRV and Save,
+`WAERUQRVText` and `WAESSaveQTCText`. All of them are settings in the window's
+setup area, with N1MM's defaults. Clicking a line in the digital window fills
+the next row, which is how a series is copied on RTTY.
+
 What is not here: N1MM's four SSB recordings — QRV, Agn, Cfm and TU — which need
-a voice keyer, and its RTTY messages for the station taking traffic down, which
-are `WAERXReadyText`, `WAEAllAgnText`, `WAEAGNText` and `WAESaveQTCText`. Those
-four are typed into the digital window's transmit pane here.
+a voice keyer, and the green mark N1MM puts on each line as Send All reads it
+out, which this sends as one message and cannot follow line by line.
 
 **Cut numbers are not sent.** N1MM can key a serial number as letters — `N` for
 9, `T` for 0 — and offers several styles. Nothing here does, in a QTC line or in