fix(user-docs): Update 404 links (#10757)

Author: chargome

docs/concepts/search/searchable-properties/events.mdx

@@ -414,13 +414,13 @@ Returns results with a matching total number of frames.
 
 ### `measurements.stall_count`
 
-A [stall](/platforms/react-native/performance/instrumentation/automatic-instrumentation/#stall-tracking) is when the JavaScript event loop takes longer than expected to complete. Only applies to React Native.
+A [stall](/platforms/react-native/tracing/instrumentation/automatic-instrumentation/#stall-tracking) is when the JavaScript event loop takes longer than expected to complete. Only applies to React Native.
 
 - **Type:** number
 
 ### `measurements.stall_longest_time`
 
-The [longest stall time](/platforms/react-native/performance/instrumentation/automatic-instrumentation/#stall-tracking) is the time, in milliseconds, of the longest event loop stall. Only applies to React Native.
+The [longest stall time](/platforms/react-native/tracing/instrumentation/automatic-instrumentation/#stall-tracking) is the time, in milliseconds, of the longest event loop stall. Only applies to React Native.
 
 - **Type:** duration
 
@@ -432,7 +432,7 @@ Stall percentage is equal to the `stall_total_time` divided by the `transaction.
 
 ### `measurements.stall_total_time`
 
-The [total stall time](/platforms/react-native/performance/instrumentation/automatic-instrumentation/#stall-tracking) is the total combined time, in milliseconds, of all stalls. Only applies to React Native.
+The [total stall time](/platforms/react-native/tracing/instrumentation/automatic-instrumentation/#stall-tracking) is the total combined time, in milliseconds, of all stalls. Only applies to React Native.
 
 - **Type:** duration
 

docs/contributing/approach/sdk-docs/write-getting-started.mdx

@@ -66,7 +66,8 @@ Provide a verification code sample for this SDK. It can be as simple as one line
 
 Add the verification code sample to this directory:
 
-- [`/src/platform-includes/getting-started-verify/`](https://github.com/getsentry/sentry-docs/tree/master/src/platform-includes/getting-started-verify)
+- [`/src/platform-includes/getting-started-verify/`](https://github.com/getsentry/sentry-docs/tree/master/platform-includes/getting-started-verify)
+
 
 ## But, that's not all
 

docs/organization/integrations/data-visualization/splunk/index.mdx

@@ -8,7 +8,7 @@ Connect Splunk to Sentry with the [Data Forwarding](/concepts/data-management/da
 
 <Note>
 
-We only support Splunk Cloud plans. We do not support Splunk Enterprise plans. See the [Splunk documentation](https://dev.splunk.com/view/event-collector/SP-CAAAE7F) for specific details on your Splunk installation.
+We only support Splunk Cloud plans. We do not support Splunk Enterprise plans. See the [Splunk documentation](https://dev.splunk.com/) for specific details on your Splunk installation.
 
 </Note>
 

docs/organization/integrations/source-code-mgmt/github/index.mdx

@@ -369,5 +369,5 @@ If you’re having issues adding a GitHub repository:
 If you're having trouble setting up Sentry with your on-premises integration, verify the following:
 
 - The provided installation URL is a fully qualified domain name (FQDN), which is resolvable on the internet.
-- The IP addresses Sentry uses to make outbound requests are [allowed](security-legal-pii/security/ip-ranges/).
+- The IP addresses Sentry uses to make outbound requests are [allowed](/security-legal-pii/security/ip-ranges/).
 - Sentry's access to your installation URL is not path restricted.

docs/platforms/apple/common/features/index.mdx

@@ -47,6 +47,7 @@ The SDK builds a crash report that persists to disk. While it attempts to send t
   - <PlatformLink to="/tracing/instrumentation/automatic-instrumentation/#user-interaction-tracing">User Interaction</PlatformLink> transactions for UI clicks
 - <PlatformLink to="/enriching-events/attachments">Attachments</PlatformLink> enrich your event by storing additional files, such as config or log files
 - <PlatformLink to="/user-feedback">User Feedback</PlatformLink> provides the ability to collect user information when an event occurs
-- <PlatformLink to="/enriching-events/viewhierarchy">View Hierarchy</PlatformLink> and <PlatformLink to="/enriching-events/screenshots">Screenshot</PlatformLink> attachments for errors
+
+- [View Hierarchy](/platforms/apple/guides/ios/enriching-events/viewhierarchy/) and [Screenshot](/platforms/apple/guides/ios/enriching-events/screenshots/) attachments for errors
 - <PlatformLink to="/data-management/debug-files/source-context">Source Context</PlatformLink> shows snippets of code around the location of stack frames
 - <PlatformLink to="/configuration/metric-kit">MetricKit</PlatformLink> integration

docs/platforms/dart/integrations/dio.mdx

@@ -44,7 +44,7 @@ dio.addSentry(...);
 
 ## Reporting Bad HTTP Requests as Errors
 
-The `Interceptors` can also catch exceptions that may occur during requests — for example [DioError](https://pub.dev/documentation/dio/latest/dio/DioError-class.html).
+The `Interceptors` can also catch exceptions that may occur during requests — for example [DioError](https://pub.dev/documentation/dio2/latest/dio2/DioError-class.html).
 
 ```dart
 import 'package:sentry_dio/sentry_dio.dart';

docs/platforms/dotnet/common/tracing/instrumentation/custom-instrumentation/queues-module.mdx

@@ -15,7 +15,7 @@ To start capturing performance metrics, use the `transaction.StartChild()` funct
 | `messaging.destination.name` | string | The queue or topic name |
 | `messaging.message.body.size` | int | Size of the message body in bytes |
 
-Your `queue.publish` span must exist inside a transaction in order to be recognized as a producer span. If you are using a supported framework, the transaction is created by the integration. If you are using plain Go, you can start a new one using `SentrySdk.StartTransaction()`.
+Your `queue.publish` span must exist inside a transaction in order to be recognized as a producer span. If you are using a supported framework, the transaction is created by the integration. If you are using plain C#, you can start a new one using `SentrySdk.StartTransaction()`.
 
 You must also include trace headers in your message so that your consumers can continue your trace once your message is picked up.
 
@@ -74,7 +74,7 @@ To start capturing performance metrics, use the `transaction.StartChild()` funct
 | `messaging.message.retry.count ` | number | The number of times a message was attempted to be processed |
 | `messaging.message.receive.latency ` | number | The time in milliseconds that a message awaited processing in queue |
 
-Your `queue.process` span must exist inside a transaction in order to be recognized as a consumer span. If you are using a <PlatformLink to="/integrations/#web-frameworks">supported web framework</PlatformLink>, the transaction is created by the integration. If you use plain Python, you can start a new one using `SentrySdk.StartTransaction()`.
+Your `queue.process` span must exist inside a transaction in order to be recognized as a consumer span. If you are using a supported framework, the transaction is created by the integration. If you use plain C#, you can start a new one using `SentrySdk.StartTransaction()`.
 
 Use `SentrySdk.ContinueTrace()` to connect your consumer spans to their associated producer spans, and `span.SetExtra()` to mark the trace of your message as success or failed.
 

docs/platforms/java/common/legacy/logback/index.mdx

@@ -9,7 +9,7 @@ A new Java SDK has superseded this deprecated version. Sentry preserves this doc
 
 </Alert>
 
-The `sentry-logback` library provides [Logback](http://logback.qos.ch/) support for Sentry via an [Appender](http://logback.qos.ch/apidocs/ch/qos/logback/core/Appender.html) that sends logged exceptions to Sentry. Once this integration is configured you can _also_ use Sentry’s static API, [as shown on the usage page](/platforms/java/legacy/usage), in order to do things like record breadcrumbs, set the current user, or manually send events.
+The `sentry-logback` library provides [Logback](http://logback.qos.ch/) support for Sentry via an [Appender](https://logback.qos.ch/manual/appenders.html) that sends logged exceptions to Sentry. Once this integration is configured you can _also_ use Sentry’s static API, [as shown on the usage page](/platforms/java/legacy/usage), in order to do things like record breadcrumbs, set the current user, or manually send events.
 
 The source can be found [on GitHub](https://github.com/getsentry/sentry-java/tree/master/sentry-logback).
 

docs/platforms/java/common/tracing/instrumentation/custom-instrumentation/caches-module.mdx

@@ -15,7 +15,7 @@ For detailed information about which data can be set, see the [Cache Module Deve
 
 ## Manual Instrumentation
 
-For now you'll need to manually instrument the [Cache Module]((https://sentry.io/orgredirect/organizations/:orgslug/insights/caches/)) by following the steps below.
+For now you'll need to manually instrument the [Cache Module](https://sentry.io/orgredirect/organizations/:orgslug/insights/caches/) by following the steps below.
 
 <PlatformSection supported={["java.spring", "java.spring-boot"]}>
 If you are using Spring caching, please take a look at our [proof of concept PR](https://github.com/getsentry/sentry-java/pull/3457) as it shows how to register a cache listener and report cache spans to Sentry.

docs/platforms/javascript/common/configuration/integrations/trpc.mdx

@@ -17,6 +17,7 @@ supported:
   - javascript.sveltekit
   - javascript.remix
   - javascript.astro
+  - javascript.deno
   - javascript.bun
 ---