[PPAPI] Fix a bunch of spelling mistakes

ppapi/cpp/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.
 
 #ifndef PPAPI_CPP_MESSAGE_LOOP_H_
 #define PPAPI_CPP_MESSAGE_LOOP_H_
 
 #include "ppapi/cpp/resource.h"
 
 namespace pp {
 
 class CompletionCallback;
 class InstanceHandle;
 
 /// A message loop allows PPAPI calls to be issued on a thread. You may not
 /// issue any API calls on a thread without creating a message loop. It also
 /// allows you to post work to the message loop for a thread.
 ///
 /// To process work posted to the message loop, as well as completion callbacks
 /// for asynchronous operations, you must run the message loop via Run().
 ///
 /// Note the system manages the lifetime of the instance (and all associated
 /// resources). If the instance is deleted from the page, background threads may
 /// suddenly see their PP_Resource handles become invalid. In this case, calls
 /// will fail with PP_ERROR_BADRESOURCE. If you need to access data associated
 /// with your instance, you will probably want to create some kind of threadsafe
-/// proxy object that can handle asynchonous destruction of the instance object.
+/// proxy object that can handle asynchronous destruction of the instance
+/// object.
 ///
 /// Typical usage:
 ///   On the main thread:
 ///    - 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 callacks should look like this:
+///   Your callbacks should look like this:
 ///      void DoMyWork(void* user_data, int32_t status) {
 ///        if (status != PP_OK) {
 ///          Cleanup();  // e.g. free user_data.
 ///          return;
 ///        }
 ///        ... do your work...
 ///      }
 /// For a C++ example, see ppapi/utility/threading/simple_thread.h
 ///
 /// (You can also create the message loop resource on the background thread,
@@ skipping 141 matching lines @@
   ///     to call run on the main thread's message loop (see above).
   int32_t Run();
 
   /// Schedules work to run on the given message loop. This may be called from
   /// any thread. Posted work will be executed in the order it was posted when
   /// the message loop is Run().
   ///
   /// @param callback A pointer to the completion callback to execute from the
   /// message loop.
   ///
-  /// @param delay_ms The number of millseconds to delay execution of the given
+  /// @param delay_ms The number of milliseconds to delay execution of the given
   /// completion callback. Passing 0 means it will get queued normally and
   /// executed in order.
   ///
   ///
   /// The completion callback will be called with PP_OK as the "result"
   /// parameter if it is run normally. It is good practice to check for PP_OK
   /// and return early otherwise.
   ///
   /// The "required" flag on the completion callback is ignored. If there is an
   /// error posting your callback, the error will be returned from PostWork and
@@ skipping 40 matching lines @@
   ///   - PP_ERROR_BADRESOURCE: The message loop was invalid.
   ///   - PP_ERROR_WRONG_THREAD: You are attempting to quit the main thread.
   ///     The main thread's message loop is managed by the system and can't be
   ///     quit.
   int32_t PostQuit(bool should_destroy);
 };
 
 }  // namespace pp
 
 #endif  // PPAPI_CPP_MESSAGE_LOOP_H_