diff --git a/docs/linking.md b/docs/linking.md
index 6000b7273d0..cc54a71c294 100644
--- a/docs/linking.md
+++ b/docs/linking.md
@@ -39,7 +39,7 @@ If you want to enable deep links in your app, please read the below guide:
 <TabItem value="android">
 
 :::info
-For instructions on how to add support for deep linking on Android, refer to [Enabling Deep Links for App Content - Add Intent Filters for Your Deep Links](https://developer.android.com/training/app-indexing/deep-linking.html#adding-filters).
+For instructions on how to add support for deep linking on Android, refer to [Create Deep Links to App Content - Add intent filters for incoming links](https://developer.android.com/training/app-links/create-deeplinks#adding-filters).
 :::
 
 If you wish to receive the intent in an existing instance of MainActivity, you may set the `launchMode` of MainActivity to `singleTask` in `AndroidManifest.xml`. See [`<activity>`](https://developer.android.com/guide/topics/manifest/activity-element.html) documentation for more information.
@@ -709,7 +709,7 @@ static getInitialURL(): Promise<string | null>;
 If the app launch was triggered by an app link, it will give the link url, otherwise it will give `null`.
 
 :::info
-To support deep linking on Android, refer https://developer.android.com/training/app-indexing/deep-linking.html#handling-intents.
+To support deep linking on Android, refer to [Create Deep Links to App Content - Read data from incoming intents](https://developer.android.com/training/app-links/create-deeplinks#handling-intents).
 :::
 
 :::tip
diff --git a/docs/signed-apk-android.md b/docs/signed-apk-android.md
index c5158f4aab0..c95465db967 100644
--- a/docs/signed-apk-android.md
+++ b/docs/signed-apk-android.md
@@ -5,7 +5,7 @@ title: Publishing to Google Play Store
 
 import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; import constants from '@site/core/TabsConstants';
 
-Android requires that all apps be digitally signed with a certificate before they can be installed. In order to distribute your Android application via [Google Play store](https://play.google.com/store) it needs to be signed with a release key that then needs to be used for all future updates. Since 2017 it is possible for Google Play to manage signing releases automatically thanks to [App Signing by Google Play](https://developer.android.com/studio/publish/app-signing#app-signing-google-play) functionality. However, before your application binary is uploaded to Google Play it needs to be signed with an upload key. The [Signing Your Applications](https://developer.android.com/tools/publishing/app-signing.html) page on Android Developers documentation describes the topic in detail. This guide covers the process in brief, as well as lists the steps required to package the JavaScript bundle.
+Android requires that all apps be digitally signed with a certificate before they can be installed. In order to distribute your Android application via [Google Play store](https://play.google.com/store) it needs to be signed with a release key that then needs to be used for all future updates. Since 2017 it is possible for Google Play to manage signing releases automatically thanks to [App Signing by Google Play](https://developer.android.com/studio/publish/app-signing#app-signing-google-play) functionality. However, before your application binary is uploaded to Google Play it needs to be signed with an upload key. The [Sign your app](https://developer.android.com/studio/publish/app-signing) page on Android Developers documentation describes the topic in detail. This guide covers the process in brief, as well as lists the steps required to package the JavaScript bundle.
 
 :::info
 If you are using Expo, read the Expo guide for [Deploying to App Stores](https://docs.expo.dev/distribution/app-stores/) to build and submit your app for the Google Play Store. This guide works with any React Native app to automate the deployment process.
diff --git a/docs/view-style-props.md b/docs/view-style-props.md
index f940aa3d99c..894685a2402 100644
--- a/docs/view-style-props.md
+++ b/docs/view-style-props.md
@@ -449,7 +449,7 @@ On iOS 17+, Setting to `pointer` allows hover effects when a pointer (such as a
 
 ### `elevation` <div className="label android">Android</div>
 
-Sets the elevation of a view, using Android's underlying [elevation API](https://developer.android.com/training/material/shadows-clipping.html#Elevation). This adds a drop shadow to the item and affects z-order for overlapping views. Only supported on Android 5.0+, has no effect on earlier versions.
+Sets the elevation of a view, using Android's underlying [elevation API](https://developer.android.com/develop/ui/views/theming/shadows-clipping#Elevation). This adds a drop shadow to the item and affects z-order for overlapping views. Only supported on Android 5.0+, has no effect on earlier versions.
 
 | Type   |
 | ------ |