[PPAPI] Fix a bunch of spelling mistakes

ppapi/api/dev/ppb_font_dev.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.
  */
 
 /**
  * This file defines the <code>PPB_Font_Dev</code> interface.
  */
 label Chrome {
   M14 = 0.6
@@ skipping 108 matching lines @@
    * treated as a 0-length string).
    */
   PP_Var text;
 
   /**
    * Set to PP_TRUE if the text is right-to-left.
    *
    * When <code>override_direction</code> is false, the browser will perform
    * the Unicode Bidirectional Algorithm (http://unicode.org/reports/tr9/) on
    * the text. The value of the <code>rtl</code> flag specifies the
-   * direcionality of the surrounding environment. This means that Hebrew
+   * directionality of the surrounding environment. This means that Hebrew
    * word will always display right to left, even if <code>rtl</code> is false.
    *
    * When <code>override_direction</code> is true, no autodetection will be done
    * and <code>rtl</code> specifies the direction of the text.
    *
    * TODO(brettw) note that autodetection with rtl = true is currently
    * unimplemented.
    */
   PP_Bool rtl;
 
   /**
    * Set to PP_TRUE to force the directionality of the text regardless of
    * content.
    *
    * If this flag is set, the browser will skip autodetection of the content
-   * and will display all text in the direction speficied by the
+   * and will display all text in the direction specified by the
    * <code>rtl</code> flag.
    */
   PP_Bool override_direction;
 };
 
 interface PPB_Font_Dev {
   /**
    * Returns a list of all available font families on the system. You can use
    * this list to decide whether to Create() a font.
    *
@@ skipping 43 matching lines @@
    * Draws the text to the image buffer.
    *
    * The given point represents the baseline of the left edge of the font,
    * regardless of whether it is left-to-right or right-to-left (in the case of
    * RTL text, this will actually represent the logical end of the text).
    *
    * The clip is optional and may be NULL. In this case, the text will be
    * clipped to the image.
    *
    * The image_data_is_opaque flag indicates whether subpixel antialiasing can
-   * be performend, if it is supported. When the image below the text is
+   * be performed, if it is supported. When the image below the text is
    * opaque, subpixel antialiasing is supported and you should set this to
    * PP_TRUE to pick up the user's default preferences. If your plugin is
    * partially transparent, then subpixel antialiasing is not possible and
    * grayscale antialiasing will be used instead (assuming the user has
    * antialiasing enabled at all).
    */
   PP_Bool DrawTextAt(
       [in] PP_Resource font,
       [in] PP_Resource image_data,
       [in] PP_TextRun_Dev text,
@@ skipping 32 matching lines @@
    * placed at the given position. This handles complex scripts such as Arabic,
    * where characters may be combined or replaced depending on context. Returns
    * -1 on error.
    */
   int32_t PixelOffsetForCharacter(
       [in] PP_Resource font,
       [in] PP_TextRun_Dev text,
       [in] uint32_t char_offset);
 };