clarify

diff --git a/isa_conflict_resolution.mdwn b/isa_conflict_resolution.mdwn
index 25146b6697da7a8d6de771052143d138f304c472..e0ea5890554a75857bd0a5d6ecf894df185658a3 100644 (file)
--- a/isa_conflict_resolution.mdwn
+++ b/isa_conflict_resolution.mdwn
@@ -429,10 +429,11 @@ So to summarise:
   an extreme unlikely outlier).
 * Compliance Testing is straightforward and allows vendors to seek and
   obtain *multiple* Compliance Certificates with past, present and future
-  variants of the RISC-V Standard (in the exact same processor), in order
-  support legacy customers and provide same customers with a way to avoid
-  "impossible-to-make" decisions that throw out ultra-expensive multi-decade
-  proprietary legacy software at the same as the hardware.
+  variants of the RISC-V Standard (in the exact same processor,
+  simultaneously), in order to support legacy customers and provide
+  same customers with a way to avoid "impossible-to-make" decisions that
+  throw out ultra-expensive multi-decade proprietary legacy software at
+  the same as the (legacy) hardware.
 
 # Conversation Exerpts