From be8b2b91d5b14e31a58afa03b0b2b3557c12c41d Mon Sep 17 00:00:00 2001 From: Sean Coyle Date: Wed, 7 Aug 2024 16:31:39 -0500 Subject: [PATCH] Docs: Upgrade verbiage --- versioned_docs/version-7.x/upgrading-from-6.x.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-7.x/upgrading-from-6.x.md b/versioned_docs/version-7.x/upgrading-from-6.x.md index f420e57494..ebc58e6d7c 100755 --- a/versioned_docs/version-7.x/upgrading-from-6.x.md +++ b/versioned_docs/version-7.x/upgrading-from-6.x.md @@ -27,7 +27,7 @@ Due to backward compatibility reasons, React Navigation 5 and 6 support navigati Due to these issues, we have a special API to navigate to a nested screen (`navigation.navigate(ParentScreenName, { screen: ScreenName })`). -From these release, this is no longer the default behavior. If you're relying on this behavior in your app, you can pass the [`navigationInChildEnabled`](navigation-container.md#navigationinchildenabled) prop to `NavigationContainer` to keep the behavior until you are able to migrate: +From this release moving forward, this is no longer the default behavior. If you're relying on this behavior in your app, you can pass the [`navigationInChildEnabled`](navigation-container.md#navigationinchildenabled) prop to `NavigationContainer` to keep the behavior until you are able to migrate: ```jsx {/* ... */}