start filling in

diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn
index f7e06b30b8698d177e9231e0c000387cdf826cf3..f1a92a744ec7838809e950ae2c7bb57ea6e17062 100644 (file)
--- a/isa_conflict_resolution.mdwn
+++ b/isa_conflict_resolution.mdwn
@@ -46,11 +46,11 @@ unpatched tools.  This practice is well-known to result in security
 flaws going unpatched, with one of many immediate undesirable consequences
 being that product in extremely large volume gets discarded into landfill.
 
 flaws going unpatched, with one of many immediate undesirable consequences
 being that product in extremely large volume gets discarded into landfill.
 

-All and any of the issues that were discussed, and all of those that
+**All and any of the issues that were discussed, and all of those that

 were not, can be avoided by providing a hardware-level runtime-enabled
 forwards and backwards compatible transition path between *all* parts
 (mandatory or not) of current and future revisions of the RISC-V ISA
 were not, can be avoided by providing a hardware-level runtime-enabled
 forwards and backwards compatible transition path between *all* parts
 (mandatory or not) of current and future revisions of the RISC-V ISA

-Standard.
+Standard.**

 
 The rest of the discussion - indicative as it was of the stark mutually
 exclusive gap being faced by the RISC-V ISA Standard given that it does
 
 The rest of the discussion - indicative as it was of the stark mutually
 exclusive gap being faced by the RISC-V ISA Standard given that it does