[PPAPI] Documentation fixes.

ppapi/c/ppb_message_loop.h

 /* 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.
  */
 
-/* From ppb_message_loop.idl modified Thu Mar 28 11:08:46 2013. */
+/* From ppb_message_loop.idl modified Mon Apr  1 12:14:25 2013. */
 
 #ifndef PPAPI_C_PPB_MESSAGE_LOOP_H_
 #define PPAPI_C_PPB_MESSAGE_LOOP_H_
 
 #include "ppapi/c/pp_bool.h"
 #include "ppapi/c/pp_completion_callback.h"
 #include "ppapi/c/pp_instance.h"
 #include "ppapi/c/pp_macros.h"
 #include "ppapi/c/pp_resource.h"
 #include "ppapi/c/pp_stdint.h"
@@ skipping 31 matching lines @@
  *    - Create the thread yourself (using pthreads).
  *    - Create the message loop resource.
  *    - Pass the message loop resource to your thread's main function.
  *    - Call PostWork() on the message loop to run functions on the thread.
  *
  *   From the background thread's main function:
  *    - Call AttachToCurrentThread() with the message loop resource.
  *    - Call Run() with the message loop resource.
  *
  *   Your callbacks should look like this:
+ *      @code
  *      void DoMyWork(void* user_data, int32_t status) {
  *        if (status != PP_OK) {
  *          Cleanup();  // e.g. free user_data.
  *          return;
  *        }
  *        ... do your work...
  *      }
+ *      @endcode
  * For a C++ example, see ppapi/utility/threading/simple_thread.h
  *
  * (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
@@ skipping 205 matching lines @@
   int32_t (*PostQuit)(PP_Resource message_loop, PP_Bool should_destroy);
 };
 
 typedef struct PPB_MessageLoop_1_0 PPB_MessageLoop;
 /**
  * @}
  */
 
 #endif  /* PPAPI_C_PPB_MESSAGE_LOOP_H_ */