diff --git a/Home.md b/Home.md
index 3f9ec5f..6950b90 100644
--- a/Home.md
+++ b/Home.md
@@ -9,7 +9,7 @@ Unlike other ports of Mini vMac, this one supports having several variants compi
 
 This is achieved by compiling all the emulation code into a bundle, which is [loaded at runtime](https://github.com/zydeco/minivmac4ios/blob/master/Mini%20vMac/AppDelegate.m#L80). These bundles implement the [`Emulator` protocol](https://github.com/zydeco/minivmac4ios/blob/master/Mini%20vMac/EmulatorProtocol.h) on their main class, which is used to interface it with the UI.
 
-For each variant, there is a framework target that compiles all the necessary C files from the core (not all of them are used for all machines: (e.g. `ADBEMDEV.c` isn't used for the Mac 128K or Plus), and a [`CNFGGLOB.h`](https://github.com/zydeco/minivmac4ios/blob/master/Mini%20vMac/MacPlus4M/CNFGGLOB.h) and [`EMCONFIG.h`](https://github.com/zydeco/minivmac4ios/blob/master/Mini%20vMac/MacPlus4M/EMCONFIG.h) with the appropriate values for emulating that machine.
+For each variant, there is a framework target that compiles all the necessary C files from the core (not all of them are used for all machines: (e.g. `ADBEMDEV.c` isn't used for the Mac 128K or Plus), and configuration header files ([`CNFUDALL.h`](https://github.com/zydeco/minivmac4ios/blob/master/Mini%20vMac/MacPlus4M/CNFUDALL.h), [`CNFUDOSG.h`](https://github.com/zydeco/minivmac4ios/blob/master/Mini%20vMac/MacPlus4M/CNFUDOSG.h) and [`CNFUDPIC.h`](https://github.com/zydeco/minivmac4ios/blob/master/Mini%20vMac/MacPlus4M/CNFUDPIC.h)) with the appropriate values for emulating that machine, as generated by the Mini vMac build system.
 
 ![Bundle structure](http://i.imgur.com/M4AoIvI.png)
 ![Bundle compiled files](http://i.imgur.com/jhD7O8u.png)