Corrected typeos

	\begin{rationale} % A.6.2.0620 ?DO

		Typical use:

		\tab \place{ed13}{\word{:} X {\ldots}} \word{qDO} {\ldots} \word{LOOP} \place{ed13}{{\ldots} \word{;}}

		\tab \place{ed13}{\word{:} \texttt{X} {\ldots}} \word{qDO} {\ldots} \word{LOOP} \place{ed13}{{\ldots} \word{;}}

	\end{rationale}

	\begin{testing}\ttfamily

See \xref[Process]{process} (page \pageref{process}) for a full description.

\section{Differences from Forth 94} % D.6

\section{Differences from Forth 94} % D.7

\label{diff:forth94}

\cbstart\patch{x:obsolete}

\end{description}

\patch{x:fp-stack}

\subsection[Obsolescent features]{\sout{Obsolescent features}}

\subsection[Obsolescent features]{\sout{Obsolescent features}} % D.7.2

\label{diff:94:obsolete}

	\sout{This standard has designated the following practice as obsolescent:}

	\uline{Forth 94 did not guarantee the presence of these queries.  Many

	systems that provided all the words in a particular word set did not

	provide the corresponding query.  Portable programs are not affected

	as they could not reply on this function.}

	as they could not rely on this function.}

\item[Transition/Conversion:] ~\\

	\uline{There is no direct equivalent to determine the presence of a whole

\patch{x:throw-iors}

\subsection[Input/Output return values]{\uline{Input/Output return values}}

\subsection[Input/Output return values]{\uline{Input/Output return values}} % D.7.5

\label{diff:12:ior}

\begin{description}

\item[\uline{Reason:}] ~\\

	\uline{Forth 94 left the error code (\param{ior}) implementation-defined,

	although it did recommend an \param{ior} be a \word[exception]{THROW}

	although it did recommend an \param{ior} to be a \word[exception]{THROW}

	code.  Forth 2012 now requires an \param{ior} to be a

	\word[exception]{THROW} code.}

\patch{x:local}

\subsection[Minimum number of locals]{\uline{Minimum number of locals}}

\subsection[Minimum number of locals]{\uline{Minimum number of locals}} % D.7.6

\label{diff:12:locals}

\begin{description}

\end{description}

\patch{x:prefix}

\subsection[Number prefixes]{\uline{Number prefixes}}

\subsection[Number prefixes]{\uline{Number prefixes}} % D.7.7

 \label{diff:12:prefix}

\uline{Decimal, hexadecimal, binary number literals can now be written

\patch{x:source-id}

\subsection[SOURCE-ID Clarification]{\uline{\word{SOURCE-ID} Clarification}}

\subsection[SOURCE-ID Clarification]{\uline{\word{SOURCE-ID} Clarification}} % D.7.7

\label{diff:12:sourceid}

\uline{%

\patch{x:FASINH}

\subsection[FASINH]{\uline{\word[floating]{FASINH}}}

\subsection[FASINH]{\uline{\word[floating]{FASINH}}} % D.7.9

 \label{diff:12:fasinh}

\uline{An ambiguous condition on \param{r1} being less than 0 was removed.}

unlikely to be affected.}

\patch{x:FATAN2}

\subsection[FATAN2]{\uline{\word[floating]{FATAN2}}}

\subsection[FATAN2]{\uline{\word[floating]{FATAN2}}} % D.7.10

\label{diff:12:fatan2}

\begin{description}

% =========================================================

\section{Additional words}

\section{Additional words} % D.8

\label{diff:new12}

The following words have been added to the standard:

\item \wref{core:IMMEDIATE}{} is applied to a word defined by \wref{tools:SYNONYM}{}.

\item \wref{tools:NRfrom}{} is used with data not stored by \wref{tools:NtoR}{}.

\item \place{x:traverse-wordlist}{adding to or deleting from the wordlist during the

	execution of \word{TRAVERSE-WORDLIST}.}

	execution of \wref{tools:TRAVERSE-WORDLIST}.}

\end{itemize}

	\param{x xt} represents the compilation semantics of the word

	\param{nt}.  The returned \param{xt} has the stack effect

%	\stack{i*x x}{j*x}. 

	( \param{i*x x} -{}- \param{j*x} )

	( \param{i*x x} -{}- \param{j*x} ).

 \word{EXECUTE}ing \param{xt} consumes

	\param{x} and performs the compilation semantics of the word

	represented by \param{nt}.

\word[file]{WRITE-FILE}, and

\word[file]{WRITE-LINE}

operate on \emph{pchars}.  Therefore, it is possible that these words

read or write incomplete xchars, which are completed in the next

read or write incomplete \emph{xchars}, which are completed in the next

consecutive operation(s).  The IO system shall combine these \emph{pchars}

into a complete xchar on output, or split an xchar into \emph{pchars} on

input, and shall not throw a ``malformed xchar'' exception when the

combination of these \emph{pchars} indeed forms a valid xchar.

\word[xchar]{-TRAILING-GARBAGE} can be used to process an incomplete xchar

at the end of such an IO operation.}

\uline{\word{ACCEPT} as input editor may be aware of xchars to provide comfort like 

backspace or cursor movement.}

into a complete \emph{xchars} on output, or split an \emph{xchars} into

\emph{pchars} on input, and shall not throw a ``malformed \emph{xchars}''

exception when the combination of these \emph{pchars} form a valid

\emph{xchars}.  \word[xchar]{-TRAILING-GARBAGE} can be used to process

an incomplete \emph{xchars} at the end of such an IO operation.}

\uline{\word{ACCEPT} as input editor may be aware of \emph{xchars} to

provide comfort like backspace or cursor movement.}

\cbend

\section{Additional documentation requirements} % 18.4

number of challenges like input method editors for different languages,

left-to-right and right-to-left writing, and most fonts contain only a subset

of Unicode glyphs, systems should document their capabilities.  File IO and

in-memory string handling should work transparently with xchars.

in-memory string handling should work transparently with \emph{xchars}.

\subsubsection{Ambiguous conditions} % 18.4.1.2

\begin{itemize}

\item the data in memory does not encode a valid xchar

	(\wref{xchar:X-SIZE}{});

\item the xchar value is outside the range of allowed code points of

\item the \emph{xchars} value is outside the range of allowed code points of

	the current character set used.

\item words improperly used outside

	\wref{core:num-start}{<\num} and \wref{core:num-end}{\num>}