Drop dangerously prefix in 5.x docs as well

Author: satya164

versioned_docs/version-5.x/navigation-events.md

@@ -21,7 +21,7 @@ Each callback registered as an event listener receive an event object as its arg
 - `target` - The route key for the screen that should receive the event. For some events, this maybe `undefined` if the event wasn't related to a specific screen.
 - `preventDefault` - For some events, there may be a `preventDefault` method on the event object. Calling this method will prevent the default action performed by the event (such as switching tabs on `tabPress`). Support for preventing actions are only available for certain events like `tabPress` and won't work for all events.
 
-One thing to keep in mind is that you can only listen to events from the immediate parent navigator. For example, if you try to add a listener in a screen is inside a stack that's nested in a tab, it won't get the `tabPress` event. If you need to listen to an event from a parent navigator, you may use `navigation.dangerouslyGetParent()` to get a reference to parent navigator's navigation prop and add a listener.
+One thing to keep in mind is that you can only listen to events from the immediate parent navigator. For example, if you try to add a listener in a screen is inside a stack that's nested in a tab, it won't get the `tabPress` event. If you need to listen to an event from a parent navigator, you may use `navigation.getParent()` to get a reference to parent navigator's navigation prop and add a listener.
 
 There are 2 ways to listen to events:
 

versioned_docs/version-5.x/navigation-prop.md

@@ -325,16 +325,20 @@ Then use it like:
 navigation.dispatch(insertBeforeLast('Home'));
 ```
 
-### `dangerouslyGetParent`
+### `getParent`
 
-This method returns the navigation prop from the parent navigator that the current navigator is nested in. For example, if you have a stack navigator and a tab navigator nested inside the stack, then you can use `dangerouslyGetParent` inside a screen of the tab navigator to get the navigation prop passed from the stack navigator.
+This method returns the navigation prop from the parent navigator that the current navigator is nested in. For example, if you have a stack navigator and a tab navigator nested inside the stack, then you can use `getParent` inside a screen of the tab navigator to get the navigation prop passed from the stack navigator.
 
-This method will return `undefined` if there is no parent navigator. Be sure to always check for `undefined` when using this method.
+It will return `undefined` if there is no parent navigator. Be sure to always check for `undefined` when using this method.
 
-### `dangerouslyGetState`
+This is only available in latest versions of `@react-navigation/native`. Earlier, it was named `dangerouslyGetParent`, which is now deprecated.
+
+### `getState`
 
 > Note: Consider the navigator's state object to be internal and subject to change in a minor release. Avoid using properties from the [navigation state](navigation-state.md) object except `index` and `routes`, unless you really need it. If there is some functionality you cannot achieve without relying on the structure of the state object, please open an issue.
 
 This method returns the state object of the navigator which contains the screen. Getting the navigator state could be useful in very rare situations. You most likely don't need to use this method. If you do, make sure you have a good reason.
 
+This is only available in latest versions of `@react-navigation/native`. Earlier, it was named `dangerouslyGetState`, which is now deprecated.
+
 If you need the state for rendering content, you should use [`useNavigationState`](use-navigation-state.md) instead of this method.

versioned_docs/version-5.x/nesting-navigators.md

@@ -80,11 +80,11 @@ navigation.dispatch(DrawerActions.toggleDrawer());
 
 For example, if you have a stack navigator nested inside a tab navigator, the screens in the stack navigator won't receive the events emitted by the parent tab navigator such as (`tabPress`) when using `navigation.addListener`.
 
-To receive events from parent navigator, you can explicitly listen to parent's events with `navigation.dangerouslyGetParent()`:
+To receive events from parent navigator, you can explicitly listen to parent's events with `navigation.getParent()`:
 
 ```js
 const unsubscribe = navigation
-  .dangerouslyGetParent()
+  .getParent()
   .addListener('tabPress', (e) => {
     // Do something
   });

versioned_docs/version-5.x/stack-actions.md

@@ -39,7 +39,7 @@ navigation.dispatch({
     user: 'jane',
   }),
   source: route.key,
-  target: navigation.dangerouslyGetState().key,
+  target: navigation.getState().key,
 });
 ```
 

versioned_docs/version-5.x/stack-navigator.md

@@ -948,7 +948,7 @@ import { TransitionPresets } from '@react-navigation/stack';
     cardOverlayEnabled: true,
     headerStatusBarHeight:
       navigation
-        .dangerouslyGetState()
+        .getState()
         .routes.findIndex((r) => r.key === route.key) > 0
         ? 0
         : undefined,

versioned_docs/version-5.x/upgrading-from-4.x.md

@@ -496,7 +496,7 @@ See [`pop` action docs](stack-actions.md#pop) for more details.
 The `dismiss` method has been removed. You can achieve similar effect with following:
 
 ```js
-navigation.dangerouslyGetParent().pop();
+navigation.getState().pop();
 ```
 
 ### `jumpTo`

versioned_docs/version-5.x/use-navigation-state.md

@@ -22,13 +22,13 @@ const state = useNavigationState(state => state);
 
 > Note: This hook is useful for advanced cases and it's easy to introduce performance issues if you're not careful. For most of the cases, you don't need the navigator's state.
 
-## How is `useNavigationState` different from `navigation.dangerouslyGetState()`?
+## How is `useNavigationState` different from `navigation.getState()`?
 
-The `navigation.dangerouslyGetState()` function also returns the current [navigation state](navigation-state.md). The main difference is that the `useNavigationState` hook will trigger a re-render when values change, while `navigation.dangerouslyGetState()` won't. For example, the following code will be incorrect:
+The `navigation.getState()` function also returns the current [navigation state](navigation-state.md). The main difference is that the `useNavigationState` hook will trigger a re-render when values change, while `navigation.getState()` won't. For example, the following code will be incorrect:
 
 ```js
 function Profile() {
-  const routesLength = navigation.dangerouslyGetState().routes.length; // Don't do this
+  const routesLength = navigation.getState().routes.length; // Don't do this
 
   return <Text>Number of routes: {routesLength}</Text>;
 }
@@ -46,7 +46,7 @@ function Profile() {
 }
 ```
 
-So when do you use `navigation.dangerouslyGetState()`? It's mostly useful within event listeners where you don't care about what's rendered. In most cases, using the hook should be preferred.
+So when do you use `navigation.getState()`? It's mostly useful within event listeners where you don't care about what's rendered. In most cases, using the hook should be preferred.
 
 ## Using with class component