[react-native] Fix capitalization of "REact"

Libraries/Components/View/View.js

@@ -29,7 +29,7 @@ var stylePropType = StyleSheetPropType(ViewStylePropTypes);
  * container that supports layout with flexbox, style, some touch handling, and
  * accessibility controls, and is designed to be nested inside other views and
  * to have 0 to many children of any type. `View` maps directly to the native
- * view equivalent on whatever platform react is running on, whether that is a
+ * view equivalent on whatever platform React is running on, whether that is a
  * `UIView`, `<div>`, `android.view`, etc.  This example creates a `View` that
  * wraps two colored boxes and custom component in a row with padding.
  *

Libraries/Image/Image.ios.js

@@ -31,7 +31,7 @@ var verifyPropTypes = require('verifyPropTypes');
 var warning = require('warning');
 
 /**
- * A react component for displaying different types of images,
+ * A React component for displaying different types of images,
  * including network images, static resources, temporary local images, and
  * images from local disk, such as the camera roll.
  *

Libraries/ReactIOS/ReactIOSComponentMixin.js

@@ -46,7 +46,7 @@ var ReactInstanceMap = require('ReactInstanceMap');
  *
  * `mountImage`: A way to represent the potential to create lower level
  * resources whos `nodeHandle` can be discovered immediately by knowing the
- * `rootNodeID`. Today's web react represents this with `innerHTML` annotated
+ * `rootNodeID`. Today's web React represents this with `innerHTML` annotated
  * with DOM ids that match the `rootNodeID`.
  *
  * Opaque name      TodaysWebReact   FutureWebWorkerReact   ReactNative

Libraries/Text/Text.js

@@ -33,7 +33,7 @@ var viewConfig = {
 };
 
 /**
- * A react component for displaying text which supports nesting,
+ * A React component for displaying text which supports nesting,
  * styling, and touch handling.  In the following example, the nested title and
  * body text will inherit the `fontFamily` from `styles.baseText`, but the title
  * provides its own additional styles.  The title and body will stack on top of

Libraries/vendor/react/platform/NodeHandle.js

@@ -19,7 +19,7 @@
   *  worker thread.
   *
   *  The only other requirement of a platform/environment is that it always be
-  *  possible to extract the react rootNodeID in a blocking manner (see
+  *  possible to extract the React rootNodeID in a blocking manner (see
   *  `getRootNodeID`).
   *
   * +------------------+ +------------------+ +------------------+

React/Base/RCTEventDispatcher.h

@@ -50,7 +50,7 @@ typedef NS_ENUM(NSInteger, RCTScrollEventType) {
 
 /**
  * Send a user input event. The body dictionary must contain a "target"
- * parameter, representing the react tag of the view sending the event
+ * parameter, representing the React tag of the view sending the event
  */
 - (void)sendInputEventWithName:(NSString *)name body:(NSDictionary *)body;
 

React/Base/RCTEventDispatcher.m

@@ -44,7 +44,7 @@ RCT_IMPORT_METHOD(RCTEventEmitter, receiveEvent);
 - (void)sendInputEventWithName:(NSString *)name body:(NSDictionary *)body
 {
   RCTAssert([body[@"target"] isKindOfClass:[NSNumber class]],
-    @"Event body dictionary must include a 'target' property containing a react tag");
+    @"Event body dictionary must include a 'target' property containing a React tag");
 
   [_bridge enqueueJSCall:@"RCTEventEmitter.receiveEvent"
                     args:body ? @[body[@"target"], name, body] : @[body[@"target"], name]];

React/Base/RCTRootView.m

@@ -110,11 +110,11 @@ RCT_IMPORT_METHOD(ReactIOS, unmountComponentAtNodeAndRemoveContainer)
   dispatch_async(dispatch_get_main_queue(), ^{
 
     /**
-     * Every root view that is created must have a unique react tag.
+     * Every root view that is created must have a unique React tag.
      * Numbering of these tags goes from 1, 11, 21, 31, etc
      *
      * NOTE: Since the bridge persists, the RootViews might be reused, so now
-     * the react tag is assigned every time we load new content.
+     * the React tag is assigned every time we load new content.
      */
     [_contentView removeFromSuperview];
     _contentView = [[UIView alloc] initWithFrame:self.bounds];

React/Base/RCTTouchHandler.m

@@ -26,7 +26,7 @@
 
   /**
    * Arrays managed in parallel tracking native touch object along with the
-   * native view that was touched, and the react touch data dictionary.
+   * native view that was touched, and the React touch data dictionary.
    * This must be kept track of because `UIKit` destroys the touch targets
    * if touches are canceled and we have no other way to recover this information.
    */

React/Modules/RCTUIManager.m

@@ -661,7 +661,7 @@ RCT_EXPORT_METHOD(manageChildren:(NSNumber *)containerReactTag
 {
   id<RCTViewNodeProtocol> container = registry[containerReactTag];
   RCTAssert(moveFromIndices.count == moveToIndices.count, @"moveFromIndices had size %tu, moveToIndices had size %tu", moveFromIndices.count, moveToIndices.count);
-  RCTAssert(addChildReactTags.count == addAtIndices.count, @"there should be at least one react child to add");
+  RCTAssert(addChildReactTags.count == addAtIndices.count, @"there should be at least one React child to add");
 
   // Removes (both permanent and temporary moves) are using "before" indices
   NSArray *permanentlyRemovedChildren = [self _childrenToRemoveFromContainer:container atIndices:removeAtIndices];
@@ -918,7 +918,7 @@ RCT_EXPORT_METHOD(measure:(NSNumber *)reactTag
     }
 
     // TODO: this doesn't work because sometimes view is inside a modal window
-    // RCTAssert([rootView isReactRootView], @"React view is not inside a react root view");
+    // RCTAssert([rootView isReactRootView], @"React view is not inside a React root view");
 
     // By convention, all coordinates, whether they be touch coordinates, or
     // measurement coordinates are with respect to the root view.
@@ -995,7 +995,7 @@ RCT_EXPORT_METHOD(measureLayoutRelativeToParent:(NSNumber *)reactTag
 }
 
 /**
- * Returns an array of computed offset layouts in a dictionary form. The layouts are of any react subviews
+ * Returns an array of computed offset layouts in a dictionary form. The layouts are of any React subviews
  * that are immediate descendants to the parent view found within a specified rect. The dictionary result
  * contains left, top, width, height and an index. The index specifies the position among the other subviews.
  * Only layouts for views that are within the rect passed in are returned. Invokes the error callback if the

React/Views/RCTNavigator.m

@@ -60,7 +60,7 @@ NSInteger kNeverProgressed = -10000;
  * or tapping the back button. In both cases, the other system is initially
  * unaware. And in both cases, `RCTNavigator` helps the other side "catch up".
  *
- * If `RCTNavigator` sees the number of react children have changed, it
+ * If `RCTNavigator` sees the number of React children have changed, it
  * pushes/pops accordingly. If `RCTNavigator` sees a `UIKit` driven push/pop, it
  * notifies JavaScript that this has happened, and expects that JavaScript will
  * eventually render more children to match `UIKit`. There's no rush for
@@ -474,7 +474,7 @@ NSInteger kNeverProgressed = -10000;
     RCTLogError(@"Cannot adjust current top of stack beyond available views");
   }
 
-  // Views before the previous react count must not have changed. Views greater than previousReactCount
+  // Views before the previous React count must not have changed. Views greater than previousReactCount
   // up to currentReactCount may have changed.
   for (NSInteger i = 0; i < MIN(_currentViews.count, MIN(_previousViews.count, previousReactCount)); i++) {
     if (_currentViews[i] != _previousViews[i]) {

React/Views/RCTViewNodeProtocol.h

@@ -35,7 +35,7 @@
 @end
 
 // TODO: this is kinda dumb - let's come up with a
-// better way of identifying root react views please!
+// better way of identifying root React views please!
 static inline BOOL RCTIsReactRootView(NSNumber *reactTag) {
   return reactTag.integerValue % 10 == 1;
 }