From e5e490b6fc496558de66a0613e17ec7d7888ffc3 Mon Sep 17 00:00:00 2001
From: stanleyoos <stanislaw.sarka@gmail.com>
Date: Wed, 7 Aug 2024 15:06:52 +0200
Subject: [PATCH 1/3] docs: Fixed swapped button titles

---
 static/examples/5.x/stack-actions.js        |  8 +++---
 static/examples/6.x/stack-actions.js        |  8 +++---
 static/examples/7.x/stack-actions.js        |  8 +++---
 versioned_docs/version-7.x/stack-actions.md | 32 ++++++++++-----------
 4 files changed, 28 insertions(+), 28 deletions(-)

diff --git a/static/examples/5.x/stack-actions.js b/static/examples/5.x/stack-actions.js
index d0323202a3a..fca2fcccb8a 100755
--- a/static/examples/5.x/stack-actions.js
+++ b/static/examples/5.x/stack-actions.js
@@ -1,7 +1,7 @@
-import * as React from 'react';
-import { View, Button, Text } from 'react-native';
 import { NavigationContainer, StackActions } from '@react-navigation/native';
 import { createStackNavigator } from '@react-navigation/stack';
+import * as React from 'react';
+import { Button, Text, View } from 'react-native';
 
 function HomeScreen({ navigation }) {
   return (
@@ -31,11 +31,11 @@ function ProfileScreen({ navigation, route }) {
       <Text>Profile!</Text>
       <Text>{route.params.user}'s profile</Text>
       <Button
-        title="Push same screen on the stack"
+        title="Pop one screen from stack"
         onPress={() => navigation.dispatch(StackActions.pop(1))}
       />
       <Button
-        title="Pop one screen from stack"
+        title="Push same screen on the stack"
         onPress={() =>
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }))
         }
diff --git a/static/examples/6.x/stack-actions.js b/static/examples/6.x/stack-actions.js
index d0323202a3a..fca2fcccb8a 100755
--- a/static/examples/6.x/stack-actions.js
+++ b/static/examples/6.x/stack-actions.js
@@ -1,7 +1,7 @@
-import * as React from 'react';
-import { View, Button, Text } from 'react-native';
 import { NavigationContainer, StackActions } from '@react-navigation/native';
 import { createStackNavigator } from '@react-navigation/stack';
+import * as React from 'react';
+import { Button, Text, View } from 'react-native';
 
 function HomeScreen({ navigation }) {
   return (
@@ -31,11 +31,11 @@ function ProfileScreen({ navigation, route }) {
       <Text>Profile!</Text>
       <Text>{route.params.user}'s profile</Text>
       <Button
-        title="Push same screen on the stack"
+        title="Pop one screen from stack"
         onPress={() => navigation.dispatch(StackActions.pop(1))}
       />
       <Button
-        title="Pop one screen from stack"
+        title="Push same screen on the stack"
         onPress={() =>
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }))
         }
diff --git a/static/examples/7.x/stack-actions.js b/static/examples/7.x/stack-actions.js
index d0323202a3a..fca2fcccb8a 100755
--- a/static/examples/7.x/stack-actions.js
+++ b/static/examples/7.x/stack-actions.js
@@ -1,7 +1,7 @@
-import * as React from 'react';
-import { View, Button, Text } from 'react-native';
 import { NavigationContainer, StackActions } from '@react-navigation/native';
 import { createStackNavigator } from '@react-navigation/stack';
+import * as React from 'react';
+import { Button, Text, View } from 'react-native';
 
 function HomeScreen({ navigation }) {
   return (
@@ -31,11 +31,11 @@ function ProfileScreen({ navigation, route }) {
       <Text>Profile!</Text>
       <Text>{route.params.user}'s profile</Text>
       <Button
-        title="Push same screen on the stack"
+        title="Pop one screen from stack"
         onPress={() => navigation.dispatch(StackActions.pop(1))}
       />
       <Button
-        title="Pop one screen from stack"
+        title="Push same screen on the stack"
         onPress={() =>
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }))
         }
diff --git a/versioned_docs/version-7.x/stack-actions.md b/versioned_docs/version-7.x/stack-actions.md
index 93fa71ec3a6..7e6aa252102 100755
--- a/versioned_docs/version-7.x/stack-actions.md
+++ b/versioned_docs/version-7.x/stack-actions.md
@@ -66,14 +66,14 @@ function ProfileScreen({ route }) {
       <Text>Profile!</Text>
       <Text>{route.params.user}'s profile</Text>
       <Button onPress={() => navigation.dispatch(StackActions.pop(1))}>
-        Push same screen on the stack
+        Pop one screen from stack
       </Button>
       <Button
         onPress={() => {
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }));
         }}
       >
-        Pop one screen from stack
+        Push same screen on the stack
       </Button>
       <Button onPress={() => navigation.dispatch(StackActions.popToTop())}>
         Pop to top
@@ -142,14 +142,14 @@ function ProfileScreen({ navigation, route }) {
       <Text>Profile!</Text>
       <Text>{route.params.user}'s profile</Text>
       <Button onPress={() => navigation.dispatch(StackActions.pop(1))}>
-        Push same screen on the stack
+         Pop one screen from stack
       </Button>
       <Button
         onPress={() => {
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }));
         }}
       >
-        Pop one screen from stack
+       Push same screen on the stack
       </Button>
       <Button onPress={() => navigation.dispatch(StackActions.popToTop())}>
         Pop to top
@@ -246,14 +246,14 @@ function ProfileScreen({ route }) {
       <Text>Profile!</Text>
       <Text>{route.params.user}'s profile</Text>
       <Button onPress={() => navigation.dispatch(StackActions.pop(1))}>
-        Push same screen on the stack
+        Pop one screen from stack
       </Button>
       <Button
         onPress={() => {
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }));
         }}
       >
-        Pop one screen from stack
+        Push same screen on the stack
       </Button>
       <Button onPress={() => navigation.dispatch(StackActions.popToTop())}>
         Pop to top
@@ -322,14 +322,14 @@ function ProfileScreen({ navigation, route }) {
       <Text>Profile!</Text>
       <Text>{route.params.user}'s profile</Text>
       <Button onPress={() => navigation.dispatch(StackActions.pop(1))}>
-        Push same screen on the stack
+        Pop one screen from stack
       </Button>
       <Button
         onPress={() => {
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }));
         }}
       >
-        Pop one screen from stack
+        Push same screen on the stack
       </Button>
       <Button onPress={() => navigation.dispatch(StackActions.popToTop())}>
         Pop to top
@@ -411,14 +411,14 @@ function ProfileScreen({ route }) {
           // codeblock-focus-end
         }}
       >
-        Push same screen on the stack
+      Pop one screen from stack
       </Button>
       <Button
         onPress={() => {
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }));
         }}
       >
-        Pop one screen from stack
+      Push same screen on the stack
       </Button>
       <Button onPress={() => navigation.dispatch(StackActions.popToTop())}>
         Pop to top
@@ -491,14 +491,14 @@ function ProfileScreen({ navigation, route }) {
           // codeblock-focus-end
         }}
       >
-        Push same screen on the stack
+        Pop one screen from stack
       </Button>
       <Button
         onPress={() => {
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }));
         }}
       >
-        Pop one screen from stack
+        Push same screen on the stack
       </Button>
       <Button onPress={() => navigation.dispatch(StackActions.popToTop())}>
         Pop to top
@@ -593,14 +593,14 @@ function ProfileScreen({ route }) {
       <Text>Profile!</Text>
       <Text>{route.params.user}'s profile</Text>
       <Button onPress={() => navigation.dispatch(StackActions.pop(1))}>
-        Push same screen on the stack
+       Pop one screen from stack
       </Button>
       <Button
         onPress={() => {
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }));
         }}
       >
-        Pop one screen from stack
+        Push same screen on the stack
       </Button>
       <Button
         onPress={() => {
@@ -673,14 +673,14 @@ function ProfileScreen({ navigation, route }) {
       <Text>Profile!</Text>
       <Text>{route.params.user}'s profile</Text>
       <Button onPress={() => navigation.dispatch(StackActions.pop(1))}>
-        Push same screen on the stack
+        Pop one screen from stack
       </Button>
       <Button
         onPress={() => {
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }));
         }}
       >
-        Pop one screen from stack
+        Push same screen on the stack
       </Button>
       <Button
         onPress={() => {

From 63243e1e75baa1fc19d262e1e23b53ae2fd7ed2a Mon Sep 17 00:00:00 2001
From: "autofix-ci[bot]" <114827586+autofix-ci[bot]@users.noreply.github.com>
Date: Wed, 7 Aug 2024 13:09:59 +0000
Subject: [PATCH 2/3] [autofix.ci] apply automated fixes

---
 versioned_docs/version-7.x/stack-actions.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/versioned_docs/version-7.x/stack-actions.md b/versioned_docs/version-7.x/stack-actions.md
index 7e6aa252102..28215aaf847 100755
--- a/versioned_docs/version-7.x/stack-actions.md
+++ b/versioned_docs/version-7.x/stack-actions.md
@@ -142,14 +142,14 @@ function ProfileScreen({ navigation, route }) {
       <Text>Profile!</Text>
       <Text>{route.params.user}'s profile</Text>
       <Button onPress={() => navigation.dispatch(StackActions.pop(1))}>
-         Pop one screen from stack
+        Pop one screen from stack
       </Button>
       <Button
         onPress={() => {
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }));
         }}
       >
-       Push same screen on the stack
+        Push same screen on the stack
       </Button>
       <Button onPress={() => navigation.dispatch(StackActions.popToTop())}>
         Pop to top
@@ -411,14 +411,14 @@ function ProfileScreen({ route }) {
           // codeblock-focus-end
         }}
       >
-      Pop one screen from stack
+        Pop one screen from stack
       </Button>
       <Button
         onPress={() => {
           navigation.dispatch(StackActions.push('Profile', { user: 'Wojtek' }));
         }}
       >
-      Push same screen on the stack
+        Push same screen on the stack
       </Button>
       <Button onPress={() => navigation.dispatch(StackActions.popToTop())}>
         Pop to top
@@ -593,7 +593,7 @@ function ProfileScreen({ route }) {
       <Text>Profile!</Text>
       <Text>{route.params.user}'s profile</Text>
       <Button onPress={() => navigation.dispatch(StackActions.pop(1))}>
-       Pop one screen from stack
+        Pop one screen from stack
       </Button>
       <Button
         onPress={() => {

From 60a12a592d619a26c95ab5edad4fad32f54bd72c Mon Sep 17 00:00:00 2001
From: stanleyoos <stanislaw.sarka@gmail.com>
Date: Wed, 7 Aug 2024 15:30:42 +0200
Subject: [PATCH 3/3] docs: Updated React Context's link

---
 versioned_docs/version-3.x/localization.md           | 2 +-
 versioned_docs/version-3.x/tab-based-navigation.md   | 2 +-
 versioned_docs/version-4.x/localization.md           | 2 +-
 versioned_docs/version-4.x/stack-navigator.md        | 2 +-
 versioned_docs/version-4.x/tab-based-navigation.md   | 2 +-
 versioned_docs/version-4.x/themes.md                 | 2 +-
 versioned_docs/version-5.x/bottom-tab-navigator.md   | 2 +-
 versioned_docs/version-5.x/configuring-links.md      | 2 +-
 versioned_docs/version-5.x/getting-started.md        | 2 +-
 versioned_docs/version-5.x/hello-react-navigation.md | 2 +-
 versioned_docs/version-5.x/nesting-navigators.md     | 2 +-
 versioned_docs/version-5.x/screen.md                 | 2 +-
 versioned_docs/version-5.x/stack-navigator.md        | 2 +-
 versioned_docs/version-5.x/tab-based-navigation.md   | 2 +-
 versioned_docs/version-5.x/upgrading-from-4.x.md     | 2 +-
 versioned_docs/version-6.x/bottom-tab-navigator.md   | 2 +-
 versioned_docs/version-6.x/configuring-links.md      | 2 +-
 versioned_docs/version-6.x/elements.md               | 2 +-
 versioned_docs/version-6.x/hello-react-navigation.md | 2 +-
 versioned_docs/version-6.x/native-stack-navigator.md | 2 +-
 versioned_docs/version-6.x/nesting-navigators.md     | 2 +-
 versioned_docs/version-6.x/screen.md                 | 2 +-
 versioned_docs/version-6.x/tab-based-navigation.md   | 2 +-
 versioned_docs/version-7.x/configuring-links.md      | 2 +-
 versioned_docs/version-7.x/elements.md               | 2 +-
 versioned_docs/version-7.x/hello-react-navigation.md | 2 +-
 versioned_docs/version-7.x/native-stack-navigator.md | 2 +-
 versioned_docs/version-7.x/nesting-navigators.md     | 2 +-
 versioned_docs/version-7.x/screen.md                 | 2 +-
 versioned_docs/version-7.x/tab-based-navigation.md   | 2 +-
 30 files changed, 30 insertions(+), 30 deletions(-)

diff --git a/versioned_docs/version-3.x/localization.md b/versioned_docs/version-3.x/localization.md
index 34a7e6b53d6..ebe03a8851a 100644
--- a/versioned_docs/version-3.x/localization.md
+++ b/versioned_docs/version-3.x/localization.md
@@ -100,4 +100,4 @@ class Screen extends React.Component {
 }
 ```
 
-You can run this example in [this Snack](https://snack.expo.io/@react-navigation/localization-example). Again, you may want to go further than just passing this through `screenProps` if you want to make it easier to access the `t` function or the other `screenProps` from any React component (and not just screen components that are rendered by React Navigation). Refer to [themes](themes.md) and the [React documentation on context](https://reactjs.org/docs/context.html) for help with that.
+You can run this example in [this Snack](https://snack.expo.io/@react-navigation/localization-example). Again, you may want to go further than just passing this through `screenProps` if you want to make it easier to access the `t` function or the other `screenProps` from any React component (and not just screen components that are rendered by React Navigation). Refer to [themes](themes.md) and the [React documentation on context](https://react.dev/reference/react/useContext) for help with that.
diff --git a/versioned_docs/version-3.x/tab-based-navigation.md b/versioned_docs/version-3.x/tab-based-navigation.md
index ffb9ad788d4..84eb86469c0 100644
--- a/versioned_docs/version-3.x/tab-based-navigation.md
+++ b/versioned_docs/version-3.x/tab-based-navigation.md
@@ -133,7 +133,7 @@ export default class IconWithBadge extends React.Component {
 }
 ```
 
-From UI perspective this component is ready to use, but you still need to find some way to pass down the badge count properly from somewhere else, like using [React Context](https://reactjs.org/docs/context.html), [Redux](https://redux.js.org/), [MobX](https://mobx.js.org/) or [event emitters](https://github.com/facebook/react-native/blob/master/Libraries/vendor/emitter/EventEmitter.js).
+From UI perspective this component is ready to use, but you still need to find some way to pass down the badge count properly from somewhere else, like using [React Context](https://react.dev/reference/react/useContext), [Redux](https://redux.js.org/), [MobX](https://mobx.js.org/) or [event emitters](https://github.com/facebook/react-native/blob/master/Libraries/vendor/emitter/EventEmitter.js).
 
 ```js
 const HomeIconWithBadge = (props) => {
diff --git a/versioned_docs/version-4.x/localization.md b/versioned_docs/version-4.x/localization.md
index 34a7e6b53d6..ebe03a8851a 100644
--- a/versioned_docs/version-4.x/localization.md
+++ b/versioned_docs/version-4.x/localization.md
@@ -100,4 +100,4 @@ class Screen extends React.Component {
 }
 ```
 
-You can run this example in [this Snack](https://snack.expo.io/@react-navigation/localization-example). Again, you may want to go further than just passing this through `screenProps` if you want to make it easier to access the `t` function or the other `screenProps` from any React component (and not just screen components that are rendered by React Navigation). Refer to [themes](themes.md) and the [React documentation on context](https://reactjs.org/docs/context.html) for help with that.
+You can run this example in [this Snack](https://snack.expo.io/@react-navigation/localization-example). Again, you may want to go further than just passing this through `screenProps` if you want to make it easier to access the `t` function or the other `screenProps` from any React component (and not just screen components that are rendered by React Navigation). Refer to [themes](themes.md) and the [React documentation on context](https://react.dev/reference/react/useContext) for help with that.
diff --git a/versioned_docs/version-4.x/stack-navigator.md b/versioned_docs/version-4.x/stack-navigator.md
index b7983ddfd96..6f41c49aa54 100644
--- a/versioned_docs/version-4.x/stack-navigator.md
+++ b/versioned_docs/version-4.x/stack-navigator.md
@@ -248,7 +248,7 @@ This is useful if you want to render a semi-transparent header or a blurred back
 
 Note that if you don't want your content to appear under the header, you need to manually add a top margin to your content. React Navigation won't do it automatically.
 
-To get the height of the header, you can use `HeaderHeightContext` with [React's Context API](https://reactjs.org/docs/context.html#contextconsumer) or `useHeaderHeight`:
+To get the height of the header, you can use `HeaderHeightContext` with [React's Context API](https://react.dev/reference/react/useContext#contextconsumer) or `useHeaderHeight`:
 
 ```js
 import { HeaderHeightContext } from 'react-navigation-stack';
diff --git a/versioned_docs/version-4.x/tab-based-navigation.md b/versioned_docs/version-4.x/tab-based-navigation.md
index f4f47b576a1..da931ae6c4e 100644
--- a/versioned_docs/version-4.x/tab-based-navigation.md
+++ b/versioned_docs/version-4.x/tab-based-navigation.md
@@ -137,7 +137,7 @@ export default class IconWithBadge extends React.Component {
 }
 ```
 
-From UI perspective this component is ready to use, but you still need to find some way to pass down the badge count properly from somewhere else, like using [React Context](https://reactjs.org/docs/context.html), [Redux](https://redux.js.org/), [MobX](https://mobx.js.org/) or [event emitters](https://github.com/facebook/react-native/blob/master/Libraries/vendor/emitter/EventEmitter.js).
+From UI perspective this component is ready to use, but you still need to find some way to pass down the badge count properly from somewhere else, like using [React Context](https://react.dev/reference/react/useContext), [Redux](https://redux.js.org/), [MobX](https://mobx.js.org/) or [event emitters](https://github.com/facebook/react-native/blob/master/Libraries/vendor/emitter/EventEmitter.js).
 
 ```js
 const HomeIconWithBadge = (props) => {
diff --git a/versioned_docs/version-4.x/themes.md b/versioned_docs/version-4.x/themes.md
index 7c92af05888..3d3d310f52e 100644
--- a/versioned_docs/version-4.x/themes.md
+++ b/versioned_docs/version-4.x/themes.md
@@ -245,7 +245,7 @@ You may want more control than what you're given with just the built-in themes.
 
 Building custom themes into an app with React Navigation is not too much different than a React app without it; the main differences are that you will need to use `screenProps` in order to update style properties controlled by `navigationOptions`, and when style properties are controlled in navigator configuration we'll need to take another approach. First we're going to recap how you would theme a React app without React Navigation, then we will dive deeper into these differences. Additionally, this guide assumes that you are already comfortable with React Navigation, in particular how to use and configure navigators.
 
-React's context API allows you to share state from an ancestor component to any of its descendants without explicitly passing the value through layers and layers of components ("prop drilling"). This is a useful tool in order to build themes because we can define the theme at the root of the app, and then access it from anywhere else and re-render every themed component whenever the theme changes. If you are not familiar with how to use context already, you might want to read the [React documentation](https://reactjs.org/docs/context.html) for it before continuing.
+React's context API allows you to share state from an ancestor component to any of its descendants without explicitly passing the value through layers and layers of components ("prop drilling"). This is a useful tool in order to build themes because we can define the theme at the root of the app, and then access it from anywhere else and re-render every themed component whenever the theme changes. If you are not familiar with how to use context already, you might want to read the [React documentation](https://react.dev/reference/react/useContext) for it before continuing.
 
 ```jsx
 import * as React from 'react';
diff --git a/versioned_docs/version-5.x/bottom-tab-navigator.md b/versioned_docs/version-5.x/bottom-tab-navigator.md
index 99aefc35a01..5e901aee713 100755
--- a/versioned_docs/version-5.x/bottom-tab-navigator.md
+++ b/versioned_docs/version-5.x/bottom-tab-navigator.md
@@ -247,7 +247,7 @@ style: {
 
 You also might need to add a bottom margin to your content if you have a absolutely positioned tab bar. React Navigation won't do it automatically.
 
-To get the height of the bottom tab bar, you can use `BottomTabBarHeightContext` with [React's Context API](https://reactjs.org/docs/context.html#contextconsumer) or `useBottomTabBarHeight`:
+To get the height of the bottom tab bar, you can use `BottomTabBarHeightContext` with [React's Context API](https://react.dev/reference/react/useContext#contextconsumer) or `useBottomTabBarHeight`:
 
 ```js
 import { BottomTabBarHeightContext } from '@react-navigation/bottom-tabs';
diff --git a/versioned_docs/version-5.x/configuring-links.md b/versioned_docs/version-5.x/configuring-links.md
index 4542bece964..a5c7d061766 100644
--- a/versioned_docs/version-5.x/configuring-links.md
+++ b/versioned_docs/version-5.x/configuring-links.md
@@ -446,7 +446,7 @@ It's not possible to pass params to the initial screen through the URL. So make
 
 In this case, any params in the URL are only passed to the `Profile` screen which matches the path pattern `users/:id`, and the `Feed` screen doesn't receive any params. If you want to have the same params in the `Feed` screen, you can specify a [custom `getStateFromPath` function](navigation-container.md#linkinggetstatefrompath) and copy those params.
 
-Similarly, if you want to access params of a parent screen from a child screen, you can use [React Context](https://reactjs.org/docs/context.html) to expose them.
+Similarly, if you want to access params of a parent screen from a child screen, you can use [React Context](https://react.dev/reference/react/useContext) to expose them.
 
 ## Matching exact paths
 
diff --git a/versioned_docs/version-5.x/getting-started.md b/versioned_docs/version-5.x/getting-started.md
index 5cead6283ab..68ac0ac6ae2 100755
--- a/versioned_docs/version-5.x/getting-started.md
+++ b/versioned_docs/version-5.x/getting-started.md
@@ -15,7 +15,7 @@ Here are some resources to help you out:
 1. [React Native Express](http://reactnativeexpress.com/) (Sections 1 to 4)
 2. [Main Concepts of React](https://reactjs.org/docs/hello-world.html)
 3. [React Hooks](https://reactjs.org/docs/hooks-intro.html)
-4. [React Context](https://reactjs.org/docs/context.html) (Advanced)
+4. [React Context](https://react.dev/reference/react/useContext) (Advanced)
 
 ## Installation
 
diff --git a/versioned_docs/version-5.x/hello-react-navigation.md b/versioned_docs/version-5.x/hello-react-navigation.md
index 22c55b7fa96..57bf8357f8d 100755
--- a/versioned_docs/version-5.x/hello-react-navigation.md
+++ b/versioned_docs/version-5.x/hello-react-navigation.md
@@ -122,7 +122,7 @@ Sometimes we will want to specify the same options for all of the screens in the
 
 Sometimes we might want to pass additional props to a screen. We can do that with 2 approaches:
 
-1. Use [React context](https://reactjs.org/docs/context.html) and wrap the navigator with a context provider to pass data to the screens (recommended).
+1. Use [React context](https://react.dev/reference/react/useContext) and wrap the navigator with a context provider to pass data to the screens (recommended).
 2. Use a render callback for the screen instead of specifying a `component` prop:
 
    ```js
diff --git a/versioned_docs/version-5.x/nesting-navigators.md b/versioned_docs/version-5.x/nesting-navigators.md
index 5aa410f5cfd..6537501e3b0 100755
--- a/versioned_docs/version-5.x/nesting-navigators.md
+++ b/versioned_docs/version-5.x/nesting-navigators.md
@@ -60,7 +60,7 @@ If you want to achieve this behavior, see the guide for [screen options with nes
 
 For example, any `params` passed to a screen in a nested navigator are in the `route` prop of that screen and aren't accessible from a screen in a parent or child navigator.
 
-If you need to access params of the parent screen from a child screen, you can use [React Context](https://reactjs.org/docs/context.html) to expose params to children.
+If you need to access params of the parent screen from a child screen, you can use [React Context](https://react.dev/reference/react/useContext) to expose params to children.
 
 ### Navigation actions are handled by current navigator and bubble up if couldn't be handled
 
diff --git a/versioned_docs/version-5.x/screen.md b/versioned_docs/version-5.x/screen.md
index 7d196003506..23243f84175 100644
--- a/versioned_docs/version-5.x/screen.md
+++ b/versioned_docs/version-5.x/screen.md
@@ -130,6 +130,6 @@ Render callback to return React Element to use for the screen:
 </Stack.Screen>
 ```
 
-You can use this approach instead of the `component` prop if you need to pass additional props. Though we recommend using [React context](https://reactjs.org/docs/context.html) for passing data instead.
+You can use this approach instead of the `component` prop if you need to pass additional props. Though we recommend using [React context](https://react.dev/reference/react/useContext) for passing data instead.
 
 > Note: By default, React Navigation applies optimizations to screen components to prevent unnecessary renders. Using a render callback removes those optimizations. So if you use a render callback, you'll need to ensure that you use [`React.memo`](https://reactjs.org/docs/react-api.html#reactmemo) or [`React.PureComponent`](https://reactjs.org/docs/react-api.html#reactpurecomponent) for your screen components to avoid performance issues.
diff --git a/versioned_docs/version-5.x/stack-navigator.md b/versioned_docs/version-5.x/stack-navigator.md
index 73071371465..076577a41f4 100755
--- a/versioned_docs/version-5.x/stack-navigator.md
+++ b/versioned_docs/version-5.x/stack-navigator.md
@@ -285,7 +285,7 @@ This is useful if you want to render a semi-transparent header or a blurred back
 
 Note that if you don't want your content to appear under the header, you need to manually add a top margin to your content. React Navigation won't do it automatically.
 
-To get the height of the header, you can use `HeaderHeightContext` with [React's Context API](https://reactjs.org/docs/context.html#contextconsumer) or `useHeaderHeight`:
+To get the height of the header, you can use `HeaderHeightContext` with [React's Context API](https://react.dev/reference/react/useContext#contextconsumer) or `useHeaderHeight`:
 
 ```js
 import { HeaderHeightContext } from '@react-navigation/stack';
diff --git a/versioned_docs/version-5.x/tab-based-navigation.md b/versioned_docs/version-5.x/tab-based-navigation.md
index d9634264ef4..acc4e901e12 100755
--- a/versioned_docs/version-5.x/tab-based-navigation.md
+++ b/versioned_docs/version-5.x/tab-based-navigation.md
@@ -116,7 +116,7 @@ Sometimes we want to add badges to some icons. You can use the [`tabBarBadge` op
 <Tab.Screen name="Home" component={HomeScreen} options={{ tabBarBadge: 3 }} />
 ```
 
-From UI perspective this component is ready to use, but you still need to find some way to pass down the badge count properly from somewhere else, like using [React Context](https://reactjs.org/docs/context.html), [Redux](https://redux.js.org/), [MobX](https://mobx.js.org/) or [event emitters](https://github.com/facebook/react-native/blob/master/Libraries/vendor/emitter/EventEmitter.js).
+From UI perspective this component is ready to use, but you still need to find some way to pass down the badge count properly from somewhere else, like using [React Context](https://react.dev/reference/react/useContext), [Redux](https://redux.js.org/), [MobX](https://mobx.js.org/) or [event emitters](https://github.com/facebook/react-native/blob/master/Libraries/vendor/emitter/EventEmitter.js).
 
 ![Tabs with badges](/assets/navigators/tabs/tabs-badges.png)
 
diff --git a/versioned_docs/version-5.x/upgrading-from-4.x.md b/versioned_docs/version-5.x/upgrading-from-4.x.md
index d44e41d1ae3..0028c656e0d 100755
--- a/versioned_docs/version-5.x/upgrading-from-4.x.md
+++ b/versioned_docs/version-5.x/upgrading-from-4.x.md
@@ -383,7 +383,7 @@ However, using `screenProps` had some disadvantages:
 - When using a type-checker like TypeScript, it was necessary to annotate `screenProps` every time we want to use it, which wasn't type-safe or convenient.
 - You could only access `screenProps` in screens. To access them in child components, you needed to pass them down as props manually. It's very inconvenient for things like translation where we often use it in a lot of components.
 
-Due to the component based API of React Navigation 5.x, we have a much better alternative to `screenProps` which doesn't have these disadvantages: [React Context](https://reactjs.org/docs/context.html). Using React Context, it's possible to pass data to any child component in a performant and type-safe way, and we don't need to learn a new API!
+Due to the component based API of React Navigation 5.x, we have a much better alternative to `screenProps` which doesn't have these disadvantages: [React Context](https://react.dev/reference/react/useContext). Using React Context, it's possible to pass data to any child component in a performant and type-safe way, and we don't need to learn a new API!
 
 ## Themes
 
diff --git a/versioned_docs/version-6.x/bottom-tab-navigator.md b/versioned_docs/version-6.x/bottom-tab-navigator.md
index 17d190ee37d..de8f09de5ed 100755
--- a/versioned_docs/version-6.x/bottom-tab-navigator.md
+++ b/versioned_docs/version-6.x/bottom-tab-navigator.md
@@ -273,7 +273,7 @@ To show your screen under the tab bar, you can set the `position` style to absol
 
 You also might need to add a bottom margin to your content if you have a absolutely positioned tab bar. React Navigation won't do it automatically.
 
-To get the height of the bottom tab bar, you can use `BottomTabBarHeightContext` with [React's Context API](https://reactjs.org/docs/context.html#contextconsumer) or `useBottomTabBarHeight`:
+To get the height of the bottom tab bar, you can use `BottomTabBarHeightContext` with [React's Context API](https://react.dev/reference/react/useContext#contextconsumer) or `useBottomTabBarHeight`:
 
 ```js
 import { BottomTabBarHeightContext } from '@react-navigation/bottom-tabs';
diff --git a/versioned_docs/version-6.x/configuring-links.md b/versioned_docs/version-6.x/configuring-links.md
index 7f4d4470afc..a0e24f2f50b 100644
--- a/versioned_docs/version-6.x/configuring-links.md
+++ b/versioned_docs/version-6.x/configuring-links.md
@@ -509,7 +509,7 @@ Another thing to keep in mind is that it's not possible to pass params to the in
 
 In this case, any params in the URL are only passed to the `Profile` screen which matches the path pattern `users/:id`, and the `Feed` screen doesn't receive any params. If you want to have the same params in the `Feed` screen, you can specify a [custom `getStateFromPath` function](navigation-container.md#linkinggetstatefrompath) and copy those params.
 
-Similarly, if you want to access params of a parent screen from a child screen, you can use [React Context](https://reactjs.org/docs/context.html) to expose them.
+Similarly, if you want to access params of a parent screen from a child screen, you can use [React Context](https://react.dev/reference/react/useContext) to expose them.
 
 ## Matching exact paths
 
diff --git a/versioned_docs/version-6.x/elements.md b/versioned_docs/version-6.x/elements.md
index 84304a7c8c6..a45c06b28c6 100644
--- a/versioned_docs/version-6.x/elements.md
+++ b/versioned_docs/version-6.x/elements.md
@@ -164,7 +164,7 @@ This is useful if you want to render a semi-transparent header or a blurred back
 
 Note that if you don't want your content to appear under the header, you need to manually add a top margin to your content. React Navigation won't do it automatically.
 
-To get the height of the header, you can use [`HeaderHeightContext`](#headerheightcontext) with [React's Context API](https://reactjs.org/docs/context.html#contextconsumer) or [`useHeaderHeight`](#useheaderheight).
+To get the height of the header, you can use [`HeaderHeightContext`](#headerheightcontext) with [React's Context API](https://react.dev/reference/react/useContext#contextconsumer) or [`useHeaderHeight`](#useheaderheight).
 
 #### `headerBackground`
 
diff --git a/versioned_docs/version-6.x/hello-react-navigation.md b/versioned_docs/version-6.x/hello-react-navigation.md
index 946ea1737f3..78f38b9091d 100755
--- a/versioned_docs/version-6.x/hello-react-navigation.md
+++ b/versioned_docs/version-6.x/hello-react-navigation.md
@@ -130,7 +130,7 @@ Sometimes we will want to specify the same options for all of the screens in the
 
 Sometimes we might want to pass additional props to a screen. We can do that with 2 approaches:
 
-1. Use [React context](https://reactjs.org/docs/context.html) and wrap the navigator with a context provider to pass data to the screens (recommended).
+1. Use [React context](https://react.dev/reference/react/useContext) and wrap the navigator with a context provider to pass data to the screens (recommended).
 2. Use a render callback for the screen instead of specifying a `component` prop:
 
    ```js
diff --git a/versioned_docs/version-6.x/native-stack-navigator.md b/versioned_docs/version-6.x/native-stack-navigator.md
index 67f096165ae..5d83b323ee9 100755
--- a/versioned_docs/version-6.x/native-stack-navigator.md
+++ b/versioned_docs/version-6.x/native-stack-navigator.md
@@ -166,7 +166,7 @@ This is useful if you want to render a semi-transparent header or a blurred back
 
 Note that if you don't want your content to appear under the header, you need to manually add a top margin to your content. React Navigation won't do it automatically.
 
-To get the height of the header, you can use [`HeaderHeightContext`](elements.md#headerheightcontext) with [React's Context API](https://reactjs.org/docs/context.html#contextconsumer) or [`useHeaderHeight`](elements.md#useheaderheight).
+To get the height of the header, you can use [`HeaderHeightContext`](elements.md#headerheightcontext) with [React's Context API](https://react.dev/reference/react/useContext#contextconsumer) or [`useHeaderHeight`](elements.md#useheaderheight).
 
 #### `headerBlurEffect`
 
diff --git a/versioned_docs/version-6.x/nesting-navigators.md b/versioned_docs/version-6.x/nesting-navigators.md
index d5849d3eba7..d490c434b23 100755
--- a/versioned_docs/version-6.x/nesting-navigators.md
+++ b/versioned_docs/version-6.x/nesting-navigators.md
@@ -64,7 +64,7 @@ If you want to achieve this behavior, see the guide for [screen options with nes
 
 For example, any `params` passed to a screen in a nested navigator are in the `route` prop of that screen and aren't accessible from a screen in a parent or child navigator.
 
-If you need to access params of the parent screen from a child screen, you can use [React Context](https://reactjs.org/docs/context.html) to expose params to children.
+If you need to access params of the parent screen from a child screen, you can use [React Context](https://react.dev/reference/react/useContext) to expose params to children.
 
 ### Navigation actions are handled by current navigator and bubble up if couldn't be handled
 
diff --git a/versioned_docs/version-6.x/screen.md b/versioned_docs/version-6.x/screen.md
index a97eb9f7de7..32c858b5ecf 100644
--- a/versioned_docs/version-6.x/screen.md
+++ b/versioned_docs/version-6.x/screen.md
@@ -170,7 +170,7 @@ Render callback to return React Element to use for the screen:
 </Stack.Screen>
 ```
 
-You can use this approach instead of the `component` prop if you need to pass additional props. Though we recommend using [React context](https://reactjs.org/docs/context.html) for passing data instead.
+You can use this approach instead of the `component` prop if you need to pass additional props. Though we recommend using [React context](https://react.dev/reference/react/useContext) for passing data instead.
 
 :::warning
 
diff --git a/versioned_docs/version-6.x/tab-based-navigation.md b/versioned_docs/version-6.x/tab-based-navigation.md
index 08e7eef4570..173d60dc0f2 100755
--- a/versioned_docs/version-6.x/tab-based-navigation.md
+++ b/versioned_docs/version-6.x/tab-based-navigation.md
@@ -116,7 +116,7 @@ Sometimes we want to add badges to some icons. You can use the [`tabBarBadge` op
 <Tab.Screen name="Home" component={HomeScreen} options={{ tabBarBadge: 3 }} />
 ```
 
-From UI perspective this component is ready to use, but you still need to find some way to pass down the badge count properly from somewhere else, like using [React Context](https://reactjs.org/docs/context.html), [Redux](https://redux.js.org/), [MobX](https://mobx.js.org/) or [event emitters](https://github.com/facebook/react-native/blob/master/Libraries/vendor/emitter/EventEmitter.js).
+From UI perspective this component is ready to use, but you still need to find some way to pass down the badge count properly from somewhere else, like using [React Context](https://react.dev/reference/react/useContext), [Redux](https://redux.js.org/), [MobX](https://mobx.js.org/) or [event emitters](https://github.com/facebook/react-native/blob/master/Libraries/vendor/emitter/EventEmitter.js).
 
 ![Tabs with badges](/assets/navigators/tabs/tabs-badges.png)
 
diff --git a/versioned_docs/version-7.x/configuring-links.md b/versioned_docs/version-7.x/configuring-links.md
index a387d79be5f..592c5aa5292 100644
--- a/versioned_docs/version-7.x/configuring-links.md
+++ b/versioned_docs/version-7.x/configuring-links.md
@@ -910,7 +910,7 @@ Another thing to keep in mind is that it's not possible to pass params to the in
 
 In this case, any params in the URL are only passed to the `Profile` screen which matches the path pattern `users/:id`, and the `Feed` screen doesn't receive any params. If you want to have the same params in the `Feed` screen, you can specify a [custom `getStateFromPath` function](navigation-container.md#linkinggetstatefrompath) and copy those params.
 
-Similarly, if you want to access params of a parent screen from a child screen, you can use [React Context](https://reactjs.org/docs/context.html) to expose them.
+Similarly, if you want to access params of a parent screen from a child screen, you can use [React Context](https://react.dev/reference/react/useContext) to expose them.
 
 ## Matching exact paths
 
diff --git a/versioned_docs/version-7.x/elements.md b/versioned_docs/version-7.x/elements.md
index 713f38fa6c7..08d1b47cc20 100644
--- a/versioned_docs/version-7.x/elements.md
+++ b/versioned_docs/version-7.x/elements.md
@@ -388,7 +388,7 @@ This is useful if you want to render a semi-transparent header or a blurred back
 
 Note that if you don't want your content to appear under the header, you need to manually add a top margin to your content. React Navigation won't do it automatically.
 
-To get the height of the header, you can use [`HeaderHeightContext`](#headerheightcontext) with [React's Context API](https://reactjs.org/docs/context.html#contextconsumer) or [`useHeaderHeight`](#useheaderheight).
+To get the height of the header, you can use [`HeaderHeightContext`](#headerheightcontext) with [React's Context API](https://react.dev/reference/react/useContext#contextconsumer) or [`useHeaderHeight`](#useheaderheight).
 
 #### `headerBackground`
 
diff --git a/versioned_docs/version-7.x/hello-react-navigation.md b/versioned_docs/version-7.x/hello-react-navigation.md
index 666056ea09c..3a6dddaec47 100755
--- a/versioned_docs/version-7.x/hello-react-navigation.md
+++ b/versioned_docs/version-7.x/hello-react-navigation.md
@@ -489,7 +489,7 @@ Passing additional props to a screen is not supported in the static API.
 
 Sometimes we might want to pass additional props to a screen. We can do that with 2 approaches:
 
-1. Use [React context](https://reactjs.org/docs/context.html) and wrap the navigator with a context provider to pass data to the screens (recommended).
+1. Use [React context](https://react.dev/reference/react/useContext) and wrap the navigator with a context provider to pass data to the screens (recommended).
 2. Use a render callback for the screen instead of specifying a `component` prop:
 
    ```js
diff --git a/versioned_docs/version-7.x/native-stack-navigator.md b/versioned_docs/version-7.x/native-stack-navigator.md
index fda80e8ebe8..a80f34e349f 100755
--- a/versioned_docs/version-7.x/native-stack-navigator.md
+++ b/versioned_docs/version-7.x/native-stack-navigator.md
@@ -278,7 +278,7 @@ This is useful if you want to render a semi-transparent header or a blurred back
 
 Note that if you don't want your content to appear under the header, you need to manually add a top margin to your content. React Navigation won't do it automatically.
 
-To get the height of the header, you can use [`HeaderHeightContext`](elements.md#headerheightcontext) with [React's Context API](https://reactjs.org/docs/context.html#contextconsumer) or [`useHeaderHeight`](elements.md#useheaderheight).
+To get the height of the header, you can use [`HeaderHeightContext`](elements.md#headerheightcontext) with [React's Context API](https://react.dev/reference/react/useContext) or [`useHeaderHeight`](elements.md#useheaderheight).
 
 #### `headerBlurEffect`
 
diff --git a/versioned_docs/version-7.x/nesting-navigators.md b/versioned_docs/version-7.x/nesting-navigators.md
index a1537b215ab..bb96f16f59b 100755
--- a/versioned_docs/version-7.x/nesting-navigators.md
+++ b/versioned_docs/version-7.x/nesting-navigators.md
@@ -189,7 +189,7 @@ If you want to achieve this behavior, see the guide for [screen options with nes
 
 For example, any `params` passed to a screen in a nested navigator are in the `route` object of that screen and aren't accessible from a screen in a parent or child navigator.
 
-If you need to access params of the parent screen from a child screen, you can use [React Context](https://reactjs.org/docs/context.html) to expose params to children.
+If you need to access params of the parent screen from a child screen, you can use [React Context](https://react.dev/reference/react/useContext) to expose params to children.
 
 ### Navigation actions are handled by current navigator and bubble up if couldn't be handled
 
diff --git a/versioned_docs/version-7.x/screen.md b/versioned_docs/version-7.x/screen.md
index b672203dc77..777e5ce01ef 100644
--- a/versioned_docs/version-7.x/screen.md
+++ b/versioned_docs/version-7.x/screen.md
@@ -348,7 +348,7 @@ Another way is to pass a render callback to return React Element to use for the
 </Stack.Screen>
 ```
 
-You can use this approach instead of the `component` prop if you need to pass additional props. Though we recommend using [React context](https://reactjs.org/docs/context.html) for passing data instead.
+You can use this approach instead of the `component` prop if you need to pass additional props. Though we recommend using [React context](https://react.dev/reference/react/useContext) for passing data instead.
 
 :::warning
 
diff --git a/versioned_docs/version-7.x/tab-based-navigation.md b/versioned_docs/version-7.x/tab-based-navigation.md
index 3bde9197125..eceef69f505 100755
--- a/versioned_docs/version-7.x/tab-based-navigation.md
+++ b/versioned_docs/version-7.x/tab-based-navigation.md
@@ -367,7 +367,7 @@ export default function App() {
 </TabItem>
 </Tabs>
 
-From UI perspective this component is ready to use, but you still need to find some way to pass down the badge count properly from somewhere else, like using [React Context](https://reactjs.org/docs/context.html), [Redux](https://redux.js.org/), [MobX](https://mobx.js.org/) or [event emitters](https://github.com/facebook/react-native/blob/master/Libraries/vendor/emitter/EventEmitter.js).
+From UI perspective this component is ready to use, but you still need to find some way to pass down the badge count properly from somewhere else, like using [React Context](https://react.dev/reference/react/useContext), [Redux](https://redux.js.org/), [MobX](https://mobx.js.org/) or [event emitters](https://github.com/facebook/react-native/blob/master/Libraries/vendor/emitter/EventEmitter.js).
 
 ![Tabs with badges](/assets/navigators/tabs/tabs-badges.png)