Bugfix - Typos

Summary:
Fixed few typos in `./Examples` and `./Libraries` folders.
Closes react#4788

Reviewed By: svcscm

Differential Revision: D2759918

Pulled By: androidtrunkagent

fb-gh-sync-id: d692b5c7f561822353e522f9d4dfde7e60b491cf

Author: jutaz

Examples/2048/GameBoard.js

@@ -17,7 +17,7 @@
 'use strict';
 
 // NB: Taken straight from: https://github.com/IvanVergiliev/2048-react/blob/master/src/board.js
-//     with no modificiation except to format it for CommonJS and fix lint/flow errors
+//     with no modification except to format it for CommonJS and fix lint/flow errors
 
 var rotateLeft = function (matrix) {
   var rows = matrix.length;

Examples/UIExplorer/UIExplorerUnitTests/LayoutSubviewsOrderingTest.m

@@ -14,7 +14,7 @@ @implementation LayoutSubviewsOrderingTest
 /**
  * This test exists to insure that didLayoutSubviews is always called immediately after layoutSubviews for a VC:View
  * pair. In Catalyst we have multiple levels of ViewController containment, and we rely on this ordering
- * to insure that layoutGuides are set on RKViewControllers before Views further down in the heirarchy have
+ * to insure that layoutGuides are set on RKViewControllers before Views further down in the hierarchy have
  * their layoutSubviews called (and need to use the aforementioned layoutGuides)
  */
 - (void)testLayoutSubviewsOrdering
@@ -63,7 +63,7 @@ - (void)testLayoutSubviewsOrdering
     }
   }] viewDidLayoutSubviews];
 
-  // setup View heirarchy and force layout
+  // setup View hierarchy and force layout
   parentVC.view = parentView;
   childVC.view = childView;
   [parentVC addChildViewController:childVC];

Examples/UIExplorer/UIExplorerUnitTests/RCTContextExecutorTests.m

@@ -98,7 +98,7 @@ - (void)testJavaScriptCallSpeed
 {
 /**
  * Since we almost don't change the RCTContextExecutor logic, and this test is
- * very likely to become flaky (specially accross different devices) leave it
+ * very likely to become flaky (specially across different devices) leave it
  * to be run manually
  *
  * Previous Values: If you change the executor code, you should update this values

Examples/UIExplorer/WebViewExample.js

@@ -148,7 +148,7 @@ var WebViewExample = React.createClass({
         url: url,
       });
     }
-    // dismiss keyoard
+    // dismiss keyboard
     this.refs[TEXT_INPUT_REF].blur();
   },
 

Examples/UIExplorer/XHRExample.android.js

@@ -30,7 +30,7 @@ var XHRExampleHeaders = require('./XHRExampleHeaders');
 var XHRExampleCookies = require('./XHRExampleCookies');
 
 
-// TODO t7093728 This is a simlified XHRExample.ios.js.
+// TODO t7093728 This is a simplified XHRExample.ios.js.
 // Once we have Camera roll, Toast, Intent (for opening URLs)
 // we should make this consistent with iOS.
 

Libraries/Animated/examples/demo.html

@@ -326,7 +326,7 @@ <h2>stopAnimation</h2>
 
 <p><code>Animated</code> can offload the animation to a different thread (CoreAnimation, CSS transitions, main thread...) and we don't have a good way to know the real value. If you try to query the value then modify it, you are going to be out of sync and the result will look terrible.</p>
 
-<p>There's however one exception: when you want to stop the current animation. You need to know where it stopped in order to continue from there. We cannot know the value synchronously so we give it via a callback in <code>stopAnimation</code>. It will not suffer from beign out of sync since the animation is no longer running.</p>
+<p>There's however one exception: when you want to stop the current animation. You need to know where it stopped in order to continue from there. We cannot know the value synchronously so we give it via a callback in <code>stopAnimation</code>. It will not suffer from being out of sync since the animation is no longer running.</p>
 
 <script type="text/jsx;harmony=true;stripTypes=true">
 examplify(React.createClass({

Libraries/Animated/src/AnimatedImplementation.js

@@ -578,7 +578,7 @@ class AnimatedValue extends AnimatedWithChildren {
   /**
    * Adds an asynchronous listener to the value so you can observe updates from
    * animations or whathaveyou.  This is useful because there is no way to
-   * syncronously read the value because it might be driven natively.
+   * synchronously read the value because it might be driven natively.
    */
   addListener(callback: ValueListenerCallback): string {
     var id = String(_uniqueId++);
@@ -1485,7 +1485,7 @@ var event = function(
  * The simplest workflow is to create an `Animated.Value`, hook it up to one or
  * more style attributes of an animated component, and then drive updates either
  * via animations, such as `Animated.timing`, or by hooking into gestures like
- * panning or scolling via `Animated.event`.  `Animated.Value` can also bind to
+ * panning or scrolling via `Animated.event`.  `Animated.Value` can also bind to
  * props other than style, and can be interpolated as well.  Here is a basic
  * example of a container view that will fade in when it's mounted:
  *
@@ -1517,7 +1517,7 @@ var event = function(
  * Note that only animatable components can be animated.  `View`, `Text`, and
  * `Image` are already provided, and you can create custom ones with
  * `createAnimatedComponent`.  These special components do the magic of binding
- * the animated values to the properties, and do targetted native updates to
+ * the animated values to the properties, and do targeted native updates to
  * avoid the cost of the react render and reconciliation process on every frame.
  * They also handle cleanup on unmount so they are safe by default.
  *
@@ -1559,7 +1559,7 @@ var event = function(
  * Animation App, and [Animations documentation guide](http://facebook.github.io/react-native/docs/animations.html).
  *
  * Note that `Animated` is designed to be fully serializable so that animations
- * can be run in a high performace way, independent of the normal JavaScript
+ * can be run in a high performance way, independent of the normal JavaScript
  * event loop. This does influence the API, so keep that in mind when it seems a
  * little trickier to do something compared to a fully synchronous system.
  * Checkout `Animated.Value.addListener` as a way to work around some of these

Libraries/CameraRoll/CameraRoll.js

@@ -128,7 +128,7 @@ class CameraRoll {
    *
    *   - local URI
    *   - assets-library tag
-   *   - a tag not maching any of the above, which means the image data will
+   *   - a tag not matching any of the above, which means the image data will
    * be stored in memory (and consume memory as long as the process is alive)
    *
    * @param successCallback Invoked with the value of `tag` on success.

Libraries/Components/DrawerAndroid/DrawerLayoutAndroid.android.js

@@ -102,7 +102,7 @@ var DrawerLayoutAndroid = React.createClass({
     /**
      * Function called when the drawer state has changed. The drawer can be in 3 states:
      * - idle, meaning there is no interaction with the navigation view happening at the time
-     * - dragging, meaning there is currently an interation with the navigation view
+     * - dragging, meaning there is currently an interaction with the navigation view
      * - settling, meaning that there was an interaction with the navigation view, and the
      * navigation view is now finishing it's closing or opening animation
      */

Libraries/Components/MapView/MapView.js

@@ -150,7 +150,7 @@ var MapView = React.createClass({
      *
      * - standard: standard road map (default)
      * - satellite: satellite view
-     * - hybrid: satellite view with roads and points of interest overlayed
+     * - hybrid: satellite view with roads and points of interest overlaid
      */
     mapType: React.PropTypes.oneOf([
       'standard',
@@ -172,7 +172,7 @@ var MapView = React.createClass({
       longitude: React.PropTypes.number.isRequired,
 
       /**
-       * Distance between the minimun and the maximum latitude/longitude
+       * Distance between the minimum and the maximum latitude/longitude
        * to be displayed.
        */
       latitudeDelta: React.PropTypes.number.isRequired,
@@ -218,7 +218,7 @@ var MapView = React.createClass({
        * and custom pin images.
        *
        * Note that on iOS 8 and earlier, only the standard PinColor constants
-       * are supported for regualr pins. For custom pin images, any tintColor
+       * are supported for regular pins. For custom pin images, any tintColor
        * value is supported on all iOS versions.
        * @platform ios
        */