X-Git-Url: https://git.libre-soc.org/?a=blobdiff_plain;f=x-list.mdwn;h=d108485f08a26809bc0e103a1ed06a4c840f5dad;hb=b22acdc5781ea29908e93f952b9728ff28ad134f;hp=174de2e68b3431062162cf83bc7814d39de7aabd;hpb=9aebfd90fb5526cd327d022c6d74e728917a65b3;p=libreriscv.git

diff --git a/x-list.mdwn b/x-list.mdwn
index 174de2e68..d108485f0 100644
--- a/x-list.mdwn
+++ b/x-list.mdwn
@@ -326,7 +326,7 @@ guidelines and I believe they should be enforced:
 
 - https://riscv.org/risc-v-trademark-usage/
 
-Example 1:  https://emb-riscv.github.io/
+Example:  https://emb-riscv.github.io/
 
 Implementation proposal that does not comply with the minimal M mode
 requirements and may not be RISC-V compliant. The “Embedded RISC-V”
@@ -339,9 +339,6 @@ group and who is the chair? Using something like X-Embedded might be
 less risky assuming this may or may not be the Foundation’s official
 Embedded Working Group? It is hard to tell. It is suggestive.
 
-Example 2:
-https://github.com/cliffordwolf/xbitmanip/blob/master/xbitmanip-draft.pdf
-
 Uses X- prefix, extends the specifications, doesn’t modify the RISC-V
 logo. Clearly fair use.