Clean up formatting to simplify post-Doxygen processing.

ppapi/api/ppb_message_loop.idl

Index: ppapi/api/ppb_message_loop.idl
diff --git a/ppapi/api/ppb_message_loop.idl b/ppapi/api/ppb_message_loop.idl
index 83c198f3ba7e18279bf6ff23dfb0c7ec539bbcb4..0adc0b34f73f6ef5a31102ddef9b02a3b6dc2a68 100644
--- a/ppapi/api/ppb_message_loop.idl
+++ b/ppapi/api/ppb_message_loop.idl
@@ -37,15 +37,15 @@ label Chrome {
  *    - 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
+ *   @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,
@@ -116,12 +116,12 @@ label Chrome {
  * 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)
- *     callback.Run(result);
- *
+ * @code
+ * pp::CompletionCallback callback = factory_.NewOptionalCallback(...);
+ * int32_t result = message_loop.PostWork(callback);
+ * if (result != PP_OK)
+ *   callback.Run(result);
+ * @endcode
  * 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.