reword redraft mvendorid-marchid idea

diff --git a/isa_conflict_resolution/mvendor_march_warl.mdwn b/isa_conflict_resolution/mvendor_march_warl.mdwn
index f48c7f0bcd8b9565990224d8a076c4da6eefedc6..32f2a539b4e405079aef1b9b1424cea2e753f715 100644 (file)
--- a/isa_conflict_resolution/mvendor_march_warl.mdwn
+++ b/isa_conflict_resolution/mvendor_march_warl.mdwn
@@ -43,7 +43,7 @@ against *different variants* of past, present and future RISC-V Standards.
 *This is clearly a desirable characteristic*
 
 It's been noted that there may be certain legitimate cases where
-an mvendorid-marchid should *specifically* not be tested for RISC-V
+a mvendorid-marchid should *specifically* not be tested for RISC-V
 Certification Compliance: native support for foreign architectures (not
 related to the JIT Extension: *actual* full entire non-RISC-V foreign
 instruction encoding).  Exactly how this would work (vis-a-vis Compliance)