(no commit message)

diff --git a/isa_conflict_resolution/isamux_isans.mdwn b/isa_conflict_resolution/isamux_isans.mdwn
index 776ef57433cc2e8cc479d7e96ba3627bdd895e1a..75943937482bc257137434d1ea7b85dd626aa745 100644 (file)
--- a/isa_conflict_resolution/isamux_isans.mdwn
+++ b/isa_conflict_resolution/isamux_isans.mdwn
@@ -210,7 +210,7 @@ Second answer: conflicts can still occur in the (unregulated, custom) 48-bit
 space, which *could* be resolved by ISAMUX/ISANS as applied to the *48* bit
 space in exactly the same way.  And the 64-bit space.
 
-# Why not leave this to individual custom vendors to solve on a case by case basis?
+# Why not leave this to individual custom vendors to solve on a case by case basis? <a name="case-by-case"></a>
 
 The suggestion was raised that a custom extension vendor could create
 their own CSR that selects between conflicting namespaces that resolve