diff --git a/docs/platforms/android/configuration/app-not-respond.mdx b/docs/platforms/android/configuration/app-not-respond.mdx
index 0152e45be58edb..61efb4ee2dbedf 100644
--- a/docs/platforms/android/configuration/app-not-respond.mdx
+++ b/docs/platforms/android/configuration/app-not-respond.mdx
@@ -105,11 +105,11 @@ SentryAndroid.init(context) { options ->
 
 ![ANR Thread Dump](./img/app-not-respond-thread-dump.png)
 
-## ANR Profiling (Experimental)
+## ANR Profiling
 
 <Alert>
 
-ANR Profiling is available starting in SDK version `8.35.0`. This feature is experimental and may change in future versions.
+ANR Profiling is available starting in SDK version `8.35.0`.
 
 </Alert>
 
diff --git a/docs/pricing/quotas/manage-ui-profile-hours.mdx b/docs/pricing/quotas/manage-ui-profile-hours.mdx
index fff9d7d73fe9d2..ec2a8e3c80f5cc 100644
--- a/docs/pricing/quotas/manage-ui-profile-hours.mdx
+++ b/docs/pricing/quotas/manage-ui-profile-hours.mdx
@@ -15,7 +15,7 @@ You can look at your UI Profile hours in aggregate in the "Usage Stats" tab of t
 
 UI Profiling only supports **client-side** sampling. To control client-side sampling behavior, you can set the `profile_session_sample_rate` configuration parameter to a value between 0.0-1.0 to control the number of profiling sessions that are sampled (the default is 0.0).
 
-Android [ANR Profiling](/platforms/android/configuration/app-not-respond/#anr-profiling-experimental) is also billed as UI Profile Hours. It uses a separate sampling option, `anrProfilingSampleRate`, which controls the probability of collecting a profile for each detected foreground ANR.
+Android [ANR Profiling](/platforms/android/configuration/app-not-respond/#anr-profiling) is also billed as UI Profile Hours. It uses a separate sampling option, `anrProfilingSampleRate`, which controls the probability of collecting a profile for each detected foreground ANR.
 
 For UI Profiling, the initial user session starts when the SDK is initialized, and sampling is first evaluated at this point. The user session will either end on termination of the application **or** depending on the platform, there can be other events that end a user session (like backgrounding a mobile application). The sampling rate will be re-evaluated on each new user session.