diff --git a/docs/adr/ADR-012-esp32-csi-sensor-mesh.md b/docs/adr/ADR-012-esp32-csi-sensor-mesh.md
index 54f41785..1e6debd3 100644
--- a/docs/adr/ADR-012-esp32-csi-sensor-mesh.md
+++ b/docs/adr/ADR-012-esp32-csi-sensor-mesh.md
@@ -166,7 +166,7 @@ typedef struct {
 The aggregator runs on any machine with WiFi/Ethernet to the nodes:
 
 ```rust
-// In wifi-densepose-rs, new module: crates/wifi-densepose-hardware/src/esp32/
+// In v2/, new module: crates/wifi-densepose-hardware/src/esp32/
 pub struct Esp32Aggregator {
     /// UDP socket listening for node streams
     socket: UdpSocket,
diff --git a/docs/adr/ADR-052-tauri-desktop-frontend.md b/docs/adr/ADR-052-tauri-desktop-frontend.md
index 085bae63..f0aad85e 100644
--- a/docs/adr/ADR-052-tauri-desktop-frontend.md
+++ b/docs/adr/ADR-052-tauri-desktop-frontend.md
@@ -29,7 +29,7 @@ There is no single tool that provides a unified view of the entire deployment 
 
 A browser-based UI cannot access serial ports (for flashing), raw UDP sockets (for node discovery), or the local filesystem (for firmware binaries). A desktop application is required for hardware management. Tauri v2 is the natural choice because:
 
-1. **Rust backend** — integrates directly with the existing Rust workspace (`wifi-densepose-rs`). Crates like `wifi-densepose-hardware` (serial port parsing), `wifi-densepose-config`, and `wifi-densepose-sensing-server` can be linked as library dependencies.
+1. **Rust backend** — integrates directly with the existing Rust workspace (`v2/`). Crates like `wifi-densepose-hardware` (serial port parsing), `wifi-densepose-config`, and `wifi-densepose-sensing-server` can be linked as library dependencies.
 2. **Small binary** — Tauri bundles the system webview rather than shipping Chromium (~150 MB savings vs Electron).
 3. **Cross-platform** — Windows, macOS, Linux from the same codebase.
 4. **Security model** — Tauri's capability-based permissions system restricts frontend access to explicitly allowed Rust commands.