@@ -79,7 +79,7 @@ of the P extension.
7979Standard unprivileged extensions can also be named by using a single "Z" followed by an
8080alphanumeric name. The name must end with an alphabetical character or an
8181optional version number. The second letter from the end cannot be numeric if the
82- last letter is ``p'' . For example, "Zifencei" names the instruction-fetch fence extension
82+ last letter is "p" . For example, "Zifencei" names the instruction-fetch fence extension
8383described in <<zifencei>>; "Zifencei2" and "Zifencei2p0" name version 2.0 are the same.
8484
8585The first letter following the "Z" conventionally indicates the most
@@ -104,7 +104,7 @@ Other standard extensions that extend the supervisor-level architecture are
104104named by using "Ss" as a prefix, followed by an alphanumeric name. The name
105105must end with an alphabetical character or an optional
106106version number. The second letter from the end cannot be numeric character
107- if the last letter is ``p'' . Supervisor-level extensions must be separated
107+ if the last letter is "p" . Supervisor-level extensions must be separated
108108from other multi-letter extensions by an underscore. These extensions are further
109109defined in Volume II.
110110
@@ -139,7 +139,7 @@ listed, they should be ordered alphabetically.
139139Non-standard extensions are named by using a single "X" followed by the alphanumeric
140140name. The name must end with an alphabetic character or an optional version number. The
141141second letter from the end cannot be numeric if the last letter is
142- ``p'' . For example, "Xhwacha" names the Hwacha vector-fetch ISA
142+ "p" . For example, "Xhwacha" names the Hwacha vector-fetch ISA
143143extension; "Xhwacha2" and "Xhwacha2p0" name version 2.0 of same.
144144
145145Non-standard extensions must be listed after all standard extensions, and,
0 commit comments