cc: Fix inappropriate use of term "texture".

cc: Fix inappropriate use of term "texture".

Avoid using the term "texture" when referring to a resource object
that can be either software bitmap or a hardware texture.

This also fixes some minor spelling mistakes.

BUG=169603
NOTRY=true


Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=178172

[reveman, 2013-01-19 17:20:27]

There's still a bunch of places where we inappropriately use the term "texture"
when referring to resources in our code but I've spent a significant amount of
time reducing it (no incorrectly named classes anymore) and would appreciate if
we avoid adding new code that makes this mistake.

I think in this case we could use "InitializeTile" instead of "SetPixels" if you
guys don't like that term? i.e. CheckForCompletedInitializeTile or
CheckForCompletedTileInitialization.

[nduca, 2013-01-22 21:33:21]

I get the texture changes. But upload makes sense to me.

[reveman, 2013-01-22 23:23:16]

On 2013/01/22 21:33:21, nduca wrote:
> I get the texture changes. But upload makes sense to me.

Latest patch keeps the 'upload' term. This is inconsistent with the resource
provider API but I think that's OK for now. PTAL.

[nduca, 2013-01-22 23:44:23]

lgtm

[brianderson, 2013-01-22 23:56:51]

lgtm too. Thanks for fixing the naming David. I'll be more careful about my use
of "texture" in future patches.

[commit-bot: I haz the power, 2013-01-23 00:07:46]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/reveman@chromium.org/12022043/4001

[commit-bot: I haz the power, 2013-01-23 00:21:15]

Change committed as 178172