eg. / e.g.
vertice / vertex
fullframe / full-frame
todo / TODO
unreckognized / unrecognized
ontop / in front
initialise / initialize
unforms / uniforms
overriden / overridden
interpolatation / interpolation
subsurve / sub-curve
Catmull-rom / Catmull-Rom
consruct / construct
colinear / collinear
perpenicular / perpendicular
minimim / minimum
segements / segments
speficied / specified
compatable / compatible
egde / edge
initalization / initialization
shiftet / shifted
childrens' / children's
ambigious / ambiguous
barycoordinates / barycentric coordinates
equi distance / equidistant
equidistance / equidistant
ist / is

And remove one `console.log`

Fixes #6266

WebGLRenderer: Avoid flat shading buffer creation when using MeshPhongMaterial and clean up. See #6117.

remove material.ambient from everything per discussion here: https://github.com/mrdoob/three.js/pull/5741#issuecomment-67893202

add THREE.error/THREE.warning to allow for easy redirection of THREE.js specific errors and warnings.

I'm seeing people modifying it :(

Reverted 4439d901. Implemented material.visible in Projector. See #5256.

Pheww... Glad that I figured this out in time.

added editor class and few methods

removed uuid

Implemented more methods

editor refactoring

editor refactoring

editor api improvements

finished editor API

hooked up editor to UI as an argument

The previous boolean type allowed for either a 0 or a 1 pixel overdraw
for fixing antialiasing gaps in CanvasRenderer. I've found the best
value to be 0.35, though this may be browser/gpu specific. Should be
backwards compatible.

Sorry, I couldn't merge cleanly nor cherry-pick.

It happens on a project I'm working on, not sure still why. I guess this approach is safer.

Official comment from VM guy is that it isn't needed.

Still waiting for an "official" recommendation from a VM guy though.