Mostly minor changes such as adding <code></code> around elements, a little rewriting, and a few ...

ppapi/c/pp_input_event.h

 /* Copyright (c) 2011 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.
  */
 #ifndef PPAPI_C_PP_INPUT_EVENT_H_
 #define PPAPI_C_PP_INPUT_EVENT_H_
 
 /**
  * @file
  * This file defines the API used to handle mouse and keyboard input events.
@@ skipping 76 matching lines @@
 /**
  * @}
  */
 
 /**
  * @addtogroup Structs
  * @{
  */
 
 /**
- * The PP_InputEvent_Key struct represents a key up or key down event.
+ * The <code>PP_InputEvent_Key</code> struct represents a key up or key down
+ * event.
  *
  * Key up and key down events correspond to physical keys on the keyboard. The
  * actual character that the user typed (if any) will be delivered in a
  * "character" event.
  *
  * If the user loses focus on the module while a key is down, a key up
  * event might not occur. For example, if the module has focus and the user
  * presses and holds the shift key, the module will see a "shift down" message.
  * Then if the user clicks elsewhere on the web page, the module's focus will
  * be lost and no more input events will be delivered.
  *
  * If your module depends on receiving key up events, it should also handle
  * "lost focus" as the equivalent of "all keys up."
  */
 struct PP_InputEvent_Key {
   /** This value is a bit field combination of the EVENT_MODIFIER flags. */
   uint32_t modifier;
 
   /**
-   * |key_code| reflects the DOM KeyboardEvent |keyCode| field.
+   * This value reflects the DOM KeyboardEvent <code>keyCode</code> field.
    * Chrome populates this with the Windows-style Virtual Key code of the key.
    */
 
   uint32_t key_code;
 };
 PP_COMPILE_ASSERT_STRUCT_SIZE_IN_BYTES(PP_InputEvent_Key, 8);
 /**
  * @}
  */
 
 /**
  * @addtogroup Structs
  * @{
  */
 
 /**
- * The PP_InputEvent_Character struct represents a typed character event.
+ * The <code>PP_InputEvent_Character</code> struct represents a typed character
+ * event.
  *
  * Normally, the program will receive a key down event, followed by a character
  * event, followed by a key up event. The character event will have any
  * modifier keys applied. Obvious examples are symbols, where Shift-5 gives you
  * a '%'. The key down and up events will give you the scan code for the "5"
  * key, and the character event will give you the '%' character.
  *
  * You may not get a character event for all key down events if the key doesn't
  * generate a character. Likewise, you may actually get multiple character
  * events in a row. For example, some locales have an accent key that modifies
  * the next character typed. You might get this stream of events: accent down,
  * accent up (it didn't generate a character), letter key down, letter with
  * accent character event (it was modified by the previous accent key), letter
  * key up.  If the letter can't be combined with the accent, like an umlaut and
  * an 'R', the system might send unlaut down, umlaut up, 'R' key down, umlaut
  * character (can't combine it with 'R', so just send the raw unlaut so it
  * isn't lost"), 'R' character event, 'R' key up.
  */
 struct PP_InputEvent_Character {
-  /** A combination of the EVENT_MODIFIER flags. */
+  /** A combination of the <code>PP_InputEvent_Modifier</code> flags. */
   uint32_t modifier;
 
   /**
    * This value represents the typed character as a single null-terminated UTF-8
    * character. Any unused bytes will be filled with null bytes. Since the
    * maximum UTF-8 character is 4 bytes, there will always be at least one null
    * at the end so you can treat this as a null-termianted UTF-8 string.
    */
   char text[5];
 };
 PP_COMPILE_ASSERT_STRUCT_SIZE_IN_BYTES(PP_InputEvent_Character, 12);
 /**
  * @}
  */
 
 /**
  * @addtogroup Structs
  * @{
  */
 
 /**
- * The PP_InputEvent_Mouse struct represents all mouse events except
- * mouse wheel events.
+ * The <code>PP_InputEvent_Mouse</code> struct represents all mouse events
+ * except mouse wheel events.
  */
 struct PP_InputEvent_Mouse {
-  /** This value is a bit field combination of the EVENT_MODIFIER flags. */
+  /**
+   * This value is a bit field combination of the
+   * <code>PP_InputEvent_Modifier</code> flags.
+   */
   uint32_t modifier;
 
   /**
    * This value represents the button that changed for mouse down or up events.
-   * This value will be PP_EVENT_MOUSEBUTTON_NONE for mouse move, enter, and
-   * leave events.
+   * This value will be <code>PP_EVENT_MOUSEBUTTON_NONE</code> for mouse move,
+   * enter, and leave events.
    */
   PP_InputEvent_MouseButton button;
 
   /**
    * This values represents the x coordinate of the mouse when the event
    * occurred.
    *
    * In most, but not all, cases these coordinates will just be integers.
    * For example, the plugin element might be arbitrarily scaled or transformed
    * in the DOM, and translating a mouse event into the coordinate space of the
@@ skipping 18 matching lines @@
 /**
  * @}
  */
 
 /**
  * @addtogroup Structs
  * @{
  */
 
 /**
- * The PP_InputEvent_Wheel struct represents all mouse wheel events.
+ * The <code>PP_InputEvent_Wheel</code> struct represents all mouse wheel
+ * events.
  */
 struct PP_InputEvent_Wheel {
-  /** This value represents a combination of the EVENT_MODIFIER flags. */
+  /**
+   * This value represents a combination of the <code>EVENT_MODIFIER</code>
+   * flags.
+   */
   uint32_t modifier;
 
   /**
    * Indicates the amount vertically and horizontally the user has requested
    * to scroll by with their mouse wheel. A scroll down or to the right (where
    * the content moves up or left) is represented as positive values, and
    * a scroll up or to the left (where the content moves down or right) is
    * represented as negative values.
    *
    * The units are either in pixels (when scroll_by_page is false) or pages
@@ skipping 12 matching lines @@
    */
   float delta_x;
 
   /** This value represents */
   float delta_y;
 
   /**
    * The number of "clicks" of the scroll wheel that have produced the
    * event. The value may have system-specific acceleration applied to it,
    * depending on the device. The positive and negative meanings are the same
-   * as for |delta|.
+   * as for <code>delta_x</code> and <code>delta_y</code>.
    *
    * If you are scrolling, you probably want to use the delta values above.
    * These tick events can be useful if you aren't doing actual scrolling and
    * don't want or pixel values. An example may be cycling between different
    * items in a game.
    *
    * You may receive fractional values for the wheel ticks if the mouse wheel
    * is high resolution or doesn't have "clicks". If your program wants
    * discrete events (as in the "picking items" example) you should accumulate
    * fractional click values from multiple messages until the total value
    * reaches positive or negative one. This should represent a similar amount
    * of scrolling as for a mouse that has a discrete mouse wheel.
    */
   float wheel_ticks_x;
 
   /** This value represents */
   float wheel_ticks_y;
 
   /**
-   * Indicates if the scroll delta_x/delta_y indicates pages or lines to
-   * scroll by. When true, the user is requesting to scroll by pages.
+   * Indicates if the scroll <code>delta_x</code>/<code>delta_y</code>
+   * indicates pages or lines to scroll by. When true, the user is requesting
+   * to scroll by pages.
    */
   PP_Bool scroll_by_page;
 };
 PP_COMPILE_ASSERT_STRUCT_SIZE_IN_BYTES(PP_InputEvent_Wheel, 24);
 /**
  * @}
  */
 
 /**
  *
@@ skipping 34 matching lines @@
      */
     char padding[64];
   } u;
 };
 PP_COMPILE_ASSERT_STRUCT_SIZE_IN_BYTES(PP_InputEvent, 80);
 /**
  * @}
  */
 
 #endif  /* PPAPI_C_PP_INPUT_EVENT_H_ */