From ee8716166ef543091b48980df209c98a09955247 Mon Sep 17 00:00:00 2001 From: Noel Yoo Date: Sun, 21 Oct 2018 05:12:28 +0900 Subject: [PATCH] Fix typo (#1274) --- content/blog/2018-09-10-introducing-the-react-profiler.md | 2 +- content/blog/2018-10-01-create-react-app-v2.md | 2 +- content/docs/optimizing-performance.md | 2 +- content/docs/reconciliation.md | 2 +- content/tutorial/tutorial.md | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/content/blog/2018-09-10-introducing-the-react-profiler.md b/content/blog/2018-09-10-introducing-the-react-profiler.md index 6fb7fcef..d73131fc 100644 --- a/content/blog/2018-09-10-introducing-the-react-profiler.md +++ b/content/blog/2018-09-10-introducing-the-react-profiler.md @@ -173,7 +173,7 @@ The tracing API is still new and we will cover it in more detail in a future blo ### No profiling data has been recorded for the selected root -If your your application has multiple "roots", you may see the following message after profiling: +If your application has multiple "roots", you may see the following message after profiling: ![No profiling data has been recorded for the selected root](../images/blog/introducing-the-react-profiler/no-profiler-data-multi-root.png) This message indicates that no performance data was recorded for the root that's selected in the "Elements" panel. diff --git a/content/blog/2018-10-01-create-react-app-v2.md b/content/blog/2018-10-01-create-react-app-v2.md index 768c8d88..cfc7c97a 100644 --- a/content/blog/2018-10-01-create-react-app-v2.md +++ b/content/blog/2018-10-01-create-react-app-v2.md @@ -55,7 +55,7 @@ Run `npm install` (or `yarn`, if you use it). **For many projects, this one-line

working here... thanks for all the new functionality 👍

— Stephen Haney (@sdothaney) October 1, 2018
-Here's a few more tips to get you started. +Here are a few more tips to get you started. **When you run `npm start` for the first time after the upgrade,** you'll get a prompt asking about which browsers you'd like to support. Press `y` to accept the default ones. They'll be written to your `package.json` and you can edit them any time. Create React App will use this information to produce smaller or polyfilled CSS bundles depending on whether you target modern browsers or older browsers. diff --git a/content/docs/optimizing-performance.md b/content/docs/optimizing-performance.md index 8d7da359..3e5d8621 100644 --- a/content/docs/optimizing-performance.md +++ b/content/docs/optimizing-performance.md @@ -187,7 +187,7 @@ Currently Chrome, Edge, and IE are the only browsers supporting this feature, bu `react-dom` 16.5+ and `react-native` 0.57+ provide enhanced profiling capabilities in DEV mode with the React DevTools Profiler. An overview of the Profiler can be found in the blog post ["Introducing the React Profiler"](/blog/2018/09/10/introducing-the-react-profiler.html). -A video walk through of the profiler is also [available on YouTube](https://www.youtube.com/watch?v=nySib7ipZdk). +A video walkthrough of the profiler is also [available on YouTube](https://www.youtube.com/watch?v=nySib7ipZdk). If you haven't yet installed the React DevTools, you can find them here: diff --git a/content/docs/reconciliation.md b/content/docs/reconciliation.md index bb39ce8a..4a45aefc 100644 --- a/content/docs/reconciliation.md +++ b/content/docs/reconciliation.md @@ -142,7 +142,7 @@ As a last resort, you can pass an item's index in the array as a key. This can w Reorders can also cause issues with component state when indexes are used as keys. Component instances are updated and reused based on their key. If the key is an index, moving an item changes it. As a result, component state for things like uncontrolled inputs can get mixed up and updated in unexpected ways. -[Here](codepen://reconciliation/index-used-as-key) is an example of the issues that can be caused by using indexes as keys on CodePen, and [here](codepen://reconciliation/no-index-used-as-key) is a updated version of the same example showing how not using indexes as keys will fix these reordering, sorting, and prepending issues. +[Here](codepen://reconciliation/index-used-as-key) is an example of the issues that can be caused by using indexes as keys on CodePen, and [here](codepen://reconciliation/no-index-used-as-key) is an updated version of the same example showing how not using indexes as keys will fix these reordering, sorting, and prepending issues. ## Tradeoffs diff --git a/content/tutorial/tutorial.md b/content/tutorial/tutorial.md index 35028946..10341595 100644 --- a/content/tutorial/tutorial.md +++ b/content/tutorial/tutorial.md @@ -164,7 +164,7 @@ The `ShoppingList` component above only renders built-in DOM components like `