fix(js): Remove redundant otel note from migration (#9829)

Author: AbhiPrasad

includes/migration/javascript-v8/node-other-changes.mdx

@@ -11,10 +11,6 @@ Sentry.init({
 });
 ```
 
-### Removal of `Sentry.Handlers.trpcMiddleware()` in favor of `Sentry.trpcMiddleware()`
-
-The Sentry tRPC middleware got moved from `Sentry.Handlers.trpcMiddleware()` to `Sentry.trpcMiddleware()`.
-
 ### Behaviour in combination with `onUncaughtException` handlers in Node.js
 
 Previously the SDK exited the process by default, even though additional `onUncaughtException` may have been registered,

includes/migration/javascript-v8/server-other-changes.mdx

@@ -2,6 +2,10 @@
 
 The `deepReadDirSync` method has been removed as an export from the SDK. There is no replacement API.
 
+### Removal of `Sentry.Handlers.trpcMiddleware()` in favor of `Sentry.trpcMiddleware()`
+
+The Sentry tRPC middleware got moved from `Sentry.Handlers.trpcMiddleware()` to `Sentry.trpcMiddleware()`.
+
 #### Removal of Client-Side health check transaction filters
 
 The SDK no longer filters out health check transactions by default. Instead, they are sent to Sentry but still dropped

platform-includes/migration/javascript-v8/important-changes/javascript.astro.mdx

@@ -25,8 +25,6 @@ We now support the following integrations out of the box with 0 configuration:
 - `postgresIntegration`: Automatically instruments PostgreSQL
 - `prismaIntegration`: Automatically instruments Prisma
 
-If you want to customize the OpenTelemetry setup, see the docs about using [OpenTelemetry with `8.x`](./v8-opentelemetry)
-
 ### Removal of `trackHeaders` option for Astro middleware
 
 Instead of opting-in via the middleware config, you can configure if headers should be captured via `requestDataIntegration` options, which defaults to `true` but can be disabled like this:

platform-includes/migration/javascript-v8/important-changes/javascript.aws-lambda.mdx

@@ -8,8 +8,6 @@ If you need to support older versions of Node.js, please use Sentry Serverless S
 
 With 8.x, the Sentry Serverless SDK for AWS Lambda has been completely overhauled. It is now powered by [OpenTelemetry](https://opentelemetry.io/) under the hood. You do not need to know or understand what OpenTelemetry is in order to use Sentry. We set up OpenTelemetry under the hood, no knowledge of it is required in order to get started, though if you use OpenTelemetry-native APIs to start spans, and Sentry will pick up everything automatically.
 
-If you want to customize the OpenTelemetry setup, see the docs about using [OpenTelemetry with `8.x`](./v8-opentelemetry)
-
 With this change, `@sentry/serverless` has been removed and will no longer be published. The AWS related code now lives in `@sentry/aws-serverless`.
 
 Here's an example of instrumentating your AWS Lambda with Sentry Serverless SDK `8.x`:

platform-includes/migration/javascript-v8/important-changes/javascript.azure-functions.mdx

@@ -8,8 +8,6 @@ If you need to support older versions of Node.js, please use Sentry Node SDK `7.
 
 With 8.x, @sentry/node has been completely overhauled. It is now powered by [OpenTelemetry](https://opentelemetry.io/) under the hood. You do not need to know or understand what OpenTelemetry is in order to use Sentry. We set up OpenTelemetry under the hood, no knowledge of it is required in order to get started, though if you use OpenTelemetry-native APIs to start spans, and Sentry will pick up everything automatically.
 
-If you want to customize the OpenTelemetry setup, see the docs about using [OpenTelemetry with `8.x`](./v8-opentelemetry)
-
 Here's an example of instrumentating your Azure Function with Sentry Node SDK `8.x`:
 
 ```JavaScript

platform-includes/migration/javascript-v8/important-changes/javascript.connect.mdx

@@ -8,8 +8,6 @@ If you need to support older versions of Node.js, please use Sentry Node SDK `7.
 
 With 8.x, @sentry/node has been completely overhauled. It is now powered by [OpenTelemetry](https://opentelemetry.io/) under the hood. You do not need to know or understand what OpenTelemetry is in order to use Sentry. We set up OpenTelemetry under the hood, no knowledge of it is required in order to get started, though if you use OpenTelemetry-native APIs to start spans, and Sentry will pick up everything automatically.
 
-If you want to customize the OpenTelemetry setup, see the docs about using [OpenTelemetry with `8.x`](./v8-opentelemetry)
-
 Here's an example of instrumentating a Connect application with Sentry Node SDK `8.x`:
 
 ```JavaScript

platform-includes/migration/javascript-v8/important-changes/javascript.express.mdx

@@ -8,8 +8,6 @@ If you need to support older versions of Node.js, please use Sentry Node SDK `7.
 
 With 8.x, @sentry/node has been completely overhauled. It is now powered by [OpenTelemetry](https://opentelemetry.io/) under the hood. You do not need to know or understand what OpenTelemetry is in order to use Sentry. We set up OpenTelemetry under the hood, no knowledge of it is required in order to get started, though if you use OpenTelemetry-native APIs to start spans, and Sentry will pick up everything automatically.
 
-If you want to customize the OpenTelemetry setup, see the docs about using [OpenTelemetry with `8.x`](./v8-opentelemetry)
-
 Here's an example of instrumentating an Express application with Sentry Node SDK `8.x`:
 
 ```JavaScript

platform-includes/migration/javascript-v8/important-changes/javascript.gcp-functions.mdx

@@ -8,8 +8,6 @@ If you need to support older versions of Node.js, please use Sentry Serverless S
 
 With 8.x, the Sentry Serverless SDK for Google Cloud Functions has been completely overhauled. It is now powered by [OpenTelemetry](https://opentelemetry.io/) under the hood. You do not need to know or understand what OpenTelemetry is in order to use Sentry. We set up OpenTelemetry under the hood, no knowledge of it is required in order to get started, though if you use OpenTelemetry-native APIs to start spans, and Sentry will pick up everything automatically.
 
-If you want to customize the OpenTelemetry setup, see the docs about using [OpenTelemetry with `8.x`](./v8-opentelemetry)
-
 With this change, `@sentry/serverless` has been removed and will no longer be published. The GCP related code now lives in `@sentry/google-cloud-serverless`.
 
 Here's an example of instrumentating your Google Cloud Function with Sentry Serverless SDK `8.x`:

platform-includes/migration/javascript-v8/important-changes/javascript.koa.mdx

@@ -8,8 +8,6 @@ If you need to support older versions of Node.js, please use Sentry Node SDK `7.
 
 With 8.x, @sentry/node has been completely overhauled. It is now powered by [OpenTelemetry](https://opentelemetry.io/) under the hood. You do not need to know or understand what OpenTelemetry is in order to use Sentry. We set up OpenTelemetry under the hood, no knowledge of it is required in order to get started, though if you use OpenTelemetry-native APIs to start spans, and Sentry will pick up everything automatically.
 
-If you want to customize the OpenTelemetry setup, see the docs about using [OpenTelemetry with `8.x`](./v8-opentelemetry)
-
 Here's an example of instrumentating a Koa application with Sentry Node SDK `8.x`:
 
 ```JavaScript

platform-includes/migration/javascript-v8/important-changes/javascript.nextjs.mdx

@@ -74,8 +74,6 @@ We now support the following integrations out of the box with 0 configuration:
 - `postgresIntegration`: Automatically instruments PostgreSQL
 - `prismaIntegration`: Automatically instruments Prisma
 
-If you want to customize the OpenTelemetry setup, see the docs about using [OpenTelemetry with `8.x`](./v8-opentelemetry)
-
 ### Updated `withSentryConfig` Usage
 
 With `8.x` of the Sentry Next.js SDK, `withSentryConfig` will no longer accept 3 arguments. The second argument (holding options for the Sentry Webpack plugin) and the third argument (holding options for SDK build-time configuration) should now be passed as one: