Cleaning up broken links.

Fixing links to the registers as defined in the -def files.

debug_module.adoc

@@ -363,9 +363,9 @@ failed, the debugger has to look at the state of the DM (e.g. contents
 of {dm-data0}) or hart (e.g. contents of a register modified by a Program Buffer program) to determine which one failed.
 ====
 
-Before starting an abstract command, a debugger must ensure that {dmcontrol-haltreq}, {dmcontrol-resumereq}, and {dmstatus-ackhavereset} are all 0.
+Before starting an abstract command, a debugger must ensure that {dmcontrol-haltreq}, {dmcontrol-resumereq}, and {dmcontrol-ackhavereset} are all 0.
 
-While an abstract command is executing ({abstractcs-busy} in <abstractcs>> is high), a debugger must not change {dm-dmcontrol,hartset}, and must not write 1 to {dmcontrol-haltreq}, {dmcontrol-resumereq}, {dmstatus-ackhavereset}, {dmcontrol-setresethaltreq}, or {dmcontrol-clrresethaltreq}.
+While an abstract command is executing ({abstractcs-busy} in {dm-abstractcs} is high), a debugger must not change `hartset`, and must not write 1 to {dmcontrol-haltreq}, {dmcontrol-resumereq}, {dmcontrol-ackhavereset}, {dmcontrol-setresethaltreq}, or {dmcontrol-clrresethaltreq}.
 
 If an abstract command does not complete in the expected time and
 appears to be hung, the debugger can try to reset the hart (using {dmcontrol-hartreset} or {dmcontrol-ndmreset}).