1 files changed, 8 insertions, 8 deletions

diff --git a/debug/risc-v-gsp-rm-vm/rmharness/README.md b/debug/risc-v-gsp-rm-vm/rmharness/README.md
index 6d33138..9481708 100644
--- a/debug/risc-v-gsp-rm-vm/rmharness/README.md
+++ b/debug/risc-v-gsp-rm-vm/rmharness/README.md
@@ -1,7 +1,7 @@
-# rmharness - host RM oracle integration for green-eye
+# rmharness - host RM oracle integration for risc-v-gsp-rm-debugger
 
 `rmharness` wires the Open-IOV host RM userspace tools (`rmtool`, `rmtop`,
-`rmq`) into the green-eye workflow so host ground truth can be captured next
+`rmq`) into the risc-v-gsp-rm-debugger workflow so host ground truth can be captured next
 to simulator sessions and compared later (docs/06-ACCURACY.md M1/M6).
 
 All three tools are **read-only**: they query the host RM through
@@ -29,7 +29,7 @@ rmharness/
                         fake-`ge` plugin import/registration check
 ```
 
-The green-eye plugin lives next to the other bundled plugins:
+The risc-v-gsp-rm-debugger plugin lives next to the other bundled plugins:
 `plugins/rmharness_plugin.py` (REPL commands `rmtool`, `rmtop`, `rmq`).
 
 ## Build and smoke
@@ -58,7 +58,7 @@ controls. They do not disturb a running CUDA job. If the driver is not bound
 they fail cleanly. Commands that would allocate or mutate anything are refused
 by the tools themselves.
 
-## Capturing into a green-eye session
+## Capturing into a risc-v-gsp-rm-debugger session
 
 ```bash
 cd debug/risc-v-gsp-rm-vm
@@ -88,10 +88,10 @@ created. The event `t` field is `0.0` for externally recorded runs; use
 and record the output through the live recorder:
 
 ```
-greeneye> rmtool gpu list
-greeneye> rmtool mem stats --format=json
-greeneye> rmtop --once
-greeneye> rmq
+risc-v-gsp-rm-debugger> rmtool gpu list
+risc-v-gsp-rm-debugger> rmtool mem stats --format=json
+risc-v-gsp-rm-debugger> rmtop --once
+risc-v-gsp-rm-debugger> rmq
 ```
 
 Arguments naming write operations (`alloc`, `map`, `pin`, `start`, ...) are