Lay the buttons out the way N1MM lays them out

The twelve function keys were one row of twelve at the bottom of the window,
with the action row under them. N1MM puts both between the entry boxes and the
bearing line, six keys to a row in two rows, each row filling the width.

The action row takes N1MM's widths as well: 23 per cent to the first button and
the rest shared out. N1MM gives the remaining seven 11 per cent each; there are
five here, because Mark and Store are missing, so they share the same 77.

Looked at under Xvfb against the N1MM screenshot: same two rows of six, same
action row under them, same order down the window.

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

README.md

@@ -206,9 +206,17 @@ the right one red while something is going out on the air.
 
 ### The buttons and the title bar
 
-Under the function keys is the row N1MM has: Esc: Stop, Wipe, Log It, Edit,
-Spot It and QRZ, each doing what its key does. QRZ opens the callsign's page in
-a browser. N1MM's Mark and Store are not there, because call stacking is not.
+The twelve function keys sit in two rows of six, with the row of actions under
+them, between the entry boxes and the bearing line, which is where N1MM puts
+them. Each row fills the width, and the first button of the action row takes the
+23 per cent N1MM gives it.
+
+The action row is N1MM's: Esc: Stop, Wipe, Log It, Edit, Spot It and QRZ, each
+doing what its key does. QRZ opens the callsign's page in a browser.
+
+N1MM's other two buttons are not there. Mark puts a `Busy@` marker on your own
+bandmap at the frequency you are on, which needs a bandmap entry that is not a
+station. Store is call stacking, which is not here either.
 
 The title bar says what N1MM's says: the frequency, the mode, whether the
 frequency came from a radio or was typed, and which radio the window belongs to