From 201a3d010a821b22e3f17b935de30e23fbad4918 Mon Sep 17 00:00:00 2001 From: Nader Dabit Date: Thu, 10 Dec 2015 17:27:46 -0600 Subject: [PATCH] fixed various spelling errors --- docs/AndroidUIPerformance.md | 2 +- docs/Animations.md | 2 +- docs/DevelopmentSetupAndroid.md | 2 +- docs/LinkingLibraries.md | 2 +- docs/NativeComponentsAndroid.md | 2 +- docs/NavigatorComparison.md | 2 +- docs/RunningOnDeviceAndroid.md | 2 +- 7 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/AndroidUIPerformance.md b/docs/AndroidUIPerformance.md index 399bd09ee..321bb0c46 100644 --- a/docs/AndroidUIPerformance.md +++ b/docs/AndroidUIPerformance.md @@ -41,7 +41,7 @@ Once the trace starts collecting, perform the animation or interaction you care ## Reading the trace -After opening the trace in your browser (preferrably Chrome), you should see something like this: +After opening the trace in your browser (preferably Chrome), you should see something like this: ![Example](/react-native/img/SystraceExample.png) diff --git a/docs/Animations.md b/docs/Animations.md index af9ccf0e9..84c3f4851 100644 --- a/docs/Animations.md +++ b/docs/Animations.md @@ -309,7 +309,7 @@ for more information. familiar with. It accepts a function as its only argument and calls that function before the next repaint. It is an essential building block for animations that underlies all of the JavaScript-based animation APIs. In -general, you shouldn't need to call this yourself - the animation API's will +general, you shouldn't need to call this yourself - the animation APIs will manage frame updates for you. ### react-tween-state (Not recommended - use [Animated](#animated) instead) diff --git a/docs/DevelopmentSetupAndroid.md b/docs/DevelopmentSetupAndroid.md index e7d1f8b36..23bf6a636 100644 --- a/docs/DevelopmentSetupAndroid.md +++ b/docs/DevelopmentSetupAndroid.md @@ -45,7 +45,7 @@ __NOTE__: You need to restart the Command Prompt (Windows) / Terminal Emulator ( ### Use gradle daemon -React Native Android use [gradle](https://docs.gradle.org) as a build system. We recommend to enable gradle daemon functionailty which may result in up to 50% improvement in incremental build times for changes in java code. Learn [here](https://docs.gradle.org/2.9/userguide/gradle_daemon.html) how to enable it for your platform. +React Native Android use [gradle](https://docs.gradle.org) as a build system. We recommend to enable gradle daemon functionality which may result in up to 50% improvement in incremental build times for changes in java code. Learn [here](https://docs.gradle.org/2.9/userguide/gradle_daemon.html) how to enable it for your platform. ### Configure your SDK diff --git a/docs/LinkingLibraries.md b/docs/LinkingLibraries.md index db29a4bc2..c5cf659cf 100644 --- a/docs/LinkingLibraries.md +++ b/docs/LinkingLibraries.md @@ -54,7 +54,7 @@ This step is not necessary for libraries that we ship with React Native with the exception of `PushNotificationIOS` and `LinkingIOS`. In the case of the `PushNotificationIOS` for example, you have to call a method -on the library from your `AppDelegate` every time a new push notifiation is +on the library from your `AppDelegate` every time a new push notification is received. For that we need to know the library's headers. To achieve that you have to go diff --git a/docs/NativeComponentsAndroid.md b/docs/NativeComponentsAndroid.md index f70c32ee6..3e729e18b 100644 --- a/docs/NativeComponentsAndroid.md +++ b/docs/NativeComponentsAndroid.md @@ -57,7 +57,7 @@ Views are created in the `createViewInstance` method, the view should initialize ## 3. Expose view property setters using `@ReactProp` (or `@ReactPropGroup`) annotation -Properties that are to be reflected in JavaScript needs to be exposed as setter method annotated with `@ReactProp` (or `@ReactPropGroup`). Setter method should take view to be updated (of the current view type) as a first argument and property value as a second argument. Setter should be declared as a `void` method and should be `public`. Property type sent to JS is determined automatically based on the type of value argumen of the setter. The following type of values are currently supported: `boolean`, `int`, `float`, `double`, `String`, `Boolean`, `Integer`, `ReadableArray`, `ReadableMap`. +Properties that are to be reflected in JavaScript needs to be exposed as setter method annotated with `@ReactProp` (or `@ReactPropGroup`). Setter method should take view to be updated (of the current view type) as a first argument and property value as a second argument. Setter should be declared as a `void` method and should be `public`. Property type sent to JS is determined automatically based on the type of value argument of the setter. The following type of values are currently supported: `boolean`, `int`, `float`, `double`, `String`, `Boolean`, `Integer`, `ReadableArray`, `ReadableMap`. Annotation `@ReactProp` has one obligatory argument `name` of type `String`. Name assigned to the `@ReactProp` annotation linked to the setter method is used to reference the property on JS side. diff --git a/docs/NavigatorComparison.md b/docs/NavigatorComparison.md index 326ef98d1..cc6c5c6c8 100644 --- a/docs/NavigatorComparison.md +++ b/docs/NavigatorComparison.md @@ -41,7 +41,7 @@ between the two. - Development belongs to open-source community - not used by the React Native team on their apps. - A result of this is that there is currently a backlog of unresolved bugs, nobody who uses this has stepped up to take ownership for it yet. - Wraps UIKit, so it works exactly the same as it would on another native app. Lives in Objective-C and JavaScript. - - Consequently, you get the animations and behaviour that Apple has developed. + - Consequently, you get the animations and behavior that Apple has developed. - iOS only. - Includes a navigation bar by default; this navigation bar is not a React Native view component and the style can only be slightly modified. diff --git a/docs/RunningOnDeviceAndroid.md b/docs/RunningOnDeviceAndroid.md index 08bc5f8da..1b64faf22 100644 --- a/docs/RunningOnDeviceAndroid.md +++ b/docs/RunningOnDeviceAndroid.md @@ -20,7 +20,7 @@ Check that your device has been **successfully connected** by running `adb devic Seeing **device** in the right column means the device is connected. Android - go figure :) You must have **only one device connected**. -Now you can use `react-native run-android` to install and lauch your app on the device. +Now you can use `react-native run-android` to install and launch your app on the device. ## Accessing development server from device