start filling in

diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn
index 746928ff14b9397d2f01ed7d54219b1954315f39..36a29009d3eaa744802274dc46f5c53021087dcf 100644 (file)
--- a/isa_conflict_resolution.mdwn
+++ b/isa_conflict_resolution.mdwn
@@ -148,7 +148,8 @@ problem, therefore there isn't a problem".
 The logical errors in this argument were quickly enumerated: namely that
 the RISC-V Foundation is not in control of the uses to which RISC-V is
 put, such that public global conflicts in binary-encoding are a hundred
-percent guaranteed to occur, and a hundred percent guaranteed to occur in
+percent guaranteed to occur (*outside* of the control and remit of the
+RISC-V Foundation), and a hundred percent guaranteed to occur in
 *commodity* hardware where Debian, Fedora, SUSE and other distros will
 be hardest hit by the resultant chaos, and that will just be the more
 "visible" aspect of the underlying problem.