Documentation - type cleanup ...

- {Number ..} was incorrectly used as a type in a few placed; updated to
  {Number}.

- Removed {} braces incorrectly used with @type; it doesn't affect the
  document rendering, but it does affect the YUIDoc metadata..

- Fixed space in "Rounded Rectangle" type

- Fixed over-qualified type name

- Changed over-qualified {PIXI.scaleModes} back to {Number} for
  consistency with rest of documentation where scale modes are used.

- @returns to @return

- Added types to normalized arrays, when such was easily visible

Documentation - Array(Normalization) ...

YUIDoc does not have a standard (or really any) way of describing inner
types of arrays and there are two general forms used in the current pixi
code:

- `Array<X>`
- `Array An array of X`, or an _inconsistent_ variation of such

The first form is not even parsed correctly by the YUIDoc tool and the
contained type, X, does not appear in the documentation output (or parsed
data) at all. Other similar forms that fail to work are: `X[]`,
`Array{X}`m and `Array.<X>`.

The second form mixes the type (`Array`) and the description of the type
("An array of X"). It would suiting to say "Array of X".

Thus thus commit changes _both_ of the above forms into a normalized
`Array(X)`

While I do not want to impose this as the final chosen representation for
such types, it does _immediately_ address the documentation issues
mentioned above _and_ renders the nested type name in the documentation
output.

If a better method or converntion is found this _consistent_ and
generatable intermim VB-like syntax can be trivially found and replaced.

Another alternative of course, it to forbid anything more complex than
`Array` as a type.

Fixed Rounded Rectangle

Revert "Polygon.contains was toggling the return value"

Polygon.contains was toggling the return value

Fixed matrix.apply ...

was using legacy code

fixes #1066

jsdoc fixes for Geom classes.

updated hit test on polygon

Updated Graphics