diff --git a/Examples/2048/GameBoard.js b/Examples/2048/GameBoard.js index 1d7f34085..6ed92e6b5 100644 --- a/Examples/2048/GameBoard.js +++ b/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; diff --git a/Examples/UIExplorer/UIExplorerUnitTests/LayoutSubviewsOrderingTest.m b/Examples/UIExplorer/UIExplorerUnitTests/LayoutSubviewsOrderingTest.m index fcd796114..39c0404e0 100644 --- a/Examples/UIExplorer/UIExplorerUnitTests/LayoutSubviewsOrderingTest.m +++ b/Examples/UIExplorer/UIExplorerUnitTests/LayoutSubviewsOrderingTest.m @@ -14,7 +14,7 @@ /** * 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 @@ } }] viewDidLayoutSubviews]; - // setup View heirarchy and force layout + // setup View hierarchy and force layout parentVC.view = parentView; childVC.view = childView; [parentVC addChildViewController:childVC]; diff --git a/Examples/UIExplorer/UIExplorerUnitTests/RCTContextExecutorTests.m b/Examples/UIExplorer/UIExplorerUnitTests/RCTContextExecutorTests.m index c1b96b13e..07d1ebfb0 100644 --- a/Examples/UIExplorer/UIExplorerUnitTests/RCTContextExecutorTests.m +++ b/Examples/UIExplorer/UIExplorerUnitTests/RCTContextExecutorTests.m @@ -98,7 +98,7 @@ static uint64_t _get_time_nanoseconds(void) { /** * 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 diff --git a/Examples/UIExplorer/WebViewExample.js b/Examples/UIExplorer/WebViewExample.js index f8183b12b..c8c547f97 100644 --- a/Examples/UIExplorer/WebViewExample.js +++ b/Examples/UIExplorer/WebViewExample.js @@ -148,7 +148,7 @@ var WebViewExample = React.createClass({ url: url, }); } - // dismiss keyoard + // dismiss keyboard this.refs[TEXT_INPUT_REF].blur(); }, diff --git a/Examples/UIExplorer/XHRExample.android.js b/Examples/UIExplorer/XHRExample.android.js index ad4bbf772..0ee51a8e3 100644 --- a/Examples/UIExplorer/XHRExample.android.js +++ b/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. diff --git a/Libraries/Animated/examples/demo.html b/Libraries/Animated/examples/demo.html index bc4c85e1f..4f95e114f 100644 --- a/Libraries/Animated/examples/demo.html +++ b/Libraries/Animated/examples/demo.html @@ -326,7 +326,7 @@ examplify(React.createClass({

Animated 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.

-

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 stopAnimation. It will not suffer from beign out of sync since the animation is no longer running.

+

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 stopAnimation. It will not suffer from being out of sync since the animation is no longer running.