From 01ab75665f4305d15206cb97ce1dbf381146eef3 Mon Sep 17 00:00:00 2001 From: Yair Date: Mon, 23 Aug 2021 20:24:37 +0300 Subject: [PATCH] typo fix --- versioned_docs/version-6.x/upgrading-from-5.x.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-6.x/upgrading-from-5.x.md b/versioned_docs/version-6.x/upgrading-from-5.x.md index 5b67ee3933a..9dd1b215456 100755 --- a/versioned_docs/version-6.x/upgrading-from-5.x.md +++ b/versioned_docs/version-6.x/upgrading-from-5.x.md @@ -173,7 +173,7 @@ A common scenario where you should use `merge: true` is if you have a custom tab ### Dropped `dangerously` from `dangerouslyGetParent` and `dangerouslyGetState` -The `dangerouslyGetParent` and `dangerouslyGetState` methods on the `navigation` prop are useful in many scenarios, and sometimes necessary. So we dropped the `dangerously` prefix to make it clear than it's safe to use. Now you can use [`navigation.getParent()`](navigation-prop.md#getparent) and [`navigation.getState()`](navigation-prop.md#getstate). +The `dangerouslyGetParent` and `dangerouslyGetState` methods on the `navigation` prop are useful in many scenarios, and sometimes necessary. So we dropped the `dangerously` prefix to make it clear that it's safe to use. Now you can use [`navigation.getParent()`](navigation-prop.md#getparent) and [`navigation.getState()`](navigation-prop.md#getstate). ### No more `state` property on the `route` prop