to new name

README.md

@@ -36,17 +36,16 @@ When I say 'Endpoint' I mean the circuit boards (and computing) we expect to fin
 
 I have started using 'Motherboards' with 'Daughters' - Mother Boards (of which I have only one so far) are home to Computing and Network Hardware: they are the minimum viable package needed to start having a Modular Controller. They feature one 60-pin (with 30 cpu pins connected) 'mezzanine' / 'board-to-board' connector.
 
-[XMEGA Motherboard](https://gitlab.cba.mit.edu/jakeread/motherboard-xmega)
+[XMEGA Motherboard](https://gitlab.cba.mit.edu/jakeread/motherboard-xmega)  
 
 ### Daughter Boards
 
 Through the 60-pin mezzanine connector mentioned above, I connect the hardware-that-does-work. These are the gate-drivers, mosfets, sensing elements etc, that you need to actually do modular control.
 
-[Router](https://gitlab.cba.mit.edu/jakeread/daughterboard-router)
-[Stepper](https://gitlab.cba.mit.edu/jakeread/daughterboard-stepper)
-
-!TODO migrate doc from BLDC, DC, Ultra, and Breadboard.
-!TODO make heating board (also current sensing big current board)
+[Router](https://gitlab.cba.mit.edu/jakeread/daughterboard-router)  
+[Stepper](https://gitlab.cba.mit.edu/jakeread/daughterboard-stepper)  
+!TODO migrate doc from BLDC, DC, Ultra, and Breadboard.  
+!TODO make heating board (also current sensing big current board)  
 
 # The Computing Contexts
 
@@ -54,9 +53,9 @@ Each of the computers participating in the control of these machines runs a *con
 
 I call these 'DMCCs' - Distributed Machine Control Contexts. None are ready for use.
 
-[Node.js DMCC](https://gitlab.cba.mit.edu/jakeread/dmcc-node)
-[Browser DMCC: the IDOE, aka RuNDMC](https://gitlab.cba.mit.edu/jakeread/rndmc)
-[XMEGA DMCC]
+[Node.js DMCC](https://gitlab.cba.mit.edu/jakeread/dmcc-node)  
+[Browser DMCC: the IDOE, aka RuNDMC](https://gitlab.cba.mit.edu/jakeread/rndmc)  
+[XMEGA DMCC (forthcoming)]
 
 # The Network