-\section {Terms and definitions}
-\subsection*{object}
-A region of data storage in the execution environment, the contents of which can represent values.
-\subsection*{implementation}
-A particular set of software, running in a particular translation environment under particular control options, that performs translations of programs for, and supports execution of functions, in a particular execution environment (typically a Quake engine).
+\section{Introduction}
+With the introduction of improvements of existing runtime environments, new features may be added to this specification. Subclauses in the language warn implementors and programmers of usages which, though valid in themselfs, may conflict with future additions.
+
+This specification is divided into three major subjects:
+\begin{enumerate}
+ \item preliminary elements
+ \item the characteristics of environments that translate and execute QuakeC programs
+ \item the languages syntax, constraints, and semantics
+\end{enumerate}
+
+Examples are provided to illustrate possible forms of the constructions described, to better facilitate the reader.
+
+\section{Scope}
+This specification only specifies the form and establishes the interpretation of programs written in the GMQCC QuakeC programming language variant. It specifies:
+\begin{enumerate}
+ \item The representation of Quake C programs;
+ \item The syntax and constraints of the Quake C language;
+ \item The semantic rules for interpreting Quake C programs;
+ \item The representation of input data to be processed by Quake C programs;
+ \item The restrictions and limits imposed by a conforming implementation of Quake C.
+\end{enumerate}
+This specification does not specify
+\begin{enumerate}
+ \item The process in which Quake C programs are transformed for use by a data-processing system;
+ \item The process in which Quake C programs are invoked for use by a data-processing system;
+ \item The process in which input data is transformed for use by a Quake C program;
+ \item The process in which output data is transformed after being produces by a Quake C program;
+ \item The size of complexity involved with a Quake C program and its data that will exceed the capacity of any specific data-processing system or the capacity of a particular processor;
+ \item The minimal requirements of a data-processing system which is capable of supporting a conforming implementation.
+\end{enumerate}
+These details are decided upon by the environment designer (usually the engine developer). The details are as such subjected to implementation-defined behavior.
+
+\section{Terms and definitions}