diff --git a/RELEASE-NOTES-5.1.0b_RC1.html b/RELEASE-NOTES-5.1.0b_RC1.html
index ede008a4..f8c16e58 100644
--- a/RELEASE-NOTES-5.1.0b_RC1.html
+++ b/RELEASE-NOTES-5.1.0b_RC1.html
@@ -56,7 +56,7 @@ If you see it, run <code>set-appcompat.bat</code> and restart the game.</p>
 <hr>
 <h2>2. Multiplayer</h2>
 <h3>16 pilots plus a cameraship now launch correctly</h3>
-<p>Previously, a full 16-pilot game with a cameraship connected would silently fail to launch ?
+<p>Previously, a full 16-pilot game with a cameraship connected would silently fail to launch --
 you pressed launch and nothing happened, with no error. Fixed. A cameraship no longer consumes
 one of the 16 pilot slots.</p>
 <p><strong>No configuration needed.</strong> This applies automatically.</p>
@@ -117,10 +117,14 @@ the zero point could be skipped.</p>
 speed without changing anything else about how the board talks to the game:</p>
 <pre><code>MW4.exe -tbaud 115200
 </code></pre>
-<p>Accepts 9600 to 921600. <strong>Leave it off</strong> and the game uses the original speed, exactly as before ?
+<p>Accepts 9600 to 921600. <strong>Leave it off</strong> and the game uses the original speed, exactly as before --
 existing original RIO boards need no change and should not use this switch.</p>
-<p>This is only the speed. The wire protocol is untouched. (The separate <code>-trio 1</code> switch changes
-the whole protocol and is <em>not</em> what you want for a replica board.)</p>
+<p><strong>Whether a particular rate actually works is a hardware question, not a software one.</strong> The
+game will happily set any rate in that range, but both ends have to support it: the serial
+UART in the pod PC, and the RIO or replica RIO board itself. If a rate misbehaves -- garbled
+input, dropped buttons, no response -- step down to a lower one.</p>
+<p>This switch only changes the speed. The wire protocol is untouched. (The separate <code>-trio 1</code>
+switch changes the whole protocol and is <em>not</em> what you want for a replica board.)</p>
 <hr>
 <h2>4. Displays and MFDs</h2>
 <h3>Split MFD mode -- two separate 640x480 MFD monitors</h3>
@@ -255,7 +259,7 @@ so you can also edit it directly.</p>
 external <strong>MySQL</strong> database after each print job, for league tables or long-term stats.</p>
 <p>Configure via <strong>File -&gt; Database Settings (Ctrl+D)</strong>, or the <code>[MySQLExport]</code> section of
 <code>mw4print.ini</code>. The table layout is documented in <code>db_schema.sql</code>.</p>
-<div class="note"><p>?? <strong>This feature has not yet been tested against a live database server.</strong> It is off unless you
+<div class="warn"><p><strong>WARNING: this feature has not yet been tested against a live database server.</strong> It is off unless you
 configure it, and printing works normally without it. If you try it, please report back.</p></div>
 <hr>
 <h2>8. Quality of life</h2>
@@ -324,7 +328,9 @@ start. Previously such failures were completely silent. Include this file with a
 <ul>
 <li><strong>Every MFD mode requires dgVoodoo2 on Windows 10/11</strong> -- the spanned modes (<code>-tmfds 1</code>
   and <code>-tmfds 3</code>) just as much as the split mode (<code>-tmfds 4</code>) -- with scaling set to
-  <code>Stretched, Keep Aspect Ratio</code>. This is a Windows limitation, not a bug we can fix.</li>
+  <code>Stretched, Keep Aspect Ratio</code>. dgVoodoo2 works around a limitation on exclusive
+  full-screen use of multiple displays on platforms after Windows XP. It may be possible
+  to fix this in a future release.</li>
 <li><strong>The MySQL export in mw4print has not been tested against a live server.</strong></li>
 <li><strong>The game renders in 4:3 only.</strong> There is no widescreen mode. On 16:9 monitors, use
   keep-aspect scaling for correct geometry with black bars at the sides.</li>
diff --git a/RELEASE-NOTES-5.1.0b_RC1.md b/RELEASE-NOTES-5.1.0b_RC1.md
index 95644b4d..091955c0 100644
--- a/RELEASE-NOTES-5.1.0b_RC1.md
+++ b/RELEASE-NOTES-5.1.0b_RC1.md
@@ -41,7 +41,7 @@ If you see it, run `set-appcompat.bat` and restart the game.
 
 ### 16 pilots plus a cameraship now launch correctly
 
-Previously, a full 16-pilot game with a cameraship connected would silently fail to launch ?
+Previously, a full 16-pilot game with a cameraship connected would silently fail to launch --
 you pressed launch and nothing happened, with no error. Fixed. A cameraship no longer consumes
 one of the 16 pilot slots.
 
@@ -110,11 +110,16 @@ speed without changing anything else about how the board talks to the game:
 MW4.exe -tbaud 115200
 ```
 
-Accepts 9600 to 921600. **Leave it off** and the game uses the original speed, exactly as before ?
+Accepts 9600 to 921600. **Leave it off** and the game uses the original speed, exactly as before --
 existing original RIO boards need no change and should not use this switch.
 
-This is only the speed. The wire protocol is untouched. (The separate `-trio 1` switch changes
-the whole protocol and is *not* what you want for a replica board.)
+**Whether a particular rate actually works is a hardware question, not a software one.** The
+game will happily set any rate in that range, but both ends have to support it: the serial
+UART in the pod PC, and the RIO or replica RIO board itself. If a rate misbehaves -- garbled
+input, dropped buttons, no response -- step down to a lower one.
+
+This switch only changes the speed. The wire protocol is untouched. (The separate `-trio 1`
+switch changes the whole protocol and is *not* what you want for a replica board.)
 
 ---
 
@@ -295,7 +300,7 @@ external **MySQL** database after each print job, for league tables or long-term
 Configure via **File -> Database Settings (Ctrl+D)**, or the `[MySQLExport]` section of
 `mw4print.ini`. The table layout is documented in `db_schema.sql`.
 
-> ?? **This feature has not yet been tested against a live database server.** It is off unless you
+> **WARNING: this feature has not yet been tested against a live database server.** It is off unless you
 > configure it, and printing works normally without it. If you try it, please report back.
 
 ---
@@ -349,7 +354,9 @@ start. Previously such failures were completely silent. Include this file with a
 
 - **Every MFD mode requires dgVoodoo2 on Windows 10/11** -- the spanned modes (`-tmfds 1`
   and `-tmfds 3`) just as much as the split mode (`-tmfds 4`) -- with scaling set to
-  `Stretched, Keep Aspect Ratio`. This is a Windows limitation, not a bug we can fix.
+  `Stretched, Keep Aspect Ratio`. dgVoodoo2 works around a limitation on exclusive
+  full-screen use of multiple displays on platforms after Windows XP. It may be possible
+  to fix this in a future release.
 - **The MySQL export in mw4print has not been tested against a live server.**
 - **The game renders in 4:3 only.** There is no widescreen mode. On 16:9 monitors, use
   keep-aspect scaling for correct geometry with black bars at the sides.