Skip to content

Commit 22ff639

Browse files
authored
address review
1 parent bb8e987 commit 22ff639

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/navigation-lifecycle.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ const TabNavigator = createBottomTabNavigator(
4040

4141
We start on the `HomeScreen` and navigate to `DetailsScreen`. Then we use the tab bar to switch to the `SettingsScreen` and navigate to `ProfileScreen`. After this sequence of operations is done, all 4 of the screens are mounted! If you use the tab bar to switch back to the `HomeStack`, you'll notice you'll be presented with the `DetailsScreen` - the navigation state of the `HomeStack` has been preserved!
4242

43-
## React-Navigation lifecycle events
43+
## React Navigation lifecycle events
4444

4545
Now that we understand how React lifecycle methods work in React Navigation, let's answer the question we asked at the beginning: "How do we find out that a user is leaving it or coming back to it?"
4646

@@ -51,4 +51,4 @@ Many of your use cases may be covered with the [`withNavigationFocus` HOC](with-
5151
## Summary
5252

5353
- while React's lifecycle methods are still valid, React Navigation adds more lifecycle events that you can subscribe to through the `navigation` prop.
54-
- you may also use the `withNavigationFocus` HOC or `<NavigationEvents />` component to react to lifecycle changes
54+
- you may also use the `withNavigationFocus` HOC or `<NavigationEvents />` component to react to lifecycle changes

0 commit comments

Comments
 (0)