Replaced nonstandard with non-standard.

Closes #851

3 files changed, 5 insertions, 5 deletions

diff --git a/src/f.tex b/src/f.tex
index 4152ae5..4e2f723 100644
--- a/src/f.tex
+++ b/src/f.tex
@@ -293,7 +293,7 @@ but this decision would have increased hardware cost.  Moreover, since this
 feature is optional in the standard, it cannot be used in portable code.
 
 Implementors are free to provide a NaN payload propagation scheme as
-a nonstandard extension enabled by a nonstandard operating mode.  However, the
+a non-standard extension enabled by a non-standard operating mode.  However, the
 canonical NaN scheme described above must always be supported and should be
 the default mode.
 \end{commentary}
diff --git a/src/hypervisor.tex b/src/hypervisor.tex
index d8f79bb..8dbec47 100644
--- a/src/hypervisor.tex
+++ b/src/hypervisor.tex
@@ -3147,7 +3147,7 @@ zero;
 \item
 a transformation of the trapping instruction;
 \item
-a custom value (allowed only if the trapping instruction is nonstandard);
+a custom value (allowed only if the trapping instruction is non-standard);
 or
 \item
 a special pseudoinstruction.
@@ -3200,7 +3200,7 @@ an instruction encoding that is explicitly designated for a custom
 instruction (\emph{not} an unused reserved encoding).
 
 This is a \textit{custom value}.
-The instruction that trapped is a nonstandard instruction.
+The instruction that trapped is a non-standard instruction.
 The interpretation of a custom value is not otherwise specified by this
 standard.
 
@@ -3245,7 +3245,7 @@ cause.
 For exceptions that prevent the fetching of an instruction, only zero or
 a pseudoinstruction value may be written.
 A custom value may be automatically written only if the instruction that
-traps is nonstandard.
+traps is non-standard.
 A future standard or extension may permit other values to be written,
 chosen from the set of allowed values established earlier.
 
diff --git a/src/machine.tex b/src/machine.tex
index abd715f..780c448 100644
--- a/src/machine.tex
+++ b/src/machine.tex
@@ -816,7 +816,7 @@ big-endian-only, with no accommodation for mixing endianness.
 Nevertheless, endianness control has been defined so as to permit, for
 instance, an OS of one endianness to execute user-mode programs of the
 opposite endianness.
-Consideration has been given also to the possibility of nonstandard
+Consideration has been given also to the possibility of non-standard
 usages whereby software flips the endianness of memory accesses as
 needed.
 \end{commentary}