fix: Update 404 links from user docs

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
 ---
 

docs/platforms/javascript/common/data-management/debug-files/file-formats/index.mdx

@@ -2,6 +2,9 @@
 title: "Debug File Formats"
 description: "Learn about platform-specific file formats and the debug information they contain."
 sidebar_order: 1
+supported:
+  - javascript.capacitor
+  - javascript.electron
 ---
 
 Sentry differentiates four kinds of debug information:

docs/platforms/javascript/common/data-management/debug-files/identifiers/index.mdx

@@ -2,6 +2,9 @@
 title: Debug Identifiers
 description: "Learn about build tooling requirements that allow Sentry to uniquely identify debug information files across builds."
 sidebar_order: 2
+supported:
+  - javascript.capacitor
+  - javascript.electron
 ---
 
 Each debug information file specifies a unique identifier. Crash reports declare

docs/platforms/javascript/common/data-management/debug-files/source-context/index.mdx

@@ -2,6 +2,9 @@
 title: Source Context
 description: "Learn about setting up source bundles to show source code in stack traces on the Issue Details page."
 sidebar_order: 5
+supported:
+  - javascript.capacitor
+  - javascript.electron
 ---
 
 If Sentry has access to your application's source code, it can show snippets of code (_source context_) around the location of stack frames, which helps to quickly pinpoint problematic code.

docs/platforms/javascript/common/data-management/debug-files/symbol-servers/index.mdx

@@ -2,6 +2,9 @@
 title: Symbol Servers
 description: "Learn about symbol servers and how to configure them with your Sentry projects."
 sidebar_order: 4
+supported:
+  - javascript.capacitor
+  - javascript.electron
 ---
 
 Sentry can download debug information files from external repositories. This

docs/platforms/javascript/common/data-management/debug-files/upload/index.mdx

@@ -2,6 +2,9 @@
 title: Uploading Files
 description: "Learn about uploading debug information files to Sentry."
 sidebar_order: 3
+supported:
+  - javascript.capacitor
+  - javascript.electron
 ---
 
 The most straightforward way to provide Sentry with debug information file is

docs/platforms/javascript/common/index.mdx

@@ -1,6 +1,6 @@
 <PlatformContent includePath="getting-started-primer" />
 
-<PlatformSection notSupported={["javascript.capacitor"]}>
+<PlatformSection notSupported={["javascript.capacitor", "javascript.cordova"]}>
 
 <Note>
   We have recently released v8 of the JavaScript SDKs. If you're using version

docs/platforms/javascript/common/migration/v7-to-v8/v8-opentelemetry.mdx

@@ -26,7 +26,7 @@ const span1 = tracer.startSpan('work-1');
 span1.end();
 ```
 
-We recommend using the [performance monitoring APIs](./v8-new-performance-api.mdx) provided by Sentry, as they are more user-friendly and provide additional features.
+We recommend using the [performance monitoring APIs](../v8-new-performance-api/) provided by Sentry, as they are more user-friendly and provide additional features.
 
 ### Custom OpenTelemetry Instrumentation
 

docs/platforms/javascript/common/sourcemaps/uploading/cli.mdx

@@ -2,6 +2,11 @@
 title: Sentry CLI
 description: "Upload your source maps using Sentry CLI."
 sidebar_order: 6
+notSupported:
+  - javascript.nextjs
+  - javascript.remix
+  - javascript.sveltekit
+  - javascript.astro
 ---
 
 In this guide, you'll learn how to successfully upload source maps using our `sentry-cli` tool.

docs/platforms/javascript/common/tracing/index.mdx

@@ -13,7 +13,9 @@ If you’re adopting Tracing in a high-throughput environment, we recommend test
 
 </Note>
 
-<Include name="opentelemetry-available.mdx" />
+<PlatformSection notSupported={["javascript.deno", "javascript.bun"]}>
+    <Include name="opentelemetry-available.mdx" />
+</PlatformSection>
 
 </PlatformCategorySection>
 

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

@@ -41,7 +41,7 @@ Sentry.init({
 
 ## Manual Instrumentation
 
-If you're using anything other than Sentry's Redis integration, you'll need to manually instrument the [Cache Module](<(https://sentry.io/orgredirect/organizations/:orgslug/performance/caches/)>) by following the steps below.
+If you're using anything other than Sentry's Redis integration, you'll need to manually instrument the [Cache Module](https://sentry.io/orgredirect/organizations/:orgslug/performance/caches/) by following the steps below.
 
 You'll need to create two spans - one indicating that something is being put into the cache, and a second one indicating that something is being fetched from the cache.
 

docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/index.mdx

@@ -183,9 +183,11 @@ Sentry.suppressTracing(() => {
 });
 ```
 
+<PlatformSection notSupported={['javascript.cordova']}>
 ### Distributed Tracing
 
 See <PlatformLink to="/tracing/trace-propagation/custom-instrumentation/">Distributed Tracing</PlatformLink> for details on how to manually set up distributed tracing.
+</PlatformSection>
 
 ## Improving Span Data
 

docs/platforms/javascript/common/tracing/instrumentation/opentelemetry.mdx

@@ -14,6 +14,9 @@ supported:
   - javascript.hapi
   - javascript.koa
   - javascript.nestjs
+  - javascript.sveltekit
+  - javascript.astro
+  - javascript.remix
 notSupported:
   - javascript
 ---

docs/platforms/javascript/common/user-feedback/index.mdx

@@ -8,7 +8,7 @@ The User Feedback feature allows you to collect user feedback from anywhere insi
 
 Note that if you're using a self-hosted Sentry instance, you'll need to be on version 24.4.2 or higher in order to use the full functionality of the User Feedback feature. Lower versions may have limited functionality.
 
-<PlatformSection notSupported={["javascript.node", "javascript.aws-lambda", "javascript.azure-functions", "javascript.connect", "javascript.express", "javascript.fastify", "javascript.gcp-functions", "javascript.hapi", "javascript.koa", "javascript.nestjs"]}>
+<PlatformSection notSupported={["javascript.node", "javascript.aws-lambda", "javascript.azure-functions", "javascript.connect", "javascript.express", "javascript.fastify", "javascript.gcp-functions", "javascript.hapi", "javascript.koa", "javascript.nestjs", "javascript.deno", "javascript.bun", "javascript.cordova", "javascript.wasm"]}>
 
 ## User Feedback Widget
 

docs/platforms/javascript/guides/react/features/react-router.mdx

@@ -77,7 +77,7 @@ You can instrument [`createMemoryRouter`](https://reactrouter.com/en/main/router
 
 ### Usage With `<Routes />` Component
 
-If you're using the `<Routes />` component from `react-router-dom` to define your routes, wrap [`Routes`](https://reactrouter.com/docs/en/v6/api#routes-and-route) using `Sentry.withSentryReactRouterV6Routing`. This creates a higher order component, which will enable Sentry to reach your router context. You can also use `Sentry.withSentryReactRouterV6Routing` for `Routes` inside `BrowserRouter`. `MemoryRouter`, and `HashRouter` components:
+If you're using the `<Routes />` component from `react-router-dom` to define your routes, wrap [`Routes`](https://reactrouter.com/en/main/components/routes) using `Sentry.withSentryReactRouterV6Routing`. This creates a higher order component, which will enable Sentry to reach your router context. You can also use `Sentry.withSentryReactRouterV6Routing` for `Routes` inside `BrowserRouter`. `MemoryRouter`, and `HashRouter` components:
 
 <SignInNote />
 

docs/platforms/javascript/guides/remix/manual-setup.mdx

@@ -183,7 +183,7 @@ NODE_OPTIONS='--require=./instrument.server.cjs' remix-serve build
 
 If you use the Express server instead of the Remix built-in server, you can alternatively import your instrumentation file directly at the top of your server implementation. See the example [here](#custom-express-server).
 
-Sentry's Remix SDK will automatically record your [`action`](https://remix.run/docs/en/main/route/action) and [`loader`](https://remix.run/docs/en/main/route/loader) transactions, as well as server-side errors. You can also initialize Sentry's database integrations, such as <Link to="/platforms/javascript/guides/node/tracing/database/opt-in/#prisma-orm-integration">Prisma</Link>, to get spans for your database calls.
+Sentry's Remix SDK will automatically record your [`action`](https://remix.run/docs/en/main/route/action) and [`loader`](https://remix.run/docs/en/main/route/loader) transactions, as well as server-side errors. You can also initialize Sentry's database integrations, such as <Link to="/platforms/javascript/guides/node/configuration/integrations/prisma/">Prisma</Link>, to get spans for your database calls.
 
 #### Server-side Errors
 

docs/platforms/javascript/legacy-sdk/install.mdx

@@ -165,15 +165,13 @@ This won’t work when opening `index.html` or any other html file from the file
 
 </Alert>
 
-To read un-minified source code for this loader, see [loader.js](https://github.com/getsentry/raven-js/blob/master/packages/raven-js/src/loader.js)
-
 ## Requirements
 
 Raven supports IE8+ and all other modern browsers, and works in Web Workers.
 
 Raven requires the browser JavaScript environment to provide:
 
-- Either [XHR Level 2](https://caniuse.com/#feat=xhr2) (IE10+, all other modern browsers) or [XDomainRequest](https://developer.mozilla.org/en-US/docs/Web/API/XDomainRequest) (IE8, IE9)
+- Either [XHR Level 2](https://caniuse.com/#feat=xhr2) (IE10+, all other modern browsers) or [XDomainRequest](https://learn.microsoft.com/en-us/previous-versions/windows/internet-explorer/ie-developer/platform-apis/cc288132(v=vs.85)) (IE8, IE9)
 - A global `JSON` object with `JSON.stringify` (IE8+ [standards mode](<https://msdn.microsoft.com/en-us/library/cc288325(VS.85).aspx>), all other modern browsers)
 
 Raven does not support IE 7 or other older browsers which do not provide the required features listed above. On those older browsers, Raven.js is designed to fail gracefully; including it on your page will have no effect, but it won’t collect and report uncaught exceptions.

docs/platforms/javascript/legacy-sdk/usage.mdx

@@ -260,10 +260,7 @@ Raven.isSetup();
 Raven and Sentry support [Source Maps](https://www.html5rocks.com/en/tutorials/developertools/sourcemaps/).
 
 For more information, please read the [Source Map
-docs](/platforms/javascript/legacy-sdk/sourcemaps/). Also, check
-out our
-[Gruntfile](https://github.com/getsentry/raven-js/blob/master/packages/raven-js/Gruntfile.js)
-for a good example of what we’re doing.
+docs](/platforms/javascript/legacy-sdk/sourcemaps/).
 
 You can use [Source Map Validator](https://sourcemaps.io/) to help verify that things are correct.
 

docs/platforms/native/common/data-management/sensitive-data/index.mdx

@@ -27,7 +27,7 @@ We offer the following options depending on your legal and operational needs:
 
 Ensure that your team is aware of your company's policy around what can and cannot be sent to Sentry. We recommend determining this policy early in your implementation and communicating it as well as enforcing it via code review.
 
-If you are using Sentry in your mobile app, read our [frequently asked questions about mobile data privacy](security-legal-pii/security/mobile-privacy/) to assist with Apple App Store and Google Play app privacy details.
+If you are using Sentry in your mobile app, read our [frequently asked questions about mobile data privacy](/security-legal-pii/security/mobile-privacy/) to assist with Apple App Store and Google Play app privacy details.
 
 </Note>