Skip to content

Commit 07a53c7

Browse files
ayunasWoLewicki
authored andcommitted
fix typo in navigation-prop.md (react-navigation#572)
just a grammatical error. Previous : `anything magic here` Propsed change : `any magic here`
1 parent 95124ee commit 07a53c7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/navigation-prop.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ Each `screen` component in your app is provided with the `navigation` prop autom
1616
- `dispatch` - send an action to router
1717
- `dangerouslyGetParent` - function that returns the parent navigator, if any
1818

19-
It's important to highlight the `navigation` prop is _not_ passed in to _all_ components; only `screen` components receive this prop automatically! React Navigation doesn't do anything magic here. For example, if you were to define a `MyBackButton` component and render it as a child of a screen component, you would not be able to access the `navigation` prop on it. If, however, you wish to access the `navigation` prop in any of your components, you may use the [`useNavigation`](use-navigation.md) HOC.
19+
It's important to highlight the `navigation` prop is _not_ passed in to _all_ components; only `screen` components receive this prop automatically! React Navigation doesn't do any magic here. For example, if you were to define a `MyBackButton` component and render it as a child of a screen component, you would not be able to access the `navigation` prop on it. If, however, you wish to access the `navigation` prop in any of your components, you may use the [`useNavigation`](use-navigation.md) HOC.
2020

2121
### Navigator-dependent functions
2222

0 commit comments

Comments
 (0)