X*/S*/Z* names must be fully alphabetical

Resolves #294

1 files changed, 6 insertions, 6 deletions

diff --git a/src/naming.tex b/src/naming.tex
index 97e24c1..43d62a4 100644
--- a/src/naming.tex
+++ b/src/naming.tex
@@ -70,8 +70,8 @@ improve readability and to provide disambiguation. For example, ``RV32I2\_M2\_A2
 
 \section{Additional Standard Extension Names}
 
-Standard extensions can also be named using a single ``Z'' followed by a name
-beginning with a letter and an optional version number.  For example,
+Standard extensions can also be named using a single ``Z'' followed by an
+alphabetical name and an optional version number.  For example,
 ``Zifencei'' names the instruction-fetch fence extension described in
 Chapter~\ref{chap:zifencei}; ``Zifencei2'' and ``Zifencei2p0'' name version
 2.0 of same.
@@ -82,8 +82,8 @@ from other multi-letter extensions by an underscore, e.g.,
 
 \section{Non-Standard Extension Names}
 
-Non-standard subsets are named using a single ``X'' followed by a name
-beginning with a letter and an optional version number.
+Non-standard subsets are named using a single ``X'' followed by an
+alphabetical name and an optional version number.
 For example, ``Xhwacha'' names the Hwacha vector-fetch ISA extension;
 ``Xhwacha2'' and ``Xhwacha2p0'' name version 2.0 of same.
 
@@ -93,8 +93,8 @@ Argle and Bargle may be named ``RV64IZifencei\_Xargle\_Xbargle''.
 
 \section{Supervisor-level Instruction-Set Extensions}
 Standard supervisor instruction-set extensions are defined in Volume II, but
-are named using ``S'' as a prefix, followed by a supervisor subset name
-beginning with a letter and an optional version number.
+are named using ``S'' as a prefix, followed by an
+alphabetical name and an optional version number.
 
 Supervisor extensions must be separated from other multi-letter extensions
 by an underscore.