README: corrections from review

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

README.md

@@ -1,16 +1,16 @@
 # Red Planet 4.12 — the Steamification
 
 **Red Planet** is VWE's pod-racing game: eight-player VTV races on Mars,
-originally played from inside full-motion cockpit pods. This repo is the
+originally played from inside VWE Tesla cockpit pods. This repo is the
 third life of that code:
 
 | Generation | What it was |
 |------------|-------------|
 | **Red Planet 4.10** | The original game, running on the **Tesla 1** pod platform (DOS-era MUNGA engine, serial RIO cockpit hardware, operator console, batch-file relaunch between missions) |
-| **Red Planet 4.11** | The **Win32 port** of 4.10 ([RP411](https://gitea.mysticmachines.com/VWE/RP411.git)) — DirectX 9, WinSock TCP, TeslaConsole/TeslaLauncher session control; still arcade pods, still a LAN |
+| **Red Planet 4.11** | The **Win32 port** of 4.10 ([RP411](https://gitea.mysticmachines.com/VWE/RP411.git)) — DirectX 9, WinSock TCP, TeslaConsole/TeslaLauncher session control; still runs in pods, still a LAN |
-| **Red Planet 4.12** | **This repo: the Steamification of 4.11** — the same engine, the same wire protocol, the same missions, made sellable on Steam and playable over the internet with no cockpit hardware |
+| **Red Planet 4.12** | **This repo: the Steamification of 4.11** — the same engine, the same wire protocol, the same missions, made distributable on Steam and playable over the internet with no cockpit hardware |
 
-The architecture is deliberately conservative: the arcade's design survives
+The architecture is deliberately conservative: the VWE's design survives
 intact, with each pod-era dependency replaced by a consumer equivalent
 behind the engine's existing seams.
 
@@ -19,13 +19,13 @@ behind the engine's existing seams.
 | RIO cockpit board (serial) | **PadRIO** — virtual RIO from XInput pad + keyboard, fully rebindable (`bindings.txt`, vRIO profile format) |
 | Seven physical displays | **Single-window cockpit** — all displays composed on a locked 1920×1080 canvas around the viewscreen, with the real button banks lamp-lit and clickable |
 | Pod button lamps | On-screen lamps, plus an **RGB keyboard mirror** (Windows Dynamic Lighting) |
-| TeslaConsole operator | **In-game front end** — race setup menu builds the mission egg locally; an in-process console marshals every race (missions still only end on a console stop, exactly as designed in 1995) |
+| TeslaConsole operator | **In-game front end** — race setup menu builds the mission egg locally; an in-process console marshals every race (missions still only end on a console stop, exactly as designed in 1994) |
 | TeslaLauncher relaunch-per-mission | **Single binary** — menu → race → results → menu in one process |
 | WinSock TCP LAN mesh | **NetTransport seam** — the deterministic pod mesh unchanged, running over plain TCP (LAN/dev) or **Steam Networking Sockets** (FakeIP + Steam Datagram Relay) |
 | Site network / fixed IPs | **Steam lobbies** — lobby owner is the console; members exchange FakeIPs and loadouts as lobby data |
 
 **Status: it works.** Release
-[v4.12.1](https://gitea.mysticmachines.com/VWE/RP412/releases/tag/v4.12.1)
+[v4.12.2](https://gitea.mysticmachines.com/VWE/RP412/releases/tag/v4.12.2)
 carries the first verified end-to-end internet build: three machines, three
 Steam accounts, lobby → mesh → marshaled five-minute race → deaths and
 respawns → timed stop → results on every machine → rematch from the same