From d9ec7b71ecfa93e7761095fe41cfb3ab8af8d010 Mon Sep 17 00:00:00 2001
From: Mohammed Bahumaish
 <38791859+mohammed-bahumaish@users.noreply.github.com>
Date: Sat, 21 Dec 2024 15:20:03 +0200
Subject: [PATCH] Fix broken link (#7910)

---
 .../react-native/content/115-using-native-modules/index.md      | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/data/roadmaps/react-native/content/115-using-native-modules/index.md b/src/data/roadmaps/react-native/content/115-using-native-modules/index.md
index 6f84292f4..f30dd355f 100644
--- a/src/data/roadmaps/react-native/content/115-using-native-modules/index.md
+++ b/src/data/roadmaps/react-native/content/115-using-native-modules/index.md
@@ -4,4 +4,4 @@ Sometimes a React Native app needs to access a native platform API that is not a
 
 The NativeModule system exposes instances of Java/Objective-C/C++ (native) classes to JavaScript (JS) as JS objects, thereby allowing you to execute arbitrary native code from within JS. While we don't expect this feature to be part of the usual development process, it is essential that it exists. If React Native doesn't export a native API that your JS app needs you should be able to export it yourself!
 
-- [@article@Native Modules Introduction](https://reactnative.dev/docs/native-modules-intro)
\ No newline at end of file
+- [@article@Native Modules Introduction](https://reactnative.dev/docs/native-platform)