Skip to content

Commit f0c4b80

Browse files
authored
Update new-architecture-app-intro.md (facebook#3938)
Fixed small spelling mistake
1 parent f89ab82 commit f0c4b80

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/new-architecture-app-intro.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ LOG Running "App" with {"fabric":true,"initialProps":{"concurrentRoot": "true"},
9595

9696
If you followed the previous steps but your app uses some custom Native Components that have not been migrated to the New Architecture completely, you are going to see some reddish/pinkish boxes saying that the component is not compatible with Fabric. This is happening because custom Native Components written for the legacy architecture can't run as-is in the New Architecture.
9797

98-
Starting from **React Native `0.72.0`**, we worked on a interoperability layer to let you use legacy components in the New Architecture without having to wait for them to be migrated.
98+
Starting from **React Native `0.72.0`**, we worked on an interoperability layer to let you use legacy components in the New Architecture without having to wait for them to be migrated.
9999

100100
You can read more about the interoperability layer and how to use it [here](https://github.com/reactwg/react-native-new-architecture/discussions/135). Follow this guide to register your components and then rerun your app with the commands:
101101

0 commit comments

Comments
 (0)