diff --git a/02_boot_sequence/kickstart-boot-diagnostics.md b/02_boot_sequence/kickstart-boot-diagnostics.md
index 3f0629c..bc48e12 100644
--- a/02_boot_sequence/kickstart-boot-diagnostics.md
+++ b/02_boot_sequence/kickstart-boot-diagnostics.md
@@ -122,10 +122,10 @@ These colors appear momentarily during a healthy boot, each signaling successful
| Constant | Value | Color | Meaning | When Set |
|---|---|---|---|---|
-| `OK_HARDWARE` | `$0111` | Dark Grey | First software action after RESET | After disabling interrupts/DMA |
-| `OK_SOFTWARE` | `$0888` | Mid Grey | Chip RAM tests passed | After exception vector verify |
-| `OK_RESLIST` | `$0AAA` | Light Grey | All resident modules found | After `FindCodeBefore` |
-| `OK_RESSTART` | `$0CCC` | Bright Grey | About to start resident chain | Just before `InitCode` |
+| `OK_HARDWARE` | `$0111` |  Dark Grey | First software action after RESET | After disabling interrupts/DMA |
+| `OK_SOFTWARE` | `$0888` |  Mid Grey | Chip RAM tests passed | After exception vector verify |
+| `OK_RESLIST` | `$0AAA` |  Light Grey | All resident modules found | After `FindCodeBefore` |
+| `OK_RESSTART` | `$0CCC` |  Bright Grey | About to start resident chain | Just before `InitCode` |
> **Design note:** In the production V40 ROM, only `OK_HARDWARE` survives — the intermediate grey stages (`OK_SOFTWARE`, `OK_RESLIST`, `OK_RESSTART`) were present in earlier revisions (visible in the RCS history of `constants.i`) but consolidated. The screen transitions from dark grey directly through to whatever the boot menu or Workbench draws. On a healthy machine, the grey flash is barely perceptible — lasting only the time it takes to checksum 512KB of ROM and verify chip RAM.
@@ -135,17 +135,17 @@ When any test fails, the color is loaded into `D0` and execution branches to `co
| Constant | Value | Color | Failure | Source Test |
|---|---|---|---|---|
-| `CC_BADROMSUM` | `$0F00` | **Red** | Kickstart ROM checksum invalid | Additive wraparound-carry sum ≠ $FFFFFFFF |
-| `CC_BADRAM` | `$00F0` | **Green** | Chip memory not writable | Exception vector write-back verify failed |
-| `CC_EXCEPTION` | `$0FE5` | **Yellow** | CPU exception before software setup | Bus/Address error or illegal instruction |
-| `CC_NOMODULES` | `$0F0F` | **Purple** | `InitCode(RTF_COLDSTART)` returned | No bootable resident modules found |
-| `CC_BADCHIPS` | `$000F` | **Blue** | Custom chip register test failed | *(Commented out in V40 — was for early hardware)* |
+| `CC_BADROMSUM` | `$0F00` |  **Red** | Kickstart ROM checksum invalid | Additive wraparound-carry sum ≠ $FFFFFFFF |
+| `CC_BADRAM` | `$00F0` |  **Green** | Chip memory not writable | Exception vector write-back verify failed |
+| `CC_EXCEPTION` | `$0FE5` |  **Yellow** | CPU exception before software setup | Bus/Address error or illegal instruction |
+| `CC_NOMODULES` | `$0F0F` |  **Purple** | `InitCode(RTF_COLDSTART)` returned | No bootable resident modules found |
+| `CC_BADCHIPS` | `$000F` |  **Blue** | Custom chip register test failed | *(Commented out in V40 — was for early hardware)* |
### 2.3 Special Modes
| Constant | Value | Color | Meaning |
|---|---|---|---|
-| `OK_DEBUG` | `$000F` | Blue | Debug/development mode — fire button held at boot |
+| `OK_DEBUG` | `$000F` |  Blue | Debug/development mode — fire button held at boot |
| `COLORON` | `$0200` | *(control)* | Written to `BPLCON0` to enable color burst output |
### 2.4 Color Progression Diagram