Just made those fixes.

I actually noticed "targetting" when I typed it, made a mental note to go
back and fix it, and then promptly forgot about it. :)




On Tue, Nov 19, 2013 at 11:53 AM, Simon Krajewski
<notifications@github.com>wrote:

> In HaxeDoc.tex:
>
> > +\label{std-math-special-numbers}
> > +The math library has defitions for several special numbers:
> > +\begin{itemize}
> > +	\item NaN (Not A Number): returned when a mathmatically incorrect operation is executed e.g. Math.sqrt(-1)
> > +	\item POSITIVE_INFINITY: e.g. divide a positive number by zero
> > +	\item NEGATIVE_INFINITY: e.g. divide a negative number by zero
> > +	\item PI : 3.1415...
> > +\end{itemize}
> > +
> > +\subsection{Mathematical Errors}
> > +\label{std-math-mathematical-errors}
> > +Although neko can fluidly handle mathematical errors, like division by zero, this is not true for all target.  Depending on the target, mathematical errors may produce exceptions and ultimately errors.
> > +
> > +\subsection{Integer Math}
> > +\label{std-math-integer-math}
> > +If you are targetting a platform that can utilize integer operations, e.g. integer division, for performance gains, wrap the operation in \emph{Std.int()}.  The Haxe compiler can then optimize for integer operations.  An example:
>
> Note that it's spelled targeting (one of the most common English typos I
> think).
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/Simn/HaxeManual/pull/46/files#r7765575>
> .
>