Commit 6c3298ea authored by darin@chromium.org's avatar darin@chromium.org

Fix comment.

TBR=brettw

Review URL: http://codereview.chromium.org/6278014

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@72242 0039d316-1c4b-4281-b951-d872f2087c98
parent 5c19e8b6
......@@ -122,9 +122,9 @@ struct PPB_Graphics2D {
* THE NEW IMAGE WILL NOT BE PAINTED UNTIL YOU CALL FLUSH.
*
* After this call, you should take care to release your references to the
* image. If you paint to the image after a Swap, there is the possibility of
* significant painting artifacts because the page might use partially-
* rendered data when copying out of the backing store.
* image. If you paint to the image after ReplaceContents, there is the
* possibility of significant painting artifacts because the page might use
* partially-rendered data when copying out of the backing store.
*
* In the case of an animation, you will want to allocate a new image for the
* next frame. It is best if you wait until the flush callback has executed
......@@ -137,7 +137,7 @@ struct PPB_Graphics2D {
void (*ReplaceContents)(PP_Resource graphics_2d, PP_Resource image_data);
/**
* Flushes any enqueued paint, scroll, and swap commands for the backing
* Flushes any enqueued paint, scroll, and replace commands for the backing
* store. This actually executes the updates, and causes a repaint of the
* webpage, assuming this graphics context is bound to a plugin instance. This
* can run in two modes:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment