Updated references to point to ratified Common Contorl spec

control.adoc

@@ -2,14 +2,12 @@
 == Encoder Control
 
 The fields required to control a Trace Encoder are defined in the
-https://github.com/riscv-non-isa/tg-nexus-trace/blob/master/docs/RISC-V-Trace-Control-Interface.adoc[RISC-V Trace Control Interface Specification], which is intended to apply to any and all RISC-V trace encoders, regardless of encoding protocol. This chapter details which of those fields apply to E-Trace. To avoid replication, descriptions are not provided here; additional E-Trace specific context or clarification is provided only where required.
+https://github.com/riscv-non-isa/e-trace-encap/releases/latest/[RISC-V Trace Control Interface Specification], which is intended to apply to any and all RISC-V trace encoders, regardless of encoding protocol. This chapter details which of those fields apply to E-Trace. To avoid replication, descriptions are not provided here; additional E-Trace specific context or clarification is provided only where required.
 
 How fields are organized and accessed (e.g packet based or memory
 mapped) is outside the scope of this document. If a memory mapped
-approach is adopted,
-https://github.com/riscv-non-isa/tg-nexus-trace/blob/master/docs/RISC-V-Trace-Control-Interface.adoc#register-map[this
-register map] from the RISC-V Trace Control Interface Specification
-should be used.
+approach is adopted, the 'Trace Component Register Map' from the 
+https://github.com/riscv-non-isa/e-trace-encap/releases/latest/[RISC-V Trace Control Interface Specification] should be used.
 
 Note: Upto and including the E-Trace v2.0.0 specification, which
 predated the creation of the RISC-V Trace Control Interface