diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index 87bd9df2ea2..969e253a80d 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,7 +1,7 @@
 blank_issues_enabled: false
 contact_links:
   - name: ⚛️ React Native Issue
-    url: https://github.com/facebook/react-native/issues
+    url: https://github.com/react/react-native/issues
     about: Please report bugs or issues in the React Native repository.
   - name: ⤴️ Upgrade Issue
     url: https://github.com/react-native-community/upgrade-support
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index fc2cbc3ff79..5301e77e50e 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -3,7 +3,7 @@ Thank you for the PR! Contributors like you keep React Native awesome!
 
 Please see the Contribution Guide for guidelines:
 
-https://github.com/facebook/react-native-website/blob/master/CONTRIBUTING.md
+https://github.com/react/react-native-website/blob/master/CONTRIBUTING.md
 
 If your PR references an existing issue, please add the issue number below:
 
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 7a4305e3938..134b6d77f30 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,6 +1,6 @@
 # Contributing to React Native website
 
-Thank you for your interest in contributing to the React Native website! From commenting on and triaging issues, to reviewing and sending Pull Requests, all contributions are welcome. We aim to build a vibrant and inclusive [ecosystem of partners, core contributors, and community](https://github.com/facebook/react-native/blob/main/ECOSYSTEM.md) that goes beyond the main React Native GitHub repository.
+Thank you for your interest in contributing to the React Native website! From commenting on and triaging issues, to reviewing and sending Pull Requests, all contributions are welcome. We aim to build a vibrant and inclusive [ecosystem of partners, core contributors, and community](https://github.com/react/react-native/blob/main/ECOSYSTEM.md) that goes beyond the main React Native GitHub repository.
 
 The [Open Source Guides](https://opensource.guide/) website has a collection of resources for individuals, communities, and companies who want to learn how to run and contribute to an open source project. Contributors and people new to open source alike will find the following guides especially useful:
 
@@ -9,10 +9,10 @@ The [Open Source Guides](https://opensource.guide/) website has a collection of
 
 ## Code of Conduct
 
-As a reminder, all contributors are expected to adhere to the [Code of Conduct](https://github.com/facebook/react-native-website/blob/main/CODE_OF_CONDUCT.md).
+As a reminder, all contributors are expected to adhere to the [Code of Conduct](https://github.com/react/react-native-website/blob/main/CODE_OF_CONDUCT.md).
 
 ## Ways to Contribute
 
 Please see our [Contributing Guide](https://reactnative.dev/contributing/overview) on the React Native website.
 
-If you are interested specifically in contributing to the React Native website check out [Contributing section](https://github.com/facebook/react-native-website#-contributing) in the React Native website repository README file.
+If you are interested specifically in contributing to the React Native website check out [Contributing section](https://github.com/react/react-native-website#-contributing) in the React Native website repository README file.
diff --git a/README.md b/README.md
index 453d5de1d1e..471a1ff1344 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,7 @@
 
 This repo contains the website configuration and documentation powering the [React Native website](https://reactnative.dev/).
 
-> If you are looking for the source code of the [React Native Archive website](https://archive.reactnative.dev/) select the [`archive`](https://github.com/facebook/react-native-website/tree/archive) branch.
+> If you are looking for the source code of the [React Native Archive website](https://archive.reactnative.dev/) select the [`archive`](https://github.com/react/react-native-website/tree/archive) branch.
 
 ## Contents
 
@@ -175,7 +175,7 @@ If possible, test any visual changes in all latest versions of the following bro
 1. `git add -A && git commit -m "My message"` to stage and commit your changes.
    > replace `My message` with a commit message, such as `Fixed header logo on Android`
 1. `git push my-fork-name the-name-of-my-branch`
-1. Go to the [react-native-website repo](https://github.com/facebook/react-native-website) and you should see recently pushed branches.
+1. Go to the [react-native-website repo](https://github.com/react/react-native-website) and you should see recently pushed branches.
 1. Follow GitHub's instructions.
 1. Describe briefly your changes (in case of visual changes, please include screenshots).
 
diff --git a/docs/animations.md b/docs/animations.md
index 3c7ae0cbbb8..7f15bce3685 100644
--- a/docs/animations.md
+++ b/docs/animations.md
@@ -557,7 +557,7 @@ The native driver also works with `Animated.event`. This is especially useful fo
 </Animated.ScrollView>
 ```
 
-You can see the native driver in action by running the [RNTester app](https://github.com/facebook/react-native/blob/main/packages/rn-tester/), then loading the Native Animated Example. You can also take a look at the [source code](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/NativeAnimation/NativeAnimationsExample.js) to learn how these examples were produced.
+You can see the native driver in action by running the [RNTester app](https://github.com/react/react-native/blob/main/packages/rn-tester/), then loading the Native Animated Example. You can also take a look at the [source code](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/NativeAnimation/NativeAnimationsExample.js) to learn how these examples were produced.
 
 #### Caveats
 
@@ -585,8 +585,8 @@ While using transform styles such as `rotateY`, `rotateX`, and others ensure the
 
 The RNTester app has various examples of `Animated` in use:
 
-- [AnimatedGratuitousApp](https://github.com/facebook/react-native/tree/main/packages/rn-tester/js/examples/AnimatedGratuitousApp)
-- [NativeAnimationsExample](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/NativeAnimation/NativeAnimationsExample.js)
+- [AnimatedGratuitousApp](https://github.com/react/react-native/tree/main/packages/rn-tester/js/examples/AnimatedGratuitousApp)
+- [NativeAnimationsExample](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/NativeAnimation/NativeAnimationsExample.js)
 
 ## `LayoutAnimation` API
 
@@ -664,7 +664,7 @@ const styles = StyleSheet.create({
 });
 ```
 
-This example uses a preset value, you can customize the animations as you need, see [LayoutAnimation.js](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/LayoutAnimation/LayoutAnimation.js) for more information.
+This example uses a preset value, you can customize the animations as you need, see [LayoutAnimation.js](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/LayoutAnimation/LayoutAnimation.js) for more information.
 
 ## Additional notes
 
diff --git a/docs/build-speed.md b/docs/build-speed.md
index 0db1929f4f3..781e5fb78d5 100644
--- a/docs/build-speed.md
+++ b/docs/build-speed.md
@@ -45,7 +45,7 @@ $ ./gradlew :app:assembleDebug -PreactNativeArchitectures=x86,x86_64
 
 This can be useful if you wish to build your Android App on a CI and use a matrix to parallelize the build of the different architectures.
 
-If you wish, you can also override this value locally, using the `gradle.properties` file you have in the [top-level folder](https://github.com/facebook/react-native/blob/19cf70266eb8ca151aa0cc46ac4c09cb987b2ceb/template/android/gradle.properties#L30-L33) of your project:
+If you wish, you can also override this value locally, using the `gradle.properties` file you have in the [top-level folder](https://github.com/react/react-native/blob/19cf70266eb8ca151aa0cc46ac4c09cb987b2ceb/template/android/gradle.properties#L30-L33) of your project:
 
 ```
 # Use this property to specify which architecture you want to build.
@@ -153,7 +153,7 @@ Open `ios/Podfile` in your editor and uncomment the `ccache_enabled` line.
 
 ```ruby
   post_install do |installer|
-    # https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
+    # https://github.com/react/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
     react_native_post_install(
       installer,
       config[:reactNativePath],
diff --git a/docs/button.md b/docs/button.md
index 23501057f52..9343da4b3de 100644
--- a/docs/button.md
+++ b/docs/button.md
@@ -5,7 +5,7 @@ title: Button
 
 A basic button component that should render nicely on any platform. Supports a minimal level of customization.
 
-If this button doesn't look right for your app, you can build your own button using [Pressable](pressable). For inspiration, look at the [source code for the Button component](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Components/Button.js).
+If this button doesn't look right for your app, you can build your own button using [Pressable](pressable). For inspiration, look at the [source code for the Button component](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Components/Button.js).
 
 ```tsx
 <Button
diff --git a/docs/communication-ios.md b/docs/communication-ios.md
index 89a64ff9b4c..ea2b21499f7 100644
--- a/docs/communication-ios.md
+++ b/docs/communication-ios.md
@@ -57,7 +57,7 @@ rootView.appProperties = @{@"images" : imageList};
 It is fine to update properties anytime. However, updates have to be performed on the main thread. You use the getter on any thread.
 
 :::note
-Currently, there is a known issue where setting appProperties during the bridge startup, the change can be lost. See https://github.com/facebook/react-native/issues/20115 for more information.
+Currently, there is a known issue where setting appProperties during the bridge startup, the change can be lost. See https://github.com/react/react-native/issues/20115 for more information.
 :::
 
 There is no way to update only a few properties at a time. We suggest that you build it into your own wrapper instead.
@@ -188,7 +188,7 @@ Let's look at an example.
 
 In the example we have a `FlexibleSizeExampleView` view that holds a root view. We create the root view, initialize it and set the delegate. The delegate will handle size updates. Then, we set the root view's size flexibility to `RCTRootViewSizeFlexibilityHeight`, which means that `rootViewDidChangeIntrinsicSize:` method will be called every time the React Native content changes its height. Finally, we set the root view's width and position. Note that we set there height as well, but it has no effect as we made the height RN-dependent.
 
-You can checkout full source code of the example [here](https://github.com/facebook/react-native/blob/main/packages/rn-tester/RNTester/NativeExampleViews/FlexibleSizeExampleView.mm).
+You can checkout full source code of the example [here](https://github.com/react/react-native/blob/main/packages/rn-tester/RNTester/NativeExampleViews/FlexibleSizeExampleView.mm).
 
 It's fine to change root view's size flexibility mode dynamically. Changing flexibility mode of a root view will schedule a layout recalculation and the delegate `rootViewDidChangeIntrinsicSize:` method will be called once the content size is known.
 
diff --git a/docs/debugging.md b/docs/debugging.md
index c4c299a2677..c7f0ae0e54c 100644
--- a/docs/debugging.md
+++ b/docs/debugging.md
@@ -87,7 +87,7 @@ LogBox.ignoreLogs([
 
 :::note
 
-LogBox will treat certain errors from React as warnings, which will mean they don't display as an in-app error notification. Advanced users can change this behaviour by customising LogBox's warning filter using [`LogBoxData.setWarningFilter()`](https://github.com/facebook/react-native/blob/d334f4d77eea538dff87fdcf2ebc090246cfdbb0/packages/react-native/Libraries/LogBox/Data/LogBoxData.js#L338).
+LogBox will treat certain errors from React as warnings, which will mean they don't display as an in-app error notification. Advanced users can change this behaviour by customising LogBox's warning filter using [`LogBoxData.setWarningFilter()`](https://github.com/react/react-native/blob/d334f4d77eea538dff87fdcf2ebc090246cfdbb0/packages/react-native/Libraries/LogBox/Data/LogBoxData.js#L338).
 
 :::
 
diff --git a/docs/flatlist.md b/docs/flatlist.md
index d37ed6dc0b6..27af30bcc5e 100644
--- a/docs/flatlist.md
+++ b/docs/flatlist.md
@@ -660,7 +660,7 @@ When `true`, offscreen child views are removed from their native backing supervi
 
 ### `viewabilityConfig`
 
-See [`ViewabilityHelper.js`](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Lists/ViewabilityHelper.js) for flow type and further documentation.
+See [`ViewabilityHelper.js`](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Lists/ViewabilityHelper.js) for flow type and further documentation.
 
 | Type              |
 | ----------------- |
@@ -675,7 +675,7 @@ See [`ViewabilityHelper.js`](https://github.com/facebook/react-native/blob/main/
 | itemVisiblePercentThreshold      | number  |
 | waitForInteraction               | boolean |
 
-At least one of the `viewAreaCoveragePercentThreshold` or `itemVisiblePercentThreshold` is required. This needs to be done in the `constructor` to avoid following error ([ref](https://github.com/facebook/react-native/issues/17408)):
+At least one of the `viewAreaCoveragePercentThreshold` or `itemVisiblePercentThreshold` is required. This needs to be done in the `constructor` to avoid following error ([ref](https://github.com/react/react-native/issues/17408)):
 
 ```
   Error: Changing viewabilityConfig on the fly is not supported
diff --git a/docs/handling-touches.md b/docs/handling-touches.md
index b9604b393c0..045365dc21a 100644
--- a/docs/handling-touches.md
+++ b/docs/handling-touches.md
@@ -176,4 +176,4 @@ Gestures commonly used on devices with touchable screens include swipes and pans
 
 ## Known issues
 
-- [react-native#29308](https://github.com/facebook/react-native/issues/29308#issuecomment-792864162): The touch area never extends past the parent view bounds and on Android negative margin is not supported.
+- [react-native#29308](https://github.com/react/react-native/issues/29308#issuecomment-792864162): The touch area never extends past the parent view bounds and on Android negative margin is not supported.
diff --git a/docs/image.md b/docs/image.md
index 3f83be8c19c..b43614057b3 100644
--- a/docs/image.md
+++ b/docs/image.md
@@ -112,7 +112,7 @@ dependencies {
 ```
 
 :::note
-The version listed above may not be updated in time. Please check [`packages/react-native/gradle/libs.versions.toml`](https://github.com/facebook/react-native/blob/main/packages/react-native/gradle/libs.versions.toml) in the main repo to see which fresco version is being used in a specific tagged version.
+The version listed above may not be updated in time. Please check [`packages/react-native/gradle/libs.versions.toml`](https://github.com/react/react-native/blob/main/packages/react-native/gradle/libs.versions.toml) in the main repo to see which fresco version is being used in a specific tagged version.
 :::
 
 ---
diff --git a/docs/imagebackground.md b/docs/imagebackground.md
index 66ee0f9a198..da1c57f1fdd 100644
--- a/docs/imagebackground.md
+++ b/docs/imagebackground.md
@@ -9,7 +9,7 @@ Use a [`View`](view.md) with an absolutely positioned [`Image`](image.md) instea
 
 A common feature request from developers familiar with the web is `background-image`. To handle this use case, you can use the `<ImageBackground>` component, which has the same props as `<Image>`, and add whatever children to it you would like to layer on top of it.
 
-You might not want to use `<ImageBackground>` in some cases, since the implementation is basic. Refer to `<ImageBackground>`'s [source code](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Image/ImageBackground.js) for more insight, and create your own custom component when needed.
+You might not want to use `<ImageBackground>` in some cases, since the implementation is basic. Refer to `<ImageBackground>`'s [source code](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Image/ImageBackground.js) for more insight, and create your own custom component when needed.
 
 Note that you must specify some width and height style attributes.
 
diff --git a/docs/inputaccessoryview.md b/docs/inputaccessoryview.md
index f0defb6ae38..6823fa8696a 100644
--- a/docs/inputaccessoryview.md
+++ b/docs/inputaccessoryview.md
@@ -64,7 +64,7 @@ const styles = StyleSheet.create({
 export default App;
 ```
 
-This component can also be used to create sticky text inputs (text inputs which are anchored to the top of the keyboard). To do this, wrap a `TextInput` with the `InputAccessoryView` component, and don't set a `nativeID`. For an example, look at [InputAccessoryViewExample.js](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/InputAccessoryView/InputAccessoryViewExample.js).
+This component can also be used to create sticky text inputs (text inputs which are anchored to the top of the keyboard). To do this, wrap a `TextInput` with the `InputAccessoryView` component, and don't set a `nativeID`. For an example, look at [InputAccessoryViewExample.js](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/InputAccessoryView/InputAccessoryViewExample.js).
 
 ---
 
@@ -98,5 +98,5 @@ An ID which is used to associate this `InputAccessoryView` to specified TextInpu
 
 # Known issues
 
-- [react-native#18997](https://github.com/facebook/react-native/issues/18997): Doesn't support multiline `TextInput`
-- [react-native#20157](https://github.com/facebook/react-native/issues/20157): Can't use with a bottom tab bar
+- [react-native#18997](https://github.com/react/react-native/issues/18997): Doesn't support multiline `TextInput`
+- [react-native#20157](https://github.com/react/react-native/issues/20157): Can't use with a bottom tab bar
diff --git a/docs/javascript-environment.md b/docs/javascript-environment.md
index d66b5a996de..300309cff36 100644
--- a/docs/javascript-environment.md
+++ b/docs/javascript-environment.md
@@ -21,7 +21,7 @@ Syntax transformers make writing code more enjoyable by allowing you to use new
 
 React Native ships with the [Babel JavaScript compiler](https://babeljs.io). Check [Babel documentation](https://babeljs.io/docs/plugins/#transform-plugins) on its supported transformations for more details.
 
-A full list of React Native's enabled transformations can be found in [@react-native/babel-preset](https://github.com/facebook/react-native/tree/main/packages/react-native-babel-preset).
+A full list of React Native's enabled transformations can be found in [@react-native/babel-preset](https://github.com/react/react-native/tree/main/packages/react-native-babel-preset).
 
 <table>
 <thead>
diff --git a/docs/layout-props.md b/docs/layout-props.md
index 87379f1e5a1..433720d88f4 100644
--- a/docs/layout-props.md
+++ b/docs/layout-props.md
@@ -658,7 +658,7 @@ See [MDN CSS Reference](https://developer.mozilla.org/en-US/docs/Web/CSS/flex-di
 
 `flexWrap` controls whether children can wrap around after they hit the end of a flex container. It works like `flex-wrap` in CSS (default: nowrap).
 
-Note it does not work anymore with `alignItems: stretch` (the default), so you may want to use `alignItems: flex-start` for example (breaking change details: https://github.com/facebook/react-native/releases/tag/v0.28.0).
+Note it does not work anymore with `alignItems: stretch` (the default), so you may want to use `alignItems: flex-start` for example (breaking change details: https://github.com/react/react-native/releases/tag/v0.28.0).
 
 See [MDN CSS Reference](https://developer.mozilla.org/en-US/docs/Web/CSS/flex-wrap) for more details.
 
diff --git a/docs/legacy/direct-manipulation.md b/docs/legacy/direct-manipulation.md
index 7eb6479d8a0..88e0e58a5bf 100644
--- a/docs/legacy/direct-manipulation.md
+++ b/docs/legacy/direct-manipulation.md
@@ -18,7 +18,7 @@ Before you use it, try to solve your problem with `setState` and [`shouldCompone
 
 ## setNativeProps with TouchableOpacity
 
-[TouchableOpacity](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Components/Touchable/TouchableOpacity.js) uses `setNativeProps` internally to update the opacity of its child component:
+[TouchableOpacity](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Components/Touchable/TouchableOpacity.js) uses `setNativeProps` internally to update the opacity of its child component:
 
 ```tsx
 const viewRef = useRef<View>();
@@ -57,7 +57,7 @@ return (
 
 This is computationally intensive compared to the original example - React needs to re-render the component hierarchy each time the opacity changes, even though other properties of the view and its children haven't changed. Usually this overhead isn't a concern but when performing continuous animations and responding to gestures, judiciously optimizing your components can improve your animations' fidelity.
 
-If you look at the implementation of `setNativeProps` in [NativeMethodsMixin](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js) you will notice that it is a wrapper around `RCTUIManager.updateView` - this is the exact same function call that results from re-rendering - see [receiveComponent in ReactNativeBaseComponent](https://github.com/facebook/react-native/blob/fb2ec1ea47c53c2e7b873acb1cb46192ac74274e/Libraries/Renderer/oss/ReactNativeRenderer-prod.js#L5793-L5813).
+If you look at the implementation of `setNativeProps` in [NativeMethodsMixin](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js) you will notice that it is a wrapper around `RCTUIManager.updateView` - this is the exact same function call that results from re-rendering - see [receiveComponent in ReactNativeBaseComponent](https://github.com/react/react-native/blob/fb2ec1ea47c53c2e7b873acb1cb46192ac74274e/Libraries/Renderer/oss/ReactNativeRenderer-prod.js#L5793-L5813).
 
 ## Composite components and setNativeProps
 
diff --git a/docs/legacy/native-components-ios.md b/docs/legacy/native-components-ios.md
index b9eb22a2dfd..cd535811278 100644
--- a/docs/legacy/native-components-ios.md
+++ b/docs/legacy/native-components-ios.md
@@ -47,7 +47,7 @@ RCT_EXPORT_MODULE(RNTMap)
 Do not attempt to set the `frame` or `backgroundColor` properties on the `UIView` instance that you expose through the `-view` method.
 React Native will overwrite the values set by your custom class in order to match your JavaScript component's layout props.
 If you need this granularity of control it might be better to wrap the `UIView` instance you want to style in another `UIView` and return the wrapper `UIView` instead.
-See [Issue 2948](https://github.com/facebook/react-native/issues/2948) for more context.
+See [Issue 2948](https://github.com/react/react-native/issues/2948) for more context.
 :::
 
 :::info
@@ -476,4 +476,4 @@ The `RCTDatePickerIOSConsts` constants are exported from native by grabbing the
 }
 ```
 
-This guide covered many of the aspects of bridging over custom native components, but there is even more you might need to consider, such as custom hooks for inserting and laying out subviews. If you want to go even deeper, check out the [source code](https://github.com/facebook/react-native/tree/main/packages/react-native/React/Views) of some of the implemented components.
+This guide covered many of the aspects of bridging over custom native components, but there is even more you might need to consider, such as custom hooks for inserting and laying out subviews. If you want to go even deeper, check out the [source code](https://github.com/react/react-native/tree/main/packages/react-native/React/Views) of some of the implemented components.
diff --git a/docs/legacy/native-modules-android.md b/docs/legacy/native-modules-android.md
index cec5857a441..1b494294b5a 100644
--- a/docs/legacy/native-modules-android.md
+++ b/docs/legacy/native-modules-android.md
@@ -270,7 +270,7 @@ class MyAppPackage : ReactPackage {
 This file imports the native module you created, `CalendarModule`. It then instantiates `CalendarModule` within the `createNativeModules()` function and returns it as a list of `NativeModules` to register. If you add more native modules down the line, you can also instantiate them and add them to the list returned here.
 
 :::note
-It is worth noting that this way of registering native modules eagerly initializes all native modules when the application starts, which adds to the startup time of an application. You can use [TurboReactPackage](https://github.com/facebook/react-native/blob/main/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/TurboReactPackage.kt) as an alternative. Instead of `createNativeModules`, which return a list of instantiated native module objects, TurboReactPackage implements a `getModule(String name, ReactApplicationContext rac)` method that creates the native module object, when required. TurboReactPackage is a bit more complicated to implement at the moment. In addition to implementing a `getModule()` method, you have to implement a `getReactModuleInfoProvider()` method, which returns a list of all the native modules the package can instantiate along with a function that instantiates them, example [here](https://github.com/facebook/react-native/blob/8ac467c51b94c82d81930b4802b2978c85539925/ReactAndroid/src/main/java/com/facebook/react/CoreModulesPackage.java#L86-L165). Again, using TurboReactPackage will allow your application to have a faster startup time, but it is currently a bit cumbersome to write. So proceed with caution if you choose to use TurboReactPackages.
+It is worth noting that this way of registering native modules eagerly initializes all native modules when the application starts, which adds to the startup time of an application. You can use [TurboReactPackage](https://github.com/react/react-native/blob/main/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/TurboReactPackage.kt) as an alternative. Instead of `createNativeModules`, which return a list of instantiated native module objects, TurboReactPackage implements a `getModule(String name, ReactApplicationContext rac)` method that creates the native module object, when required. TurboReactPackage is a bit more complicated to implement at the moment. In addition to implementing a `getModule()` method, you have to implement a `getReactModuleInfoProvider()` method, which returns a list of all the native modules the package can instantiate along with a function that instantiates them, example [here](https://github.com/react/react-native/blob/8ac467c51b94c82d81930b4802b2978c85539925/ReactAndroid/src/main/java/com/facebook/react/CoreModulesPackage.java#L86-L165). Again, using TurboReactPackage will allow your application to have a faster startup time, but it is currently a bit cumbersome to write. So proceed with caution if you choose to use TurboReactPackages.
 :::
 
 To register the `CalendarModule` package, you must add `MyAppPackage` to the list of packages returned in ReactNativeHost's `getPackages()` method. Open up your `MainApplication.java` or `MainApplication.kt` file, which can be found in the following path: `android/app/src/main/java/com/your-app-name/`.
@@ -777,7 +777,7 @@ code: String, message: String, userInfo: WritableMap, throwable: Throwable
 </TabItem>
 </Tabs>
 
-For more detail, you can find the `Promise.java` interface [here](https://github.com/facebook/react-native/blob/main/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/bridge/Promise.kt). If `userInfo` is not provided, ReactNative will set it to null. For the rest of the parameters React Native will use a default value. The `message` argument provides the error `message` shown at the top of an error call stack. Below is an example of the error message shown in JavaScript from the following reject call in Java/Kotlin.
+For more detail, you can find the `Promise.java` interface [here](https://github.com/react/react-native/blob/main/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/bridge/Promise.kt). If `userInfo` is not provided, ReactNative will set it to null. For the rest of the parameters React Native will use a default value. The `message` argument provides the error `message` shown at the top of an error call stack. Below is an example of the error message shown in JavaScript from the following reject call in Java/Kotlin.
 
 Java/Kotlin reject call:
 
@@ -896,7 +896,7 @@ sendEvent(reactContext, "EventReminder", params)
 </TabItem>
 </Tabs>
 
-JavaScript modules can then register to receive events by `addListener` on the [NativeEventEmitter](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/EventEmitter/NativeEventEmitter.js) class.
+JavaScript modules can then register to receive events by `addListener` on the [NativeEventEmitter](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/EventEmitter/NativeEventEmitter.js) class.
 
 ```tsx
 import {NativeEventEmitter, NativeModules} from 'react-native';
diff --git a/docs/legacy/native-modules-ios.md b/docs/legacy/native-modules-ios.md
index d3239e16a90..7736690b66e 100644
--- a/docs/legacy/native-modules-ios.md
+++ b/docs/legacy/native-modules-ios.md
@@ -289,7 +289,7 @@ The following types are currently supported but will not be supported in TurboMo
 - Number -> float
   :::
 
-For iOS, you can also write native module methods with any argument type that is supported by the `RCTConvert` class (see [RCTConvert](https://github.com/facebook/react-native/blob/main/packages/react-native/React/Base/RCTConvert.h) for details about what is supported). The RCTConvert helper functions all accept a JSON value as input and map it to a native Objective-C type or class.
+For iOS, you can also write native module methods with any argument type that is supported by the `RCTConvert` class (see [RCTConvert](https://github.com/react/react-native/blob/main/packages/react-native/React/Base/RCTConvert.h) for details about what is supported). The RCTConvert helper functions all accept a JSON value as input and map it to a native Objective-C type or class.
 
 ### Exporting Constants
 
@@ -361,7 +361,7 @@ const onSubmit = () => {
 };
 ```
 
-A native module is supposed to invoke its callback only once. It can, however, store the callback and invoke it later. This pattern is often used to wrap iOS APIs that require delegates— see [`RCTAlertManager`](https://github.com/facebook/react-native/blob/main/packages/react-native/React/CoreModules/RCTAlertManager.mm) for an example. If the callback is never invoked, some memory is leaked.
+A native module is supposed to invoke its callback only once. It can, however, store the callback and invoke it later. This pattern is often used to wrap iOS APIs that require delegates— see [`RCTAlertManager`](https://github.com/react/react-native/blob/main/packages/react-native/React/CoreModules/RCTAlertManager.mm) for an example. If the callback is never invoked, some memory is leaked.
 
 There are two approaches to error handling with callbacks. The first is to follow Node’s convention and treat the first argument passed to the callback array as an error object.
 
@@ -426,7 +426,7 @@ const onPress = () => {
 };
 ```
 
-If you want to pass error-like objects to JavaScript, use `RCTMakeError` from [`RCTUtils.h.`](https://github.com/facebook/react-native/blob/main/packages/react-native/React/Base/RCTUtils.h) Right now this only passes an Error-shaped dictionary to JavaScript, but React Native aims to automatically generate real JavaScript Error objects in the future. You can also provide a `RCTResponseErrorBlock` argument, which is used for error callbacks and accepts an `NSError \* object`. Please note that this argument type will not be supported with TurboModules.
+If you want to pass error-like objects to JavaScript, use `RCTMakeError` from [`RCTUtils.h.`](https://github.com/react/react-native/blob/main/packages/react-native/React/Base/RCTUtils.h) Right now this only passes an Error-shaped dictionary to JavaScript, but React Native aims to automatically generate real JavaScript Error objects in the future. You can also provide a `RCTResponseErrorBlock` argument, which is used for error callbacks and accepts an `NSError \* object`. Please note that this argument type will not be supported with TurboModules.
 
 ### Promises
 
@@ -618,7 +618,7 @@ For those of you new to Swift and Objective-C, whenever you [mix the two languag
 #import <React/RCTBridgeModule.h>
 ```
 
-You can also use `RCT_EXTERN_REMAP_MODULE` and `_RCT_EXTERN_REMAP_METHOD` to alter the JavaScript name of the module or methods you are exporting. For more information see [`RCTBridgeModule`](https://github.com/facebook/react-native/blob/main/packages/react-native/React/Base/RCTBridgeModule.h).
+You can also use `RCT_EXTERN_REMAP_MODULE` and `_RCT_EXTERN_REMAP_METHOD` to alter the JavaScript name of the module or methods you are exporting. For more information see [`RCTBridgeModule`](https://github.com/react/react-native/blob/main/packages/react-native/React/Base/RCTBridgeModule.h).
 
 :::note
 Important when making third party modules: Static libraries with Swift are only supported in Xcode 9 and later. In order for the Xcode project to build when you use Swift in the iOS static library you include in the module, your main app project must contain Swift code and a bridging header itself. If your app project does not contain any Swift code, a workaround can be a single empty .swift file and an empty bridging header.
@@ -628,4 +628,4 @@ Important when making third party modules: Static libraries with Swift are only
 
 #### invalidate()
 
-Native modules can conform to the [RCTInvalidating](https://github.com/facebook/react-native/blob/main/packages/react-native/React/Base/RCTInvalidating.h) protocol on iOS by implementing the `invalidate()` method. This method [can be invoked](https://github.com/facebook/react-native/blob/0.62-stable/ReactCommon/turbomodule/core/platform/ios/RCTTurboModuleManager.mm#L456) when the native bridge is invalidated (i.e.: on devmode reload). Please use this mechanism as necessary to do the required cleanup for your native module.
+Native modules can conform to the [RCTInvalidating](https://github.com/react/react-native/blob/main/packages/react-native/React/Base/RCTInvalidating.h) protocol on iOS by implementing the `invalidate()` method. This method [can be invoked](https://github.com/react/react-native/blob/0.62-stable/ReactCommon/turbomodule/core/platform/ios/RCTTurboModuleManager.mm#L456) when the native bridge is invalidated (i.e.: on devmode reload). Please use this mechanism as necessary to do the required cleanup for your native module.
diff --git a/docs/network.md b/docs/network.md
index 414629e3d66..d456a5b6cc1 100644
--- a/docs/network.md
+++ b/docs/network.md
@@ -256,8 +256,8 @@ The following options are currently not working with `fetch`
 - `redirect:manual`
 - `credentials:omit`
 
-* Having same name headers on Android will result in only the latest one being present. A temporary solution can be found here: https://github.com/facebook/react-native/issues/18837#issuecomment-398779994.
-* Cookie based authentication is currently unstable. You can view some of the issues raised here: https://github.com/facebook/react-native/issues/23185
+* Having same name headers on Android will result in only the latest one being present. A temporary solution can be found here: https://github.com/react/react-native/issues/18837#issuecomment-398779994.
+* Cookie based authentication is currently unstable. You can view some of the issues raised here: https://github.com/react/react-native/issues/23185
 * As a minimum on iOS, when redirected through a `302`, if a `Set-Cookie` header is present, the cookie is not set properly. Since the redirect cannot be handled manually this might cause a scenario where infinite requests occur if the redirect is the result of an expired session.
 
 ## Configuring NSURLSession on iOS
diff --git a/docs/panresponder.md b/docs/panresponder.md
index 1a32583a1ef..520aa0f3ede 100644
--- a/docs/panresponder.md
+++ b/docs/panresponder.md
@@ -138,7 +138,7 @@ const styles = StyleSheet.create({
 export default App;
 ```
 
-Try the [PanResponder example in RNTester](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/PanResponder/PanResponderExample.js).
+Try the [PanResponder example in RNTester](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/PanResponder/PanResponderExample.js).
 
 ---
 
diff --git a/docs/platformcolor.md b/docs/platformcolor.md
index 040c6d2c18a..6a7c7417f3f 100644
--- a/docs/platformcolor.md
+++ b/docs/platformcolor.md
@@ -86,5 +86,5 @@ export default App;
 The string value provided to the `PlatformColor` function must match the string as it exists on the native platform where the app is running. In order to avoid runtime errors, the function should be wrapped in a platform check, either through a `Platform.OS === 'platform'` or a `Platform.select()`, as shown on the example above.
 
 :::note
-You can find a complete example that demonstrates proper, intended use of `PlatformColor` in [PlatformColorExample.js](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).
+You can find a complete example that demonstrates proper, intended use of `PlatformColor` in [PlatformColorExample.js](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).
 :::
diff --git a/docs/pressable.md b/docs/pressable.md
index 5c1a0933fc0..e8b8c427be8 100644
--- a/docs/pressable.md
+++ b/docs/pressable.md
@@ -41,7 +41,7 @@ The touch area never extends past the parent view bounds and the Z-index of sibl
 </figure>
 
 :::info
-`Pressable` uses React Native's `Pressability` API. For more information around the state machine flow of Pressability and how it works, check out the implementation for [Pressability](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Pressability/Pressability.js#L350).
+`Pressable` uses React Native's `Pressability` API. For more information around the state machine flow of Pressability and how it works, check out the implementation for [Pressability](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Pressability/Pressability.js#L350).
 :::
 
 ## Example
diff --git a/docs/release-levels.md b/docs/release-levels.md
index edb459f9c17..6ce18fecb38 100644
--- a/docs/release-levels.md
+++ b/docs/release-levels.md
@@ -14,7 +14,7 @@ This approach is similar to [Canary and Experimental releases in React](https://
 React Native is also not using `@canary` or `@experimental` NPM tags, as release levels are available for both stable and nightly releases of React Native.
 :::
 
-Moreover, setting the release level to `EXPERIMENTAL` or `CANARY` will **not** result in consuming `react@nightly` or `react@canary` due to how react-native is consuming the React version ([you can read more about it here](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Renderer/README.md#react--react-native-versions)).
+Moreover, setting the release level to `EXPERIMENTAL` or `CANARY` will **not** result in consuming `react@nightly` or `react@canary` due to how react-native is consuming the React version ([you can read more about it here](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Renderer/README.md#react--react-native-versions)).
 
 ## When to Use Each Release Level
 
diff --git a/docs/roottag.md b/docs/roottag.md
index 541724b9365..0d688ad3933 100644
--- a/docs/roottag.md
+++ b/docs/roottag.md
@@ -21,7 +21,7 @@ Another use case for `RootTag` is when your app needs to attribute a certain Jav
 
 ## How to access the RootTag... if you need it
 
-In versions 0.65 and below, RootTag is accessed via a [legacy context](https://github.com/facebook/react-native/blob/v0.64.1/Libraries/ReactNative/AppContainer.js#L56). To prepare React Native for Concurrent features coming in React 18 and beyond, we are migrating to the latest [Context API](https://react.dev/reference/react/createContext) via `RootTagContext` in 0.66. Version 0.65 supports both the legacy context and the recommended `RootTagContext` to allow developers time to migrate their call-sites. See the breaking changes summary.
+In versions 0.65 and below, RootTag is accessed via a [legacy context](https://github.com/react/react-native/blob/v0.64.1/Libraries/ReactNative/AppContainer.js#L56). To prepare React Native for Concurrent features coming in React 18 and beyond, we are migrating to the latest [Context API](https://react.dev/reference/react/createContext) via `RootTagContext` in 0.66. Version 0.65 supports both the legacy context and the recommended `RootTagContext` to allow developers time to migrate their call-sites. See the breaking changes summary.
 
 How to access `RootTag` via the `RootTagContext`.
 
@@ -71,4 +71,4 @@ The legacy context access to `RootTag` will be removed and replaced by `RootTagC
 
 ## Future Plans
 
-With the new React Native architecture progressing, there will be future iterations to `RootTag`, with the intention to keep the `RootTag` type opaque and prevent thrash in React Native codebases. Please do not rely on the fact that RootTag currently aliases to a number! If your app relies on RootTags, keep an eye on our version change logs, which you can find [here](https://github.com/facebook/react-native/blob/main/CHANGELOG.md).
+With the new React Native architecture progressing, there will be future iterations to `RootTag`, with the intention to keep the `RootTag` type opaque and prevent thrash in React Native codebases. Please do not rely on the fact that RootTag currently aliases to a number! If your app relies on RootTags, keep an eye on our version change logs, which you can find [here](https://github.com/react/react-native/blob/main/CHANGELOG.md).
diff --git a/docs/safeareaview.md b/docs/safeareaview.md
index 1298898b64e..1e6f668b919 100644
--- a/docs/safeareaview.md
+++ b/docs/safeareaview.md
@@ -50,5 +50,5 @@ export default App;
 Inherits [View Props](view.md#props).
 
 :::note
-As padding is used to implement the behavior of the component, padding rules in styles applied to a `SafeAreaView` will be ignored and can cause different results depending on the platform. See [#22211](https://github.com/facebook/react-native/issues/22211) for details.
+As padding is used to implement the behavior of the component, padding rules in styles applied to a `SafeAreaView` will be ignored and can cause different results depending on the platform. See [#22211](https://github.com/react/react-native/issues/22211) for details.
 :::
diff --git a/docs/scrollview.md b/docs/scrollview.md
index 77a22c56b39..1cd85c7bc3c 100644
--- a/docs/scrollview.md
+++ b/docs/scrollview.md
@@ -74,7 +74,7 @@ Inherits [View Props](view#props).
 
 ### `StickyHeaderComponent`
 
-A React Component that will be used to render sticky headers, should be used together with `stickyHeaderIndices`. You may need to set this component if your sticky header uses custom transforms, for example, when you want your list to have an animated and hidable header. If a component has not been provided, the default [`ScrollViewStickyHeader`](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Components/ScrollView/ScrollViewStickyHeader.js) component will be used.
+A React Component that will be used to render sticky headers, should be used together with `stickyHeaderIndices`. You may need to set this component if your sticky header uses custom transforms, for example, when you want your list to have an animated and hidable header. If a component has not been provided, the default [`ScrollViewStickyHeader`](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Components/ScrollView/ScrollViewStickyHeader.js) component will be used.
 
 | Type               |
 | ------------------ |
diff --git a/docs/style.md b/docs/style.md
index 4890db4fbfa..25f12dfbe38 100644
--- a/docs/style.md
+++ b/docs/style.md
@@ -48,4 +48,4 @@ Now you can make your text beautiful. The next step in becoming a style expert i
 
 ## Known issues
 
-- [react-native#29308](https://github.com/facebook/react-native/issues/29308#issuecomment-792864162): In some cases React Native does not match how CSS works on the web, for example the touch area never extends past the parent view bounds and on Android negative margin is not supported.
+- [react-native#29308](https://github.com/react/react-native/issues/29308#issuecomment-792864162): In some cases React Native does not match how CSS works on the web, for example the touch area never extends past the parent view bounds and on Android negative margin is not supported.
diff --git a/docs/textinput.md b/docs/textinput.md
index 18eae0c77a1..4ba1305f2eb 100644
--- a/docs/textinput.md
+++ b/docs/textinput.md
@@ -1141,6 +1141,6 @@ Returns `true` if the input is currently focused; `false` otherwise.
 
 # Known issues
 
-- [react-native#19096](https://github.com/facebook/react-native/issues/19096): Doesn't support Android's `onKeyPreIme`.
-- [react-native#19366](https://github.com/facebook/react-native/issues/19366): Calling .focus() after closing Android's keyboard via back button doesn't bring keyboard up again.
-- [react-native#26799](https://github.com/facebook/react-native/issues/26799): Doesn't support Android's `secureTextEntry` when `keyboardType="email-address"` or `keyboardType="phone-pad"`.
+- [react-native#19096](https://github.com/react/react-native/issues/19096): Doesn't support Android's `onKeyPreIme`.
+- [react-native#19366](https://github.com/react/react-native/issues/19366): Calling .focus() after closing Android's keyboard via back button doesn't bring keyboard up again.
+- [react-native#26799](https://github.com/react/react-native/issues/26799): Doesn't support Android's `secureTextEntry` when `keyboardType="email-address"` or `keyboardType="phone-pad"`.
diff --git a/docs/the-new-architecture/custom-cxx-types.md b/docs/the-new-architecture/custom-cxx-types.md
index edc490b8070..e270cb480e2 100644
--- a/docs/the-new-architecture/custom-cxx-types.md
+++ b/docs/the-new-architecture/custom-cxx-types.md
@@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con
 This guide assumes that you are familiar with the [**Pure C++ Turbo Native Modules**](pure-cxx-modules.md) guide. This will build on top of that guide.
 :::
 
-C++ Turbo Native Modules support [bridging functionality](https://github.com/facebook/react-native/tree/main/packages/react-native/ReactCommon/react/bridging) for most `std::` standard types. You can use most of those types in your modules without any additional code required.
+C++ Turbo Native Modules support [bridging functionality](https://github.com/react/react-native/tree/main/packages/react-native/ReactCommon/react/bridging) for most `std::` standard types. You can use most of those types in your modules without any additional code required.
 
 If you want to add support for new and custom types in your app or library, you need to provide the necessary `bridging` header file.
 
diff --git a/docs/the-new-architecture/native-modules-lifecycle.md b/docs/the-new-architecture/native-modules-lifecycle.md
index 361e845591e..4264f6acbe3 100644
--- a/docs/the-new-architecture/native-modules-lifecycle.md
+++ b/docs/the-new-architecture/native-modules-lifecycle.md
@@ -12,17 +12,17 @@ In this guide, you will explore how to initialize and invalidate a Native Module
 
 ## Android
 
-When it comes to Android, all the Native Modules already implements a [TurboModule](https://github.com/facebook/react-native/blob/main/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/interfaces/TurboModule.kt) interface that defines two methods: `initialize()` and `invalidate()`.
+When it comes to Android, all the Native Modules already implements a [TurboModule](https://github.com/react/react-native/blob/main/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/interfaces/TurboModule.kt) interface that defines two methods: `initialize()` and `invalidate()`.
 
-The `initialize()` method is called by the Native Module infrastructure when the Native Module is created. This is the best place to put all the initialization code that needs access to the ReactApplicationContext, for example. These are some Native Modules from core that implements the `initialize()` method: [BlobModule](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/blob/BlobModule.java#L155-L157), [NetworkingModule](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/network/NetworkingModule.java#L193-L197).
+The `initialize()` method is called by the Native Module infrastructure when the Native Module is created. This is the best place to put all the initialization code that needs access to the ReactApplicationContext, for example. These are some Native Modules from core that implements the `initialize()` method: [BlobModule](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/blob/BlobModule.java#L155-L157), [NetworkingModule](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/network/NetworkingModule.java#L193-L197).
 
-The `invalidate()` method is called by the Native Module infrastructure when the Native Module is destroyed. This is the best place to put all the cleanup code, resetting the Native Module state and release resources that are no longer needed, such as memory and files. These are some Native Modules from core that implements the `invalidate()` method: [DeviceInfoModule](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/deviceinfo/DeviceInfoModule.kt#L72-L76), [NetworkModule](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/network/NetworkingModule.java#L200-L212)
+The `invalidate()` method is called by the Native Module infrastructure when the Native Module is destroyed. This is the best place to put all the cleanup code, resetting the Native Module state and release resources that are no longer needed, such as memory and files. These are some Native Modules from core that implements the `invalidate()` method: [DeviceInfoModule](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/deviceinfo/DeviceInfoModule.kt#L72-L76), [NetworkModule](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/network/NetworkingModule.java#L200-L212)
 
 ## iOS
 
-On iOS, Native Modules conforms to the [`RCTTurboModule`](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactCommon/react/nativemodule/core/platform/ios/ReactCommon/RCTTurboModule.h#L196-L200) protocol. However, this protocol does not expose the `initialize` and `invalidate` method that are exposed by the Android's `TurboModule` class.
+On iOS, Native Modules conforms to the [`RCTTurboModule`](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactCommon/react/nativemodule/core/platform/ios/ReactCommon/RCTTurboModule.h#L196-L200) protocol. However, this protocol does not expose the `initialize` and `invalidate` method that are exposed by the Android's `TurboModule` class.
 
-Instead, on iOS, there are two additional protocols: [`RCTInitializing`](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/Base/RCTInitializing.h) and [`RCTInvalidating`](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/Base/RCTInvalidating.h). These protocols are used to define the `initialize` and `invalidate` methods, respectively.
+Instead, on iOS, there are two additional protocols: [`RCTInitializing`](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/Base/RCTInitializing.h) and [`RCTInvalidating`](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/Base/RCTInvalidating.h). These protocols are used to define the `initialize` and `invalidate` methods, respectively.
 
 If your module needs to run some initialization code, then you can conform to the `RCTInitializing` protocol and implement the `initialize` method. To do so, you have to:
 
@@ -53,7 +53,7 @@ If your module needs to run some initialization code, then you can conform to th
 @end
 ```
 
-These are some Native Modules from core that implements the `initialize` method: [RCTBlobManager](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/Libraries/Blob/RCTBlobManager.mm#L58-L68), [RCTTiming](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/CoreModules/RCTTiming.mm#L121-L124).
+These are some Native Modules from core that implements the `initialize` method: [RCTBlobManager](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/Libraries/Blob/RCTBlobManager.mm#L58-L68), [RCTTiming](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/CoreModules/RCTTiming.mm#L121-L124).
 
 If your module needs to run some cleanup code, then you can conform to the `RCTInvalidating` protocol and implement the `invalidate` method. To do so, you have to:
 
@@ -87,4 +87,4 @@ If your module needs to run some cleanup code, then you can conform to the `RCTI
 @end
 ```
 
-These are some Native Modules from core that implements the `invalidate` method: [RCTAppearance](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/CoreModules/RCTAppearance.mm#L151-L155), [RCTDeviceInfo](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/CoreModules/RCTDeviceInfo.mm#L127-L133).
+These are some Native Modules from core that implements the `invalidate` method: [RCTAppearance](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/CoreModules/RCTAppearance.mm#L151-L155), [RCTDeviceInfo](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/CoreModules/RCTDeviceInfo.mm#L127-L133).
diff --git a/docs/the-new-architecture/pure-cxx-modules.md b/docs/the-new-architecture/pure-cxx-modules.md
index 083bd8f7a42..71cba2e7459 100644
--- a/docs/the-new-architecture/pure-cxx-modules.md
+++ b/docs/the-new-architecture/pure-cxx-modules.md
@@ -229,7 +229,7 @@ The final step is to register the new C++ Turbo Native Module in the runtime, so
 1. From the folder `SampleApp/android/app/src/main/jni`, run the following command:
 
 <CodeBlock language="sh" title="shell">
-{`curl -O https://raw.githubusercontent.com/facebook/react-native/${getCoreBranchNameForCurrentVersion()}/packages/react-native/ReactAndroid/cmake-utils/default-app-setup/OnLoad.cpp`}
+{`curl -O https://raw.githubusercontent.com/react/react-native/${getCoreBranchNameForCurrentVersion()}/packages/react-native/ReactAndroid/cmake-utils/default-app-setup/OnLoad.cpp`}
 </CodeBlock>
 
 2. Then, modify this file as follows:
diff --git a/docs/the-new-architecture/using-codegen.mdx b/docs/the-new-architecture/using-codegen.mdx
index adac9313115..7c68e48fae4 100644
--- a/docs/the-new-architecture/using-codegen.mdx
+++ b/docs/the-new-architecture/using-codegen.mdx
@@ -69,7 +69,7 @@ You can add this snippet to your app and customize the various fields:
   - `.modules[moduleName]:`
     - `.className`: This module's ObjC class. Or, if it's a [C++-only module](/docs/next/the-new-architecture/pure-cxx-modules), its `RCTModuleProvider` class.
     - `.unstableRequiresMainQueueSetup`: Initialize this module on the UI Thread, before running any JavaScript.
-    - `.conformsToProtocols`: Annotate which of these protocols this module conforms to any of the following protocols: [`RCTImageURLLoader`](https://github.com/facebook/react-native/blob/00d5caee9921b6c10be8f7d5b3903c6afe8dbefa/packages/react-native/Libraries/Image/RCTImageURLLoader.h#L26-L81), [`RCTURLRequestHandler`](https://github.com/facebook/react-native/blob/00d5caee9921b6c10be8f7d5b3903c6afe8dbefa/packages/react-native/React/Base/RCTURLRequestHandler.h#L11-L52), [`RCTImageDataDecoder`](https://github.com/facebook/react-native/blob/00d5caee9921b6c10be8f7d5b3903c6afe8dbefa/packages/react-native/Libraries/Image/RCTImageDataDecoder.h#L15-L53).
+    - `.conformsToProtocols`: Annotate which of these protocols this module conforms to any of the following protocols: [`RCTImageURLLoader`](https://github.com/react/react-native/blob/00d5caee9921b6c10be8f7d5b3903c6afe8dbefa/packages/react-native/Libraries/Image/RCTImageURLLoader.h#L26-L81), [`RCTURLRequestHandler`](https://github.com/react/react-native/blob/00d5caee9921b6c10be8f7d5b3903c6afe8dbefa/packages/react-native/React/Base/RCTURLRequestHandler.h#L11-L52), [`RCTImageDataDecoder`](https://github.com/react/react-native/blob/00d5caee9921b6c10be8f7d5b3903c6afe8dbefa/packages/react-native/Libraries/Image/RCTImageDataDecoder.h#L15-L53).
   - `.components[componentName]`:
     - `.className`: This component's ObjC class (e.g: `TextInput` -> `RCTTextInput`).
 
diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
index 540f38b984f..b166c182a9f 100644
--- a/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -5,7 +5,7 @@ title: Troubleshooting
 
 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
 
-These are some common issues you may run into while setting up React Native. If you encounter something that is not listed here, try [searching for the issue in GitHub](https://github.com/facebook/react-native/issues/).
+These are some common issues you may run into while setting up React Native. If you encounter something that is not listed here, try [searching for the issue in GitHub](https://github.com/react/react-native/issues/).
 
 ### Port already in use
 
@@ -88,7 +88,7 @@ To revert the `User Search Header Paths` and `Header Search Paths` build setting
 
 ### No transports available
 
-React Native implements a polyfill for WebSockets. These [polyfills](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Core/InitializeCore.js) are initialized as part of the react-native module that you include in your application through `import React from 'react'`. If you load another module that requires WebSockets, such as [Firebase](https://github.com/facebook/react-native/issues/3645), be sure to load/require it after react-native:
+React Native implements a polyfill for WebSockets. These [polyfills](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Core/InitializeCore.js) are initialized as part of the react-native module that you include in your application through `import React from 'react'`. If you load another module that requires WebSockets, such as [Firebase](https://github.com/react/react-native/issues/3645), be sure to load/require it after react-native:
 
 ```
 import Firebase from 'firebase';
diff --git a/docs/turbo-native-modules-android.md b/docs/turbo-native-modules-android.md
index 83d922f9918..a1a067fdfcc 100644
--- a/docs/turbo-native-modules-android.md
+++ b/docs/turbo-native-modules-android.md
@@ -203,7 +203,7 @@ class NativeLocalStoragePackage : BaseReactPackage() {
 
 Finally, we need to tell the React Native in our main application how to find this `Package`. We call this "registering" the package in React Native.
 
-In this case, you add it to be returned by the [getPackages](https://github.com/facebook/react-native/blob/8d8b8c343e62115a5509e1aed62047053c2f6e39/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/ReactNativeHost.java#L233) method.
+In this case, you add it to be returned by the [getPackages](https://github.com/react/react-native/blob/8d8b8c343e62115a5509e1aed62047053c2f6e39/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/ReactNativeHost.java#L233) method.
 
 :::info
 Later you’ll learn how to distribute your Native Modules as [npm packages](the-new-architecture/create-module-library.mdx#publish-the-library-on-npm), which our build tooling will autolink for you.
diff --git a/docs/usecolorscheme.md b/docs/usecolorscheme.md
index 14b7becabe8..fec009f6815 100644
--- a/docs/usecolorscheme.md
+++ b/docs/usecolorscheme.md
@@ -45,4 +45,4 @@ const styles = StyleSheet.create({
 export default App;
 ```
 
-You can find a complete example that demonstrates the use of this hook alongside a React context to add support for light and dark themes to your application in [`AppearanceExample.js`](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/Appearance/AppearanceExample.js).
+You can find a complete example that demonstrates the use of this hook alongside a React context to add support for light and dark themes to your application in [`AppearanceExample.js`](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/Appearance/AppearanceExample.js).
diff --git a/docs/view-style-props.md b/docs/view-style-props.md
index fbe71ec81e7..f940aa3d99c 100644
--- a/docs/view-style-props.md
+++ b/docs/view-style-props.md
@@ -109,8 +109,8 @@ style={{
 
 More complex examples of usage can be found in the RNTester app (with `PlatformColor` supports):
 
-- <a href={`https://github.com/facebook/react-native/blob/${getCoreBranchNameForCurrentVersion()}/packages/rn-tester/js/examples/LinearGradient/LinearGradientExample.js`}>LinearGradientExample.js</a>
-- <a href={`https://github.com/facebook/react-native/blob/${getCoreBranchNameForCurrentVersion()}/packages/rn-tester/js/examples/RadialGradient/RadialGradientExample.js`}>RadialGradientExample.js</a>
+- <a href={`https://github.com/react/react-native/blob/${getCoreBranchNameForCurrentVersion()}/packages/rn-tester/js/examples/LinearGradient/LinearGradientExample.js`}>LinearGradientExample.js</a>
+- <a href={`https://github.com/react/react-native/blob/${getCoreBranchNameForCurrentVersion()}/packages/rn-tester/js/examples/RadialGradient/RadialGradientExample.js`}>RadialGradientExample.js</a>
 
 | Type                                                                                                                                                                                               |
 | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/docs/viewtoken.md b/docs/viewtoken.md
index 28d285deefa..aedeb40f037 100644
--- a/docs/viewtoken.md
+++ b/docs/viewtoken.md
@@ -3,7 +3,7 @@ id: viewtoken
 title: ViewToken Object Type
 ---
 
-`ViewToken` object is returned as one of the properties in the `onViewableItemsChanged` callback (for example, in the [FlatList](flatlist) component). It is exported by [`ViewabilityHelper.js`](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Lists/ViewabilityHelper.js).
+`ViewToken` object is returned as one of the properties in the `onViewableItemsChanged` callback (for example, in the [FlatList](flatlist) component). It is exported by [`ViewabilityHelper.js`](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Lists/ViewabilityHelper.js).
 
 ## Example
 
diff --git a/website/architecture/bundled-hermes.md b/website/architecture/bundled-hermes.md
index a8ea37e1997..b9688fbe382 100644
--- a/website/architecture/bundled-hermes.md
+++ b/website/architecture/bundled-hermes.md
@@ -21,7 +21,7 @@ From 0.69 on, you will always have a JS engine that has been built and tested al
 
 Historically, React Native and Hermes followed two **distinct release processes** with distinct versioning. Having distinct releases with distinct numbers created confusion in the OSS ecosystem, where it was not clear if a specific version of Hermes was compatible with a specific version of React Native (i.e. you needed to know that Hermes 0.11.0 was compatible only with React Native 0.68.0, etc.)
 
-Both Hermes and React Native, share the JSI code ([Hermes here](https://github.com/facebook/hermes/tree/main/API/jsi/jsi) and [React Native here](https://github.com/facebook/react-native/tree/main/packages/react-native/ReactCommon/jsi/jsi)). If the two JSI copies of JSI get out of sync, a build of Hermes won't be compatible with a build of React Native. You can read more about this [ABI incompatibility problem here](https://github.com/react-native-community/discussions-and-proposals/issues/257).
+Both Hermes and React Native, share the JSI code ([Hermes here](https://github.com/facebook/hermes/tree/main/API/jsi/jsi) and [React Native here](https://github.com/react/react-native/tree/main/packages/react-native/ReactCommon/jsi/jsi)). If the two JSI copies of JSI get out of sync, a build of Hermes won't be compatible with a build of React Native. You can read more about this [ABI incompatibility problem here](https://github.com/react-native-community/discussions-and-proposals/issues/257).
 
 To overcome this problem, we've extended the React Native release process to download and build Hermes and made sure only one copy of JSI is used when building Hermes.
 
@@ -40,11 +40,11 @@ On iOS, we've moved the `hermes-engine` you're using.
 Prior to React Native 0.69, users would download a pod (here you can find the [podspec](https://github.com/CocoaPods/Specs/blob/master/Specs/5/d/0/hermes-engine/0.11.0/hermes-engine.podspec.json)).
 
 On React Native 0.69, users would instead use a podspec that is defined inside the `sdks/hermes-engine/hermes-engine.podspec` file in the `react-native` NPM package.
-That podspec relies on a pre-built tarball of Hermes that we upload to Maven and to the React Native GitHub Release, as part of the React Native release process (i.e. [see the assets of this release](https://github.com/facebook/react-native/releases/tag/v0.70.4)).
+That podspec relies on a pre-built tarball of Hermes that we upload to Maven and to the React Native GitHub Release, as part of the React Native release process (i.e. [see the assets of this release](https://github.com/react/react-native/releases/tag/v0.70.4)).
 
 ### Android Users
 
-On Android, we're going to update the [`android/app/build.gradle`](https://github.com/facebook/react-native/blob/main/template/android/app/build.gradle) file in the default template the following way:
+On Android, we're going to update the [`android/app/build.gradle`](https://github.com/react/react-native/blob/main/template/android/app/build.gradle) file in the default template the following way:
 
 ```diff
 dependencies {
@@ -66,7 +66,7 @@ dependencies {
 Prior to React Native 0.69, users will be consuming `hermes-debug.aar` and `hermes-release.aar` from the `hermes-engine` NPM package.
 
 On React Native 0.69, users will be consuming the Android multi-variant artifacts available inside the `android/com/facebook/react/hermes-engine/` folder in the `react-native` NPM package.
-Please also note that we're going to [remove the dependency](https://github.com/facebook/react-native/blob/c418bf4c8fe8bf97273e3a64211eaa38d836e0a0/package.json#L105) on `hermes-engine` entirely in one of the future version of React Native.
+Please also note that we're going to [remove the dependency](https://github.com/react/react-native/blob/c418bf4c8fe8bf97273e3a64211eaa38d836e0a0/package.json#L105) on `hermes-engine` entirely in one of the future version of React Native.
 
 #### Android Users on New Architecture
 
@@ -102,11 +102,11 @@ If you're a React Native contributor or you're building an extension on top of R
 
 ### How is Bundled Hermes working under the hood?
 
-This mechanism relies on **downloading a tarball** with the Hermes source code from the `facebook/hermes` repository inside the `facebook/react-native` repository. We have a similar mechanism in place for other native dependencies (Folly, Glog, etc.) and we aligned Hermes to follow the same setup.
+This mechanism relies on **downloading a tarball** with the Hermes source code from the `facebook/hermes` repository inside the `react/react-native` repository. We have a similar mechanism in place for other native dependencies (Folly, Glog, etc.) and we aligned Hermes to follow the same setup.
 
 When building React Native from `main`, we will be fetching a tarball of `main` of facebook/hermes and building it as part of the build process of React Native.
 
-When building React Native from a release branch (say `0.69-stable`), we will instead use a **tag** on the Hermes repo to **synchronize the code** between the two repos. The specific tag name used will then be stored inside the `sdks/.hermesversion` file inside React Native in the release branch (e.g. [this is the file](https://github.com/facebook/react-native/blob/0.69-stable/sdks/.hermesversion) on the 0.69 release branch).
+When building React Native from a release branch (say `0.69-stable`), we will instead use a **tag** on the Hermes repo to **synchronize the code** between the two repos. The specific tag name used will then be stored inside the `sdks/.hermesversion` file inside React Native in the release branch (e.g. [this is the file](https://github.com/react/react-native/blob/0.69-stable/sdks/.hermesversion) on the 0.69 release branch).
 
 In a sense, you can think of this approach similarly to a **git submodule**.
 
@@ -114,7 +114,7 @@ If you're building on top of Hermes, you can rely on those tags to understand wh
 
 #### Android implementation details
 
-To implement this on Android, we've added a new build inside the `/ReactAndroid/hermes-engine` of React Native that will take care of building Hermes and packaging for consumption ([See here for more context](https://github.com/facebook/react-native/pull/33396)).
+To implement this on Android, we've added a new build inside the `/ReactAndroid/hermes-engine` of React Native that will take care of building Hermes and packaging for consumption ([See here for more context](https://github.com/react/react-native/pull/33396)).
 
 You can now trigger a build of Hermes engine by invoking:
 
@@ -137,16 +137,16 @@ However, this made this line necessary in the template:
 exclude group:'com.facebook.fbjni'
 ```
 
-This is needed as React Native is consuming `fbjni` using the non-prefab approach (i.e. unzipping the `.aar` and extracting `.so` files). Hermes-engine, and other libraries, are using prefab instead to consume fbjni. We're looking into [addressing this issue](https://github.com/facebook/react-native/pull/33397) in the future so the Hermes import will be a oneliner.
+This is needed as React Native is consuming `fbjni` using the non-prefab approach (i.e. unzipping the `.aar` and extracting `.so` files). Hermes-engine, and other libraries, are using prefab instead to consume fbjni. We're looking into [addressing this issue](https://github.com/react/react-native/pull/33397) in the future so the Hermes import will be a oneliner.
 
 #### iOS implementation details
 
 The iOS implementation relies on a series of scripts that lives in the following locations:
 
-- [`/scripts/hermes`](https://github.com/facebook/react-native/tree/main/scripts/hermes). Those scripts contain logic to download the Hermes tarball, unzip it, and configure the iOS build. They're invoked at `pod install` time if you have the `hermes_enabled` field set to `true`.
-- [`/sdks/hermes-engine`](https://github.com/facebook/react-native/tree/main/sdks/hermes-engine). Those scripts contain the build logic that is effectively building Hermes. They were copied and adapted from the `facebook/hermes` repo to properly work within React Native. Specifically, the scripts inside the `utils` folder are responsible of building Hermes for all the Mac platforms.
+- [`/scripts/hermes`](https://github.com/react/react-native/tree/main/scripts/hermes). Those scripts contain logic to download the Hermes tarball, unzip it, and configure the iOS build. They're invoked at `pod install` time if you have the `hermes_enabled` field set to `true`.
+- [`/sdks/hermes-engine`](https://github.com/react/react-native/tree/main/sdks/hermes-engine). Those scripts contain the build logic that is effectively building Hermes. They were copied and adapted from the `facebook/hermes` repo to properly work within React Native. Specifically, the scripts inside the `utils` folder are responsible of building Hermes for all the Mac platforms.
 
-Hermes is built as part of the `build_hermes_macos` Job on CircleCI. The job will produce as artifact a tarball which will be downloaded by the `hermes-engine` podspec when using a published React Native release ([here is an example of the artifacts created for React Native 0.69 in `build_hermes_macos`](https://app.circleci.com/pipelines/github/facebook/react-native/13679/workflows/5172f8e4-6b02-4ccb-ab97-7cb954911fae/jobs/258701/artifacts)).
+Hermes is built as part of the `build_hermes_macos` Job on CircleCI. The job will produce as artifact a tarball which will be downloaded by the `hermes-engine` podspec when using a published React Native release ([here is an example of the artifacts created for React Native 0.69 in `build_hermes_macos`](https://app.circleci.com/pipelines/github/react/react-native/13679/workflows/5172f8e4-6b02-4ccb-ab97-7cb954911fae/jobs/258701/artifacts)).
 
 ##### Prebuilt Hermes
 
diff --git a/website/architecture/landing-page.md b/website/architecture/landing-page.md
index 5416be0420f..6b2fc2ad223 100644
--- a/website/architecture/landing-page.md
+++ b/website/architecture/landing-page.md
@@ -209,7 +209,7 @@ You can follow along and contribute in our dedicated [discussions & proposals](h
 
 With 0.76, The New Architecture is enabled by default in all the React Native projects.
 
-If you find anything that is not working well, please open an issue using [this template](https://github.com/facebook/react-native/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2CType%3A+New+Architecture&projects=&template=new_architecture_bug_report.yml).
+If you find anything that is not working well, please open an issue using [this template](https://github.com/react/react-native/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2CType%3A+New+Architecture&projects=&template=new_architecture_bug_report.yml).
 
 If, for any reasons, you can't use the New Architecture, you can still opt-out from it:
 
diff --git a/website/community/communities.md b/website/community/communities.md
index 9e5a8059efe..755d3b4de59 100644
--- a/website/community/communities.md
+++ b/website/community/communities.md
@@ -3,7 +3,7 @@ title: Communities
 description: The React Native Community
 ---
 
-The React Native ecosystem is far and wide, and people can be part of it in many forms; here you will find but a partial list of different ways one developer can be part of it. If you know of other, or want to help expand this page, [submit a PR](https://github.com/facebook/react-native-website/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc)!
+The React Native ecosystem is far and wide, and people can be part of it in many forms; here you will find but a partial list of different ways one developer can be part of it. If you know of other, or want to help expand this page, [submit a PR](https://github.com/react/react-native-website/pulls?q=is%3Apr+is%3Aopen+sort%3Aupdated-desc)!
 
 ### Local communities
 
@@ -34,4 +34,4 @@ React Native tagged content can be found on many platforms, such as:
 - [Hacker News](https://hn.algolia.com/?q=react-native)
 - [r/reactnative/](https://www.reddit.com/r/reactnative/)
 
-These are places where you can share React Native projects, articles and tutorials as well as start discussions and ask for feedback on React Native related topics. (but remember to give some love to the [main documentation](https://github.com/facebook/react-native-website) too!)
+These are places where you can share React Native projects, articles and tutorials as well as start discussions and ask for feedback on React Native related topics. (but remember to give some love to the [main documentation](https://github.com/react/react-native-website) too!)
diff --git a/website/community/overview.md b/website/community/overview.md
index bc062521e12..4f0281d2acf 100644
--- a/website/community/overview.md
+++ b/website/community/overview.md
@@ -3,7 +3,7 @@ title: Overview
 description: The React Native Community
 ---
 
-React Native is a widely used technology, empowered by a massive community of [hundreds of thousands of developers](https://github.com/facebook/react-native/stargazers) and downloaded [over 2 million times](https://www.npmjs.com/package/react-native) every week.
+React Native is a widely used technology, empowered by a massive community of [hundreds of thousands of developers](https://github.com/react/react-native/stargazers) and downloaded [over 2 million times](https://www.npmjs.com/package/react-native) every week.
 
 In this section you will find listed ways you can also be part of the React Native-related communities, depending on your wants and needs:
 
@@ -11,4 +11,4 @@ In this section you will find listed ways you can also be part of the React Nati
 - [Participating in the community](communities)
 - [Needing and providing help](support)
 
-We expect all folks participating in React Native' communities to adhere to the guidelines within our [Code of Conduct](https://github.com/facebook/react-native/blob/main/CODE_OF_CONDUCT.md).
+We expect all folks participating in React Native' communities to adhere to the guidelines within our [Code of Conduct](https://github.com/react/react-native/blob/main/CODE_OF_CONDUCT.md).
diff --git a/website/community/support.md b/website/community/support.md
index bf1db2110ce..045a2378744 100644
--- a/website/community/support.md
+++ b/website/community/support.md
@@ -7,7 +7,7 @@ If you need help with your React Native app, the right place to go depends on th
 
 ### Repository
 
-The core of **React Native** is worked on full-time by Meta's React Native team. But there are far more people in the community who make key contributions and fix things. If the issue you are facing is code related, you should check the open issues in the [main repository](https://github.com/facebook/react-native/issues).
+The core of **React Native** is worked on full-time by Meta's React Native team. But there are far more people in the community who make key contributions and fix things. If the issue you are facing is code related, you should check the open issues in the [main repository](https://github.com/react/react-native/issues).
 
 If you cannot find an existing issue, please refer to [How to report a bug](/contributing/how-to-report-a-bug).
 
diff --git a/website/contributing/_markdown-GH-release-notes-prerelease.mdx b/website/contributing/_markdown-GH-release-notes-prerelease.mdx
index c8829bc954f..7e31fcf20bd 100644
--- a/website/contributing/_markdown-GH-release-notes-prerelease.mdx
+++ b/website/contributing/_markdown-GH-release-notes-prerelease.mdx
@@ -15,7 +15,7 @@ npx react-native init RN069RC0 --version 0.69.0-rc.0
 
 - To help you upgrade to this version, you can use the [upgrade helper](https://react-native-community.github.io/upgrade-helper/) ⚛️
 
-- See changes from this release in the [changelog PR](https://github.com/facebook/react-native/labels/%F0%9F%93%9D%20Changelog)
+- See changes from this release in the [changelog PR](https://github.com/react/react-native/labels/%F0%9F%93%9D%20Changelog)
 
 ---
 
diff --git a/website/contributing/_markdown-road-to-release-template.mdx b/website/contributing/_markdown-road-to-release-template.mdx
index a98315775d1..419074c18be 100644
--- a/website/contributing/_markdown-road-to-release-template.mdx
+++ b/website/contributing/_markdown-road-to-release-template.mdx
@@ -29,7 +29,7 @@ The branch cut has happened.
 - [ ] Ship changelog
 - [ ] Ship blog post
 - [ ] Prepare typescript PR (see https://github.com/DefinitelyTyped/DefinitelyTyped/pull/60929)
-- [ ] Make PR to `react-native-website` with the new version cut ([see docs](https://github.com/facebook/react-native-website#cutting-a-new-version))
+- [ ] Make PR to `react-native-website` with the new version cut ([see docs](https://github.com/react/react-native-website#cutting-a-new-version))
 
 #### Retrospective Topics
 
@@ -66,13 +66,13 @@ Tracking 0.69.0-rc.1 (released ✅)
 </details>
 -->
 
-[changelog-pr]: https://github.com/facebook/react-native/labels/%F0%9F%93%9D%20Changelog
-[current-release]: https://github.com/facebook/react-native/releases
+[changelog-pr]: https://github.com/react/react-native/labels/%F0%9F%93%9D%20Changelog
+[current-release]: https://github.com/react/react-native/releases
 [changelog-wiki]: https://reactnative.dev/contributing/changelogs-in-pull-requests
 [release-dependencies]: https://reactnative.dev/contributing/release-dependencies
 [release-faq]: https://reactnative.dev/contributing/release-faq
-[issue-form]: https://github.com/facebook/react-native/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2Cpre-release&template=release_blocker_form.yml
-[releases]: https://github.com/facebook/react-native/releases
+[issue-form]: https://github.com/react/react-native/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2Cpre-release&template=release_blocker_form.yml
+[releases]: https://github.com/react/react-native/releases
 [release-processes]: https://reactnative.dev/contributing/overview
 [upgrade-helper]: https://reactnative.dev/contributing/updating-upgrade-helper
 ```
diff --git a/website/contributing/bots-reference.md b/website/contributing/bots-reference.md
index 73ea1deb9ca..c6e1b269e8f 100644
--- a/website/contributing/bots-reference.md
+++ b/website/contributing/bots-reference.md
@@ -4,19 +4,19 @@ title: Bots Reference
 
 ## pull-bot
 
-This pull request linter bot performs basic sanity checks whenever a pull request is created. It might leave a comment on a pull request if it is unable to find a test plan or a changelog in the description, or if it notices that the pull request was not opened against the `main` branch. This bot uses [Danger](https://danger.systems), and its configuration can be found in the [`dangerfile.js`](https://github.com/facebook/react-native/blob/main/packages/react-native-bots/dangerfile.js).
+This pull request linter bot performs basic sanity checks whenever a pull request is created. It might leave a comment on a pull request if it is unable to find a test plan or a changelog in the description, or if it notices that the pull request was not opened against the `main` branch. This bot uses [Danger](https://danger.systems), and its configuration can be found in the [`dangerfile.js`](https://github.com/react/react-native/blob/main/packages/react-native-bots/dangerfile.js).
 
 ## analysis-bot
 
-The code analysis bot collects feedback from tools such as Prettier, eslint, and Flow whenever a commit is added to a pull request. If any of these tools finds issues with the code, the bot will add these as inline review comments on the pull request. Its configuration can be found in the [`analyze_code.sh`](https://github.com/facebook/react-native/blob/main/scripts/circleci/analyze_code.sh) file in core repository.
+The code analysis bot collects feedback from tools such as Prettier, eslint, and Flow whenever a commit is added to a pull request. If any of these tools finds issues with the code, the bot will add these as inline review comments on the pull request. Its configuration can be found in the [`analyze_code.sh`](https://github.com/react/react-native/blob/main/scripts/circleci/analyze_code.sh) file in core repository.
 
 ## label-actions
 
-A bot that acts on an issue or pull request based on a label. Configured in [`.github/workflows/on-issue-labeled.yml`](https://github.com/facebook/react-native/blob/main/.github/workflows/on-issue-labeled.yml).
+A bot that acts on an issue or pull request based on a label. Configured in [`.github/workflows/on-issue-labeled.yml`](https://github.com/react/react-native/blob/main/.github/workflows/on-issue-labeled.yml).
 
 ## github-actions
 
-A bot that performs actions defined in a GitHub workflow. Workflows are configured in [`.github/workflows`](https://github.com/facebook/react-native/tree/main/.github/workflows).
+A bot that performs actions defined in a GitHub workflow. Workflows are configured in [`.github/workflows`](https://github.com/react/react-native/tree/main/.github/workflows).
 
 ## facebook-github-bot
 
diff --git a/website/contributing/contributing-overview.mdx b/website/contributing/contributing-overview.mdx
index c77fc70c7e2..36bb973f98a 100644
--- a/website/contributing/contributing-overview.mdx
+++ b/website/contributing/contributing-overview.mdx
@@ -7,7 +7,7 @@ description: How to contribute to React Native
 {/* alex disable simple simply */}
 
 Thank you for your interest in contributing to React Native! From commenting on and triaging issues, to reviewing and sending Pull Requests, all contributions are welcome.
-We aim to build a vibrant and inclusive [ecosystem of partners, core contributors, and community](https://github.com/facebook/react-native/blob/main/ECOSYSTEM.md) that goes beyond the main React Native GitHub repository.
+We aim to build a vibrant and inclusive [ecosystem of partners, core contributors, and community](https://github.com/react/react-native/blob/main/ECOSYSTEM.md) that goes beyond the main React Native GitHub repository.
 
 The [Open Source Guides](https://opensource.guide/) website has a collection of resources for individuals, communities, and companies who want to learn how to run and contribute to an open source project.
 
@@ -18,7 +18,7 @@ Contributors and people new to open source alike will find the following guides
 
 ### Code of Conduct
 
-As a reminder, all contributors are expected to adhere to the [Code of Conduct](https://github.com/facebook/react-native/blob/HEAD/CODE_OF_CONDUCT.md).
+As a reminder, all contributors are expected to adhere to the [Code of Conduct](https://github.com/react/react-native/blob/HEAD/CODE_OF_CONDUCT.md).
 
 ## Versioning Policy
 
@@ -27,7 +27,7 @@ In that page we describe which versions of React Native are supported, how often
 
 ## Ways to Contribute
 
-If you are eager to start contributing code right away, we have a list of [good first issues](https://github.com/facebook/react-native/labels/good%20first%20issue) that contain bugs which have a relatively limited scope.
+If you are eager to start contributing code right away, we have a list of [good first issues](https://github.com/react/react-native/labels/good%20first%20issue) that contain bugs which have a relatively limited scope.
 As you gain more experience and demonstrate a commitment to evolving React Native, you may be granted issue management permissions in the repository.
 
 There are other ways you can contribute without writing a single line of code. Here are a few things you can do to help out:
@@ -39,7 +39,7 @@ There are other ways you can contribute without writing a single line of code. H
 
 2. **Reviewing pull requests for the docs.**
 
-   Reviewing [documentation updates](https://github.com/facebook/react-native-website/pulls) can be as simple as checking for spelling and grammar.
+   Reviewing [documentation updates](https://github.com/react/react-native-website/pulls) can be as simple as checking for spelling and grammar.
    If you encounter situations that can be explained better in the docs, click **Edit** at the top of most docs pages to get started with your own contribution.
 
 3. **Help people write test plans.**
@@ -50,7 +50,7 @@ Each of these tasks is highly impactful, and maintainers will greatly appreciate
 
 ### Our Development Process
 
-We use GitHub issues and pull requests to keep track of bug reports and contributions from the community. All changes from engineers at Meta will sync to [GitHub](https://github.com/facebook/react-native) through a bridge with Meta's internal source control. Changes from the community are handled through GitHub pull requests.
+We use GitHub issues and pull requests to keep track of bug reports and contributions from the community. All changes from engineers at Meta will sync to [GitHub](https://github.com/react/react-native) through a bridge with Meta's internal source control. Changes from the community are handled through GitHub pull requests.
 
 Once a change made on GitHub is approved, it will first be imported into Facebook's internal source control and tested against Facebook's codebase. Once merged at Facebook, the change will eventually sync back to GitHub as a single commit once it has passed Facebook's internal tests.
 
@@ -67,9 +67,9 @@ The main repository contains the React Native framework itself, and it is here w
 
 There are a few other repositories you might want to familiarize yourself with:
 
-- **React Native website** which contains the source code for the website, including the documentation, located [in this repository](https://github.com/facebook/react-native-website).
+- **React Native website** which contains the source code for the website, including the documentation, located [in this repository](https://github.com/react/react-native-website).
 - **Releases** conversations are happening [in this discussion repo](https://github.com/reactwg/react-native-releases/discussions).
-- **Changelog** for the releases can be found [here](https://github.com/facebook/react-native/blob/main/CHANGELOG.md).
+- **Changelog** for the releases can be found [here](https://github.com/react/react-native/blob/main/CHANGELOG.md).
 - **Discussions** about React Native take place in the [Discussions and Proposals](https://github.com/react-native-community/discussions-and-proposals) repository.
 - **Discussions** about the new architecture of React Native take place in the [React Native New Architecture Working Group](https://github.com/reactwg/react-native-new-architecture) repository.
 - **High-quality plugins** for React Native can be found throughout the [React Native Directory](https://reactnative.directory) website.
@@ -92,12 +92,12 @@ If you are adding new functionality or introducing a change in behavior, we will
 
 ### Contributing to the Blog
 
-The React Native blog is generated [from the Markdown sources for the blog](https://github.com/facebook/react-native-website/tree/HEAD/website/blog).
+The React Native blog is generated [from the Markdown sources for the blog](https://github.com/react/react-native-website/tree/HEAD/website/blog).
 
 Please open an issue in the React Native website repository or tag us on [@ReactNative on Twitter](https://twitter.com/reactnative) and get the go-ahead from a maintainer before writing an article intended for the React Native blog.
 In most cases, you might want to share your article on your own blog or writing medium instead. It's worth asking, though, in case we find your article is a good fit for the blog.
 
-We recommend referring to the `react-native-website` repository [Readme file](https://github.com/facebook/react-native-website#-contributing) to learn more about contributing to the website in general.
+We recommend referring to the `react-native-website` repository [Readme file](https://github.com/react/react-native-website#-contributing) to learn more about contributing to the website in general.
 
 ## Contributing Code
 
@@ -109,7 +109,7 @@ Whenever you are ready to contribute code, check out our [step-by-step guide to
 
 ### Tests
 
-Tests help us prevent regressions from being introduced to the codebase. The GitHub repository is continuously tested using CircleCI, the results of which are available through the Checks functionality on [commits](https://github.com/facebook/react-native/commits/HEAD) and pull requests.
+Tests help us prevent regressions from being introduced to the codebase. The GitHub repository is continuously tested using CircleCI, the results of which are available through the Checks functionality on [commits](https://github.com/react/react-native/commits/HEAD) and pull requests.
 
 You can learn more about running and writing tests on the [How to Run and Write Tests](/contributing/how-to-run-and-write-tests) page.
 
diff --git a/website/contributing/how-to-contribute-code.md b/website/contributing/how-to-contribute-code.md
index 4bff72313b0..46ba27a7b76 100644
--- a/website/contributing/how-to-contribute-code.md
+++ b/website/contributing/how-to-contribute-code.md
@@ -4,8 +4,8 @@ title: How to Contribute Code
 
 Thank you for your interest in contributing to React Native! From commenting on and triaging issues, to reviewing and sending PRs, [all contributions are welcome](/contributing/overview). In this document, we'll cover the steps to contributing code to React Native.
 
-If you are eager to start contributing code right away, we have a list of [`Good first issues`](https://github.com/facebook/react-native/labels/good%20first%20issue) that contain bugs which have a relatively limited scope.
-Issues labeled [`Help wanted`](https://github.com/facebook/react-native/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A%22help+wanted+%3Aoctocat%3A%22+sort%3Aupdated-desc+) are good issues to submit a PR for.
+If you are eager to start contributing code right away, we have a list of [`Good first issues`](https://github.com/react/react-native/labels/good%20first%20issue) that contain bugs which have a relatively limited scope.
+Issues labeled [`Help wanted`](https://github.com/react/react-native/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A%22help+wanted+%3Aoctocat%3A%22+sort%3Aupdated-desc+) are good issues to submit a PR for.
 
 ## Prerequisites
 
@@ -31,14 +31,14 @@ Now you are set up to run several commands:
 - `yarn test-typescript` runs the [TypeScript](https://www.typescriptlang.org/) typechecks.
 - `yarn test-ios` runs the iOS test suite (macOS required).
 - `yarn build` builds all configured packages — in general, this command only needs to be run by CI ahead of publishing.
-  - Packages which require a build are configured in [scripts/build/config.js](https://github.com/facebook/react-native/blob/main/scripts/build/config.js).
+  - Packages which require a build are configured in [scripts/build/config.js](https://github.com/react/react-native/blob/main/scripts/build/config.js).
 - `yarn build-types` generates TypeScript types for the public API and updates the snapshot.
 
 ## Testing your Changes
 
 Tests help us prevent regressions from being introduced to the codebase. We recommend running `yarn test` or the platform-specific scripts above to make sure you don't introduce any regressions as you work on your change.
 
-The GitHub repository is [continuously tested](/contributing/how-to-run-and-write-tests#continuous-testing) using CircleCI, the results of which are available through the Checks functionality on [commits](https://github.com/facebook/react-native/commits/main) and pull requests.
+The GitHub repository is [continuously tested](/contributing/how-to-run-and-write-tests#continuous-testing) using CircleCI, the results of which are available through the Checks functionality on [commits](https://github.com/react/react-native/commits/main) and pull requests.
 
 You can learn more about running and writing tests on the [How to Run and Write Tests](/contributing/how-to-run-and-write-tests) page.
 
@@ -88,4 +88,4 @@ In order to accept your pull request, we need you to submit a [Contributor Licen
 
 ## License
 
-By contributing to React Native, you agree that your contributions will be licensed under the [LICENSE](https://github.com/facebook/react-native/blob/main/LICENSE) file in the root directory of the React Native repository.
+By contributing to React Native, you agree that your contributions will be licensed under the [LICENSE](https://github.com/react/react-native/blob/main/LICENSE) file in the root directory of the React Native repository.
diff --git a/website/contributing/how-to-open-a-pull-request.md b/website/contributing/how-to-open-a-pull-request.md
index ee67f066139..5bf291c08b6 100644
--- a/website/contributing/how-to-open-a-pull-request.md
+++ b/website/contributing/how-to-open-a-pull-request.md
@@ -18,16 +18,16 @@ The React Native source code is hosted on GitHub. You can interact with the git
 
 ### 2. Get the source code
 
-While you can browse the source code for React Native on [GitHub](https://github.com/facebook/react-native), we recommend you set up a fork on your local machine.
+While you can browse the source code for React Native on [GitHub](https://github.com/react/react-native), we recommend you set up a fork on your local machine.
 
-1. Go to https://github.com/facebook/react-native.
+1. Go to https://github.com/react/react-native.
 2. Click on "Fork" button on the upper right.
 3. When asked, select your username as the host for this fork.
 
 You will now have a fork of React Native on GitHub at https://github.com/your_username/react-native. Next, you will grab a copy of the source code for your local machine. Open a shell and type the following commands:
 
 ```bash
-git clone https://github.com/facebook/react-native.git
+git clone https://github.com/react/react-native.git
 cd react-native
 git remote add fork https://github.com/your_username/react-native.git
 ```
@@ -38,7 +38,7 @@ If the above seems new to you, do not be scared. You can access a shell through
 
 A new `react-native` directory will be created with the contents of the core React Native repository. This directory is actually a clone of the React Native git repository. It is set up with two remotes:
 
-- `origin` for the upstream https://github.com/facebook/react-native repository
+- `origin` for the upstream https://github.com/react/react-native repository
 - `fork` for the fork of React Native on your own GitHub account.
 
 ### 3. Create a branch
@@ -79,7 +79,7 @@ IDE project configurations:
 
 ### 3. Run your changes
 
-The package rn-tester can be used to run and validate your changes. You can learn more in [RNTester readme](https://github.com/facebook/react-native/blob/main/packages/rn-tester/README.md).
+The package rn-tester can be used to run and validate your changes. You can learn more in [RNTester readme](https://github.com/react/react-native/blob/main/packages/rn-tester/README.md).
 
 ### 4. Test your changes
 
@@ -123,7 +123,7 @@ This guide covers enough information to help you along with your first contribut
 
 ### 2. Push your changes to GitHub
 
-Once your changes have been commited to version control, you can push them to GitHub.
+Once your changes have been committed to version control, you can push them to GitHub.
 
 ```bash
 git push fork <my_feature_branch>
diff --git a/website/contributing/how-to-report-a-bug.md b/website/contributing/how-to-report-a-bug.md
index 8ba22b879c0..7926da1893a 100644
--- a/website/contributing/how-to-report-a-bug.md
+++ b/website/contributing/how-to-report-a-bug.md
@@ -2,14 +2,14 @@
 title: How to Report a Bug
 ---
 
-Reporting a bug for React Native is one of the best way to start contributing to the project. We use [GitHub issues](https://github.com/facebook/react-native/issues) as the main channel for handling new bug reports.
+Reporting a bug for React Native is one of the best way to start contributing to the project. We use [GitHub issues](https://github.com/react/react-native/issues) as the main channel for handling new bug reports.
 
-Before opening a new bug, please [search if the bug already exists](https://github.com/facebook/react-native/issues?q=sort%3Aupdated-desc%20is%3Aissue) in our issue tracker. Most of the time, that's the fastest way to find a response as someone else already experienced the same problem.
+Before opening a new bug, please [search if the bug already exists](https://github.com/react/react-native/issues?q=sort%3Aupdated-desc%20is%3Aissue) in our issue tracker. Most of the time, that's the fastest way to find a response as someone else already experienced the same problem.
 
 If you can't find your bug in the issue tracker, you can open a new one. Once you create a new issue, make sure you:
 
 - Add a description of the problem.
-- Follow the instructions on the [issue template](https://github.com/facebook/react-native/issues/new?template=bug_report.yml).
+- Follow the instructions on the [issue template](https://github.com/react/react-native/issues/new?template=bug_report.yml).
 - Add the React Native version you're using.
 - Add the output of the `npx @react-native-community/cli info` command.
 - Add screenshots and videos of the problem if applicable.
@@ -35,13 +35,13 @@ This process is crucial, as often issues are actually solved by creating a repro
 
 Due to the amount of traffic we have on React Native, we can accept only one of those as a valid reproducer:
 
-1. For majority of bugs: send us a Pull Request with the [RNTesterPlayground.js](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/Playground/RNTesterPlayground.js) edited to reproduce your bug.
+1. For majority of bugs: send us a Pull Request with the [RNTesterPlayground.js](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/Playground/RNTesterPlayground.js) edited to reproduce your bug.
 2. If your bug is UI related: a [Snack](https://snack.expo.dev).
 3. If your bug is build/upgrade related: a project using our [Reproducer Template](https://github.com/react-native-community/reproducer-react-native/generate).
 
 ### RNTesterPlayground.js
 
-The best way for you to provide a reproducer is to open a Pull Request against React Native that edits the [`RNTesterPlayground.js`](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/Playground/RNTesterPlayground.js) file.
+The best way for you to provide a reproducer is to open a Pull Request against React Native that edits the [`RNTesterPlayground.js`](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/Playground/RNTesterPlayground.js) file.
 
 :::tip
 
@@ -49,9 +49,9 @@ This reproducer will run your code against `main` of `react-native` and is the *
 
 :::
 
-The `RNTesterPlayground.js` file is located inside the RN-Tester application, our reference App. You can read more about it how it works and how to build it inside its [dedicated README file](https://github.com/facebook/react-native/blob/main/packages/rn-tester/README.md).
+The `RNTesterPlayground.js` file is located inside the RN-Tester application, our reference App. You can read more about it how it works and how to build it inside its [dedicated README file](https://github.com/react/react-native/blob/main/packages/rn-tester/README.md).
 
-An example of such type of reproducer is here: [Reproduce modal layout issues #50704](https://github.com/facebook/react-native/pull/50704/).
+An example of such type of reproducer is here: [Reproduce modal layout issues #50704](https://github.com/react/react-native/pull/50704/).
 
 Once you edit the `RNTesterPlayground.js`, you'll be able to see your code running inside the **Playground** Tab of RNTester:
 
diff --git a/website/contributing/how-to-run-and-write-tests.md b/website/contributing/how-to-run-and-write-tests.md
index fe1cee3603f..02d5052fd9d 100644
--- a/website/contributing/how-to-run-and-write-tests.md
+++ b/website/contributing/how-to-run-and-write-tests.md
@@ -25,7 +25,7 @@ yarn lint
 
 ### iOS Tests
 
-Follow the [README.md](https://github.com/facebook/react-native/blob/main/packages/rn-tester/README.md) instructions in the `packages/rn-tester` directory.
+Follow the [README.md](https://github.com/react/react-native/blob/main/packages/rn-tester/README.md) instructions in the `packages/rn-tester` directory.
 
 Then, go back to the root of your React Native checkout and run `yarn`. This will set up your JavaScript dependencies.
 
@@ -72,7 +72,7 @@ Whenever you are fixing a bug or adding new functionality to React Native, it is
 
 The JavaScript tests can be found inside `__test__` directories, colocated next to the files that are being tested. See [`TouchableHighlight-test.js`][js-jest-test] for a basic example. You can also follow Jest's [Testing React Native Apps][jest-tutorial] tutorial to learn more.
 
-[js-jest-test]: https://github.com/facebook/react-native/blob/main/Libraries/Components/Touchable/__tests__/TouchableHighlight-test.js
+[js-jest-test]: https://github.com/react/react-native/blob/main/Libraries/Components/Touchable/__tests__/TouchableHighlight-test.js
 [jest-tutorial]: https://jestjs.io/docs/en/tutorial-react-native
 
 ### iOS Integration Tests
@@ -91,21 +91,21 @@ See the following for example usage and integration points:
 - [`RNTesterIntegrationTests.m`][f-ios-integration-tests]
 - [`IntegrationTestsApp.js`][f-ios-integration-test-app]
 
-[f-ios-test-harness]: https://github.com/facebook/react-native/blob/main/IntegrationTests/IntegrationTestHarnessTest.js
-[f-ios-integration-tests]: https://github.com/facebook/react-native/blob/main/RNTester/RNTesterIntegrationTests/RNTesterIntegrationTests.m
-[f-ios-integration-test-app]: https://github.com/facebook/react-native/blob/main/IntegrationTests/IntegrationTestsApp.js
+[f-ios-test-harness]: https://github.com/react/react-native/blob/main/IntegrationTests/IntegrationTestHarnessTest.js
+[f-ios-integration-tests]: https://github.com/react/react-native/blob/main/RNTester/RNTesterIntegrationTests/RNTesterIntegrationTests.m
+[f-ios-integration-test-app]: https://github.com/react/react-native/blob/main/IntegrationTests/IntegrationTestsApp.js
 
 ### iOS Snapshot Tests
 
 A common type of integration test is the snapshot test. These tests render a component, and verify snapshots of the screen against reference images using `TestModule.verifySnapshot()`, using the [`FBSnapshotTestCase`](https://github.com/facebook/ios-snapshot-test-case) library behind the scenes. Reference images are recorded by setting `recordMode = YES` on the `RCTTestRunner`, then running the tests.
 
-Snapshots will differ slightly between 32 and 64 bit, and various OS versions, so it's recommended that you enforce tests are run with the [correct configuration](https://github.com/facebook/react-native/blob/main/scripts/.tests.env).
+Snapshots will differ slightly between 32 and 64 bit, and various OS versions, so it's recommended that you enforce tests are run with the [correct configuration](https://github.com/react/react-native/blob/main/scripts/.tests.env).
 
-It's also highly recommended that all network data be mocked out, along with other potentially troublesome dependencies. See [`SimpleSnapshotTest`](https://github.com/facebook/react-native/blob/main/IntegrationTests/SimpleSnapshotTest.js) for a basic example.
+It's also highly recommended that all network data be mocked out, along with other potentially troublesome dependencies. See [`SimpleSnapshotTest`](https://github.com/react/react-native/blob/main/IntegrationTests/SimpleSnapshotTest.js) for a basic example.
 
 If you make a change that affects a snapshot test in a pull request, such as adding a new example case to one of the examples that is snapshotted, you'll need to re-record the snapshot reference image.
 
-To do this, change `recordMode` flag to `_runner.recordMode = YES;` in [RNTester/RNTesterSnapshotTests.m](https://github.com/facebook/react-native/blob/136666e2e7d2bb8d3d51d599fc1384a2f68c43d3/RNTester/RNTesterIntegrationTests/RNTesterSnapshotTests.m#L29), re-run the failing tests, then flip record back to `NO` and submit/update your pull request and wait to see if the CircleCI build passes.
+To do this, change `recordMode` flag to `_runner.recordMode = YES;` in [RNTester/RNTesterSnapshotTests.m](https://github.com/react/react-native/blob/136666e2e7d2bb8d3d51d599fc1384a2f68c43d3/RNTester/RNTesterIntegrationTests/RNTesterSnapshotTests.m#L29), re-run the failing tests, then flip record back to `NO` and submit/update your pull request and wait to see if the CircleCI build passes.
 
 ### Android Unit Tests
 
@@ -117,7 +117,7 @@ We recommend browsing through these to get an idea of what a good unit test migh
 
 We use [CircleCI][config-circleci] to automatically run our open source tests. CircleCI will run these tests whenever a commit is added to a pull request, as a way to help maintainers understand whether a code change introduces a regression. The tests also run on commits to the `main` and `*-stable` branches in order to keep track of the health of these branches.
 
-[config-circleci]: https://github.com/facebook/react-native/blob/main/.circleci/config.yml
+[config-circleci]: https://github.com/react/react-native/blob/main/.circleci/config.yml
 
 There's another set of tests that run within Meta's internal test infrastructure. Some of these tests are integration tests defined by internal consumers of React Native (e.g. unit tests for a React Native surface in the Facebook app).
 
diff --git a/website/contributing/labeling-github-issues.md b/website/contributing/labeling-github-issues.md
index ff71019e783..a8929e74ea8 100644
--- a/website/contributing/labeling-github-issues.md
+++ b/website/contributing/labeling-github-issues.md
@@ -2,22 +2,22 @@
 title: Labeling GitHub Issues
 ---
 
-Most of [our labels](https://github.com/facebook/react-native/issues/labels) have a prefix that provides a hint of their purpose.
+Most of [our labels](https://github.com/react/react-native/issues/labels) have a prefix that provides a hint of their purpose.
 
-You'll notice right away there's two label prefixes that dominate the list, [API:](https://github.com/facebook/react-native/labels?utf8=%E2%9C%93&q=API%3A), and [Component:](https://github.com/facebook/react-native/labels?utf8=%E2%9C%93&q=Component%3A).
+You'll notice right away there's two label prefixes that dominate the list, [API:](https://github.com/react/react-native/labels?utf8=%E2%9C%93&q=API%3A), and [Component:](https://github.com/react/react-native/labels?utf8=%E2%9C%93&q=Component%3A).
 
 These generally denote issues and pull requests related to an API or Component in the core React Native library. It helps us understand, at a glance, which components are in dire need of documentation or support.
 
 These labels are added automatically by one of our [bots](/contributing/bots-reference), but feel free to adjust them if the bot mis-attributes an issue.
 
-- The `p:` class of labels denote a company with whom with maintain some sort of [relationship](https://github.com/facebook/react-native/blob/main/ECOSYSTEM.md). These include Microsoft and Expo, for example. These are also added automatically by our tooling, based on the issue author.
+- The `p:` class of labels denote a company with whom with maintain some sort of [relationship](https://github.com/react/react-native/blob/main/ECOSYSTEM.md). These include Microsoft and Expo, for example. These are also added automatically by our tooling, based on the issue author.
 - The `DX:` class of labels denote areas that deal with the developer experience. Use these for issues that negatively impact people who use React Native.
 - The `Tool:` class of labels denote tooling. CocoaPods, Buck...
 - The `Resolution:` labels help us communicate the status of an issue. Does it need more information? What needs to be done before it can move forward?
 - The `Type:` labels are added by a bot, based on the changelog field in a pull request. They may also refer to types of issues that are not bug reports.
 - The `Platform:` labels help us identify which development platform or target OS is affected by the issue.
 
-When unsure of the meaning of a particular label, go to https://github.com/facebook/react-native/labels and look at the description field. We'll do our best to properly document these.
+When unsure of the meaning of a particular label, go to https://github.com/react/react-native/labels and look at the description field. We'll do our best to properly document these.
 
 ### Label Actions
 
diff --git a/website/contributing/managing-pull-requests.mdx b/website/contributing/managing-pull-requests.mdx
index 5eb3299a3ff..c8d40aef037 100644
--- a/website/contributing/managing-pull-requests.mdx
+++ b/website/contributing/managing-pull-requests.mdx
@@ -14,7 +14,7 @@ Any pull request may require a deeper understanding of some area of React Native
 
 ## Reviewing PRs
 
-Pull Requests need to be reviewed and approved using GitHub's review feature before they can be merged. While anyone has the ability to review and approve a pull request, we typically only consider a pull request ready to be merged when the approval comes from one of the [contributors](https://github.com/facebook/react-native/blob/main/ECOSYSTEM.md).
+Pull Requests need to be reviewed and approved using GitHub's review feature before they can be merged. While anyone has the ability to review and approve a pull request, we typically only consider a pull request ready to be merged when the approval comes from one of the [contributors](https://github.com/react/react-native/blob/main/ECOSYSTEM.md).
 
 {/* alex ignore clearly */}
 
@@ -22,17 +22,17 @@ So you've found a pull request that you feel confident reviewing. Please make us
 
 Consider starting with pull requests that have been flagged as lacking a changelog or test plan.
 
-- [PRs that appear to lack a changelog](https://github.com/facebook/react-native/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+label%3A%22Missing+Changelog%22+) - take a look and see if you can add the changelog yourself by editing the PR. After doing so, remove the "Missing Changelog" label.
-- [PRs that are missing a test plan](https://github.com/facebook/react-native/pulls?q=is%3Apr+label%3A%22Missing+Test+Plan%22+is%3Aclosed) - open the pull request and look for a test plan. If the test plan looks sufficient, remove the "Missing Test Plan"" label. If there is no test plan, or it looks incomplete, add a comment politely asking the author to consider adding a test plan.
+- [PRs that appear to lack a changelog](https://github.com/react/react-native/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+label%3A%22Missing+Changelog%22+) - take a look and see if you can add the changelog yourself by editing the PR. After doing so, remove the "Missing Changelog" label.
+- [PRs that are missing a test plan](https://github.com/react/react-native/pulls?q=is%3Apr+label%3A%22Missing+Test+Plan%22+is%3Aclosed) - open the pull request and look for a test plan. If the test plan looks sufficient, remove the "Missing Test Plan"" label. If there is no test plan, or it looks incomplete, add a comment politely asking the author to consider adding a test plan.
 
-A pull request must pass all the tests before it can be merged. They run on every commit on `main` and pull request. A quick way to help us get pull requests ready for review is to [search for pull requests that are failing the pre-commit tests](https://github.com/facebook/react-native/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+label%3A%22CLA+Signed%22+status%3Afailure+) and determine if they need to be revised. The failing test is usually listed near the bottom of the thread, under "Some checks were not successful."
+A pull request must pass all the tests before it can be merged. They run on every commit on `main` and pull request. A quick way to help us get pull requests ready for review is to [search for pull requests that are failing the pre-commit tests](https://github.com/react/react-native/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+label%3A%22CLA+Signed%22+status%3Afailure+) and determine if they need to be revised. The failing test is usually listed near the bottom of the thread, under "Some checks were not successful."
 
-- Take a quick glance at the [latest tests runs on main](https://circleci.com/gh/facebook/react-native/tree/main). Is `main` green? If so,
+- Take a quick glance at the [latest tests runs on main](https://circleci.com/gh/react/react-native/tree/main). Is `main` green? If so,
   - Does it look like the failure may be related to the changes in this pull request? Ask the author to investigate.
   - Even if `main` is currently green, consider the possibility that the commits in the pull requests may be based off a commit from a point in time when `main` was broken. If you believe this may be the case, ask the author to rebase their changes on top of `main` in order to pull in any fixes that may have landed after they started working on the pull request.
-- If `main` appears to be broken, look for any [issues labeled as "CI Test Failure"](https://github.com/facebook/react-native/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A%22%E2%9D%8CCI+Test+Failure%22+).
+- If `main` appears to be broken, look for any [issues labeled as "CI Test Failure"](https://github.com/react/react-native/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+label%3A%22%E2%9D%8CCI+Test+Failure%22+).
   - If you find an issue that seems related to the failure on `main`, go back to the pull request and thank the author for proposing these changes, and let them know that the test failure may be unrelated to their particular change (do not forget to link back to the CI Test Failure issue, as this will help the author know when they can try running tests again).
-  - If you cannot find an existing CI Test Failure issue that describes the problem you've observed on `main`, please submit a new issue and use the "CI Test Failure" label to let others know that `main` is broken (see [this issue](https://github.com/facebook/react-native/issues/23108) for an example).
+  - If you cannot find an existing CI Test Failure issue that describes the problem you've observed on `main`, please submit a new issue and use the "CI Test Failure" label to let others know that `main` is broken (see [this issue](https://github.com/react/react-native/issues/23108) for an example).
 
 ## How we prioritize PRs
 
diff --git a/website/contributing/triaging-github-issues.md b/website/contributing/triaging-github-issues.md
index a08dc8dd9d9..138b4c78423 100644
--- a/website/contributing/triaging-github-issues.md
+++ b/website/contributing/triaging-github-issues.md
@@ -2,7 +2,7 @@
 title: Triaging GitHub Issues
 ---
 
-Start out by looking at issues that need triage, as identified by the ["Needs: Triage" label](https://github.com/facebook/react-native/issues?q=is%3Aissue+is%3Aopen+label%3A%22Needs%3A+Triage+%3Amag%3A%22).
+Start out by looking at issues that need triage, as identified by the ["Needs: Triage" label](https://github.com/react/react-native/issues?q=is%3Aissue+is%3Aopen+label%3A%22Needs%3A+Triage+%3Amag%3A%22).
 
 - Is this a request for code-level help with an individual app? Would this be a better fit for Stack Overflow? If so, apply the "Resolution: For Stack Overflow" label.
 - Does this issue make appropriate use of the template? If not, apply the "Needs: Template" label.
@@ -27,7 +27,7 @@ If the issue contains an unformatted block of code, surround it with three back
 
 Are there any labels you can add to help categorize it better? If the issue only affects Android apps, you may add a "Platform: Android" label. Perhaps the issue only manifests itself when developing on Windows, in which case you might add the "Platform: Windows" label.
 
-We have a long list of [labels](https://github.com/facebook/react-native/issues/labels), please take a look and see if anything might apply!
+We have a long list of [labels](https://github.com/react/react-native/issues/labels), please take a look and see if anything might apply!
 
 ## Handling Duplicates
 
diff --git a/website/core/RNRepoLink.tsx b/website/core/RNRepoLink.tsx
index 77d68b3ed2a..02b067c0901 100644
--- a/website/core/RNRepoLink.tsx
+++ b/website/core/RNRepoLink.tsx
@@ -7,7 +7,7 @@ type Props = ComponentProps<'a'>;
 export default function RNRepoLink({href, children, ...rest}: Props) {
   return (
     <A
-      href={`https://github.com/facebook/react-native/blob/${getTemplateBranchNameForCurrentVersion()}/${href.startsWith('/') ? href.slice(1) : href}`}
+      href={`https://github.com/react/react-native/blob/${getTemplateBranchNameForCurrentVersion()}/${href.startsWith('/') ? href.slice(1) : href}`}
       {...rest}>
       {children}
     </A>
diff --git a/website/docusaurus.config.ts b/website/docusaurus.config.ts
index 04af0c9015f..4552a5a2057 100644
--- a/website/docusaurus.config.ts
+++ b/website/docusaurus.config.ts
@@ -36,8 +36,7 @@ const commonDocsOptions: PluginContentDocs.Options = {
   showLastUpdateAuthor: false,
   showLastUpdateTime: true,
   editUrl: (options => {
-    const baseUrl =
-      'https://github.com/facebook/react-native-website/edit/main';
+    const baseUrl = 'https://github.com/react/react-native-website/edit/main';
     const nextReleasePath = `docs/${options.docPath}`;
     const isNextRelease = options.version === 'current';
     const buttons: EditUrlButton[] = [
@@ -80,7 +79,7 @@ const config: Config = {
     v4: true,
     // Make Docusaurus build faster - enabled by default
     // See https://github.com/facebook/docusaurus/issues/10556
-    // See https://github.com/facebook/react-native-website/pull/4268
+    // See https://github.com/react/react-native-website/pull/4268
     // See https://docusaurus.io/blog/releases/3.6
     faster: (process.env.DOCUSAURUS_FASTER ?? 'true') === 'true',
   },
@@ -479,7 +478,7 @@ const config: Config = {
           position: 'right',
         },
         {
-          href: 'https://github.com/facebook/react-native',
+          href: 'https://github.com/react/react-native',
           'aria-label': 'GitHub repository',
           position: 'right',
           className: 'navbar-github-link',
@@ -549,7 +548,7 @@ const config: Config = {
             },
             {
               label: 'GitHub',
-              href: 'https://github.com/facebook/react-native',
+              href: 'https://github.com/react/react-native',
             },
           ],
         },
diff --git a/website/package.json b/website/package.json
index 4cab8b5a324..8803350d1fb 100644
--- a/website/package.json
+++ b/website/package.json
@@ -5,9 +5,9 @@
   "private": true,
   "license": "CC-BY-4.0",
   "homepage": "https://reactnative.dev/",
-  "repository": "github:facebook/react-native-website",
+  "repository": "github:react/react-native-website",
   "bugs": {
-    "url": "https://github.com/facebook/react-native-website/issues"
+    "url": "https://github.com/react/react-native-website/issues"
   },
   "scripts": {
     "docusaurus": "docusaurus",
diff --git a/website/src/components/Home/Hero/index.tsx b/website/src/components/Home/Hero/index.tsx
index c22036dfa0d..672069f932b 100644
--- a/website/src/components/Home/Hero/index.tsx
+++ b/website/src/components/Home/Hero/index.tsx
@@ -29,11 +29,11 @@ function Hero() {
           Follow @reactnative
         </a>
         <GitHubButton
-          href="https://github.com/facebook/react-native"
+          href="https://github.com/react/react-native"
           data-icon="octicon-star"
           data-size="large"
           data-color-scheme={colorMode}
-          aria-label="Star facebook/react-native on GitHub">
+          aria-label="Star react/react-native on GitHub">
           Star
         </GitHubButton>
       </div>
diff --git a/website/src/theme/MDXComponents/InlineCode.tsx b/website/src/theme/MDXComponents/InlineCode.tsx
index d2eec0bddab..206e23da5e7 100644
--- a/website/src/theme/MDXComponents/InlineCode.tsx
+++ b/website/src/theme/MDXComponents/InlineCode.tsx
@@ -33,7 +33,7 @@ const MarkdownInlineCode = React.memo(function MarkdownInlineCodeInner(
 
 // Gives the ability to use basic Markdown links inside inline code blocks
 // We use RegExp because a full Markdown parser would be quite heavy
-// See https://github.com/facebook/react-native-website/pull/3807
+// See https://github.com/react/react-native-website/pull/3807
 function linkify(input) {
   // Inspired by https://github.com/gakimball/transform-markdown-links
   // Thank you: http://stackoverflow.com/a/32382702 (with some modifications)
diff --git a/website/versioned_docs/version-0.87/animations.md b/website/versioned_docs/version-0.87/animations.md
index 3c7ae0cbbb8..7f15bce3685 100644
--- a/website/versioned_docs/version-0.87/animations.md
+++ b/website/versioned_docs/version-0.87/animations.md
@@ -557,7 +557,7 @@ The native driver also works with `Animated.event`. This is especially useful fo
 </Animated.ScrollView>
 ```
 
-You can see the native driver in action by running the [RNTester app](https://github.com/facebook/react-native/blob/main/packages/rn-tester/), then loading the Native Animated Example. You can also take a look at the [source code](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/NativeAnimation/NativeAnimationsExample.js) to learn how these examples were produced.
+You can see the native driver in action by running the [RNTester app](https://github.com/react/react-native/blob/main/packages/rn-tester/), then loading the Native Animated Example. You can also take a look at the [source code](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/NativeAnimation/NativeAnimationsExample.js) to learn how these examples were produced.
 
 #### Caveats
 
@@ -585,8 +585,8 @@ While using transform styles such as `rotateY`, `rotateX`, and others ensure the
 
 The RNTester app has various examples of `Animated` in use:
 
-- [AnimatedGratuitousApp](https://github.com/facebook/react-native/tree/main/packages/rn-tester/js/examples/AnimatedGratuitousApp)
-- [NativeAnimationsExample](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/NativeAnimation/NativeAnimationsExample.js)
+- [AnimatedGratuitousApp](https://github.com/react/react-native/tree/main/packages/rn-tester/js/examples/AnimatedGratuitousApp)
+- [NativeAnimationsExample](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/NativeAnimation/NativeAnimationsExample.js)
 
 ## `LayoutAnimation` API
 
@@ -664,7 +664,7 @@ const styles = StyleSheet.create({
 });
 ```
 
-This example uses a preset value, you can customize the animations as you need, see [LayoutAnimation.js](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/LayoutAnimation/LayoutAnimation.js) for more information.
+This example uses a preset value, you can customize the animations as you need, see [LayoutAnimation.js](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/LayoutAnimation/LayoutAnimation.js) for more information.
 
 ## Additional notes
 
diff --git a/website/versioned_docs/version-0.87/build-speed.md b/website/versioned_docs/version-0.87/build-speed.md
index 0db1929f4f3..781e5fb78d5 100644
--- a/website/versioned_docs/version-0.87/build-speed.md
+++ b/website/versioned_docs/version-0.87/build-speed.md
@@ -45,7 +45,7 @@ $ ./gradlew :app:assembleDebug -PreactNativeArchitectures=x86,x86_64
 
 This can be useful if you wish to build your Android App on a CI and use a matrix to parallelize the build of the different architectures.
 
-If you wish, you can also override this value locally, using the `gradle.properties` file you have in the [top-level folder](https://github.com/facebook/react-native/blob/19cf70266eb8ca151aa0cc46ac4c09cb987b2ceb/template/android/gradle.properties#L30-L33) of your project:
+If you wish, you can also override this value locally, using the `gradle.properties` file you have in the [top-level folder](https://github.com/react/react-native/blob/19cf70266eb8ca151aa0cc46ac4c09cb987b2ceb/template/android/gradle.properties#L30-L33) of your project:
 
 ```
 # Use this property to specify which architecture you want to build.
@@ -153,7 +153,7 @@ Open `ios/Podfile` in your editor and uncomment the `ccache_enabled` line.
 
 ```ruby
   post_install do |installer|
-    # https://github.com/facebook/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
+    # https://github.com/react/react-native/blob/main/packages/react-native/scripts/react_native_pods.rb#L197-L202
     react_native_post_install(
       installer,
       config[:reactNativePath],
diff --git a/website/versioned_docs/version-0.87/button.md b/website/versioned_docs/version-0.87/button.md
index 23501057f52..9343da4b3de 100644
--- a/website/versioned_docs/version-0.87/button.md
+++ b/website/versioned_docs/version-0.87/button.md
@@ -5,7 +5,7 @@ title: Button
 
 A basic button component that should render nicely on any platform. Supports a minimal level of customization.
 
-If this button doesn't look right for your app, you can build your own button using [Pressable](pressable). For inspiration, look at the [source code for the Button component](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Components/Button.js).
+If this button doesn't look right for your app, you can build your own button using [Pressable](pressable). For inspiration, look at the [source code for the Button component](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Components/Button.js).
 
 ```tsx
 <Button
diff --git a/website/versioned_docs/version-0.87/communication-ios.md b/website/versioned_docs/version-0.87/communication-ios.md
index 89a64ff9b4c..ea2b21499f7 100644
--- a/website/versioned_docs/version-0.87/communication-ios.md
+++ b/website/versioned_docs/version-0.87/communication-ios.md
@@ -57,7 +57,7 @@ rootView.appProperties = @{@"images" : imageList};
 It is fine to update properties anytime. However, updates have to be performed on the main thread. You use the getter on any thread.
 
 :::note
-Currently, there is a known issue where setting appProperties during the bridge startup, the change can be lost. See https://github.com/facebook/react-native/issues/20115 for more information.
+Currently, there is a known issue where setting appProperties during the bridge startup, the change can be lost. See https://github.com/react/react-native/issues/20115 for more information.
 :::
 
 There is no way to update only a few properties at a time. We suggest that you build it into your own wrapper instead.
@@ -188,7 +188,7 @@ Let's look at an example.
 
 In the example we have a `FlexibleSizeExampleView` view that holds a root view. We create the root view, initialize it and set the delegate. The delegate will handle size updates. Then, we set the root view's size flexibility to `RCTRootViewSizeFlexibilityHeight`, which means that `rootViewDidChangeIntrinsicSize:` method will be called every time the React Native content changes its height. Finally, we set the root view's width and position. Note that we set there height as well, but it has no effect as we made the height RN-dependent.
 
-You can checkout full source code of the example [here](https://github.com/facebook/react-native/blob/main/packages/rn-tester/RNTester/NativeExampleViews/FlexibleSizeExampleView.mm).
+You can checkout full source code of the example [here](https://github.com/react/react-native/blob/main/packages/rn-tester/RNTester/NativeExampleViews/FlexibleSizeExampleView.mm).
 
 It's fine to change root view's size flexibility mode dynamically. Changing flexibility mode of a root view will schedule a layout recalculation and the delegate `rootViewDidChangeIntrinsicSize:` method will be called once the content size is known.
 
diff --git a/website/versioned_docs/version-0.87/debugging.md b/website/versioned_docs/version-0.87/debugging.md
index c4c299a2677..c7f0ae0e54c 100644
--- a/website/versioned_docs/version-0.87/debugging.md
+++ b/website/versioned_docs/version-0.87/debugging.md
@@ -87,7 +87,7 @@ LogBox.ignoreLogs([
 
 :::note
 
-LogBox will treat certain errors from React as warnings, which will mean they don't display as an in-app error notification. Advanced users can change this behaviour by customising LogBox's warning filter using [`LogBoxData.setWarningFilter()`](https://github.com/facebook/react-native/blob/d334f4d77eea538dff87fdcf2ebc090246cfdbb0/packages/react-native/Libraries/LogBox/Data/LogBoxData.js#L338).
+LogBox will treat certain errors from React as warnings, which will mean they don't display as an in-app error notification. Advanced users can change this behaviour by customising LogBox's warning filter using [`LogBoxData.setWarningFilter()`](https://github.com/react/react-native/blob/d334f4d77eea538dff87fdcf2ebc090246cfdbb0/packages/react-native/Libraries/LogBox/Data/LogBoxData.js#L338).
 
 :::
 
diff --git a/website/versioned_docs/version-0.87/flatlist.md b/website/versioned_docs/version-0.87/flatlist.md
index 7bc9884fa34..ee79cdf88de 100644
--- a/website/versioned_docs/version-0.87/flatlist.md
+++ b/website/versioned_docs/version-0.87/flatlist.md
@@ -650,7 +650,7 @@ When `true`, offscreen child views are removed from their native backing supervi
 
 ### `viewabilityConfig`
 
-See [`ViewabilityHelper.js`](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Lists/ViewabilityHelper.js) for flow type and further documentation.
+See [`ViewabilityHelper.js`](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Lists/ViewabilityHelper.js) for flow type and further documentation.
 
 | Type              |
 | ----------------- |
@@ -665,7 +665,7 @@ See [`ViewabilityHelper.js`](https://github.com/facebook/react-native/blob/main/
 | itemVisiblePercentThreshold      | number  |
 | waitForInteraction               | boolean |
 
-At least one of the `viewAreaCoveragePercentThreshold` or `itemVisiblePercentThreshold` is required. This needs to be done in the `constructor` to avoid following error ([ref](https://github.com/facebook/react-native/issues/17408)):
+At least one of the `viewAreaCoveragePercentThreshold` or `itemVisiblePercentThreshold` is required. This needs to be done in the `constructor` to avoid following error ([ref](https://github.com/react/react-native/issues/17408)):
 
 ```
   Error: Changing viewabilityConfig on the fly is not supported
diff --git a/website/versioned_docs/version-0.87/handling-touches.md b/website/versioned_docs/version-0.87/handling-touches.md
index b9604b393c0..045365dc21a 100644
--- a/website/versioned_docs/version-0.87/handling-touches.md
+++ b/website/versioned_docs/version-0.87/handling-touches.md
@@ -176,4 +176,4 @@ Gestures commonly used on devices with touchable screens include swipes and pans
 
 ## Known issues
 
-- [react-native#29308](https://github.com/facebook/react-native/issues/29308#issuecomment-792864162): The touch area never extends past the parent view bounds and on Android negative margin is not supported.
+- [react-native#29308](https://github.com/react/react-native/issues/29308#issuecomment-792864162): The touch area never extends past the parent view bounds and on Android negative margin is not supported.
diff --git a/website/versioned_docs/version-0.87/image.md b/website/versioned_docs/version-0.87/image.md
index 3f83be8c19c..b43614057b3 100644
--- a/website/versioned_docs/version-0.87/image.md
+++ b/website/versioned_docs/version-0.87/image.md
@@ -112,7 +112,7 @@ dependencies {
 ```
 
 :::note
-The version listed above may not be updated in time. Please check [`packages/react-native/gradle/libs.versions.toml`](https://github.com/facebook/react-native/blob/main/packages/react-native/gradle/libs.versions.toml) in the main repo to see which fresco version is being used in a specific tagged version.
+The version listed above may not be updated in time. Please check [`packages/react-native/gradle/libs.versions.toml`](https://github.com/react/react-native/blob/main/packages/react-native/gradle/libs.versions.toml) in the main repo to see which fresco version is being used in a specific tagged version.
 :::
 
 ---
diff --git a/website/versioned_docs/version-0.87/imagebackground.md b/website/versioned_docs/version-0.87/imagebackground.md
index 66ee0f9a198..da1c57f1fdd 100644
--- a/website/versioned_docs/version-0.87/imagebackground.md
+++ b/website/versioned_docs/version-0.87/imagebackground.md
@@ -9,7 +9,7 @@ Use a [`View`](view.md) with an absolutely positioned [`Image`](image.md) instea
 
 A common feature request from developers familiar with the web is `background-image`. To handle this use case, you can use the `<ImageBackground>` component, which has the same props as `<Image>`, and add whatever children to it you would like to layer on top of it.
 
-You might not want to use `<ImageBackground>` in some cases, since the implementation is basic. Refer to `<ImageBackground>`'s [source code](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Image/ImageBackground.js) for more insight, and create your own custom component when needed.
+You might not want to use `<ImageBackground>` in some cases, since the implementation is basic. Refer to `<ImageBackground>`'s [source code](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Image/ImageBackground.js) for more insight, and create your own custom component when needed.
 
 Note that you must specify some width and height style attributes.
 
diff --git a/website/versioned_docs/version-0.87/inputaccessoryview.md b/website/versioned_docs/version-0.87/inputaccessoryview.md
index 30c86719e14..f971697270a 100644
--- a/website/versioned_docs/version-0.87/inputaccessoryview.md
+++ b/website/versioned_docs/version-0.87/inputaccessoryview.md
@@ -60,7 +60,7 @@ const styles = StyleSheet.create({
 export default App;
 ```
 
-This component can also be used to create sticky text inputs (text inputs which are anchored to the top of the keyboard). To do this, wrap a `TextInput` with the `InputAccessoryView` component, and don't set a `nativeID`. For an example, look at [InputAccessoryViewExample.js](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/InputAccessoryView/InputAccessoryViewExample.js).
+This component can also be used to create sticky text inputs (text inputs which are anchored to the top of the keyboard). To do this, wrap a `TextInput` with the `InputAccessoryView` component, and don't set a `nativeID`. For an example, look at [InputAccessoryViewExample.js](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/InputAccessoryView/InputAccessoryViewExample.js).
 
 ---
 
@@ -94,5 +94,5 @@ An ID which is used to associate this `InputAccessoryView` to specified TextInpu
 
 # Known issues
 
-- [react-native#18997](https://github.com/facebook/react-native/issues/18997): Doesn't support multiline `TextInput`
-- [react-native#20157](https://github.com/facebook/react-native/issues/20157): Can't use with a bottom tab bar
+- [react-native#18997](https://github.com/react/react-native/issues/18997): Doesn't support multiline `TextInput`
+- [react-native#20157](https://github.com/react/react-native/issues/20157): Can't use with a bottom tab bar
diff --git a/website/versioned_docs/version-0.87/javascript-environment.md b/website/versioned_docs/version-0.87/javascript-environment.md
index d66b5a996de..300309cff36 100644
--- a/website/versioned_docs/version-0.87/javascript-environment.md
+++ b/website/versioned_docs/version-0.87/javascript-environment.md
@@ -21,7 +21,7 @@ Syntax transformers make writing code more enjoyable by allowing you to use new
 
 React Native ships with the [Babel JavaScript compiler](https://babeljs.io). Check [Babel documentation](https://babeljs.io/docs/plugins/#transform-plugins) on its supported transformations for more details.
 
-A full list of React Native's enabled transformations can be found in [@react-native/babel-preset](https://github.com/facebook/react-native/tree/main/packages/react-native-babel-preset).
+A full list of React Native's enabled transformations can be found in [@react-native/babel-preset](https://github.com/react/react-native/tree/main/packages/react-native-babel-preset).
 
 <table>
 <thead>
diff --git a/website/versioned_docs/version-0.87/layout-props.md b/website/versioned_docs/version-0.87/layout-props.md
index 87379f1e5a1..433720d88f4 100644
--- a/website/versioned_docs/version-0.87/layout-props.md
+++ b/website/versioned_docs/version-0.87/layout-props.md
@@ -658,7 +658,7 @@ See [MDN CSS Reference](https://developer.mozilla.org/en-US/docs/Web/CSS/flex-di
 
 `flexWrap` controls whether children can wrap around after they hit the end of a flex container. It works like `flex-wrap` in CSS (default: nowrap).
 
-Note it does not work anymore with `alignItems: stretch` (the default), so you may want to use `alignItems: flex-start` for example (breaking change details: https://github.com/facebook/react-native/releases/tag/v0.28.0).
+Note it does not work anymore with `alignItems: stretch` (the default), so you may want to use `alignItems: flex-start` for example (breaking change details: https://github.com/react/react-native/releases/tag/v0.28.0).
 
 See [MDN CSS Reference](https://developer.mozilla.org/en-US/docs/Web/CSS/flex-wrap) for more details.
 
diff --git a/website/versioned_docs/version-0.87/legacy/direct-manipulation.md b/website/versioned_docs/version-0.87/legacy/direct-manipulation.md
index 7eb6479d8a0..88e0e58a5bf 100644
--- a/website/versioned_docs/version-0.87/legacy/direct-manipulation.md
+++ b/website/versioned_docs/version-0.87/legacy/direct-manipulation.md
@@ -18,7 +18,7 @@ Before you use it, try to solve your problem with `setState` and [`shouldCompone
 
 ## setNativeProps with TouchableOpacity
 
-[TouchableOpacity](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Components/Touchable/TouchableOpacity.js) uses `setNativeProps` internally to update the opacity of its child component:
+[TouchableOpacity](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Components/Touchable/TouchableOpacity.js) uses `setNativeProps` internally to update the opacity of its child component:
 
 ```tsx
 const viewRef = useRef<View>();
@@ -57,7 +57,7 @@ return (
 
 This is computationally intensive compared to the original example - React needs to re-render the component hierarchy each time the opacity changes, even though other properties of the view and its children haven't changed. Usually this overhead isn't a concern but when performing continuous animations and responding to gestures, judiciously optimizing your components can improve your animations' fidelity.
 
-If you look at the implementation of `setNativeProps` in [NativeMethodsMixin](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js) you will notice that it is a wrapper around `RCTUIManager.updateView` - this is the exact same function call that results from re-rendering - see [receiveComponent in ReactNativeBaseComponent](https://github.com/facebook/react-native/blob/fb2ec1ea47c53c2e7b873acb1cb46192ac74274e/Libraries/Renderer/oss/ReactNativeRenderer-prod.js#L5793-L5813).
+If you look at the implementation of `setNativeProps` in [NativeMethodsMixin](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Renderer/implementations/ReactNativeRenderer-prod.js) you will notice that it is a wrapper around `RCTUIManager.updateView` - this is the exact same function call that results from re-rendering - see [receiveComponent in ReactNativeBaseComponent](https://github.com/react/react-native/blob/fb2ec1ea47c53c2e7b873acb1cb46192ac74274e/Libraries/Renderer/oss/ReactNativeRenderer-prod.js#L5793-L5813).
 
 ## Composite components and setNativeProps
 
diff --git a/website/versioned_docs/version-0.87/legacy/native-components-ios.md b/website/versioned_docs/version-0.87/legacy/native-components-ios.md
index b9eb22a2dfd..cd535811278 100644
--- a/website/versioned_docs/version-0.87/legacy/native-components-ios.md
+++ b/website/versioned_docs/version-0.87/legacy/native-components-ios.md
@@ -47,7 +47,7 @@ RCT_EXPORT_MODULE(RNTMap)
 Do not attempt to set the `frame` or `backgroundColor` properties on the `UIView` instance that you expose through the `-view` method.
 React Native will overwrite the values set by your custom class in order to match your JavaScript component's layout props.
 If you need this granularity of control it might be better to wrap the `UIView` instance you want to style in another `UIView` and return the wrapper `UIView` instead.
-See [Issue 2948](https://github.com/facebook/react-native/issues/2948) for more context.
+See [Issue 2948](https://github.com/react/react-native/issues/2948) for more context.
 :::
 
 :::info
@@ -476,4 +476,4 @@ The `RCTDatePickerIOSConsts` constants are exported from native by grabbing the
 }
 ```
 
-This guide covered many of the aspects of bridging over custom native components, but there is even more you might need to consider, such as custom hooks for inserting and laying out subviews. If you want to go even deeper, check out the [source code](https://github.com/facebook/react-native/tree/main/packages/react-native/React/Views) of some of the implemented components.
+This guide covered many of the aspects of bridging over custom native components, but there is even more you might need to consider, such as custom hooks for inserting and laying out subviews. If you want to go even deeper, check out the [source code](https://github.com/react/react-native/tree/main/packages/react-native/React/Views) of some of the implemented components.
diff --git a/website/versioned_docs/version-0.87/legacy/native-modules-android.md b/website/versioned_docs/version-0.87/legacy/native-modules-android.md
index cec5857a441..1b494294b5a 100644
--- a/website/versioned_docs/version-0.87/legacy/native-modules-android.md
+++ b/website/versioned_docs/version-0.87/legacy/native-modules-android.md
@@ -270,7 +270,7 @@ class MyAppPackage : ReactPackage {
 This file imports the native module you created, `CalendarModule`. It then instantiates `CalendarModule` within the `createNativeModules()` function and returns it as a list of `NativeModules` to register. If you add more native modules down the line, you can also instantiate them and add them to the list returned here.
 
 :::note
-It is worth noting that this way of registering native modules eagerly initializes all native modules when the application starts, which adds to the startup time of an application. You can use [TurboReactPackage](https://github.com/facebook/react-native/blob/main/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/TurboReactPackage.kt) as an alternative. Instead of `createNativeModules`, which return a list of instantiated native module objects, TurboReactPackage implements a `getModule(String name, ReactApplicationContext rac)` method that creates the native module object, when required. TurboReactPackage is a bit more complicated to implement at the moment. In addition to implementing a `getModule()` method, you have to implement a `getReactModuleInfoProvider()` method, which returns a list of all the native modules the package can instantiate along with a function that instantiates them, example [here](https://github.com/facebook/react-native/blob/8ac467c51b94c82d81930b4802b2978c85539925/ReactAndroid/src/main/java/com/facebook/react/CoreModulesPackage.java#L86-L165). Again, using TurboReactPackage will allow your application to have a faster startup time, but it is currently a bit cumbersome to write. So proceed with caution if you choose to use TurboReactPackages.
+It is worth noting that this way of registering native modules eagerly initializes all native modules when the application starts, which adds to the startup time of an application. You can use [TurboReactPackage](https://github.com/react/react-native/blob/main/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/TurboReactPackage.kt) as an alternative. Instead of `createNativeModules`, which return a list of instantiated native module objects, TurboReactPackage implements a `getModule(String name, ReactApplicationContext rac)` method that creates the native module object, when required. TurboReactPackage is a bit more complicated to implement at the moment. In addition to implementing a `getModule()` method, you have to implement a `getReactModuleInfoProvider()` method, which returns a list of all the native modules the package can instantiate along with a function that instantiates them, example [here](https://github.com/react/react-native/blob/8ac467c51b94c82d81930b4802b2978c85539925/ReactAndroid/src/main/java/com/facebook/react/CoreModulesPackage.java#L86-L165). Again, using TurboReactPackage will allow your application to have a faster startup time, but it is currently a bit cumbersome to write. So proceed with caution if you choose to use TurboReactPackages.
 :::
 
 To register the `CalendarModule` package, you must add `MyAppPackage` to the list of packages returned in ReactNativeHost's `getPackages()` method. Open up your `MainApplication.java` or `MainApplication.kt` file, which can be found in the following path: `android/app/src/main/java/com/your-app-name/`.
@@ -777,7 +777,7 @@ code: String, message: String, userInfo: WritableMap, throwable: Throwable
 </TabItem>
 </Tabs>
 
-For more detail, you can find the `Promise.java` interface [here](https://github.com/facebook/react-native/blob/main/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/bridge/Promise.kt). If `userInfo` is not provided, ReactNative will set it to null. For the rest of the parameters React Native will use a default value. The `message` argument provides the error `message` shown at the top of an error call stack. Below is an example of the error message shown in JavaScript from the following reject call in Java/Kotlin.
+For more detail, you can find the `Promise.java` interface [here](https://github.com/react/react-native/blob/main/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/bridge/Promise.kt). If `userInfo` is not provided, ReactNative will set it to null. For the rest of the parameters React Native will use a default value. The `message` argument provides the error `message` shown at the top of an error call stack. Below is an example of the error message shown in JavaScript from the following reject call in Java/Kotlin.
 
 Java/Kotlin reject call:
 
@@ -896,7 +896,7 @@ sendEvent(reactContext, "EventReminder", params)
 </TabItem>
 </Tabs>
 
-JavaScript modules can then register to receive events by `addListener` on the [NativeEventEmitter](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/EventEmitter/NativeEventEmitter.js) class.
+JavaScript modules can then register to receive events by `addListener` on the [NativeEventEmitter](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/EventEmitter/NativeEventEmitter.js) class.
 
 ```tsx
 import {NativeEventEmitter, NativeModules} from 'react-native';
diff --git a/website/versioned_docs/version-0.87/legacy/native-modules-ios.md b/website/versioned_docs/version-0.87/legacy/native-modules-ios.md
index d3239e16a90..7736690b66e 100644
--- a/website/versioned_docs/version-0.87/legacy/native-modules-ios.md
+++ b/website/versioned_docs/version-0.87/legacy/native-modules-ios.md
@@ -289,7 +289,7 @@ The following types are currently supported but will not be supported in TurboMo
 - Number -> float
   :::
 
-For iOS, you can also write native module methods with any argument type that is supported by the `RCTConvert` class (see [RCTConvert](https://github.com/facebook/react-native/blob/main/packages/react-native/React/Base/RCTConvert.h) for details about what is supported). The RCTConvert helper functions all accept a JSON value as input and map it to a native Objective-C type or class.
+For iOS, you can also write native module methods with any argument type that is supported by the `RCTConvert` class (see [RCTConvert](https://github.com/react/react-native/blob/main/packages/react-native/React/Base/RCTConvert.h) for details about what is supported). The RCTConvert helper functions all accept a JSON value as input and map it to a native Objective-C type or class.
 
 ### Exporting Constants
 
@@ -361,7 +361,7 @@ const onSubmit = () => {
 };
 ```
 
-A native module is supposed to invoke its callback only once. It can, however, store the callback and invoke it later. This pattern is often used to wrap iOS APIs that require delegates— see [`RCTAlertManager`](https://github.com/facebook/react-native/blob/main/packages/react-native/React/CoreModules/RCTAlertManager.mm) for an example. If the callback is never invoked, some memory is leaked.
+A native module is supposed to invoke its callback only once. It can, however, store the callback and invoke it later. This pattern is often used to wrap iOS APIs that require delegates— see [`RCTAlertManager`](https://github.com/react/react-native/blob/main/packages/react-native/React/CoreModules/RCTAlertManager.mm) for an example. If the callback is never invoked, some memory is leaked.
 
 There are two approaches to error handling with callbacks. The first is to follow Node’s convention and treat the first argument passed to the callback array as an error object.
 
@@ -426,7 +426,7 @@ const onPress = () => {
 };
 ```
 
-If you want to pass error-like objects to JavaScript, use `RCTMakeError` from [`RCTUtils.h.`](https://github.com/facebook/react-native/blob/main/packages/react-native/React/Base/RCTUtils.h) Right now this only passes an Error-shaped dictionary to JavaScript, but React Native aims to automatically generate real JavaScript Error objects in the future. You can also provide a `RCTResponseErrorBlock` argument, which is used for error callbacks and accepts an `NSError \* object`. Please note that this argument type will not be supported with TurboModules.
+If you want to pass error-like objects to JavaScript, use `RCTMakeError` from [`RCTUtils.h.`](https://github.com/react/react-native/blob/main/packages/react-native/React/Base/RCTUtils.h) Right now this only passes an Error-shaped dictionary to JavaScript, but React Native aims to automatically generate real JavaScript Error objects in the future. You can also provide a `RCTResponseErrorBlock` argument, which is used for error callbacks and accepts an `NSError \* object`. Please note that this argument type will not be supported with TurboModules.
 
 ### Promises
 
@@ -618,7 +618,7 @@ For those of you new to Swift and Objective-C, whenever you [mix the two languag
 #import <React/RCTBridgeModule.h>
 ```
 
-You can also use `RCT_EXTERN_REMAP_MODULE` and `_RCT_EXTERN_REMAP_METHOD` to alter the JavaScript name of the module or methods you are exporting. For more information see [`RCTBridgeModule`](https://github.com/facebook/react-native/blob/main/packages/react-native/React/Base/RCTBridgeModule.h).
+You can also use `RCT_EXTERN_REMAP_MODULE` and `_RCT_EXTERN_REMAP_METHOD` to alter the JavaScript name of the module or methods you are exporting. For more information see [`RCTBridgeModule`](https://github.com/react/react-native/blob/main/packages/react-native/React/Base/RCTBridgeModule.h).
 
 :::note
 Important when making third party modules: Static libraries with Swift are only supported in Xcode 9 and later. In order for the Xcode project to build when you use Swift in the iOS static library you include in the module, your main app project must contain Swift code and a bridging header itself. If your app project does not contain any Swift code, a workaround can be a single empty .swift file and an empty bridging header.
@@ -628,4 +628,4 @@ Important when making third party modules: Static libraries with Swift are only
 
 #### invalidate()
 
-Native modules can conform to the [RCTInvalidating](https://github.com/facebook/react-native/blob/main/packages/react-native/React/Base/RCTInvalidating.h) protocol on iOS by implementing the `invalidate()` method. This method [can be invoked](https://github.com/facebook/react-native/blob/0.62-stable/ReactCommon/turbomodule/core/platform/ios/RCTTurboModuleManager.mm#L456) when the native bridge is invalidated (i.e.: on devmode reload). Please use this mechanism as necessary to do the required cleanup for your native module.
+Native modules can conform to the [RCTInvalidating](https://github.com/react/react-native/blob/main/packages/react-native/React/Base/RCTInvalidating.h) protocol on iOS by implementing the `invalidate()` method. This method [can be invoked](https://github.com/react/react-native/blob/0.62-stable/ReactCommon/turbomodule/core/platform/ios/RCTTurboModuleManager.mm#L456) when the native bridge is invalidated (i.e.: on devmode reload). Please use this mechanism as necessary to do the required cleanup for your native module.
diff --git a/website/versioned_docs/version-0.87/network.md b/website/versioned_docs/version-0.87/network.md
index 1266f8cb0d3..c9dc1a6c0c0 100644
--- a/website/versioned_docs/version-0.87/network.md
+++ b/website/versioned_docs/version-0.87/network.md
@@ -256,8 +256,8 @@ The following options are currently not working with `fetch`
 - `redirect:manual`
 - `credentials:omit`
 
-* Having same name headers on Android will result in only the latest one being present. A temporary solution can be found here: https://github.com/facebook/react-native/issues/18837#issuecomment-398779994.
-* Cookie based authentication is currently unstable. You can view some of the issues raised here: https://github.com/facebook/react-native/issues/23185
+* Having same name headers on Android will result in only the latest one being present. A temporary solution can be found here: https://github.com/react/react-native/issues/18837#issuecomment-398779994.
+* Cookie based authentication is currently unstable. You can view some of the issues raised here: https://github.com/react/react-native/issues/23185
 * As a minimum on iOS, when redirected through a `302`, if a `Set-Cookie` header is present, the cookie is not set properly. Since the redirect cannot be handled manually this might cause a scenario where infinite requests occur if the redirect is the result of an expired session.
 
 ## Configuring NSURLSession on iOS
diff --git a/website/versioned_docs/version-0.87/panresponder.md b/website/versioned_docs/version-0.87/panresponder.md
index 1a32583a1ef..520aa0f3ede 100644
--- a/website/versioned_docs/version-0.87/panresponder.md
+++ b/website/versioned_docs/version-0.87/panresponder.md
@@ -138,7 +138,7 @@ const styles = StyleSheet.create({
 export default App;
 ```
 
-Try the [PanResponder example in RNTester](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/PanResponder/PanResponderExample.js).
+Try the [PanResponder example in RNTester](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/PanResponder/PanResponderExample.js).
 
 ---
 
diff --git a/website/versioned_docs/version-0.87/platformcolor.md b/website/versioned_docs/version-0.87/platformcolor.md
index 040c6d2c18a..6a7c7417f3f 100644
--- a/website/versioned_docs/version-0.87/platformcolor.md
+++ b/website/versioned_docs/version-0.87/platformcolor.md
@@ -86,5 +86,5 @@ export default App;
 The string value provided to the `PlatformColor` function must match the string as it exists on the native platform where the app is running. In order to avoid runtime errors, the function should be wrapped in a platform check, either through a `Platform.OS === 'platform'` or a `Platform.select()`, as shown on the example above.
 
 :::note
-You can find a complete example that demonstrates proper, intended use of `PlatformColor` in [PlatformColorExample.js](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).
+You can find a complete example that demonstrates proper, intended use of `PlatformColor` in [PlatformColorExample.js](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/PlatformColor/PlatformColorExample.js).
 :::
diff --git a/website/versioned_docs/version-0.87/pressable.md b/website/versioned_docs/version-0.87/pressable.md
index 5c1a0933fc0..e8b8c427be8 100644
--- a/website/versioned_docs/version-0.87/pressable.md
+++ b/website/versioned_docs/version-0.87/pressable.md
@@ -41,7 +41,7 @@ The touch area never extends past the parent view bounds and the Z-index of sibl
 </figure>
 
 :::info
-`Pressable` uses React Native's `Pressability` API. For more information around the state machine flow of Pressability and how it works, check out the implementation for [Pressability](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Pressability/Pressability.js#L350).
+`Pressable` uses React Native's `Pressability` API. For more information around the state machine flow of Pressability and how it works, check out the implementation for [Pressability](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Pressability/Pressability.js#L350).
 :::
 
 ## Example
diff --git a/website/versioned_docs/version-0.87/release-levels.md b/website/versioned_docs/version-0.87/release-levels.md
index 11123402880..a93db709d22 100644
--- a/website/versioned_docs/version-0.87/release-levels.md
+++ b/website/versioned_docs/version-0.87/release-levels.md
@@ -14,7 +14,7 @@ This approach is similar to [Canary and Experimental releases in React](https://
 React Native is also not using `@canary` or `@experimental` NPM tags, as release levels are available for both stable and nightly releases of React Native.
 :::
 
-Moreover, setting the release level to `EXPERIMENTAL` or `CANARY` will **not** result in consuming `react@nightly` or `react@canary` due to how react-native is consuming the React version ([you can read more about it here](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Renderer/README.md#react--react-native-versions)).
+Moreover, setting the release level to `EXPERIMENTAL` or `CANARY` will **not** result in consuming `react@nightly` or `react@canary` due to how react-native is consuming the React version ([you can read more about it here](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Renderer/README.md#react--react-native-versions)).
 
 ## When to Use Each Release Level
 
diff --git a/website/versioned_docs/version-0.87/roottag.md b/website/versioned_docs/version-0.87/roottag.md
index 541724b9365..0d688ad3933 100644
--- a/website/versioned_docs/version-0.87/roottag.md
+++ b/website/versioned_docs/version-0.87/roottag.md
@@ -21,7 +21,7 @@ Another use case for `RootTag` is when your app needs to attribute a certain Jav
 
 ## How to access the RootTag... if you need it
 
-In versions 0.65 and below, RootTag is accessed via a [legacy context](https://github.com/facebook/react-native/blob/v0.64.1/Libraries/ReactNative/AppContainer.js#L56). To prepare React Native for Concurrent features coming in React 18 and beyond, we are migrating to the latest [Context API](https://react.dev/reference/react/createContext) via `RootTagContext` in 0.66. Version 0.65 supports both the legacy context and the recommended `RootTagContext` to allow developers time to migrate their call-sites. See the breaking changes summary.
+In versions 0.65 and below, RootTag is accessed via a [legacy context](https://github.com/react/react-native/blob/v0.64.1/Libraries/ReactNative/AppContainer.js#L56). To prepare React Native for Concurrent features coming in React 18 and beyond, we are migrating to the latest [Context API](https://react.dev/reference/react/createContext) via `RootTagContext` in 0.66. Version 0.65 supports both the legacy context and the recommended `RootTagContext` to allow developers time to migrate their call-sites. See the breaking changes summary.
 
 How to access `RootTag` via the `RootTagContext`.
 
@@ -71,4 +71,4 @@ The legacy context access to `RootTag` will be removed and replaced by `RootTagC
 
 ## Future Plans
 
-With the new React Native architecture progressing, there will be future iterations to `RootTag`, with the intention to keep the `RootTag` type opaque and prevent thrash in React Native codebases. Please do not rely on the fact that RootTag currently aliases to a number! If your app relies on RootTags, keep an eye on our version change logs, which you can find [here](https://github.com/facebook/react-native/blob/main/CHANGELOG.md).
+With the new React Native architecture progressing, there will be future iterations to `RootTag`, with the intention to keep the `RootTag` type opaque and prevent thrash in React Native codebases. Please do not rely on the fact that RootTag currently aliases to a number! If your app relies on RootTags, keep an eye on our version change logs, which you can find [here](https://github.com/react/react-native/blob/main/CHANGELOG.md).
diff --git a/website/versioned_docs/version-0.87/safeareaview.md b/website/versioned_docs/version-0.87/safeareaview.md
index 1298898b64e..1e6f668b919 100644
--- a/website/versioned_docs/version-0.87/safeareaview.md
+++ b/website/versioned_docs/version-0.87/safeareaview.md
@@ -50,5 +50,5 @@ export default App;
 Inherits [View Props](view.md#props).
 
 :::note
-As padding is used to implement the behavior of the component, padding rules in styles applied to a `SafeAreaView` will be ignored and can cause different results depending on the platform. See [#22211](https://github.com/facebook/react-native/issues/22211) for details.
+As padding is used to implement the behavior of the component, padding rules in styles applied to a `SafeAreaView` will be ignored and can cause different results depending on the platform. See [#22211](https://github.com/react/react-native/issues/22211) for details.
 :::
diff --git a/website/versioned_docs/version-0.87/scrollview.md b/website/versioned_docs/version-0.87/scrollview.md
index 77a22c56b39..1cd85c7bc3c 100644
--- a/website/versioned_docs/version-0.87/scrollview.md
+++ b/website/versioned_docs/version-0.87/scrollview.md
@@ -74,7 +74,7 @@ Inherits [View Props](view#props).
 
 ### `StickyHeaderComponent`
 
-A React Component that will be used to render sticky headers, should be used together with `stickyHeaderIndices`. You may need to set this component if your sticky header uses custom transforms, for example, when you want your list to have an animated and hidable header. If a component has not been provided, the default [`ScrollViewStickyHeader`](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Components/ScrollView/ScrollViewStickyHeader.js) component will be used.
+A React Component that will be used to render sticky headers, should be used together with `stickyHeaderIndices`. You may need to set this component if your sticky header uses custom transforms, for example, when you want your list to have an animated and hidable header. If a component has not been provided, the default [`ScrollViewStickyHeader`](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Components/ScrollView/ScrollViewStickyHeader.js) component will be used.
 
 | Type               |
 | ------------------ |
diff --git a/website/versioned_docs/version-0.87/style.md b/website/versioned_docs/version-0.87/style.md
index 4890db4fbfa..25f12dfbe38 100644
--- a/website/versioned_docs/version-0.87/style.md
+++ b/website/versioned_docs/version-0.87/style.md
@@ -48,4 +48,4 @@ Now you can make your text beautiful. The next step in becoming a style expert i
 
 ## Known issues
 
-- [react-native#29308](https://github.com/facebook/react-native/issues/29308#issuecomment-792864162): In some cases React Native does not match how CSS works on the web, for example the touch area never extends past the parent view bounds and on Android negative margin is not supported.
+- [react-native#29308](https://github.com/react/react-native/issues/29308#issuecomment-792864162): In some cases React Native does not match how CSS works on the web, for example the touch area never extends past the parent view bounds and on Android negative margin is not supported.
diff --git a/website/versioned_docs/version-0.87/textinput.md b/website/versioned_docs/version-0.87/textinput.md
index 18eae0c77a1..4ba1305f2eb 100644
--- a/website/versioned_docs/version-0.87/textinput.md
+++ b/website/versioned_docs/version-0.87/textinput.md
@@ -1141,6 +1141,6 @@ Returns `true` if the input is currently focused; `false` otherwise.
 
 # Known issues
 
-- [react-native#19096](https://github.com/facebook/react-native/issues/19096): Doesn't support Android's `onKeyPreIme`.
-- [react-native#19366](https://github.com/facebook/react-native/issues/19366): Calling .focus() after closing Android's keyboard via back button doesn't bring keyboard up again.
-- [react-native#26799](https://github.com/facebook/react-native/issues/26799): Doesn't support Android's `secureTextEntry` when `keyboardType="email-address"` or `keyboardType="phone-pad"`.
+- [react-native#19096](https://github.com/react/react-native/issues/19096): Doesn't support Android's `onKeyPreIme`.
+- [react-native#19366](https://github.com/react/react-native/issues/19366): Calling .focus() after closing Android's keyboard via back button doesn't bring keyboard up again.
+- [react-native#26799](https://github.com/react/react-native/issues/26799): Doesn't support Android's `secureTextEntry` when `keyboardType="email-address"` or `keyboardType="phone-pad"`.
diff --git a/website/versioned_docs/version-0.87/the-new-architecture/custom-cxx-types.md b/website/versioned_docs/version-0.87/the-new-architecture/custom-cxx-types.md
index edc490b8070..e270cb480e2 100644
--- a/website/versioned_docs/version-0.87/the-new-architecture/custom-cxx-types.md
+++ b/website/versioned_docs/version-0.87/the-new-architecture/custom-cxx-types.md
@@ -6,7 +6,7 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import con
 This guide assumes that you are familiar with the [**Pure C++ Turbo Native Modules**](pure-cxx-modules.md) guide. This will build on top of that guide.
 :::
 
-C++ Turbo Native Modules support [bridging functionality](https://github.com/facebook/react-native/tree/main/packages/react-native/ReactCommon/react/bridging) for most `std::` standard types. You can use most of those types in your modules without any additional code required.
+C++ Turbo Native Modules support [bridging functionality](https://github.com/react/react-native/tree/main/packages/react-native/ReactCommon/react/bridging) for most `std::` standard types. You can use most of those types in your modules without any additional code required.
 
 If you want to add support for new and custom types in your app or library, you need to provide the necessary `bridging` header file.
 
diff --git a/website/versioned_docs/version-0.87/the-new-architecture/native-modules-lifecycle.md b/website/versioned_docs/version-0.87/the-new-architecture/native-modules-lifecycle.md
index 361e845591e..4264f6acbe3 100644
--- a/website/versioned_docs/version-0.87/the-new-architecture/native-modules-lifecycle.md
+++ b/website/versioned_docs/version-0.87/the-new-architecture/native-modules-lifecycle.md
@@ -12,17 +12,17 @@ In this guide, you will explore how to initialize and invalidate a Native Module
 
 ## Android
 
-When it comes to Android, all the Native Modules already implements a [TurboModule](https://github.com/facebook/react-native/blob/main/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/interfaces/TurboModule.kt) interface that defines two methods: `initialize()` and `invalidate()`.
+When it comes to Android, all the Native Modules already implements a [TurboModule](https://github.com/react/react-native/blob/main/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/turbomodule/core/interfaces/TurboModule.kt) interface that defines two methods: `initialize()` and `invalidate()`.
 
-The `initialize()` method is called by the Native Module infrastructure when the Native Module is created. This is the best place to put all the initialization code that needs access to the ReactApplicationContext, for example. These are some Native Modules from core that implements the `initialize()` method: [BlobModule](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/blob/BlobModule.java#L155-L157), [NetworkingModule](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/network/NetworkingModule.java#L193-L197).
+The `initialize()` method is called by the Native Module infrastructure when the Native Module is created. This is the best place to put all the initialization code that needs access to the ReactApplicationContext, for example. These are some Native Modules from core that implements the `initialize()` method: [BlobModule](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/blob/BlobModule.java#L155-L157), [NetworkingModule](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/network/NetworkingModule.java#L193-L197).
 
-The `invalidate()` method is called by the Native Module infrastructure when the Native Module is destroyed. This is the best place to put all the cleanup code, resetting the Native Module state and release resources that are no longer needed, such as memory and files. These are some Native Modules from core that implements the `invalidate()` method: [DeviceInfoModule](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/deviceinfo/DeviceInfoModule.kt#L72-L76), [NetworkModule](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/network/NetworkingModule.java#L200-L212)
+The `invalidate()` method is called by the Native Module infrastructure when the Native Module is destroyed. This is the best place to put all the cleanup code, resetting the Native Module state and release resources that are no longer needed, such as memory and files. These are some Native Modules from core that implements the `invalidate()` method: [DeviceInfoModule](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/deviceinfo/DeviceInfoModule.kt#L72-L76), [NetworkModule](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/modules/network/NetworkingModule.java#L200-L212)
 
 ## iOS
 
-On iOS, Native Modules conforms to the [`RCTTurboModule`](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactCommon/react/nativemodule/core/platform/ios/ReactCommon/RCTTurboModule.h#L196-L200) protocol. However, this protocol does not expose the `initialize` and `invalidate` method that are exposed by the Android's `TurboModule` class.
+On iOS, Native Modules conforms to the [`RCTTurboModule`](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/ReactCommon/react/nativemodule/core/platform/ios/ReactCommon/RCTTurboModule.h#L196-L200) protocol. However, this protocol does not expose the `initialize` and `invalidate` method that are exposed by the Android's `TurboModule` class.
 
-Instead, on iOS, there are two additional protocols: [`RCTInitializing`](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/Base/RCTInitializing.h) and [`RCTInvalidating`](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/Base/RCTInvalidating.h). These protocols are used to define the `initialize` and `invalidate` methods, respectively.
+Instead, on iOS, there are two additional protocols: [`RCTInitializing`](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/Base/RCTInitializing.h) and [`RCTInvalidating`](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/Base/RCTInvalidating.h). These protocols are used to define the `initialize` and `invalidate` methods, respectively.
 
 If your module needs to run some initialization code, then you can conform to the `RCTInitializing` protocol and implement the `initialize` method. To do so, you have to:
 
@@ -53,7 +53,7 @@ If your module needs to run some initialization code, then you can conform to th
 @end
 ```
 
-These are some Native Modules from core that implements the `initialize` method: [RCTBlobManager](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/Libraries/Blob/RCTBlobManager.mm#L58-L68), [RCTTiming](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/CoreModules/RCTTiming.mm#L121-L124).
+These are some Native Modules from core that implements the `initialize` method: [RCTBlobManager](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/Libraries/Blob/RCTBlobManager.mm#L58-L68), [RCTTiming](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/CoreModules/RCTTiming.mm#L121-L124).
 
 If your module needs to run some cleanup code, then you can conform to the `RCTInvalidating` protocol and implement the `invalidate` method. To do so, you have to:
 
@@ -87,4 +87,4 @@ If your module needs to run some cleanup code, then you can conform to the `RCTI
 @end
 ```
 
-These are some Native Modules from core that implements the `invalidate` method: [RCTAppearance](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/CoreModules/RCTAppearance.mm#L151-L155), [RCTDeviceInfo](https://github.com/facebook/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/CoreModules/RCTDeviceInfo.mm#L127-L133).
+These are some Native Modules from core that implements the `invalidate` method: [RCTAppearance](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/CoreModules/RCTAppearance.mm#L151-L155), [RCTDeviceInfo](https://github.com/react/react-native/blob/0617accecdcb11159ba15c34885f294bc206aa89/packages/react-native/React/CoreModules/RCTDeviceInfo.mm#L127-L133).
diff --git a/website/versioned_docs/version-0.87/the-new-architecture/pure-cxx-modules.md b/website/versioned_docs/version-0.87/the-new-architecture/pure-cxx-modules.md
index 083bd8f7a42..71cba2e7459 100644
--- a/website/versioned_docs/version-0.87/the-new-architecture/pure-cxx-modules.md
+++ b/website/versioned_docs/version-0.87/the-new-architecture/pure-cxx-modules.md
@@ -229,7 +229,7 @@ The final step is to register the new C++ Turbo Native Module in the runtime, so
 1. From the folder `SampleApp/android/app/src/main/jni`, run the following command:
 
 <CodeBlock language="sh" title="shell">
-{`curl -O https://raw.githubusercontent.com/facebook/react-native/${getCoreBranchNameForCurrentVersion()}/packages/react-native/ReactAndroid/cmake-utils/default-app-setup/OnLoad.cpp`}
+{`curl -O https://raw.githubusercontent.com/react/react-native/${getCoreBranchNameForCurrentVersion()}/packages/react-native/ReactAndroid/cmake-utils/default-app-setup/OnLoad.cpp`}
 </CodeBlock>
 
 2. Then, modify this file as follows:
diff --git a/website/versioned_docs/version-0.87/the-new-architecture/using-codegen.mdx b/website/versioned_docs/version-0.87/the-new-architecture/using-codegen.mdx
index adac9313115..7c68e48fae4 100644
--- a/website/versioned_docs/version-0.87/the-new-architecture/using-codegen.mdx
+++ b/website/versioned_docs/version-0.87/the-new-architecture/using-codegen.mdx
@@ -69,7 +69,7 @@ You can add this snippet to your app and customize the various fields:
   - `.modules[moduleName]:`
     - `.className`: This module's ObjC class. Or, if it's a [C++-only module](/docs/next/the-new-architecture/pure-cxx-modules), its `RCTModuleProvider` class.
     - `.unstableRequiresMainQueueSetup`: Initialize this module on the UI Thread, before running any JavaScript.
-    - `.conformsToProtocols`: Annotate which of these protocols this module conforms to any of the following protocols: [`RCTImageURLLoader`](https://github.com/facebook/react-native/blob/00d5caee9921b6c10be8f7d5b3903c6afe8dbefa/packages/react-native/Libraries/Image/RCTImageURLLoader.h#L26-L81), [`RCTURLRequestHandler`](https://github.com/facebook/react-native/blob/00d5caee9921b6c10be8f7d5b3903c6afe8dbefa/packages/react-native/React/Base/RCTURLRequestHandler.h#L11-L52), [`RCTImageDataDecoder`](https://github.com/facebook/react-native/blob/00d5caee9921b6c10be8f7d5b3903c6afe8dbefa/packages/react-native/Libraries/Image/RCTImageDataDecoder.h#L15-L53).
+    - `.conformsToProtocols`: Annotate which of these protocols this module conforms to any of the following protocols: [`RCTImageURLLoader`](https://github.com/react/react-native/blob/00d5caee9921b6c10be8f7d5b3903c6afe8dbefa/packages/react-native/Libraries/Image/RCTImageURLLoader.h#L26-L81), [`RCTURLRequestHandler`](https://github.com/react/react-native/blob/00d5caee9921b6c10be8f7d5b3903c6afe8dbefa/packages/react-native/React/Base/RCTURLRequestHandler.h#L11-L52), [`RCTImageDataDecoder`](https://github.com/react/react-native/blob/00d5caee9921b6c10be8f7d5b3903c6afe8dbefa/packages/react-native/Libraries/Image/RCTImageDataDecoder.h#L15-L53).
   - `.components[componentName]`:
     - `.className`: This component's ObjC class (e.g: `TextInput` -> `RCTTextInput`).
 
diff --git a/website/versioned_docs/version-0.87/troubleshooting.md b/website/versioned_docs/version-0.87/troubleshooting.md
index 540f38b984f..b166c182a9f 100644
--- a/website/versioned_docs/version-0.87/troubleshooting.md
+++ b/website/versioned_docs/version-0.87/troubleshooting.md
@@ -5,7 +5,7 @@ title: Troubleshooting
 
 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
 
-These are some common issues you may run into while setting up React Native. If you encounter something that is not listed here, try [searching for the issue in GitHub](https://github.com/facebook/react-native/issues/).
+These are some common issues you may run into while setting up React Native. If you encounter something that is not listed here, try [searching for the issue in GitHub](https://github.com/react/react-native/issues/).
 
 ### Port already in use
 
@@ -88,7 +88,7 @@ To revert the `User Search Header Paths` and `Header Search Paths` build setting
 
 ### No transports available
 
-React Native implements a polyfill for WebSockets. These [polyfills](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Core/InitializeCore.js) are initialized as part of the react-native module that you include in your application through `import React from 'react'`. If you load another module that requires WebSockets, such as [Firebase](https://github.com/facebook/react-native/issues/3645), be sure to load/require it after react-native:
+React Native implements a polyfill for WebSockets. These [polyfills](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Core/InitializeCore.js) are initialized as part of the react-native module that you include in your application through `import React from 'react'`. If you load another module that requires WebSockets, such as [Firebase](https://github.com/react/react-native/issues/3645), be sure to load/require it after react-native:
 
 ```
 import Firebase from 'firebase';
diff --git a/website/versioned_docs/version-0.87/turbo-native-modules-android.md b/website/versioned_docs/version-0.87/turbo-native-modules-android.md
index 83d922f9918..a1a067fdfcc 100644
--- a/website/versioned_docs/version-0.87/turbo-native-modules-android.md
+++ b/website/versioned_docs/version-0.87/turbo-native-modules-android.md
@@ -203,7 +203,7 @@ class NativeLocalStoragePackage : BaseReactPackage() {
 
 Finally, we need to tell the React Native in our main application how to find this `Package`. We call this "registering" the package in React Native.
 
-In this case, you add it to be returned by the [getPackages](https://github.com/facebook/react-native/blob/8d8b8c343e62115a5509e1aed62047053c2f6e39/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/ReactNativeHost.java#L233) method.
+In this case, you add it to be returned by the [getPackages](https://github.com/react/react-native/blob/8d8b8c343e62115a5509e1aed62047053c2f6e39/packages/react-native/ReactAndroid/src/main/java/com/facebook/react/ReactNativeHost.java#L233) method.
 
 :::info
 Later you’ll learn how to distribute your Native Modules as [npm packages](the-new-architecture/create-module-library.mdx#publish-the-library-on-npm), which our build tooling will autolink for you.
diff --git a/website/versioned_docs/version-0.87/usecolorscheme.md b/website/versioned_docs/version-0.87/usecolorscheme.md
index 14b7becabe8..fec009f6815 100644
--- a/website/versioned_docs/version-0.87/usecolorscheme.md
+++ b/website/versioned_docs/version-0.87/usecolorscheme.md
@@ -45,4 +45,4 @@ const styles = StyleSheet.create({
 export default App;
 ```
 
-You can find a complete example that demonstrates the use of this hook alongside a React context to add support for light and dark themes to your application in [`AppearanceExample.js`](https://github.com/facebook/react-native/blob/main/packages/rn-tester/js/examples/Appearance/AppearanceExample.js).
+You can find a complete example that demonstrates the use of this hook alongside a React context to add support for light and dark themes to your application in [`AppearanceExample.js`](https://github.com/react/react-native/blob/main/packages/rn-tester/js/examples/Appearance/AppearanceExample.js).
diff --git a/website/versioned_docs/version-0.87/view-style-props.md b/website/versioned_docs/version-0.87/view-style-props.md
index 2828c681ff8..f06be92cd7e 100644
--- a/website/versioned_docs/version-0.87/view-style-props.md
+++ b/website/versioned_docs/version-0.87/view-style-props.md
@@ -109,8 +109,8 @@ style={{
 
 More complex examples of usage can be found in the RNTester app (with `PlatformColor` supports):
 
-- <a href={`https://github.com/facebook/react-native/blob/${getCoreBranchNameForCurrentVersion()}/packages/rn-tester/js/examples/LinearGradient/LinearGradientExample.js`}>LinearGradientExample.js</a>
-- <a href={`https://github.com/facebook/react-native/blob/${getCoreBranchNameForCurrentVersion()}/packages/rn-tester/js/examples/RadialGradient/RadialGradientExample.js`}>RadialGradientExample.js</a>
+- <a href={`https://github.com/react/react-native/blob/${getCoreBranchNameForCurrentVersion()}/packages/rn-tester/js/examples/LinearGradient/LinearGradientExample.js`}>LinearGradientExample.js</a>
+- <a href={`https://github.com/react/react-native/blob/${getCoreBranchNameForCurrentVersion()}/packages/rn-tester/js/examples/RadialGradient/RadialGradientExample.js`}>RadialGradientExample.js</a>
 
 | Type                                                                                                                                                                                               |
 | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
diff --git a/website/versioned_docs/version-0.87/viewtoken.md b/website/versioned_docs/version-0.87/viewtoken.md
index 28d285deefa..aedeb40f037 100644
--- a/website/versioned_docs/version-0.87/viewtoken.md
+++ b/website/versioned_docs/version-0.87/viewtoken.md
@@ -3,7 +3,7 @@ id: viewtoken
 title: ViewToken Object Type
 ---
 
-`ViewToken` object is returned as one of the properties in the `onViewableItemsChanged` callback (for example, in the [FlatList](flatlist) component). It is exported by [`ViewabilityHelper.js`](https://github.com/facebook/react-native/blob/main/packages/react-native/Libraries/Lists/ViewabilityHelper.js).
+`ViewToken` object is returned as one of the properties in the `onViewableItemsChanged` callback (for example, in the [FlatList](flatlist) component). It is exported by [`ViewabilityHelper.js`](https://github.com/react/react-native/blob/main/packages/react-native/Libraries/Lists/ViewabilityHelper.js).
 
 ## Example