Fix the comment of PPB_MessageLoop.PostWork()

ppapi/api/ppb_message_loop.idl

 /* Copyright (c) 2012 The Chromium Authors. All rights reserved.
  * Use of this source code is governed by a BSD-style license that can be
  * found in the LICENSE file.
  */
 
 /**
  * Defines the PPB_MessageLoop interface.
  */
 label Chrome {
   M25 = 1.0
@@ skipping 99 matching lines @@
  * callback. This is true even for callbacks with the "required" flag set,
  * since the system may not even know what thread to issue the error callback
  * on.
  *
  * Therefore, you should check for errors from PostWork and destroy any
  * associated memory to avoid leaks. If you're using the C++
  * CompletionCallbackFactory, use the following pattern:
  *
  *   pp::CompletionCallback callback = factory_.NewOptionalCallback(...);
  *   int32_t result = message_loop.PostWork(callback);
- *   if (result != PP_OK_COMPLETIONPENDING)
+ *   if (result != PP_OK)
  *     callback.Run(result);
  *
  * This will run the callback with an error value, and assumes that the
  * implementation of your callback checks the "result" argument and returns
  * immediately on error.
  */
 interface PPB_MessageLoop {
   /**
    * Creates a message loop resource.
    *
@@ skipping 93 matching lines @@
    * free this or manually run the callback. See "Desctruction and error
    * handling" above.
    *
    *
    * You can call this function before the message loop has started and the
    * work will get queued until the message loop is run. You can also post
    * work after the message loop has exited as long as should_destroy was
    * PP_FALSE. It will be queued until the next invocation of Run().
    *
    * @return
-   *   - PP_OK_COMPLETIONPENDING: The work was posted to the message loop's
-   *     queue. As described above, this does not mean that the work has been
-   *     or will be executed (if you never run the message loop after posting).
+   *   - PP_OK: The work was posted to the message loop's queue. As described
+   *     above, this does not mean that the work has been or will be executed
+   *     (if you never run the message loop after posting).
    *   - PP_ERROR_BADRESOURCE: The given message loop resource is invalid.
    *   - PP_ERROR_BADARGUMENT: The function pointer for the completion callback
    *     is null (this will be the case if you pass PP_BlockUntilComplete()).
    *   - PP_ERROR_FAILED: The message loop has been destroyed.
    */
   int32_t PostWork([in] PP_Resource message_loop,
                    [in] PP_CompletionCallback callback,
                    [in] int64_t delay_ms);
 
   /**
@@ skipping 13 matching lines @@
    *
    * @return
    *   - PP_OK: The request to quit was successfully posted.
    *   - PP_ERROR_BADRESOURCE: The message loop was invalid.
    *   - PP_ERROR_WRONG_THREAD: You are attempting to quit the main thread.
    *     The main thread's message loop is managed by the system and can't be
    *     quit.
    */
   int32_t PostQuit([in] PP_Resource message_loop, PP_Bool should_destroy);
 };