docs: Updated references to React documentation

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) or `useBottomTabBarHeight`:
 
 ```js
 import { BottomTabBarHeightContext } from '@react-navigation/bottom-tabs';

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
 

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) or [`useHeaderHeight`](#useheaderheight).
 
 #### `headerBackground`
 

versioned_docs/version-6.x/getting-started.md

@@ -12,7 +12,7 @@ If you're already familiar with JavaScript, React and React Native, then you'll
 
 Here are some resources to help you out:
 
-1. [React Native Express](https://www.reactnative.express) (Sections 1 to 4)
+1. [React Native](https://reactnative.dev/docs/getting-started) (Sections 1 to 4)
 2. [Main Concepts of React](https://react.dev/learn)
 3. [React Hooks](https://react.dev/reference/react)
 4. [React Context](https://react.dev/learn/passing-data-deeply-with-context) (Advanced)

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

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) or [`useHeaderHeight`](elements.md#useheaderheight).
 
 #### `headerBlurEffect`
 

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
 

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
 

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)
 

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
 

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`
 

versioned_docs/version-7.x/getting-started.md

@@ -15,7 +15,7 @@ If you're already familiar with JavaScript, React and React Native, then you'll
 
 Here are some resources to help you out:
 
-1. [React Native Express](https://www.reactnative.express) (Sections 1 to 4)
+1. [React Native](https://reactnative.dev/docs/getting-started) (Sections 1 to 4)
 2. [Main Concepts of React](https://react.dev/learn)
 3. [React Hooks](https://react.dev/reference/react)
 4. [React Context](https://react.dev/learn/passing-data-deeply-with-context) (Advanced)

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

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#contextconsumer) or [`useHeaderHeight`](elements.md#useheaderheight).
 
 #### `headerBlurEffect`
 

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
 

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
 

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)