renaming run-efi to run-x86-64

docs/README.md

@@ -87,5 +87,5 @@ behind the [arch](arch.md) boundary, and when idle, or on a panic, it **halts**
 | Framebuffer text console (mirrors to serial) | `src/console.zig` |
 | In-kernel test cases | `src/tests.zig` |
 | Arch-specific kernel code (`halt`, GDT/IDT/TSS, exception + interrupt stubs, page tables, APIC/timer, serial, linker script) | `src/arch/x86_64/` |
-| Build + `run-efi` (QEMU/OVMF) | `build.zig` |
+| Build + `run-x86-64` (QEMU/OVMF) | `build.zig` |
 | QEMU integration test harness | `test/qemu_test.py` |

docs/efi.md

@@ -25,7 +25,7 @@ esp/EFI/BOOT/BOOTX64.efi     <- the "removable media" default for x86-64
 
 That's exactly the layout `build.zig` assembles. It builds `src/efi.zig` for the
 `uefi` target, installs it to `esp/EFI/BOOT/BOOTX64.efi`, and drops the kernel ELF
-at `esp/danos`. The `run-efi` step then points QEMU at OVMF (UEFI firmware for
+at `esp/danos`. The `run-x86-64` step then points QEMU at OVMF (UEFI firmware for
 virtual machines) and presents that `esp/` directory to the guest as a FAT drive.
 The firmware finds `BOOTX64.efi` and runs it — that's our `main()`.