Rename GetForCurrentThread() in comments to GetCurrent().

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 40 matching lines @@
  * (You can also create the message loop resource on the background thread,
  * but then the main thread will have no reference to it should you want to
  * call PostWork()).
  *
  *
  * THREAD HANDLING
  *
  * The main thread has an implicitly created message loop. The main thread is
  * the thread where PPP_InitializeModule and PPP_Instance functions are called.
  * You can retrieve a reference to this message loop by calling
- * GetForMainThread() or, if your code is on the main thread,
- * GetForCurrentThread() will also work.
+ * GetForMainThread() or, if your code is on the main thread, GetCurrent() will
+ * also work.
  *
  * Some special threads created by the system can not have message loops. In
  * particular, the background thread created for audio processing has this
  * requirement because it's intended to be highly responsive to keep up with
  * the realtime requirements of audio processing. You can not make PPAPI calls
  * from these threads.
  *
  * Once you associate a message loop with a thread, you don't have to keep a
  * reference to it. The system will hold a reference to the message loop for as
  * long as the thread is running. The current message loop can be retrieved
@@ skipping 189 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);
 };