[PPAPI] Documentation fixes.

ppapi/api/pp_completion_callback.idl

Index: ppapi/api/pp_completion_callback.idl
diff --git a/ppapi/api/pp_completion_callback.idl b/ppapi/api/pp_completion_callback.idl
index 871a135a3fcab17c1e73b455efaf988474003c8a..46b6342aa2b83b6a53579f66162bef57636f343b 100644
--- a/ppapi/api/pp_completion_callback.idl
+++ b/ppapi/api/pp_completion_callback.idl
@@ -66,10 +66,10 @@ enum PP_CompletionCallback_Flag {
  * ways:
  *   - Required: The callback will always be invoked asynchronously on the
  *               thread where the associated PPB method was invoked. The method
- *               will always return <code>PP_OK_COMPLETIONPENDING</code> when a
- *               required callback, and the callback will be invoked later
- *               (barring system or thread shutdown; see PPB_MessageLoop for
- *               details). Required callbacks are the default.
+ *               will always return PP_OK_COMPLETIONPENDING when a required
+ *               callback, and the callback will be invoked later (barring
+ *               system or thread shutdown; see PPB_MessageLoop for details).
+ *               Required callbacks are the default.
  *
  *               NOTE: If you use a required callback on a background thread,
  *               you must have created and attached a PPB_MessageLoop.
@@ -141,16 +141,16 @@ enum PP_CompletionCallback_Flag {
  *
  * <strong>Example, creating a Required callback:</strong>
  *
- * <code>
+ * @code
  * struct PP_CompletionCallback cc = PP_MakeCompletionCallback(Foo, NULL);
- * </code>
+ * @endcode
  *
  * <strong>Example, creating an Optional callback:</strong>
  *
- * <code>
+ * @code
  * struct PP_CompletionCallback cc = PP_MakeCompletionCallback(Foo, NULL);
  * cc.flags = cc.flags | PP_COMPLETIONCALLBACK_FLAG_OPTIONAL;
- * </code>
+ * @endcode
  *
  * @param[in] func A <code>PP_CompletionCallback_Func</code> that will be
  * called.