diff --git a/docs/deployment.md b/docs/deployment.md
index 1d50696..b98c69f 100644
--- a/docs/deployment.md
+++ b/docs/deployment.md
@@ -1,9 +1,15 @@
 # Deploying to the Gimbal LattePanda
 
-Step-by-step guide to deploy `fire_gimbal_control` on a tower's LattePanda Sigma (Linux x86-64). Like the
+Step-by-step guide to deploy `fire_gimbal_control` on a tower's LattePanda (Linux x86-64). Like the
 firmware workflow, this is a repeatable **build → install → configure → enable → verify** cycle; the
 [Update / redeploy](#9-update--redeploy) section at the end is the short loop you run for every new version.
 
+> **Which LattePanda.** The deployed fleet is the **3 Delta** — read from tower 111's DMI
+> `product_name`, *not* the Sigma, which this page claimed until 2026-09-18. Tower 121 is a
+> **LattePanda IOTA**; see [lattepanda-iota.md](lattepanda-iota.md) and its setup kit under
+> `hardware/lattepanda-iota/`. Nothing in this guide is board-specific — it is x86-64 Linux either way —
+> so the distinction matters for the device paths in `hardware.ini`, not for these steps.
+>
 > Assumes a Debian/Ubuntu-based Linux on the LattePanda. For Arch/Manjaro swap `apt` for `pacman`
 > (see [build-and-setup.md](build-and-setup.md)). Run as a normal user with `sudo` rights; the service runs
 > under a dedicated `ggs` user.
diff --git a/docs/hardware-porting-plan.md b/docs/hardware-porting-plan.md
index 1928a52..040d630 100644
--- a/docs/hardware-porting-plan.md
+++ b/docs/hardware-porting-plan.md
@@ -31,7 +31,7 @@ Device bindings in the live `config.ini`:
 | Modem | `/dev/ttyUSB0-3` | USB `2c7c:0801` Quectel RM520N-GL, **M.2 B-key** |
 | Extra NIC | — | USB `0b95:1790` ASIX AX88179 GbE |
 
-> **Doc bug:** `docs/deployment.md:3` says "LattePanda Sigma". It is a 3 Delta. Fix as part of this work.
+> **Doc bug — FIXED 2026-09-18.** `docs/deployment.md` said "LattePanda Sigma"; it is a 3 Delta. The page now names both boards the fleet actually runs (3 Delta on 111, IOTA on 121) and notes that nothing in that guide is board-specific — the distinction belongs to `hardware.ini`, not to the deploy steps.
 
 ---