react-devtools\OVERVIEW.md --> fixed typos (#22372)
BIKI DAS committed
Sep 21, 2021 at 00:39 UTC
c62d5831d3d66c19eb652f4f5d229acb1e85ff82
1 file changed
+2
-2
packages/react-devtools/OVERVIEW.md
+2
-2
@@ -166,7 +166,7 @@ We only send the serialized messages as part of the `inspectElement` event.
166
167
#### Removing a root
168
169
-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.
169
+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.
170
171
```js
172
[
@@ -253,7 +253,7 @@ Elements can update frequently, especially in response to things like scrolling
253
254
### Deeply nested properties
255
256
-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.
256
+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.
257
258
### Inspecting hooks
259