From 25b8121dc0cde26de2a1a7e64621f1887880f719 Mon Sep 17 00:00:00 2001 From: Mert Ciflikli Date: Fri, 10 Sep 2021 12:10:12 +0200 Subject: [PATCH] fix typos --- packages/react-devtools-inline/README.md | 2 +- packages/react-devtools/CONTRIBUTING.md | 2 +- packages/react-devtools/OVERVIEW.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/packages/react-devtools-inline/README.md b/packages/react-devtools-inline/README.md index 35b0127f41d..b7b3f8373ad 100644 --- a/packages/react-devtools-inline/README.md +++ b/packages/react-devtools-inline/README.md @@ -66,7 +66,7 @@ const DevTools = initialize(contentWindow); ### Supporting named hooks -DevTools can display hook "names" for an inspected component, although determining the "names" requires loading the source (and source-maps), parsing the code, and infering the names based on which variables hook values get assigned to. Because the code for this is non-trivial, it's lazy-loaded only if the feature is enabled. +DevTools can display hook "names" for an inspected component, although determining the "names" requires loading the source (and source-maps), parsing the code, and inferring the names based on which variables hook values get assigned to. Because the code for this is non-trivial, it's lazy-loaded only if the feature is enabled. To configure this package to support this functionality, you'll need to provide a prop that dynamically imports the extra functionality: ```js diff --git a/packages/react-devtools/CONTRIBUTING.md b/packages/react-devtools/CONTRIBUTING.md index 3b930220096..ab12117e3c8 100644 --- a/packages/react-devtools/CONTRIBUTING.md +++ b/packages/react-devtools/CONTRIBUTING.md @@ -1,5 +1,5 @@ -Intrested in contributing to React DevTools, but not sure where to start? This is the place! +Interested in contributing to React DevTools, but not sure where to start? This is the place! # Install project dependencies To get started, check out the React repo: diff --git a/packages/react-devtools/OVERVIEW.md b/packages/react-devtools/OVERVIEW.md index d78d0c7f187..70b2c9ba095 100644 --- a/packages/react-devtools/OVERVIEW.md +++ b/packages/react-devtools/OVERVIEW.md @@ -166,7 +166,7 @@ We only send the serialized messages as part of the `inspectElement` event. #### Removing a root -Special case of unmounting an entire root (include its decsendants). This specialized message replaces what would otherwise be a series of remove-node operations. It is currently only used in one case: updating component filters. The primary motivation for this is actually to preserve fiber ids for components that are re-added to the tree after the updated filters have been applied. This preserves mappings between the Fiber (id) and things like error and warning logs. +Special case of unmounting an entire root (include its descendants). This specialized message replaces what would otherwise be a series of remove-node operations. It is currently only used in one case: updating component filters. The primary motivation for this is actually to preserve fiber ids for components that are re-added to the tree after the updated filters have been applied. This preserves mappings between the Fiber (id) and things like error and warning logs. ```js [ @@ -253,7 +253,7 @@ Elements can update frequently, especially in response to things like scrolling ### Deeply nested properties -Even when dealing with a single component, serializing deeply nested properties can be expensive. Because of this, DevTools uses a technique referred to as "dehyration" to only send a shallow copy of the data on initial inspection. DevTools then fills in the missing data on demand as a user expands nested objects or arrays. Filled in paths are remembered (for the currently inspected element) so they are not "dehyrated" again as part of a polling update. +Even when dealing with a single component, serializing deeply nested properties can be expensive. Because of this, DevTools uses a technique referred to as "dehydration" to only send a shallow copy of the data on initial inspection. DevTools then fills in the missing data on demand as a user expands nested objects or arrays. Filled in paths are remembered (for the currently inspected element) so they are not "dehydrated" again as part of a polling update. ### Inspecting hooks