Browse Source

Fix small typo in concurrent-mode-adoption.md (#2531)

"You can use in new code" => "You can use them in new code"
main
David Cho-Lerat 5 years ago
committed by GitHub
parent
commit
81681dda2a
No known key found for this signature in database GPG Key ID: 4AEE18F83AFDEB23
  1. 2
      content/docs/concurrent-mode-adoption.md

2
content/docs/concurrent-mode-adoption.md

@ -54,7 +54,7 @@ We're using this code in production (and it works for us) but there are still so
### Enabling Concurrent Mode {#enabling-concurrent-mode}
Normally, when we add features to React, you can start using them immediately. Fragments, Context, and even Hooks are examples of such features. You can use in new code without making any changes to the existing code.
Normally, when we add features to React, you can start using them immediately. Fragments, Context, and even Hooks are examples of such features. You can use them in new code without making any changes to the existing code.
Concurrent Mode is different. It introduces semantic changes to how React works. Otherwise, the [new features](/docs/concurrent-mode-patterns.html) enabled by it *wouldn't be possible*. This is why they're grouped into a new "mode" rather than released one by one in isolation.

Loading…
Cancel
Save