diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index e10ebbc1668fe9..af3cce1509c681 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -38,10 +38,10 @@
 
 # /src/docs/cli/dif.mdx @getsentry/owners-native
 
-# /.github/labels.yml @getsentry/open-source
-# /.github/workflows/react-to-product-owners-yml-changes.yml @getsentry/open-source
-# /bin/react-to-product-owners-yml-changes.py @getsentry/open-source
-# /bin/react-to-product-owners-yml-changes.sh @getsentry/open-source
+# /.github/labels.yml @getsentry/dev-infra
+# /.github/workflows/react-to-product-owners-yml-changes.yml @getsentry/dev-infra
+# /bin/react-to-product-owners-yml-changes.py @getsentry/dev-infra
+# /bin/react-to-product-owners-yml-changes.sh @getsentry/dev-infra
 
 # ###### Replays #######
 
diff --git a/app/platform-redirect/page.tsx b/app/platform-redirect/page.tsx
index 0183bb96b70e0d..3cfd54088e637d 100644
--- a/app/platform-redirect/page.tsx
+++ b/app/platform-redirect/page.tsx
@@ -79,7 +79,7 @@ export default async function Page(props: {
 
   return (
     <DocPage frontMatter={frontMatter}>
-      <Alert level="info">{platformInfo}</Alert>
+      <Alert>{platformInfo}</Alert>
 
       <ul>
         {platformList.map(p => (
diff --git a/apps/changelog/package.json b/apps/changelog/package.json
index 2bb3a426cbbc9b..174e7a1d74247c 100644
--- a/apps/changelog/package.json
+++ b/apps/changelog/package.json
@@ -21,10 +21,11 @@
     "@auth/prisma-adapter": "^2.7.4",
     "@google-cloud/storage": "^7.7.0",
     "@prisma/client": "^5.8.1",
+    "@prisma/instrumentation": "^5.8.1",
     "@radix-ui/react-icons": "^1.3.2",
     "@radix-ui/react-toolbar": "^1.1.0",
     "@radix-ui/themes": "^3.1.3",
-    "@sentry/nextjs": "8.36.0",
+    "@sentry/nextjs": "9.0.0-alpha.0",
     "@spotlightjs/spotlight": "^2.1.1",
     "next": "15.1.2",
     "next-auth": "^4.24.5",
diff --git a/apps/changelog/sentry.server.config.ts b/apps/changelog/sentry.server.config.ts
index baffc0d1106248..98855961e6e3b3 100644
--- a/apps/changelog/sentry.server.config.ts
+++ b/apps/changelog/sentry.server.config.ts
@@ -1,9 +1,14 @@
 import * as Sentry from '@sentry/nextjs';
+import {PrismaInstrumentation} from '@prisma/instrumentation';
 
 Sentry.init({
   dsn: process.env.NEXT_PUBLIC_SENTRY_DSN,
   tracesSampleRate: 1,
   environment: process.env.NODE_ENV,
-  integrations: [Sentry.prismaIntegration()],
+  integrations: [
+    Sentry.prismaIntegration({
+      prismaInstrumentation: new PrismaInstrumentation(),
+    }),
+  ],
   spotlight: process.env.NODE_ENV === 'development',
 });
diff --git a/apps/changelog/src/instrumentation.ts b/apps/changelog/src/instrumentation.ts
index 540f292628b6bc..8aff09f087d02c 100644
--- a/apps/changelog/src/instrumentation.ts
+++ b/apps/changelog/src/instrumentation.ts
@@ -10,4 +10,4 @@ export async function register() {
   }
 }
 
-export const onRequestError = Sentry.experimental_captureRequestError;
+export const onRequestError = Sentry.captureRequestError;
diff --git a/develop-docs/application-architecture/dynamic-sampling/architecture.mdx b/develop-docs/application-architecture/dynamic-sampling/architecture.mdx
index a27e2feb03c325..e7f57477eb1100 100644
--- a/develop-docs/application-architecture/dynamic-sampling/architecture.mdx
+++ b/develop-docs/application-architecture/dynamic-sampling/architecture.mdx
@@ -133,7 +133,7 @@ In this case, the matching will happen from **top to bottom** and the following
 1. Rule `1` is matched against the event payload, since it is of type `transaction`. The `samplingValue` is a `factor`, thus the accumulated factors will now be `2.0 * 1.0`, where `1.0` is the identity for the multiplication.
 2. Because rule `1` was a factor rule, the matching continues and rule `2` will be matched against the DSC, since it is of type `trace`. The `samplingValue` is a `sampleRate`, thus the matching will stop and the sample rate will be computed as `2.0 * 0.5 = 1.0`, where `2.0` is the factor accumulated from the previous rule and `0.5` is the sample rate of the current rule.
 
-<Alert title="✨ Note" level="info">
+<Alert title="✨ Note">
 
 It is important to note that a `sampleRate` rule must match in order for a sampling decision to be made; in case this condition is not met, the event will be kept. In practice, each project will have a uniform trace rule which will always match and contain the base sample rate of the organization.
 
diff --git a/develop-docs/application-architecture/dynamic-sampling/fidelity-and-biases.mdx b/develop-docs/application-architecture/dynamic-sampling/fidelity-and-biases.mdx
index f2d450eebda67a..96df0be998bf3f 100644
--- a/develop-docs/application-architecture/dynamic-sampling/fidelity-and-biases.mdx
+++ b/develop-docs/application-architecture/dynamic-sampling/fidelity-and-biases.mdx
@@ -5,7 +5,7 @@ sidebar_order: 2
 
 Dynamic Sampling allows Sentry to automatically adjust the amount of data retained based on how valuable the data is to the user. This is technically achieved by applying a **sample rate** to every event, which is determined by a **set of rules** that are evaluated for each event.
 
-<Alert title="✨ Note" level="info">
+<Alert title="✨ Note">
 
 A sample rate is a number in the interval `[0.0, 1.0]` that will determine the likelihood of a transaction to be retained. For example, a sample rate of `0.5` means that the transaction will be retained on average 50% of the time.
 
@@ -21,15 +21,15 @@ There are two available modes to govern the target sample rates for Dynamic Samp
 - **Automatic Mode** dynamically manages the target sample rate for each project based on the target sample rate for the organization, prioritizing lower volume projects to increase visibility. Automatic Mode is active if the organization option `sentry:sampling_mode` is set to `organization`. The target sample rate for the organization is stored in the **organization** option `sentry:target_sample_rate`, and project target sample rates are calculated based on the organization target sample rate.
 - **Manual Mode** allows the user to set static target sample rates on a per-project basis that serve as the baseline sample rate before applying the dynamic biases outlined below. Target sample rates are not adjusted by the system. Manual Mode is active if the organization option `sentry:sampling_mode` is set to `project`. The target sample rates for projects are stored in the **project** option `sentry:target_sample_rate`.
 
-All functionality defaults to Automatic Mode if the option `sentry:sampling_mode` is not set, and all target sample rates default to 1 if the option `sentry:target_sample_rate` is not set. 
+All functionality defaults to Automatic Mode if the option `sentry:sampling_mode` is not set, and all target sample rates default to 1 if the option `sentry:target_sample_rate` is not set.
 
 When the user switches between modes, target sample rates are transferred unless changed explicitly. For example, if the user switches from Automatic Mode to Manual Mode, the sample rates calculated during Automatic Mode are persisted in the project option `sentry:target_sample_rate`. Conversely, if the user switches from Manual Mode to Automatic Mode, the project target sample rates are recalculated based on the overall organization target sample rate.
 
-The [sample rates are periodically recalibrated](https://github.com/getsentry/sentry/blob/9b98be6b97323a78809a829e06dcbef26a16365c/src/sentry/dynamic_sampling/rules/biases/recalibration_bias.py#L11-L44) to ensure that the overall target sample rate is met. This recalibration is done on a project level or organization level, depending on the dynamic sampling mode. Within the target sample rate, Dynamic Sampling **biases towards more meaningful data**. This is achieved by constantly updating and communicating special rules to Relay, via a project configuration, which then applies targeted sampling to every event. 
+The [sample rates are periodically recalibrated](https://github.com/getsentry/sentry/blob/9b98be6b97323a78809a829e06dcbef26a16365c/src/sentry/dynamic_sampling/rules/biases/recalibration_bias.py#L11-L44) to ensure that the overall target sample rate is met. This recalibration is done on a project level or organization level, depending on the dynamic sampling mode. Within the target sample rate, Dynamic Sampling **biases towards more meaningful data**. This is achieved by constantly updating and communicating special rules to Relay, via a project configuration, which then applies targeted sampling to every event.
 
 ![Concept of Fidelity](./images/fidelityAndPriorities.png)
 
-<Alert title="✨ Note" level="info">
+<Alert title="✨ Note">
 For orgs under AM2, Dynamic sampling uses a [sliding window function](https://github.com/getsentry/sentry/blob/cc8cc38c8a108719d068e5622b24a8d0c744e84c/src/sentry/dynamic_sampling/tasks/sliding_window_org.py#L37-L61) over the incoming volume to calculate the target sample rate.
 </Alert>
 
@@ -39,7 +39,7 @@ It is important to note that fidelity only determines an **approximate target sa
 
 Instead, the Sentry backend **computes a set of rules** whose goal is to cooperatively achieve the target sample rate. Determining when and how to set these rules is part of the Dynamic Sampling infrastructure.
 
-<Alert title="✨ Note" level="info">
+<Alert title="✨ Note">
 
 The effectively applied sample rate, in the end, depends on how much data matches each of the bias overrides.
 
@@ -59,7 +59,7 @@ To achieve trace sampling, SDKs pass all fields that can be sampled by [Dynamic
 
 ![Trace Sampling](./images/traceSampling.png)
 
-<Alert title="✨ Note" level="info">
+<Alert title="✨ Note">
 
 In order to achieve full trace sampling, the random number generator used by Relay is seeded with the trace ID inside of the DSC sent by the SDK. This ensures that traces with the same trace ID will always yield the same sampling decision.
 
@@ -115,7 +115,7 @@ The list of development environments is available [here](https://github.com/gets
 For prioritizing dev environments, we use a sample rate of `1.0` (100%), which results in all traces being sampled.
 
 ### Prioritize Low Volume Projects
-<Alert title="✨ Note" level="info">
+<Alert title="✨ Note">
 This bias is only active in Automatic Mode (and not in Manual Mode). It applies to any incoming trace and is defined on a per-project basis.
 </Alert>
 
@@ -126,13 +126,13 @@ The algorithm used in this bias computes a new sample rate with the goal of prio
 ### Prioritize Low Volume Transactions
 This bias is used to prioritize low-volume transactions that can be drowned out by high-volume transactions. The goal is to rebalance sample rates of the individual transactions so that low-volume transactions are more likely to have representative samples. The bias is of type trace, which means that the transaction considered for rebalancing will be the root transaction of the trace.
 
-Prioritization of low volume transactions works slightly differently depending on the dynamic sampling mode: 
-- In **Automatic Mode** (`sentry:sampling_mode` == `organization`), the output of the [boost_low_volume_projects](https://github.com/getsentry/sentry/blob/dee539472e999bf590cfc4e99b9b12981963defb/src/sentry/dynamic_sampling/tasks/boost_low_volume_transactions.py#L183) task is used as the base sample rate for the balancing algorithm. 
+Prioritization of low volume transactions works slightly differently depending on the dynamic sampling mode:
+- In **Automatic Mode** (`sentry:sampling_mode` == `organization`), the output of the [boost_low_volume_projects](https://github.com/getsentry/sentry/blob/dee539472e999bf590cfc4e99b9b12981963defb/src/sentry/dynamic_sampling/tasks/boost_low_volume_transactions.py#L183) task is used as the base sample rate for the balancing algorithm.
 - In **Manual Mode** (`sentry:sampling_mode` == `project`), the project target sample rate is used as the base sample rate for the balancing algorithm.
 
-In order to rebalance transactions, the system retrieves the counts of the transactions for each project and calculates a new sample rate for each transaction. 
+In order to rebalance transactions, the system retrieves the counts of the transactions for each project and calculates a new sample rate for each transaction.
 
-<Alert title="✨ Note" level="info">
+<Alert title="✨ Note">
 
 The algorithms for boosting low volume events are run periodically (with cron jobs) with a sliding window to account for changes in the incoming volume.
 
diff --git a/develop-docs/application-architecture/dynamic-sampling/the-big-picture.mdx b/develop-docs/application-architecture/dynamic-sampling/the-big-picture.mdx
index 00ba3b12035460..dc5e09e5f9b9ff 100644
--- a/develop-docs/application-architecture/dynamic-sampling/the-big-picture.mdx
+++ b/develop-docs/application-architecture/dynamic-sampling/the-big-picture.mdx
@@ -7,7 +7,7 @@ sidebar_order: 1
 ![Sequencing](./images/sequencing.png)
 
 
-<Alert title="💡 Note" level="info">
+<Alert title="💡 Note">
 
 Dynamic Sampling currently operates on either spans or transactions to measure data throughput. This is controlled by the feature flag `organizations:dynamic-sampling-spans` and usually set to what the organization's subscription is metered by. In development, this currently defaults to transactions.
 The logic between the two data categories is identical, so most of this documentation is kept at a generic level and important differences are pointed out explicitly.
@@ -27,7 +27,7 @@ When events arrive, in a simplified model, they go through the following steps:
 4. **Dynamic Sampling**: based on an internal set of rules, Relay determines a sample rate for every incoming event. A random number generator finally decides whether a payload should be kept or dropped.
 5. **Rate limiting**: events that are sampled by Dynamic Sampling will be stored and indexed. To protect the infrastructure, internal rate limits apply at this point. Under normal operation, this **rate limit is never reached** since dynamic sampling already reduces the volume of events stored.
 
-<Alert title="💡 Example" level="info">
+<Alert title="💡 Example">
 
 A client is sending 1000 events per second to Sentry:
 1. 100 events per second are from old browsers and get dropped through an inbound data filter.
@@ -44,7 +44,7 @@ The ingestion pipeline has two kinds of rate limits that  behave differently com
 1. **High-level request limits on load balancers**: these limits do not differentiate which data is sent by clients and drop requests as soon as the throughput from clients reaches the limit.
 2. **Specific limits per data category in Relay**: these limits apply once requests have been parsed and have gone through basic handling (see [Sequencing](#sequencing) above).
 
-<Alert title="✨️ Note" level="info">
+<Alert title="✨️ Note">
 
 There is a dedicated rate limit for stored events after inbound filters and dynamic sampling. However, it does not affect total events since the fidelity decreases with higher total event volumes and this rate limit is not expected to trigger since Dynamic Sampling already reduces the stored event throughput.
 
@@ -56,7 +56,7 @@ Dynamic sampling ensures complete traces by retaining all events associated with
 
 Despite dynamic sampling providing trace completeness, events or other items (errors, replays, ...) may still be missing from a trace when rate limiting drops one or more of them. Rate limiting drops items without regard for the trace, making each decision independently and potentially resulting in broken traces.
 
-<Alert title="💡 Example" level="info">
+<Alert title="💡 Example">
 
 For example, if there is a trace from `Project A` to `Project B` and `Project B` is subject to rate limiting or quota enforcement, events of `Project B` from the trace initiated by `Project A` are lost.
 
@@ -84,7 +84,7 @@ Each of these metrics can be filtered and grouped by a number of predefined tags
 
 For more granular queries, **stored events are needed**. _The purpose of dynamic sampling here is to ensure that there are always sufficient representative sample events._
 
-<Alert title="💡 Example" level="info">
+<Alert title="💡 Example">
 
 If Sentry applies a 1% dynamic sample rate, you can still receive accurate events per minute (SPM or TPM, depending on event type) and web vital quantiles through total event data backed by metrics. There is also a listing of each of these numbers by the transaction.
 
diff --git a/develop-docs/application-architecture/multi-region-deployment/control-silo.mdx b/develop-docs/application-architecture/multi-region-deployment/control-silo.mdx
index 7e4b889939d905..44959e0cd4b222 100644
--- a/develop-docs/application-architecture/multi-region-deployment/control-silo.mdx
+++ b/develop-docs/application-architecture/multi-region-deployment/control-silo.mdx
@@ -15,7 +15,7 @@ Prior to our multi-region offering, all API traffic from customers would be sent
 - DSN host
 - A static list of URL names (region pin list)
 
-<Alert level="info">
+<Alert>
 💡 Requests going to sentry.io do not meet data residency requirements. Customers will need to use region domains in order to not have requests go to the US.
 </Alert>
 
diff --git a/develop-docs/application-architecture/overview.mdx b/develop-docs/application-architecture/overview.mdx
index cbc9aab0607e37..d8bd6813f7b949 100644
--- a/develop-docs/application-architecture/overview.mdx
+++ b/develop-docs/application-architecture/overview.mdx
@@ -100,7 +100,7 @@ In order to offer customers data residency we needed to co-locate the bulk of an
 
 These constraints led our design to having multiple 'silo modes'.
 
-<Alert level="info">
+<Alert>
     ☝ The term ‘silo’ was chosen as other applicable terms (region, zone, partition, cluster) are all taken.
 </Alert>
 
diff --git a/develop-docs/backend/api/design.mdx b/develop-docs/backend/api/design.mdx
index 84dfc70763e1da..ed902f1c501d5e 100644
--- a/develop-docs/backend/api/design.mdx
+++ b/develop-docs/backend/api/design.mdx
@@ -32,7 +32,7 @@ Here are some additional examples:
 - 👍 `/projects/\{organization_slug}/\{project_slug}/issues/`
 - 👎 `/projects/`
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 Hierarchy here does not necessarily mean that one collection belongs to a parent collection. For example:
 - `projects/\{project_identifier}/teams/` refers to the **teams** that have been added to specific project
@@ -82,7 +82,7 @@ Here are some notes that can help you decide between similar methods. We use *Ge
 ## Response Object
 Each response object returned from an API should be a serialized version of the Django model associated with the resource. You can see all the existing serializers [here](https://github.com/getsentry/sentry/tree/master/src/sentry/api/serializers/models).
 
- <Alert title="Note" level="info">
+ <Alert title="Note">
 
  Some models might have different serializers based on use case. For example, `Project` can be serialized into `DetailedProjectSerializer` or `ProjectSerializer`. Decide which one to use based on your use case and API scope but **DO NOT RETURN CUSTOM OBJECTS** like \{`slug: project_slug, platform: project_platform`}. We want the API responses to be uniform and useable in multiple automations without adding extra complication to the external developers' code.
 
diff --git a/develop-docs/backend/api/public.mdx b/develop-docs/backend/api/public.mdx
index 2100b00a154538..f21ec5068981ff 100644
--- a/develop-docs/backend/api/public.mdx
+++ b/develop-docs/backend/api/public.mdx
@@ -38,7 +38,7 @@ build. With that being said, there are 3 exceptions where we don't publish APIs:
    that you think it should be published let [owners-api](https://github.com/orgs/getsentry/teams/owners-api)
    know and we can help with that.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 Always keep in mind that your APIs may still be used even if they're `private`. All the APIs
 in the Sentry repo are accessible due to our open-source nature.
diff --git a/develop-docs/backend/application-domains/feature-flags/flagpole.mdx b/develop-docs/backend/application-domains/feature-flags/flagpole.mdx
index 1b081fc74c70ee..774fd64990ab93 100644
--- a/develop-docs/backend/application-domains/feature-flags/flagpole.mdx
+++ b/develop-docs/backend/application-domains/feature-flags/flagpole.mdx
@@ -183,7 +183,7 @@ features.add(
 feature.<feature_scope>:<feature_name>
 ```
 
-<Alert level="info">
+<Alert>
     The feature config should not be merged until the registration commit in step 1 has been fully deployed to all target environments. This is because Options Automator will fail to push options to any environments missing the option registration.
     If this happens, make sure to rerun the options deployment once all environments have been updated to ensure your feature is active.
 </Alert>
diff --git a/develop-docs/backend/application-domains/options.mdx b/develop-docs/backend/application-domains/options.mdx
index e94bf86f759e89..621fee952d54e5 100644
--- a/develop-docs/backend/application-domains/options.mdx
+++ b/develop-docs/backend/application-domains/options.mdx
@@ -22,7 +22,7 @@ Follow these rules when adding new options:
 
 The value of an option can be any pickleable value.
 
-<Alert level="info">
+<Alert>
   It is safe to declare and use an option in the same pull request, you don't need to
   split them up.
 </Alert>
@@ -55,7 +55,7 @@ from sentry import options
 options.set("performance.some-feature-rate", 0.01)
 ```
 
-<Alert level="info">
+<Alert>
   If you do not have access to the shell, you'll need to contact OPS to set the option
   value for you.
 </Alert>
@@ -125,7 +125,7 @@ from sentry import options
 options.delete("performance.some-feature-rate")
 ```
 
-<Alert level="info">
+<Alert>
   If you do not have access to the shell, you'll need to contact OPS to remove the option
   for you.
 </Alert>
diff --git a/develop-docs/development-infrastructure/backend-development-server.mdx b/develop-docs/development-infrastructure/backend-development-server.mdx
index eb838a6423d78f..4e830e29933019 100644
--- a/develop-docs/development-infrastructure/backend-development-server.mdx
+++ b/develop-docs/development-infrastructure/backend-development-server.mdx
@@ -23,7 +23,6 @@ When you browse `localhost:9001`, the browser will load JavaScript from producti
 
 This will do literally nothing except bring up the web workers. You are now responsible to manually:
 
-* Starting Relay if you need it: `sentry devservices attach relay`
 * Starting relevant Kafka consumers if you need them (e.g. for ingestion). This highly depends on which dataset you're working on.
 * Starting Celery workers using `sentry run worker` to run most kinds of background jobs.
 
diff --git a/develop-docs/development-infrastructure/devservices.mdx b/develop-docs/development-infrastructure/devservices.mdx
index 866fb37b26686f..00e05f03474d42 100644
--- a/develop-docs/development-infrastructure/devservices.mdx
+++ b/develop-docs/development-infrastructure/devservices.mdx
@@ -3,52 +3,54 @@ title: Service Manager (devservices)
 sidebar_order: 40
 ---
 
-Sentry provides an abstraction to Docker to run required services within development called `devservices`.
+A standalone CLI tool called [`devservices`](https://github.com/getsentry/devservices) is used to bring up and manage service dependencies. The tool reads from a `config.yml` file within a repository's `devservices` directory. It is an abstraction built on top of Docker Compose and Docker.
 
 ```shell
-Usage: sentry devservices [OPTIONS] COMMAND [ARGS]...
-
-  Manage dependent development services required for Sentry.
-
-  Do not use in production!
-
-Options:
-  --help  Show this message and exit.
-
-Commands:
-  attach  Run a single devservice in foreground, as...
-  down    Shut down all services.
-  rm      Delete all services and associated data.
-  up      Run/update dependent services.
+usage: devservices [-h] [--version] COMMAND ...
+
+CLI tool for managing service dependencies.
+
+options:
+  -h, --help            show this help message and exit
+  --version             show program's version number and exit
+
+commands:
+  up                  Bring up a service and its dependencies
+  down                Bring down a service and its dependencies
+  list-dependencies   List the dependencies of a service
+  list-services (ls)  List the services installed locally
+  status              View status of a service
+  logs                View logs for a service
+  update              update devservices to the latest version
+  purge               Purge the local devservices cache
 ```
 
 ## Viewing logs for a service
 
 ```shell
-# Follow snuba logs
-docker logs -f sentry_snuba
+devservices logs
 ```
 
 ## Running CLI clients for redis, postgres and clickhouse
 
 ```shell
 # redis
-docker exec -it sentry_redis redis-cli
+docker exec -it redis-redis-1 redis-cli
 
 # clickhouse
-docker exec -it sentry_clickhouse clickhouse-client
+docker exec -it snuba-clickhouse-1 clickhouse-client
 
 # psql
-docker exec -it sentry_postgres psql -U postgres
+docker exec -it sentry-postgres-1 psql -U postgres
 ```
 
 ## Removing container state
 
-Should you really bamboozle your containers or volumes, you can use `devservices rm` to start over.
+Should you really bamboozle your containers or volumes, you can use `devservices purge` to start over.
 
 ```shell
 # Remove all data (containers, volumes, and networks) associated with ALL services
-sentry devservices rm
+devservices purge
 ```
 
 As an example, let's say we've managed to corrupt our postgres
@@ -57,5 +59,59 @@ your postgres data you can do:
 
 ```shell
 # Remove all data (containers, volumes, and networks) associated with a single service
-sentry devservices rm postgres
+docker container rm sentry-postgres-1
+docker volume rm sentry_postgres-data
+```
+
+## Running devservices with a specific mode
+
+Common modes:
+
+- `symbolicator`: Bring up sentry dependencies and symbolicator
+- `chartcuterie`: Bring up sentry dependencies and chartcuterie
+- `minimal`: Bring up minimal services for local development
+- `profiling`: Bring up sentry dependencies and vroom
+- `full`: Bring up all services (symbolicator, taskbroker, snuba, vroom, etc)
+
+```shell
+devservices up --mode symbolicator
+```
+
+## Migrating data from the deprecated `sentry devservices`
+
+<Alert level="warning" title="Important">
+  These instructions can result in data loss. Please proceed with caution. This is an example with postgres, but can be done with other docker volumes as well.
+</Alert>
+
+Volume names are different for each service.
+
+Clickhouse:
+  - old: `sentry_clickhouse`
+  - new: `snuba_clickhouse-data`
+
+Postgres:
+  - old: `sentry_postgres`
+  - new: `sentry_postgres-data`
+
+Kafka:
+  - old: `sentry_kafka`
+  - new: `kafka_kafka-data`
+
+Redis:
+  - old: `sentry_redis`
+  - new: `redis_redis-data`
+
+```shell
+# Create a new postgres volume
+docker volume create sentry_postgres-data
+
+# Copy over the data from the old volume
+docker run --rm \
+  -v sentry_postgres:/old_volume \
+  -v sentry_postgres-data:/new_volume \
+  ubuntu \
+  bash -c "cd /old_volume && cp -a . /new_volume"
+
+# Validate that data has been copied over
+docker run --rm -v sentry_postgres-data:/data ubuntu ls -l /data
 ```
diff --git a/develop-docs/development-infrastructure/environment/index.mdx b/develop-docs/development-infrastructure/environment/index.mdx
index fb9a5cbba5c069..3762bb46f7d3d1 100644
--- a/develop-docs/development-infrastructure/environment/index.mdx
+++ b/develop-docs/development-infrastructure/environment/index.mdx
@@ -28,7 +28,7 @@ The `devservices` ensure that you have all the services required for local devel
 When setting up `sentry`, execute the following command in the `sentry` folder:
 
 ```shell
-sentry devservices up
+devservices up
 ```
 
 After that, you can start the development server inside the `sentry` folder:
@@ -44,7 +44,7 @@ Access it at [http://dev.getsentry.net:8000](http://dev.getsentry.net:8000) (you
 A superuser account should have been created for you during bootstrap - `admin@sentry.io` with password `admin`.
 You can create other users with `sentry createuser`.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
   When asked for the root address of the server, make sure that you use
   [http://dev.getsentry.net:8000](http://dev.getsentry.net:8000), as both
   protocol _and_ port are required in order for DNS and some pages' URLs to be
@@ -75,7 +75,7 @@ yarn https-proxy
 
 After the server is running we can visit the dev server using `https` at port `:8003` instead of over `http` at `:8000`.
 
-<Alert title="HTTP Strict-Transport-Security" level="info">
+<Alert title="HTTP Strict-Transport-Security">
   You might get into a situation where [HSTS](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security) is enabled for your domain and you're unable to visit using `http` anymore.
 
   To clear the HSTS visit `chrome://net-internals/#hsts` in Chrome based browsers and use the "Delete domain security policies" form.
@@ -85,31 +85,10 @@ After the server is running we can visit the dev server using `https` at port `:
 
 <Link to="/relay/">Relay</Link> and the ingest workers are not started by default. Follow the instructions below to start them so you can send events to your dev environment Sentry instance:
 
-- Set `SENTRY_USE_RELAY = True` in `~/.sentry/sentry.conf.py`. This will tell `sentry devservices up` to also start services that Relay needs.
-- Run `sentry devservices up` to start the services Relay needs. (like for example Kafka)
+- Set `SENTRY_USE_RELAY = True` in `~/.sentry/sentry.conf.py`.
+- Run `devservices up` to start the services Relay needs. (like for example Kafka)
 - (Re-)Start your devserver with the `--ingest` flag (e.g. `sentry devserver --workers --ingest`). This will start the Relay container and all related services alongside your devserver.
 
-Note: To update Relay, manually run `sentry devservices up --skip-only-if relay`.
-
-#### Metrics Ingestion Pipeline
-
-**If you want to enable the entire metrics ingestion pipeline:** You need to add the following to your config at `~/.sentry/sentry.conf.py`:
-
-```python
-SENTRY_USE_RELAY = True
-SENTRY_USE_METRICS_DEV = True
-SENTRY_EVENTSTREAM = "sentry.eventstream.kafka.KafkaEventStream"
-SENTRY_FEATURES['organizations:metrics-extraction'] = True  # Enables session metrics
-SENTRY_FEATURES['organizations:transaction-metrics-extraction'] = True  # Enables transaction metrics
-```
-
-After enabling `KafkaEventStream` the `snuba` service has to be reset to pick up the new configuration:
-
-```shell
-sentry devservices rm snuba
-sentry devservices up snuba
-```
-
 ## Running the Getsentry Development Server
 
 <Alert title="Employees Only" level="warning">
@@ -123,7 +102,7 @@ Before running `getsentry`, you might need to run `devenv sync` inside the `gets
 Just like running `sentry` (see above), you can start the `devservices` using the following command in the `getsentry` folder:
 
 ```shell
-sentry devservices up
+devservices up
 ```
 
 After that, you can start the development server inside the `getsentry` folder:
@@ -210,6 +189,23 @@ following in getsentry:
 
 ---
 
+**Problem:** `Error response from daemon: driver failed programming external connectivity on endpoint sentry-postgres-1 (e9e631ff7f32bd00052c25064c56609794a3b96da0dc04742f558e3ae659fa66): Bind for 127.0.0.1:5432 failed: port is already allocated`
+
+**Solution:**
+
+There is another process using the port. Try running `docker ps`. If you are currently running services through `sentry devservices`, you will need to stop them.
+
+```shell
+sentry devservices down
+devservices up
+```
+Otherwise, check to see if you have another process running on the allocated port.
+```shell
+lsof -i :5432
+```
+Then, either end the process or kill it if you need to.
+---
+
 **Problem:** You see an error that mentions something like `pkg_resources.DistributionNotFound: The 'some_dependency<0.6.0,>=0.5.5' distribution was not found and is required by sentry`
 
 **Solution:** Your virtualenv needs to be updated. Run `devenv sync`.
@@ -267,12 +263,12 @@ brew upgrade --cask chromedriver
 
 ---
 
-**Problem:** You see something like `Error: No such container: sentry_postgres`, or you don't see `sentry_snuba`, `sentry_postgres`, `sentry_clickhouse`, and `sentry_redis` listed under `COMMAND NAMES`.
+**Problem:** You see something like `Error: No such container: sentry-postgres-1`, or you don't see `snuba-snuba-1`, `redis-redis-1`, `snuba-clickhouse-1`, and `kafka-kafka-1` listed under `COMMAND NAMES`.
 
 **Solution:**
 
 ```shell
-sentry devservices up
+devservices up
 ```
 
 ---
diff --git a/develop-docs/development-infrastructure/testing.mdx b/develop-docs/development-infrastructure/testing.mdx
index 3d019b0398c04f..6f5a0047f9d989 100644
--- a/develop-docs/development-infrastructure/testing.mdx
+++ b/develop-docs/development-infrastructure/testing.mdx
@@ -13,24 +13,13 @@ to use the `--project` flag to separate local testing volumes from test suite
 volumes:
 
 ```shell
-# Turn off services for local testing.
-sentry devservices down
+# Bring up services for testing
+devservices up
 
-# Turn on services with a test prefix to use separate containers and volumes
-sentry devservices up --project test
-
-# Verify that test containers came up correctly
-docker ps --format '{{.Names}}'
-
-# Later when you're done running tests and want to run local servers again
-sentry devservices down --project test && sentry devservices up
+# Verify that containers came up correctly
+devservices status
 ```
 
-When using the `--project` option you can confirm which containers are running
-`docker ps`. Each running container should be prefixed with `test_`. See the
-[devservices docs](/development/devservices/) section for more information on
-managing services.
-
 ## Python Tests
 
 For python tests we use [pytest](https://docs.pytest.org/en/latest/) and testing tools
@@ -341,7 +330,7 @@ SENTRY_SCREENSHOT=1 VISUAL_SNAPSHOT_ENABLE=1 \
     -k test_with_onboarding
 ```
 
-<Alert title="Tip!" level="info">
+<Alert title="Tip!">
   If you're seeing `WARNING: Failed to gather log types: Message: unknown command:
   Cannot call non W3C standard command while in W3C mode`, it means that `Webpack` hasn't compiled assets properly.
 </Alert>
diff --git a/develop-docs/engineering-practices/code-review.mdx b/develop-docs/engineering-practices/code-review.mdx
index 1d227405f56245..54719abffb6c47 100644
--- a/develop-docs/engineering-practices/code-review.mdx
+++ b/develop-docs/engineering-practices/code-review.mdx
@@ -216,3 +216,11 @@ Please be pragmatic, and consider the cost of each incremental request for chang
 - Feedback is objective and actionable
 - Submitter responds to feedback and makes changes promptly
 - PR is approved and merged within 48 hours
+
+### LOGAF Scale
+
+For feedback in PRs, you can use the [LOGAF scale](https://blog.danlew.net/2020/04/15/the-logaf-scale/) to specify how important a comment is:
+
+- `l`: low - nitpick. You may address this comment, but you don't have to.
+- `m`: medium - normal comment. Worth addressing and fixing.
+- `h`: high - Very important. We must not merge this PR without addressing this issue.
diff --git a/develop-docs/frontend/component-library.mdx b/develop-docs/frontend/component-library.mdx
index ebd6c04f27e041..15d972505c5684 100644
--- a/develop-docs/frontend/component-library.mdx
+++ b/develop-docs/frontend/component-library.mdx
@@ -3,7 +3,7 @@ title: UI Component Library
 sidebar_order: 40
 ---
 
-<Alert level="info">
+<Alert>
   To jump straight in visit <Link to="https://sentry.io/orgredirect/organizations/:orgslug/stories/"><code>/stories/</code></Link> on your existing Sentry Org/Install.
 </Alert>
 
diff --git a/develop-docs/frontend/design-tenets.mdx b/develop-docs/frontend/design-tenets.mdx
index d36c9ecd2956a7..e1300def30b8d6 100644
--- a/develop-docs/frontend/design-tenets.mdx
+++ b/develop-docs/frontend/design-tenets.mdx
@@ -3,7 +3,7 @@ title: Frontend Design Tenets
 sidebar_order: 20
 ---
 
-<Alert level="info">
+<Alert>
   <strong>ten·et (noun)</strong>
 
   _a principle or belief, especially one of the main principles of a religion or philosophy._
@@ -19,7 +19,7 @@ Why disable (grey out)?
 - Educates the user on capabilities they don't have permission for (yet)
 - Informs of the current value (read access)
 
-<Alert level="info">
+<Alert>
   Bonus: where it makes sense, consider <Link href="https://blog.sentry.io/how-we-grew-sentrys-monthly-active-users-by-rethinking-invitations/" remote>prompting the user to request access</Link>.
 </Alert>
 
@@ -36,7 +36,7 @@ Why preserve state change in the URL?
 - Preserves browser back and forward buttons
 - Makes content shareable (user can share exact view with a teammate)
 
-<Alert level="info">
+<Alert>
   Ask yourself this question: "If I was sharing this page with my coworker on Slack, is it important that they see the exact view I'm looking at?" If the answer is "yes", then the state to regenerate that view should be present in the URL.
 </Alert>
 
@@ -49,7 +49,7 @@ Why minimize content refreshes?
 - Less rendering / data fetching for the browser
 - Assists user navigation by preserving sense of state ("where am I?")
 
-<Alert level="error">
+<Alert level="warning">
   Note: while there are a few good examples of this in action in the app, we are actually pretty inconsistent applying this design principle.
 </Alert>
 
diff --git a/develop-docs/frontend/index.mdx b/develop-docs/frontend/index.mdx
index fcaa10cf2172c8..2c599a6add5830 100644
--- a/develop-docs/frontend/index.mdx
+++ b/develop-docs/frontend/index.mdx
@@ -108,7 +108,7 @@ For event callback props passed to the component use the `on` prefix, e.g:
 
 ## State management
 
-<Alert level="info">
+<Alert>
   For React Hooks tips check out <Link to="/frontend/using-hooks/">this page</Link>.
 </Alert>
 
@@ -120,7 +120,7 @@ Reflux implements the unidirectional data flow pattern outlined by [Flux](https:
 
 ## Testing
 
-<Alert level="info">
+<Alert>
   For React Testing Library (RTL) tips check out <Link to="/frontend/using-rtl/">this page</Link>.
 </Alert>
 
diff --git a/develop-docs/frontend/upgrade-policies.mdx b/develop-docs/frontend/upgrade-policies.mdx
index 7bfab521e7833a..be437010cbddbb 100644
--- a/develop-docs/frontend/upgrade-policies.mdx
+++ b/develop-docs/frontend/upgrade-policies.mdx
@@ -43,7 +43,7 @@ Overall, our approach to upgrading packages is **a balanced one**, taking into a
 
 ## How to upgrade a package
 
-<Alert level="info">
+<Alert>
 
 You may not have to do this manually! See the below section on [Take advantage of tooling](#take-advantage-of-tooling) to learn more about our usage of `dependabot` for automatic frontend package upgrades.
 
@@ -61,7 +61,7 @@ yarn outdated --color | sort
 yarn upgrade --latest [package-name] [...]
 ```
 
-<Alert level="note">
+<Alert>
 
 Don’t forget to upgrade the `@types/[package-name]` package as well if necessary.
 
diff --git a/develop-docs/frontend/using-styled-components.mdx b/develop-docs/frontend/using-styled-components.mdx
index 26481f24c99c3f..a31734df6d2483 100644
--- a/develop-docs/frontend/using-styled-components.mdx
+++ b/develop-docs/frontend/using-styled-components.mdx
@@ -58,7 +58,7 @@ const SomeComponent = styled('div')`
 
 ## Dynamic Properties
 
-<Alert level="info">
+<Alert>
   Most of the time dynamic properties are not needed!
 </Alert>
 
diff --git a/develop-docs/ingestion/relay/relay-best-practices.mdx b/develop-docs/ingestion/relay/relay-best-practices.mdx
index c701ac7ebb4df8..d82005320dc33c 100644
--- a/develop-docs/ingestion/relay/relay-best-practices.mdx
+++ b/develop-docs/ingestion/relay/relay-best-practices.mdx
@@ -53,7 +53,7 @@ But they aren't always the right choice for Relay.
 Some of the listed issues are specific to the [regex](https://docs.rs/regex/latest/regex/) Rust crate Relay uses
 and others apply to regular expressions in general.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 Review the [Rust crate's documentation](https://docs.rs/regex/latest/regex/#overview) carefully before introducing a Regex.
 </Alert>
 
diff --git a/develop-docs/ingestion/relay/transaction-span-ratelimits.mdx b/develop-docs/ingestion/relay/transaction-span-ratelimits.mdx
index ff1676bdaf3d74..844d0b49c6dd5a 100644
--- a/develop-docs/ingestion/relay/transaction-span-ratelimits.mdx
+++ b/develop-docs/ingestion/relay/transaction-span-ratelimits.mdx
@@ -17,7 +17,7 @@ A dropped transaction results in dropped spans.
 
 The following document describes how transaction and span quotas interact with each other within Relay.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 This section describes how Relay has to interpret quotas, SDKs and other consumers
 should read [SDK Development / Rate Limiting](/sdk/rate-limiting/).
 </Alert>
@@ -69,19 +69,19 @@ Relay stage: customer managed, PoP-Relay or Processing-Relay. Until spans are ex
 should count the contained spans and generate an outcome with the contained span quantity + 1, for the segment span
 which would be generated from the transaction itself.
 
-<Note>
+<Alert>
 While it is desirable to have span counts correctly extracted from dropped transactions, it may not be feasible
 to do so at any stage of the processing pipeline. For example, it may not be possible to do so (malformed transactions)
 or simply too expensive to compute.
-</Note>
+</Alert>
 
 After spans have been extracted, the transaction is no longer a container of span items and just represents itself,
 thus, a dropped transaction with spans already extracted only generates outcomes for the total transactions and
 indexed transaction categories.
 
-<Note>
+<Alert>
 Span quotas are equivalent to transactions quotas, so all the above also applies for a span quota.
-</Note>
+</Alert>
 
 
 ## Examples
diff --git a/develop-docs/integrations/azuredevops/index.mdx b/develop-docs/integrations/azuredevops/index.mdx
index 79a3a11c79abba..20234b0a9b9e55 100644
--- a/develop-docs/integrations/azuredevops/index.mdx
+++ b/develop-docs/integrations/azuredevops/index.mdx
@@ -25,12 +25,12 @@ When configuring the app, use the following values:
 | Supported account types         | Accounts in any organizational directory |
 | Redirect URI                    | `{YOUR_DOMAIN}/extensions/vsts/setup`                                                              |
 
-<Note>
+<Alert>
 
 Take note of your App ID as we'll need it later.
 ![App ID](./app-id.png)
 
-</Note>
+</Alert>
 
 Next go to Manager -> API Permissions to add the following permissions:
 * Azure DevOps (`vso.code`, `vso.graph`, `vso.work_item`, `vso.service_endpoint`)
@@ -66,7 +66,7 @@ Add the following to your `devlocal.py` file:
 SENTRY_FEATURES["organizations:migrate-azure-devops-integration"] = True
 ```
 
-<Alert title="Feature Flag" level="info">
+<Alert title="Feature Flag">
 
 This is a temporary measure until we fully migrate to the new Azure DevOps integration and remove references to the old one.
 
diff --git a/develop-docs/integrations/discord/index.mdx b/develop-docs/integrations/discord/index.mdx
index 4dc07cbad7f480..8b232664cb0fcf 100644
--- a/develop-docs/integrations/discord/index.mdx
+++ b/develop-docs/integrations/discord/index.mdx
@@ -47,7 +47,7 @@ Interactions Endpoint URL: {YOUR_DOMAIN}/extensions/discord/interactions/
 
 Click __Save Changes__.
 
-<Alert level="info">
+<Alert>
 When you enter the Interactions Endpoint URL, Discord will try to verify it. The verification will fail if you haven't configured the bot credentials properly, haven't restarted your server since adding them, or don't have your server properly exposed to the internet.
 </Alert>
 
diff --git a/develop-docs/integrations/github.mdx b/develop-docs/integrations/github.mdx
index 5d1bddf4a82daa..066c5eaddc1998 100644
--- a/develop-docs/integrations/github.mdx
+++ b/develop-docs/integrations/github.mdx
@@ -43,7 +43,7 @@ When prompted to subscribe to events, choose the following:
  - Pull Request
  - Push
 
-<Alert title="Trick" level="info">
+<Alert title="Trick">
   Enabling optional permissions will also enable the <Link to="/self-hosted/sso/#github-auth">GitHub SSO</Link> for your instance.
 </Alert>
 
@@ -62,7 +62,7 @@ github-app.client-secret: "GITHUB_CLIENT_SECRET"
 github-app.webhook-secret: "my-super-secret-example-secret"
 ```
 
-<Alert title="Invalid Application Name" level="info">
+<Alert title="Invalid Application Name">
   If you're receiving invalid application or application not found error, it's suggested to change the `github-app.name` to the correct application slug.
   This can occur if the application includes non-alphanumeric characters.
 </Alert>
diff --git a/develop-docs/integrations/jira/images/jira-setup1.5.png b/develop-docs/integrations/jira/images/jira-setup1.5.png
new file mode 100644
index 00000000000000..433c50bf10f905
Binary files /dev/null and b/develop-docs/integrations/jira/images/jira-setup1.5.png differ
diff --git a/develop-docs/integrations/jira/images/jira-setup1.png b/develop-docs/integrations/jira/images/jira-setup1.png
new file mode 100644
index 00000000000000..3451a188413ce3
Binary files /dev/null and b/develop-docs/integrations/jira/images/jira-setup1.png differ
diff --git a/develop-docs/integrations/jira/images/jira-setup2.png b/develop-docs/integrations/jira/images/jira-setup2.png
new file mode 100644
index 00000000000000..a3c8b20bb246f3
Binary files /dev/null and b/develop-docs/integrations/jira/images/jira-setup2.png differ
diff --git a/develop-docs/integrations/jira/images/jira-setup3.png b/develop-docs/integrations/jira/images/jira-setup3.png
new file mode 100644
index 00000000000000..9ed6d575c9b8d1
Binary files /dev/null and b/develop-docs/integrations/jira/images/jira-setup3.png differ
diff --git a/develop-docs/integrations/jira/images/jira-setup4.png b/develop-docs/integrations/jira/images/jira-setup4.png
new file mode 100644
index 00000000000000..582ab31f755485
Binary files /dev/null and b/develop-docs/integrations/jira/images/jira-setup4.png differ
diff --git a/develop-docs/integrations/jira/images/jira-setup5.png b/develop-docs/integrations/jira/images/jira-setup5.png
new file mode 100644
index 00000000000000..f43b0f1449adc8
Binary files /dev/null and b/develop-docs/integrations/jira/images/jira-setup5.png differ
diff --git a/develop-docs/integrations/jira/images/jira-setup6.png b/develop-docs/integrations/jira/images/jira-setup6.png
new file mode 100644
index 00000000000000..465e9754fe7386
Binary files /dev/null and b/develop-docs/integrations/jira/images/jira-setup6.png differ
diff --git a/develop-docs/integrations/jira/index.mdx b/develop-docs/integrations/jira/index.mdx
index 3b0ba8a94f465f..00b2b57e73b492 100644
--- a/develop-docs/integrations/jira/index.mdx
+++ b/develop-docs/integrations/jira/index.mdx
@@ -3,26 +3,46 @@ title: Jira Integration
 sidebar_title: Jira
 ---
 
-Create an [Atlassian Cloud Developer Instance](http://go.atlassian.com/cloud-dev)
+## Create an Atlassian Cloud Developer Instance
 
-Atlassian offers a development-specific org option, different from simply having a personal Jira organization. Even if you already have a personal Jira org, it's worth creating a development org, because it will correctly set a number of necessary options for you automatically.
+[Atlassian offers a development-specific org](http://go.atlassian.com/cloud-dev) option, different from simply having a personal Jira organization. Even if you already have a personal Jira org, it's worth creating a development org, because it will correctly set a number of necessary options for you automatically.
 
-Set Up ngrok
+### Permissions for Certain Features
 
-(This is only necessary if you're developing locally.) [Download](https://ngrok.com/download) and [set up](https://ngrok.com/docs/getting-started/) ngrok, then start an ngrok server.
+To enable issue-sync between Jira and a locally hosted Sentry Jira integration, you must set your email address permission to "Anyone". This setting can be found in the [Profile and visiblity](https://id.atlassian.com/manage-profile/profile-and-visibility) page under "Contact".
 
-Configure Jira Settings
+
+## Set Up ngrok
+
+[Download](https://ngrok.com/download) and [set up](https://ngrok.com/docs/getting-started/) ngrok, then start an ngrok server. If you are using getsentry devserver, follow our [ngrok guide](https://develop.sentry.dev/development-infrastructure/ngrok/).
+
+## Installing Local Jira App
 
 1. If you don't have any projects in your Jira org yet, create a new project.
-2. In the navigation bar at the top of the screen, go to Apps > Manage Your Apps.
-3. At the bottom of the Manage Apps page, click Settings (1).
-4. Select Enable Development Mode and Enable Private Listings (2), and click Apply.
+2. In the navigation bar at the top of the screen, click on the waffle icon (1), select the desired organization and click "Administration" (2).
+![Navigating to Administration](./images/jira-setup1.png)
+
+3. In the navigation bar, click "Products" (3) and under "Sites and products" (4) select the appropriate site/product with your Jira project.
+![Navigating to the Correct Site](./images/jira-setup1.5.png)
+
+4. In the sidebar on the left, click on "Connected apps" (5) and then click on the Settings tab (6).
+5. Click on the button labeled "Install a private app" (7).
+![Navigating to Connected Apps](./images/jira-setup2.png)
+
+6. In the new modal, select JIRA for the product to install the app on (8).
+7. For the "App descriptor URL" (9), use the following URL, `https://{YOUR_SENTRY_DOMAIN}/extensions/jira/descriptor/`.
+    * Note that if you are running a local devserver, `YOUR_SENTRY_DOMAIN` will be your ngrok (or other tunneling service) domain.
+    * For self-hosted Sentry users: Replace `https://{YOUR_SENTRY_DOMAIN}` with your Sentry address.
+![Filling out Modal](./images/jira-setup3.png)
 
-![Jira Settings](./configure-jira.png)
+8. Click "Install app" (10), now if you select the "Installed Apps" (11) tab next to "Settings", you should see your newly installed app listed under "Sentry" (12). (Note: that "Sentry for Jira" is the SaaS integration).
+9. On the right the newly installed app click on the three dots and then click "Manage" (13).
+![Navigating to App Listing](./images/jira-setup4.png)
 
-5. Reload the page, and Upload App should appear next to Build a New App.
-6. Click Upload App and upload the Atlassian Connect descriptor by using the URL  `https://{YOUR_SENTRY_DOMAIN}/extensions/jira/descriptor/`. Note that if you are running a local devserver, `YOUR_SENTRY_DOMAIN` will be your ngrok (or other tunneling service) domain.
+10. In the app listing, click on the three dots in the top right and click "Configure" (14).
+![Navigating to Configure App](./images/jira-setup5.png)
 
-![Upload Descriptor to Jira](./upload-descriptor.png)
+11. Click "Finish Installation in Sentry" and select the desired organization to install the Jira integration on.
+![Last step on Jira site](./images/jira-setup6.png)
 
-Follow our [documentation on installing and configuring the Jira integration](https://docs.sentry.io/product/integrations/issue-tracking/jira/) to use the integration.
+From here follow our [documentation on installing and configuring the Jira integration](https://docs.sentry.io/product/integrations/issue-tracking/jira/) to use the integration (For reference: We just completed the equivalent to Step 4 under that page's "Install" section).
diff --git a/develop-docs/integrations/msteams/index.mdx b/develop-docs/integrations/msteams/index.mdx
index de67410fe6980e..a7cec53cd18dd6 100644
--- a/develop-docs/integrations/msteams/index.mdx
+++ b/develop-docs/integrations/msteams/index.mdx
@@ -4,7 +4,7 @@ sidebar_title: Microsoft Teams
 ---
 
 
-<Alert title="Admin Privileges" level="info">
+<Alert title="Admin Privileges">
 
 You will need to be a Microsoft Teams Administrator to perform some of the required steps.
 
@@ -55,7 +55,7 @@ msteams.client-secret: 'your-bot-secret'
 
 ## Installation
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 We have encountered recent issues with this installation method. For a smoother experience, please refer to the Troubleshooting section for alternative steps.
 
diff --git a/develop-docs/integrations/pagerduty.mdx b/develop-docs/integrations/pagerduty.mdx
index 4286284a3e5c95..b265f056c57e78 100644
--- a/develop-docs/integrations/pagerduty.mdx
+++ b/develop-docs/integrations/pagerduty.mdx
@@ -42,6 +42,6 @@ pagerduty.app-id: 'PV5SD0T'
 
 Restart your Sentry instance and follow our [documentation on configuring the PagerDuty integration](https://docs.sentry.io/product/integrations/pagerduty/) to use the integration.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
     After changing configuration files, re-run the <code>./install.sh</code> script, to rebuild and restart the containers. See the <Link to="/self-hosted/#configuration">configuration section</Link> for more information.
 </Alert>
diff --git a/develop-docs/integrations/slack/index.mdx b/develop-docs/integrations/slack/index.mdx
index 34c2e942902389..37d8e8fb9166ee 100644
--- a/develop-docs/integrations/slack/index.mdx
+++ b/develop-docs/integrations/slack/index.mdx
@@ -27,7 +27,7 @@ If you're a Sentry employee, you can set the `slack.client-id` and `slack.client
 
 After you update the `config.yml`, `sentry.conf.py`, or `devlocal.py` you need to restart your Sentry server to continue configuring the Slack app.
 
-<Alert title="Note (for self-hosted users)" level="info">
+<Alert title="Note (for self-hosted users)">
     After changing configuration files, re-run the <code>./install.sh</code> script, to rebuild and restart the containers. See the <Link to="/self-hosted/#configuration">configuration section</Link> for more information.
 </Alert>
 
@@ -77,7 +77,7 @@ Add the following scopes to __User Scopes__:
 * `users:read`
 * `users:read.email`
 
-<Alert level="info">
+<Alert>
 You have the option to set 'Restrict API Token Usage' on this page if you want to limit use of your app’s OAuth tokens to a list of IP addresses and ranges you provide.
 </Alert>
 
@@ -87,7 +87,7 @@ You’ll see “Verified” when you’ve entered the correct URL.
 
 ![Events](./events.png)
 
-<Alert level="info">
+<Alert>
 When you enter the 'Request URL', Slack tries to verify it. The request will fail if you didn’t configure the client keys/secret and restart Sentry to ensure those config changes were picked up. If it fails to validate, first make sure your Sentry instance is running and Slack can talk to it (Slack <Link to="https://twitter.com/slackapi/status/567110311476350976?lang=en">doesn’t have an IP range</Link>).
 </Alert>
 
@@ -118,7 +118,7 @@ Navigate to __Slash Commands__ under __Features__. Click __Create New Command__
 | Request URL                     | `{YOUR_DOMAIN}/extensions/slack/commands/`    |
 
 
-<Alert title="Note" level="info">
+<Alert title="Note">
     When creating the slash command, don’t use `/sentry`. Do something like `/{your_name}-sentry`. If multiple apps are installed with the same slash command, the most recently installed one takes over.
 </Alert>
 
diff --git a/develop-docs/sdk/data-model/envelope-items.mdx b/develop-docs/sdk/data-model/envelope-items.mdx
index c5adff7fb6d2be..cb116ecf6713c1 100644
--- a/develop-docs/sdk/data-model/envelope-items.mdx
+++ b/develop-docs/sdk/data-model/envelope-items.mdx
@@ -260,8 +260,7 @@ Envelope.
 
 ### User Report - Deprecated
 
-Item type `"user_report"`. This is an older way of submitting user feedback we
-are have now deprecated. It continues to work so older SDKs won't break. But new implementation should follow the `feedback` item type described above.
+Item type `"user_report"`. This is an older, deprecated way of submitting user feedback. It continues to work so older SDKs won't break. New implementations should follow the `feedback` item type described above.
 
 This item works by associating user information and comments with an event. If both the item and its associated event are accepted, we convert it to a user feedback.
 
diff --git a/develop-docs/sdk/data-model/envelopes.mdx b/develop-docs/sdk/data-model/envelopes.mdx
index b8b7c4fd1bb1b4..1a7953ec29c100 100644
--- a/develop-docs/sdk/data-model/envelopes.mdx
+++ b/develop-docs/sdk/data-model/envelopes.mdx
@@ -7,7 +7,7 @@ This document defines the Envelope and Item formats used by Sentry for data
 ingestion, forwarding, and offline storage. The target audience of this document
 is Sentry SDK developers and maintainers of the ingestion pipeline.
 
-<Alert title="Backward Compatibility" level="info">
+<Alert title="Backward Compatibility">
 
 Envelopes require Relay, which has been introduced in **Sentry v20.6.0**.
 Earlier versions of Sentry do not support Envelopes and respond with HTTP error
@@ -134,7 +134,7 @@ Envelopes can have a number of headers which are valid in all situations:
   [RFC 3339](https://tools.ietf.org/html/rfc3339) format. Used for clock drift
   correction of the event timestamp. The time zone must be UTC.
 
-<Alert title="Implementation Guidance for the sent_at Header" level="info">
+<Alert title="Implementation Guidance for the sent_at Header">
 
 It is recommend to *always* send the `sent_at` envelope header. Do not try to determine
 whether it should be sent or not, as that determination can be made on the receiving side.
@@ -326,7 +326,7 @@ If multiple forms of authentication are given, the endpoint validates that the
 information matches and otherwise rejects the request. If both are missing, the
 Envelope is rejected with status code `403 Forbidden`.
 
-<Alert title="Backward Compatibility" level="info">
+<Alert title="Backward Compatibility">
 
 Envelope header authentication requires **Relay v21.6.0**.
 Earlier versions of Relay do not support Envelope header authentication and respond with HTTP error
diff --git a/develop-docs/sdk/data-model/event-payloads/breadcrumbs.mdx b/develop-docs/sdk/data-model/event-payloads/breadcrumbs.mdx
index 77f3c6e2a4bb94..8860d30021115d 100644
--- a/develop-docs/sdk/data-model/event-payloads/breadcrumbs.mdx
+++ b/develop-docs/sdk/data-model/event-payloads/breadcrumbs.mdx
@@ -100,7 +100,7 @@ Contains a dictionary whose contents depend on the breadcrumb type. Additional p
 : A timestamp representing when the breadcrumb occurred. The format is either a string as defined in [RFC 3339](https://tools.ietf.org/html/rfc3339) or a numeric (integer or float) value representing the number of seconds that have elapsed since the [Unixepoch](https://en.wikipedia.org/wiki/Unix_time).
 Breadcrumbs are most useful when they include a timestamp, as it creates a timeline leading up to an event `expection/error`.
 
-<Alert level="info">
+<Alert>
   Breadcrumbs will not be sorted by timestamp, they keep their order in the way they were added.
 </Alert>
 
diff --git a/develop-docs/sdk/data-model/event-payloads/debugmeta.mdx b/develop-docs/sdk/data-model/event-payloads/debugmeta.mdx
index 804eb9a5f13cf6..585dac02e65869 100644
--- a/develop-docs/sdk/data-model/event-payloads/debugmeta.mdx
+++ b/develop-docs/sdk/data-model/event-payloads/debugmeta.mdx
@@ -359,6 +359,12 @@ Proguard images refer to `mapping.txt` files generated when Proguard obfuscates
 function names. The Java SDK integrations assign this file a unique identifier,
 which has to be included in the list of images.
 
+Attributes:
+
+`type`
+
+: **Required**. Type of the debug image. Must be `"proguard"`.
+
 `uuid`
 
 : **Required**. The unique identifier assigned by the Java SDK.
@@ -367,6 +373,7 @@ Example:
 
 ```json
 {
+  "type": "proguard",
   "uuid": "395835f4-03e0-4436-80d3-136f0749a893"
 }
 ```
diff --git a/develop-docs/sdk/data-model/event-payloads/index.mdx b/develop-docs/sdk/data-model/event-payloads/index.mdx
index 447c7eef581c61..c604b71b87481f 100644
--- a/develop-docs/sdk/data-model/event-payloads/index.mdx
+++ b/develop-docs/sdk/data-model/event-payloads/index.mdx
@@ -10,7 +10,7 @@ Events are packed into [envelopes](/sdk/data-model/envelopes/) and are sent to t
 
 Sending event payloads to the `/api/{PROJECT_ID}/store/` API endpoint is deprecated.
 
-<Alert title="Note on backwards compatibility" level="info"><markdown>
+<Alert title="Note on backwards compatibility"><markdown>
 
 We strive to document the canonical format of an event and its additional
 interfaces. However, for backwards compatibility the server also
diff --git a/develop-docs/sdk/data-model/event-payloads/lockreason.mdx b/develop-docs/sdk/data-model/event-payloads/lockreason.mdx
index 0a63e1f36101f3..ae85f391235c5d 100644
--- a/develop-docs/sdk/data-model/event-payloads/lockreason.mdx
+++ b/develop-docs/sdk/data-model/event-payloads/lockreason.mdx
@@ -6,11 +6,11 @@ Represents an instance of a held lock (monitor object) in a thread. Typically, t
 to determine which other thread is holding the lock in case the current thread is blocked. In languages like
 `Java` or `Kotlin` this typically will be represented by a `java.lang.Object` type.
 
-<Note>
+<Alert>
 
 Lock reasons are always part of a [thread](/sdk/data-model/event-payloads/threads/). They cannot be declared as a top-level event property.
 
-</Note>
+</Alert>
 
 ## Attributes
 
diff --git a/develop-docs/sdk/data-model/event-payloads/stacktrace.mdx b/develop-docs/sdk/data-model/event-payloads/stacktrace.mdx
index 4841d310021f51..7990c3b5b77b67 100644
--- a/develop-docs/sdk/data-model/event-payloads/stacktrace.mdx
+++ b/develop-docs/sdk/data-model/event-payloads/stacktrace.mdx
@@ -7,7 +7,7 @@ A stack trace contains a list of frames, each with various bits (most optional)
 describing the context of that frame. Frames should be sorted from oldest to
 newest.
 
-<Note><markdown>
+<Alert>
 
 Stack traces are always part of an exception or a thread. They cannot be
 declared as a top-level event property. When adding a stack trace to an event,
@@ -16,7 +16,7 @@ follow this rule of thumb:
 - If the stack trace is part of an error, exception or crash, add it to the [Exception Interface](/sdk/data-model/event-payloads/exception/).
 - Otherwise, add it as a thread in the [Threads Interface](/sdk/data-model/event-payloads/threads/).
 
-</markdown></Note>
+</Alert>
 
 ## Attributes
 
diff --git a/develop-docs/sdk/data-model/event-payloads/transaction.mdx b/develop-docs/sdk/data-model/event-payloads/transaction.mdx
index fd88f1dec72d14..b7e40c39f03892 100644
--- a/develop-docs/sdk/data-model/event-payloads/transaction.mdx
+++ b/develop-docs/sdk/data-model/event-payloads/transaction.mdx
@@ -6,7 +6,7 @@ Transactions are used to send tracing events to Sentry.
 
 Transactions must be wrapped in an [Envelope](/sdk/data-model/envelopes/) and therefore also be sent to the Envelope endpoint.
 
-<Alert title="Note on backwards compatibility" level="info">
+<Alert title="Note on backwards compatibility">
   Envelopes are a new format and therefore only work on Sentry >= 10. More
   information can be found on the <Link to="/sdk/data-model/envelopes/">Envelope</Link> page.
 </Alert>
diff --git a/develop-docs/sdk/expected-features/setup-wizards/index.mdx b/develop-docs/sdk/expected-features/setup-wizards/index.mdx
index 32f0a63785074b..138dea175ec597 100644
--- a/develop-docs/sdk/expected-features/setup-wizards/index.mdx
+++ b/develop-docs/sdk/expected-features/setup-wizards/index.mdx
@@ -72,7 +72,7 @@ If not already specified via the `--url` param, wizards should ask if users are
 
 When creating a new wizard, the execution flow should roughly adhere to the outlined steps. Additional steps can be added as necessary.
 
-<Alert level="info">
+<Alert>
 
 Many of the individual steps and checks are already implemented in <Link to="#building-blocks-and-helper-functions">helper functions</Link>.
 
@@ -151,7 +151,7 @@ const continueWithoutGit = await abortIfCancelled(
 );
 ```
 
-<Alert level="info">
+<Alert>
 
 A lot of <Link to="https://github.com/getsentry/sentry-wizard/blob/master/src/utils/clack-utils.ts">helpers</Link> around specific user input questions can be reused.
 For example, the entire authentication and project selection flow is <Link to="https://github.com/getsentry/sentry-wizard/blob/master/src/utils/clack-utils.ts#L518">already covered</Link>.
diff --git a/develop-docs/sdk/miscellaneous/hub_and_scope_refactoring.mdx b/develop-docs/sdk/miscellaneous/hub_and_scope_refactoring.mdx
index 0f45a3b4457ad7..a86c4097331556 100644
--- a/develop-docs/sdk/miscellaneous/hub_and_scope_refactoring.mdx
+++ b/develop-docs/sdk/miscellaneous/hub_and_scope_refactoring.mdx
@@ -3,7 +3,7 @@ title: Hub & Scope Refactoring
 sidebar_order: 3
 ---
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 This is work in progress.
 
 Development has started in JS and Python, but we are still ironing out the wrinkles.
@@ -35,7 +35,7 @@ Hubs and scopes is a complicated system, that can easily be misused (also see [h
 2. The new Scopes API is implemented in the API and can be used.
 3. The old `Hub` based API still works as expected for backwards compatibility. After a transition phase the `Hub` will be removed in a major update of the SDK.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 The decision of removing the Hub from all Sentry SDKs was confirmed in a meeting on 2024-05-03 with most of the SDK engineers and Armin present. This decision is final.
 </Alert>
 
diff --git a/develop-docs/sdk/miscellaneous/unified-api/index.mdx b/develop-docs/sdk/miscellaneous/unified-api/index.mdx
index 5b8476a08e5c7b..d45db1da41e23e 100644
--- a/develop-docs/sdk/miscellaneous/unified-api/index.mdx
+++ b/develop-docs/sdk/miscellaneous/unified-api/index.mdx
@@ -7,7 +7,7 @@ sidebar_order: 1
 The unified API is deprecated. It served us well over the years, but we are in the process of simplifying the API by removing the Hub and also move some of our instrumentation to OpenTelementry.
 </Alert>
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 Everything written here sounds real nice. However, we live in a practical world, and expect each platform to adhere to what makese sense for the developers there. What is written below is not to be taken as strict rules. It is a guide and to be thought of as a tool to help developers build SDKs which work well which eachother.
 
diff --git a/develop-docs/sdk/overview.mdx b/develop-docs/sdk/overview.mdx
index 225693ce119a18..b660f65ccf556c 100644
--- a/develop-docs/sdk/overview.mdx
+++ b/develop-docs/sdk/overview.mdx
@@ -77,7 +77,7 @@ Sentry.init({
 })
 ```
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 SDKs should accept an empty DSN as valid configuration.
 
 If an SDK is not initialized or if it is initialized with an empty DSN, the SDK should not send any data over the network, such as captured exceptions.
@@ -168,7 +168,7 @@ The `sentry_secret` must only be included if a secret key portion was contained
 in the DSN.  Future versions of the protocol will fully deprecate the secret
 key.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 You should include the SDK version string in the User-Agent portion of the header, and it will be used if `sentry_client` is not sent in the auth header.
 </Alert>
 
@@ -320,7 +320,7 @@ The `X-Sentry-Error` header and response body will not always contain a message,
 but they can still be helpful in debugging clients. When emitted, they will
 contain a precise error message, which is useful to identify root cause.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 We do not recommend that SDKs retry event submissions automatically on error
 &nbsp; not even if `Retry-After` is declared in the response headers. If a
 request fails once, it is very likely to fail again on the next attempt.
diff --git a/develop-docs/sdk/platform-specifics/javascript-sdks/browser-tracing.mdx b/develop-docs/sdk/platform-specifics/javascript-sdks/browser-tracing.mdx
index b899f12ef00ebb..03f83997d94059 100644
--- a/develop-docs/sdk/platform-specifics/javascript-sdks/browser-tracing.mdx
+++ b/develop-docs/sdk/platform-specifics/javascript-sdks/browser-tracing.mdx
@@ -6,12 +6,12 @@ sidebar_order: 10
 
 The tracing behavior in our browser SDKs is somewhat unique and significantly differs from tracing in the backend. This page collects the most important aspects.
 
-<Note>
+<Alert>
   The aspects described in this document apply to all browser SDKs. This
   includes `@sentry/browser` and all SDKs building on top of it like
   `@sentry/react`, `@sentry/angular` or `@sentry/vue` but also the client-side
   parts of meta frameworks like `@sentry/nextjs`.
-</Note>
+</Alert>
 
 Please note that any kind of automatic tracing instrumentation in the browser requires the `browserTracingIntegration()` to be added to the SDK configuration.
 The default configuration of the SDK does not include any performance or tracing-related instrumentation to save on [bundle size](../bundle-size) for errors-only users.
@@ -103,13 +103,13 @@ There are sometimes discrepancies between the values we capture and the values t
 Generally speaking, most web vitals are accumulated while the pageload span is active and captured when we _end_ the pageload span. This works well for vitals that stabilize themselves very early in the lifecycle but
 it leads to discrepancies for vitals that are still changing after the pageload span ends. This is the case for `LCP` and `CLS` in particular.
 
-<Note>
+<Alert>
   At the time of writing, we're transitioning to a [more sophisticated `LCP` and
   `CLS` capturing
   technique](https://github.com/getsentry/sentry-javascript/issues/12714) that
   should improve the accuracy of these metrics. It will essentially work like
   `INP` collection works today.
-</Note>
+</Alert>
 
 ### Interaction To Next paint (INP)
 
@@ -134,13 +134,13 @@ This tracing model has a couple of consequences that are important to understand
 - **Quota Management**: Since the trace state does not change throughout a single page or route, the sampling decision of the initial span is carried over for all subsequent events. This means that the sampling decision is only made once per page or route and is not reevaluated for each event. Furthermore, subsequent http (`fetch` or `XmlHttpRequest`) also propagate this sampling decision to potential downstream services. This can lead to a higher number of events being sent to Sentry than before.
 - **Long-lived Traces**: Not every web application features navigations (hard or soft). For pages where users simply remain on one page without making navigations (e.g. a chat application), the trace id will remain constant for the entire duration of the user journey. This can lead to very long-lived traces that can potentially grow very large.
 
-<Note>
+<Alert>
 
 As outlined above, some of the consequences have negative product or UX implications.
 This is a known issue and we're working on an update to the trace lifetime model to address these issues.
 However, this is a complex topic and we're still in the process of evaluating the best solution.
 
-</Note>
+</Alert>
 
 ## Trace Propagation
 
diff --git a/develop-docs/sdk/telemetry/check-ins.mdx b/develop-docs/sdk/telemetry/check-ins.mdx
index 5fecd7afbb732f..8f5862670c34b2 100644
--- a/develop-docs/sdk/telemetry/check-ins.mdx
+++ b/develop-docs/sdk/telemetry/check-ins.mdx
@@ -135,10 +135,10 @@ result in a poor DX.
 
 ### Schedule configuration
 
-<Note>
+<Alert>
 This configuration format differs slightly from what is accepted in the
 monitors frontend APIs.
-</Note>
+</Alert>
 
 `type`
 
diff --git a/develop-docs/sdk/telemetry/profiles/sample-format-v1.mdx b/develop-docs/sdk/telemetry/profiles/sample-format-v1.mdx
index fddbbf7b2afdf8..cf6aeded675e82 100644
--- a/develop-docs/sdk/telemetry/profiles/sample-format-v1.mdx
+++ b/develop-docs/sdk/telemetry/profiles/sample-format-v1.mdx
@@ -295,15 +295,15 @@ stack ID.
 You should collect samples at a frequency of 101Hz, or roughly once every 10
 milliseconds.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 The 101Hz number above is not a typo. It is intentionally slightly off from 100Hz to avoid a condition
 named "lockstep sampling" where the profiling samples occur at the same frequency as a loop in the
 application. Ideally, the samples should be much more frequent than any cycles in the application, or
 at random intervals, so that the chance it occurs in any particular operation is proportional to the
 amount of time that operation takes. But this is often not feasible, so the next best thing is to use
-a sampling rate that doesn't coincide with the likely frequency of program cycles. 
+a sampling rate that doesn't coincide with the likely frequency of program cycles.
 
-We also chose 101 for its primality, whereas 1 below 100–99–is evenly divisible by several 
+We also chose 101 for its primality, whereas 1 below 100–99–is evenly divisible by several
 smaller numbers, which could lead to similar lockstep behavior.
 
 This explanation is an excerpt from [this awesome StackOverflow answer](https://stackoverflow.com/a/45471031/1181370)
diff --git a/develop-docs/sdk/telemetry/scopes.mdx b/develop-docs/sdk/telemetry/scopes.mdx
index 45e0cabc6f5fd4..1939ee6b432c17 100644
--- a/develop-docs/sdk/telemetry/scopes.mdx
+++ b/develop-docs/sdk/telemetry/scopes.mdx
@@ -2,7 +2,7 @@
 title: Scopes
 ---
 
-<Alert level="info">
+<Alert>
   This document uses key words such as "MUST", "SHOULD", and "MAY" as defined in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt) to indicate requirement levels.
 </Alert>
 
diff --git a/develop-docs/sdk/telemetry/sessions/index.mdx b/develop-docs/sdk/telemetry/sessions/index.mdx
index 106b65955ed308..f5e498cba515be 100644
--- a/develop-docs/sdk/telemetry/sessions/index.mdx
+++ b/develop-docs/sdk/telemetry/sessions/index.mdx
@@ -3,11 +3,11 @@ title: Sessions
 sidebar_order: 6
 ---
 
-<Note>
+<Alert>
 
 Looking for Sentry's **Session Replay**? Click <a class href="https://docs.sentry.io/product/session-replay/">here</a> to learn more.
 
-</Note>
+</Alert>
 
 For basic health tracking Sentry accepts <Link to="/sdk/data-model/envelopes/">envelopes</Link>
 containing session update events. These session update events can be used to
@@ -455,7 +455,7 @@ The most basic API exposed is on the hub level and lets you start and stop sessi
 
 ## SDK Implementation Guideline
 
-<Alert title="WIP" level="info">
+<Alert title="WIP">
   Before jumping into implementing this feature in an SDK, please reach out to
   the team. https://github.com/getsentry/develop/pull/323
 </Alert>
diff --git a/develop-docs/sdk/telemetry/spans/filtering.mdx b/develop-docs/sdk/telemetry/spans/filtering.mdx
index 5ef9a8d6223efe..cb7ba442d775e5 100644
--- a/develop-docs/sdk/telemetry/spans/filtering.mdx
+++ b/develop-docs/sdk/telemetry/spans/filtering.mdx
@@ -6,7 +6,7 @@ title: Filtering
   🚧 This document is work in progress.
 </Alert>
 
-<Alert level="info">
+<Alert>
   This document uses key words such as "MUST", "SHOULD", and "MAY" as defined in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt) to indicate requirement levels.
 </Alert>
 
diff --git a/develop-docs/sdk/telemetry/spans/sampling.mdx b/develop-docs/sdk/telemetry/spans/sampling.mdx
index 2344c7ab8fc699..69a86f37315a49 100644
--- a/develop-docs/sdk/telemetry/spans/sampling.mdx
+++ b/develop-docs/sdk/telemetry/spans/sampling.mdx
@@ -6,7 +6,7 @@ title: Sampling
   🚧 This document is work in progress.
 </Alert>
 
-<Alert level="info">
+<Alert>
   This document uses key words such as "MUST", "SHOULD", and "MAY" as defined in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt) to indicate requirement levels.
 </Alert>
 
diff --git a/develop-docs/sdk/telemetry/spans/scrubbing-data.mdx b/develop-docs/sdk/telemetry/spans/scrubbing-data.mdx
index cdc032c663cd24..6d042e32873377 100644
--- a/develop-docs/sdk/telemetry/spans/scrubbing-data.mdx
+++ b/develop-docs/sdk/telemetry/spans/scrubbing-data.mdx
@@ -6,7 +6,7 @@ title: Scrubbing data
   🚧 This document is work in progress.
 </Alert>
 
-<Alert level="info">
+<Alert>
   This document uses key words such as "MUST", "SHOULD", and "MAY" as defined in [RFC 2119](https://www.ietf.org/rfc/rfc2119.txt) to indicate requirement levels.
 </Alert>
 
diff --git a/develop-docs/sdk/telemetry/traces/dynamic-sampling-context.mdx b/develop-docs/sdk/telemetry/traces/dynamic-sampling-context.mdx
index 540ed01c3f9af2..d563793fa1db93 100644
--- a/develop-docs/sdk/telemetry/traces/dynamic-sampling-context.mdx
+++ b/develop-docs/sdk/telemetry/traces/dynamic-sampling-context.mdx
@@ -134,7 +134,7 @@ The `sentry-` prefix allows SDKs to put all of the sentry key-value pairs from t
 Being able to simply copy key-value pairs from the `baggage` header onto the `trace` envelope header gives us the flexibility to provide dedicated API methods to propagate additional values using Dynamic Sampling Context.
 This, in return, allows users to define their own values in the Dynamic Sampling Context so they can sample by those in the Sentry interface.
 
-<Alert level="info">
+<Alert>
 
 #### Note on `baggage` headers from other vendors
 
diff --git a/develop-docs/sdk/telemetry/traces/index.mdx b/develop-docs/sdk/telemetry/traces/index.mdx
index 73b98aae306d5f..619fbf94483d55 100644
--- a/develop-docs/sdk/telemetry/traces/index.mdx
+++ b/develop-docs/sdk/telemetry/traces/index.mdx
@@ -14,11 +14,11 @@ Reference implementations:
 - [JavaScript SDK](https://github.com/getsentry/sentry-javascript/tree/master/packages/core/src/tracing)
 - [Python SDK](https://github.com/getsentry/sentry-python/blob/master/sentry_sdk/tracing.py)
 
-<Note>
+<Alert>
 
 This document uses standard interval notation, where `[` and `]` indicates closed intervals, which include the endpoints of the interval, while `(` and `)` indicates open intervals, which exclude the endpoints of the interval. An interval `[x, y)` covers all values starting from `x` up to but excluding `y`.
 
-</Note>
+</Alert>
 
 ## SDK Configuration
 
@@ -66,7 +66,7 @@ URLs matching: 'localhost:8443/api/users', 'mylocalhost:8080/api/users', '/api/e
 URLs not matching: 'someHost.com/data', 'myApi.com/v1/projects'
 ```
 
-<Alert level="info" title="Deprecation of tracingOrigins">
+<Alert title="Deprecation of tracingOrigins">
 
 This Option replaces the non-standardized `tracingOrigins` option which was previously used in some SDKs. SDKs that support `tracingOrigins` are encouraged to deprecate and and eventually remove `tracingOrigins` in favour `tracePropagationTargets`. In case both options are specified by users, SDKs should only rely on the `tracePropagationTargets` array.
 
@@ -201,7 +201,7 @@ If more than one option could apply, the following rules determine which takes p
 3. If `tracesSampler` is not defined, but there's a parent sampling decision, the parent sampling decision will be used.
 4. If `tracesSampler` is not defined and there's no parent sampling decision, `tracesSampleRate` will be used.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 <markdown>
 
 Transactions should be sampled only by `tracesSampleRate` or `tracesSampler`. The `sampleRate` configuration is used for error events and should not apply to transactions.
diff --git a/develop-docs/sdk/telemetry/traces/span-operations.mdx b/develop-docs/sdk/telemetry/traces/span-operations.mdx
index 66b57ee6c49675..37c1566ebb88d7 100644
--- a/develop-docs/sdk/telemetry/traces/span-operations.mdx
+++ b/develop-docs/sdk/telemetry/traces/span-operations.mdx
@@ -8,7 +8,7 @@ Operations are expected to follow [OpenTelemetry's semantic conventions](https:/
 
 It's important to keep categories consistent between SDKs and integrations as they are used by Sentry in various parts of the platform. For example, both `db.init` and `db.query` will be categorized as database operations (`db`). The default operations breakdown config can be seen [here](https://github.com/getsentry/sentry/blob/9f36200d665209c9328f5ccc21135d3de9b65318/src/sentry/projectoptions/defaults.py#L80).
 
-<Alert title="Note" level="info">
+<Alert title="Note">
   Span operations should be lower case and use snake_case
 </Alert>
 
diff --git a/develop-docs/self-hosted/backup.mdx b/develop-docs/self-hosted/backup.mdx
index b966a15ef210fc..e4ce9af057db42 100644
--- a/develop-docs/self-hosted/backup.mdx
+++ b/develop-docs/self-hosted/backup.mdx
@@ -52,7 +52,7 @@ docker compose run -v $(pwd)/sentry:/sentry-data/backup  --rm -T -e SENTRY_LOG_L
 ./scripts/backup.sh [user | organization | config | global]
 ```
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 <markdown>
 
 If you choose to backup using the `docker compose run ...` command, omitting the `-T` or `-e
@@ -185,7 +185,7 @@ data are already defined as global volumes at install time and are prefixed with
 - `sentry-clickhouse`
 - `sentry-symbolicator`
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 Only backing up and restoring these volumes should bring back all persisted data. If you also need
 to back up in-flight data, we recommend backing up any project-specific volumes that <code>docker
diff --git a/develop-docs/self-hosted/custom-ca-roots.mdx b/develop-docs/self-hosted/custom-ca-roots.mdx
index 2103b42fd20bfd..bbe6674155f729 100644
--- a/develop-docs/self-hosted/custom-ca-roots.mdx
+++ b/develop-docs/self-hosted/custom-ca-roots.mdx
@@ -7,7 +7,7 @@ description: Add custom Certificate Authority (CA) root certificates to your sel
 
 Starting with Sentry `21.8.0`, if you need to have Sentry access services which do not have TLS certificates from publicly trusted CA roots, it's now possible to easily add them to the containers. Just add the certificates to the `certificates` folder inside the root of your Sentry install and restart the containers. Your custom CA roots will be used in addition to the publicly trusted CA roots.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
   While you can run <a href="https://manpages.debian.org/buster/ca-certificates/update-ca-certificates.8.en.html"><code>update-ca-certificates</code></a> in each container, that will update the system's root bundle on disk, but does nothing for any copies in memory. Restarting the container will update the bundle and make sure it is used.
 </Alert>
 
diff --git a/develop-docs/self-hosted/email.mdx b/develop-docs/self-hosted/email.mdx
index eda9d4c8f8461b..e84fe5303a61e8 100644
--- a/develop-docs/self-hosted/email.mdx
+++ b/develop-docs/self-hosted/email.mdx
@@ -5,7 +5,7 @@ sidebar_order: 40
 description: Set up and configure email notifications for your self-hosted Sentry instance
 ---
 
-<Alert title="Note" level="info">
+<Alert title="Note">
     After changing configuration files, re-run the <code>./install.sh</code> script, to rebuild and restart the containers. See the <Link to="/self-hosted/#configuration">configuration section</Link> for more information.
 </Alert>
 
diff --git a/develop-docs/self-hosted/experimental/external-storage.mdx b/develop-docs/self-hosted/experimental/external-storage.mdx
index 64ba4dbe3ff1a7..a107f42653a381 100644
--- a/develop-docs/self-hosted/experimental/external-storage.mdx
+++ b/develop-docs/self-hosted/experimental/external-storage.mdx
@@ -9,7 +9,7 @@ In some cases, storing Sentry data on-disk is not really something people can do
 <Alert title="Important" level="warning">
     These are community-contributed docs. Sentry does not officially provide support for self-hosted configurations beyond the default install.
 </Alert>
-<Alert title="Note" level="info">
+<Alert title="Note">
     After changing configuration files, re-run the <code>./install.sh</code> script, to rebuild and restart the containers. See the <Link to="/self-hosted/#configuration">configuration section</Link> for more information.
 </Alert>
 
diff --git a/develop-docs/self-hosted/index.mdx b/develop-docs/self-hosted/index.mdx
index 77275d669f62b5..f70a624188c26d 100644
--- a/develop-docs/self-hosted/index.mdx
+++ b/develop-docs/self-hosted/index.mdx
@@ -121,7 +121,7 @@ By default Sentry sends anonymous usage statistics to the Sentry team. It helps
 
 To apply new Docker daemon configuration, restart your Docker service with `systemctl restart docker.service`.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
   The value `172.17.0.0/16` is the default IP pools for Docker. If you are customizing your Docker default IP pools, please modify the value accordingly.
   Further information regarding Docker default IP pools can be found on the [Troubleshooting guide](/self-hosted/troubleshooting/docker/#docker-network-conflicting-ip-address).
 </Alert>
@@ -148,7 +148,7 @@ You very likely will want to adjust the default configuration for your Sentry in
 
 You can find more about configuring Sentry at [the configuration section of our developer documentation](/config/).
 
-<Alert title="Note" level="info">
+<Alert title="Note">
   Once you change your configuration, it's highly recommended to re-run <code>./install.sh</code> script rather than restarting all services using <code>docker compose restart</code>. This ensures no other configuration or migrations that might be missing when something is toggled on.
 </Alert>
 
diff --git a/develop-docs/self-hosted/releases.mdx b/develop-docs/self-hosted/releases.mdx
index e5ff5454bfc981..95c807a377ec2f 100644
--- a/develop-docs/self-hosted/releases.mdx
+++ b/develop-docs/self-hosted/releases.mdx
@@ -7,7 +7,7 @@ description: Learn how to upgrade your self-hosted Sentry installation and stay
 
 Sentry cuts regular releases for self-hosting to keep it as close to [sentry.io](https://sentry.io) as possible. We decided to follow a monthly release schedule using the [CalVer](https://calver.org/#scheme) versioning scheme, with a primary release on the [15th of each month](https://github.com/getsentry/self-hosted/blob/704e4c3b5b7360080f79bcfbe26583e5a95ae675/.github/workflows/release.yml#L20-L24). We don't patch old versions, but if a bug is bad enough we may cut an out-of-cycle point release, which, like our regular monthly releases, is a snapshot of the latest versions of all of our components. You can find the [latest release](https://github.com/getsentry/self-hosted/releases/latest) over at the [releases section of our self-hosted repository](https://github.com/getsentry/self-hosted/releases/).
 
-<Alert title="Why CalVer?" level="info">
+<Alert title="Why CalVer?">
   In short, this is to keep the self-hosted Sentry as close to the live version
   hosted at <Link to="https://sentry.io">sentry.io</Link>. There are more details for the
   curious over at our <Link to="https://blog.sentry.io/2020/06/22/self-hosted-sentry-switching-to-calver">blog post announcing the switch</Link>.
diff --git a/develop-docs/self-hosted/sso.mdx b/develop-docs/self-hosted/sso.mdx
index a4fe79864dbd2e..38807a7dd2ecaa 100644
--- a/develop-docs/self-hosted/sso.mdx
+++ b/develop-docs/self-hosted/sso.mdx
@@ -24,7 +24,7 @@ Please refer to our [main SAML documentation](https://docs.sentry.io/accounts/ss
 
 ## SSO with OAuth
 
-<Alert title="Note" level="info">
+<Alert title="Note">
     Once you enable SSO, this will be the only way to login to your self-hosted instance. If you need free registration along with SSO, you can comment on the <Link to="https://github.com/getsentry/sentry/pull/16247">GitHub PR</Link> for this.
 </Alert>
 
@@ -37,7 +37,7 @@ auth-google.client-id: '<client id>'
 auth-google.client-secret: '<client secret>'
 ```
 
-<Alert title="Note" level="info">
+<Alert title="Note">
     After changing configuration files, re-run the <code>./install.sh</code> script, to rebuild and restart the containers. See the <Link to="/self-hosted/#configuration">configuration section</Link> for more information.
 </Alert>
 
@@ -121,7 +121,7 @@ github-login.client-secret: '<Client secret>'
 
 This will also enable the [GitHub Integration](/integrations/github/) for your instance.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
     After changing configuration files, re-run the <code>./install.sh</code> script, to rebuild and restart the containers. See the <Link to="/self-hosted/#configuration">configuration section</Link> for more information.
 </Alert>
 
diff --git a/develop-docs/self-hosted/support.mdx b/develop-docs/self-hosted/support.mdx
index 9840907b8a1aaf..37b615980e9a64 100644
--- a/develop-docs/self-hosted/support.mdx
+++ b/develop-docs/self-hosted/support.mdx
@@ -7,7 +7,7 @@ sidebar_order: 8000
 We strive to provide a great self-hosted experience for folks willing to try Sentry that way. The [self-hosted repository](https://github.com/getsentry/self-hosted) is geared towards low traffic loads (less than ~1 million submitted Sentry events per month). We believe keeping this setup simple is important to show
 how various components fit together. Folks needing larger setups can expand from here based on their specific needs and environments.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 Please see our <Link to="/self-hosted/troubleshooting/">troubleshooting section</Link> before posting on the forum or filing an issue.
 </Alert>
 
diff --git a/develop-docs/self-hosted/troubleshooting/kafka.mdx b/develop-docs/self-hosted/troubleshooting/kafka.mdx
index 1e5e272aefbf98..e90934626d12bf 100644
--- a/develop-docs/self-hosted/troubleshooting/kafka.mdx
+++ b/develop-docs/self-hosted/troubleshooting/kafka.mdx
@@ -41,7 +41,7 @@ The _proper_ solution is as follows ([reported](https://github.com/getsentry/sel
    docker compose run --rm kafka kafka-consumer-groups --bootstrap-server kafka:9092 --group snuba-consumers --topic events --reset-offsets --to-latest --execute
    ```
 
-<Alert title="Tip" level="info">
+<Alert title="Tip">
 You can replace <code>snuba-consumers</code> with other consumer groups or <code>events</code> with other topics when needed.
 </Alert>
 
diff --git a/develop-docs/services/chartcuterie.mdx b/develop-docs/services/chartcuterie.mdx
index 1cb8e3da84dbeb..a9e30bdba3a57d 100644
--- a/develop-docs/services/chartcuterie.mdx
+++ b/develop-docs/services/chartcuterie.mdx
@@ -116,7 +116,7 @@ check that the chart-render.enabled key is correctly set to `true` (Use `sentry
 config get chart-rendering.enabled`).
 
 ```shell
-sentry devservices up chartcuterie
+devservices up --mode chartcuterie
 ```
 
 You can validate that the service has successfully started by checking the logs
diff --git a/docs/account/user-settings/index.mdx b/docs/account/user-settings/index.mdx
index 22be5378efe25c..be63470cef5ee8 100644
--- a/docs/account/user-settings/index.mdx
+++ b/docs/account/user-settings/index.mdx
@@ -14,11 +14,11 @@ Security Settings include options to reset a password, sign out of all devices,
 
 After setting up your two-factor authentication codes, click "View Codes" to download, print, or copy your codes to a secure location. If you cannot receive two-factor authentication codes in the future, such as if you lose your device, use your recovery codes to access your account.
 
-<Note>
+<Alert>
 
 Clicking "Sign out of all devices" will end your sessions with any device logged in to Sentry using your account.
 
-</Note>
+</Alert>
 
 ## Notifications
 
diff --git a/docs/api/auth.mdx b/docs/api/auth.mdx
index 952be7377a0b0f..1b71c1152824e6 100644
--- a/docs/api/auth.mdx
+++ b/docs/api/auth.mdx
@@ -51,8 +51,8 @@ As an example, to get information about the project which your key is bound to,
 curl -u {API_KEY}: https://sentry.io/api/0/organizations/{organization_slug}/projects/
 ```
 
-<Note>
+<Alert>
 
 You **must** pass a value for the password, which is the reason the `:` is present in our example.
 
-</Note>
+</Alert>
diff --git a/docs/api/ratelimits.mdx b/docs/api/ratelimits.mdx
index 19f7da9f5cc549..36a97199789fb9 100644
--- a/docs/api/ratelimits.mdx
+++ b/docs/api/ratelimits.mdx
@@ -32,8 +32,8 @@ Every API request response includes the following headers:
 
 The rate limiter looks at the caller's identity instead of the bearer token or cookie. As such, the rate limit cannot be bypassed by generating multiple tokens.
 
-<Note>
+<Alert>
 
 Polling the API for updates is likely to quickly trigger rate limiting. We recommend using our [webhooks](/organization/integrations/integration-platform/webhooks/), if possible.
 
-</Note>
+</Alert>
diff --git a/docs/cli/configuration.mdx b/docs/cli/configuration.mdx
index 60dc57eb7b1767..e372d57c545219 100644
--- a/docs/cli/configuration.mdx
+++ b/docs/cli/configuration.mdx
@@ -26,9 +26,9 @@ You can manually create an [Organization Auth Token](https://sentry.io/orgredire
 
 You can also sign in to your Sentry account (if you're not already) and create an Auth Token directly from this page.
 
-<Note>
+<Alert>
 Some CLI functionality, such as [Crons Monitoring](/product/crons/getting-started/cli/), is dependent on DSN authentication.
-</Note>
+</Alert>
 
 You can create an Auth Token from this page in one of the following three ways:
 
@@ -112,7 +112,7 @@ The header that will be added to every outgoing request in `key:value` format.
 
 `SENTRY_ALLOW_FAILURE`
 
-Note: This option will ignore the CLI's failure when uploading symbols. **BE AWARE** this will unblock your CI in case Sentry has issues, but you won't have unminified/unsymbolicated crashes in production. 
+Note: This option will ignore the CLI's failure when uploading symbols. **BE AWARE** this will unblock your CI in case Sentry has issues, but you won't have unminified/unsymbolicated crashes in production.
 When using this flag, you should download your sourcemaps/debug files from CI, to re-run the upload symbols command at a later point once Sentry is available.
 
 (_http.keepalive_):
diff --git a/docs/cli/crons.mdx b/docs/cli/crons.mdx
index b49bb88038a5fe..f31a1d21e1dc55 100644
--- a/docs/cli/crons.mdx
+++ b/docs/cli/crons.mdx
@@ -4,7 +4,7 @@ sidebar_order: 200
 description: "Follow this guide to set up and manage monitors using the Sentry CLI."
 ---
 
-<Alert level="note" title="Deprecation Notice">
+<Alert title="Deprecation Notice">
 
 Starting with v2.16.1 of the Sentry CLI, the ability to monitor check-ins using an auth token for authorization has been deprecated. Read on to learn how to update your CLI and use your project's DSN instead.
 
diff --git a/docs/cli/dif.mdx b/docs/cli/dif.mdx
index 29f306e589b63d..175cd4954c7797 100644
--- a/docs/cli/dif.mdx
+++ b/docs/cli/dif.mdx
@@ -13,12 +13,12 @@ information, refer to [_Debug Information Files_](/platforms/native/data-managem
 
 The `sentry-cli` requires an [Organization Auth Token](https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/) so that Debug Information Files can be uploaded.
 
-<Note>
+<Alert>
 
 Source maps, while also being debug information files, are handled
 differently in Sentry. For more information see [Source Maps in sentry-cli](/cli/releases/#sentry-cli-sourcemaps).
 
-</Note>
+</Alert>
 
 ## Checking Files
 
@@ -97,13 +97,13 @@ application. Alternatively, files can be uploaded during the build process. See
 [_Debug Information Files_](/platforms/native/data-management/debug-files/)
 for more information.
 
-<Note>
+<Alert>
 
 You need to specify the organization and project you are working with because
 debug information files work on projects. For more information about this refer
 to [Working with Projects](/cli/configuration/#sentry-cli-working-with-projects).
 
-</Note>
+</Alert>
 
 A basic debug file upload can be started with:
 
@@ -183,13 +183,13 @@ plugin](https://github.com/getsentry/sentry-android-gradle-plugin) to do that. N
 situations where you would upload ProGuard files manually. For instance,
 when you only release some of the builds you're creating.
 
-<Note>
+<Alert>
 
 You need to specify the organization and project you are working with
 because ProGuard files work on projects. For more information about this refer to
 [Working with Projects](/cli/configuration/#sentry-cli-working-with-projects).
 
-</Note>
+</Alert>
 
 The `upload-proguard` command is the one to use for uploading ProGuard files. It
 takes the path to one or more ProGuard mapping files and will upload them to
@@ -252,12 +252,12 @@ See the build tool plugins we currently support here:
 You can also upload ProGuard files manually with `sentry-cli` for any JVM-based language like
 Java or Kotlin.
 
-<Note>
+<Alert>
 
 Before you can upload source files, you must configure the Sentry CLI with the organization and project you are uploading bundle files for. See the CLI docs on
 [Working with Projects](/cli/configuration/#sentry-cli-working-with-projects) to learn how to do this.
 
-</Note>
+</Alert>
 
 ### Creating a Source Bundle
 
diff --git a/docs/cli/installation.mdx b/docs/cli/installation.mdx
index 9797f684037ef0..de9f079c466a09 100644
--- a/docs/cli/installation.mdx
+++ b/docs/cli/installation.mdx
@@ -61,11 +61,11 @@ In case you want to install this with npm system wide with sudo you will need to
 sudo npm install -g @sentry/cli --unsafe-perm
 ```
 
-<Note>
+<Alert>
 
 This installation is not recommended however.
 
-</Note>
+</Alert>
 
 ### Downloading From a Custom Source
 
diff --git a/docs/cli/releases.mdx b/docs/cli/releases.mdx
index 056996d2b75b2a..5bc554b53ef850 100644
--- a/docs/cli/releases.mdx
+++ b/docs/cli/releases.mdx
@@ -6,11 +6,11 @@ description: "Sentry's command line interface can be used for release management
 
 The `sentry-cli` tool can be used for release management on Sentry. It allows you to create, edit and delete releases as well as upload release artifacts for them. Note that releases are global per organization. If you want the releases in different projects to be treated as separate entities, make the version name unique across the organization. For example, if you have projectA and projectB that share version numbers, you can name the releases `projectA-1.0` and `projectB-1.0` respectively.
 
-<Note>
+<Alert>
 
 Because releases work on projects you will need to specify the organization and project you are working with. For more information about this refer to [Working with Projects](/cli/configuration/#sentry-cli-working-with-projects).
 
-</Note>
+</Alert>
 
 ## Creating Releases
 
diff --git a/docs/concepts/data-management/event-grouping/index.mdx b/docs/concepts/data-management/event-grouping/index.mdx
index eab51900c22acc..f20a993b1901a9 100644
--- a/docs/concepts/data-management/event-grouping/index.mdx
+++ b/docs/concepts/data-management/event-grouping/index.mdx
@@ -70,11 +70,11 @@ You can customize error grouping using a combination of the following options, l
 1. In your SDK, using [SDK Fingerprinting](/platform-redirect/?next=/usage/sdk-fingerprinting/)
    > Sets a new fingerprint for incoming events based on matchers in the SDK. This doesn't affect already existing issues. Note that is not supported in WebAssembly.
 
-<Note>
+<Alert>
 
 Stack trace rules can work as a combination of both SDK and project settings. As a result, we maintain the documentation in one location.
 
-</Note>
+</Alert>
 
 ## How to View the Fingerprint
 
diff --git a/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx b/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx
index 3b08813980124c..9e14754e52f50a 100644
--- a/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx
+++ b/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx
@@ -8,7 +8,7 @@ description: "Learn how to use stack trace rules to group incoming events based
 
 Stack trace rules improve issue tracking by ensuring accurate grouping and better classification of stack frames as in-app or system. This helps focus on relevant code, reduces noise, and minimizes false positives. By tailoring rules to your project, you can streamline debugging and maintain consistency across teams or multiple applications.
 
-When you set stack trace rules (previously known as _grouping enhancements_) for grouping in Sentry, they influence the data that's fed into the grouping algorithm. These rules can be configured on a per-project basis by going to your project settings and then clicking on "Issue Grouping". 
+When you set stack trace rules (previously known as _grouping enhancements_) for grouping in Sentry, they influence the data that's fed into the grouping algorithm. These rules can be configured on a per-project basis by going to your project settings and then clicking on "Issue Grouping".
 
 Here are a few things to note about stack trace rules:
 
@@ -16,14 +16,14 @@ Here are a few things to note about stack trace rules:
 - Rules consist of one or more match expressions followed by one or more actions triggered when all expressions match.
 - Rules are applied sequentially, from top to bottom, across all frames in the stack trace.
 
-In addition, the stack trace rules using the below matchers and actions can also be applied to incoming profiles to improve frame classification (in-app vs system, for example). 
+In addition, the stack trace rules using the below matchers and actions can also be applied to incoming profiles to improve frame classification (in-app vs system, for example).
 
 Allowed Matchers:
   * `stack.abs_path`
   * `stack.module`
   * `stack.function`
   * `stack.package`
-  
+
 Allowed Actions:
   * `+app`
   * `-app`
@@ -235,11 +235,11 @@ stack.function:std::*    -app
 stack.function:boost::*  -app
 ```
 
-<Note>
+<Alert>
 
 You need to force all frames to be in-app first because there might already have been some defaults set by the client SDK or earlier processing.
 
-</Note>
+</Alert>
 
 If you're using the `sentry-cocoa` SDK, you can also achieve the same result by marking other frames `not inApp`. The following sample marks functions from the classes `DataRequest` and `DownloadRequest` as `not inApp`.
 
diff --git a/docs/concepts/key-terms/dsn-explainer.mdx b/docs/concepts/key-terms/dsn-explainer.mdx
index 1abb06ae3bc7c9..4289f276b87f3d 100644
--- a/docs/concepts/key-terms/dsn-explainer.mdx
+++ b/docs/concepts/key-terms/dsn-explainer.mdx
@@ -48,8 +48,8 @@ Has the following settings:
 - Public Key = public
 - Project ID = 1
 
-<Note>
+<Alert>
 
 The secret part of the DSN is optional and effectively deprecated. While clients will still honor it, if supplied, future versions of Sentry will entirely ignore it.
 
-</Note>
+</Alert>
diff --git a/docs/concepts/key-terms/sample-rates.mdx b/docs/concepts/key-terms/sample-rates.mdx
index 61a5825650e013..a4a6eaa65d4be6 100644
--- a/docs/concepts/key-terms/sample-rates.mdx
+++ b/docs/concepts/key-terms/sample-rates.mdx
@@ -23,9 +23,9 @@ Choose a sampling rate that balances data accuracy with performance and storage
 
 ## Sampling Rate Options
 
-<Note>
+<Alert>
 Some of the options below aren't available in every SDK; check out our platform-specific docs for more info.
-</Note>
+</Alert>
 
 ### Error Events
 
diff --git a/docs/concepts/key-terms/tracing/distributed-tracing.mdx b/docs/concepts/key-terms/tracing/distributed-tracing.mdx
index 8c3edc97ef34cd..bd9b88fc4a745d 100644
--- a/docs/concepts/key-terms/tracing/distributed-tracing.mdx
+++ b/docs/concepts/key-terms/tracing/distributed-tracing.mdx
@@ -4,7 +4,7 @@ sidebar_order: 10
 description: With distributed tracing, you can track software performance and measure throughput & latency, while seeing the impact of errors across multiple systems.
 ---
 
-Distributed tracing provides a connected view of your application from frontend to backend. It helps track software performance, measure [metrics](/product/performance/metrics/) like throughput and latency, and display the impact of errors across multiple systems. This makes Sentry a more complete [performance monitoring](/product/performance/) solution, aiding in diagnosing problems and measuring your application's overall health. 
+Distributed tracing provides a connected view of your application from frontend to backend. It helps track software performance, measure [metrics](/product/performance/metrics/) like throughput and latency, and display the impact of errors across multiple systems. This makes Sentry a more complete [performance monitoring](/product/performance/) solution, aiding in diagnosing problems and measuring your application's overall health.
 
 [Tracing](/concepts/key-terms/tracing/distributed-tracing/) in Sentry provides insights such as:
 
@@ -36,11 +36,11 @@ Transactions share most properties (start and end time, tags, and so on) with th
 Before the transaction is sent, the `tags` and `data` properties will get merged with data from the global scope. (Global scope data is set in `Sentry.init()` or by using `Sentry.configureScope()`, `Sentry.setTag()`, `Sentry.setUser()`, or `Sentry.setExtra()`.)
 
 
-<Note>
+<Alert>
 
 Transaction names can contain **sensitive data**. See [Scrubbing Sensitive Data](/platforms/javascript/data-management/sensitive-data/#scrubbing-data) for more information.
 
-</Note>
+</Alert>
 
 #### Spans
 
diff --git a/docs/concepts/search/index.mdx b/docs/concepts/search/index.mdx
index 7aa946166ba94d..02df2924042fed 100644
--- a/docs/concepts/search/index.mdx
+++ b/docs/concepts/search/index.mdx
@@ -8,9 +8,9 @@ Search is available on several features throughout [sentry.io](https://sentry.io
 
 ## Query Syntax
 
-<Note>
+<Alert>
 You'll only need to use query syntax if you're using a Sentry [API](/api/). You'll get pre-populated suggestions once you start typing in your search terms when using the search bar anywhere in [Sentry.io](https://sentry.sentry.io/).
-</Note>
+</Alert>
 
 Search queries are constructed using a `key:value` pattern, with an optional raw search at the end. Each `key:value` pair is a `token` and the optional raw search is itself a single `token`. The `key:value` pair `tokens` are treated as issue or event properties. The optional raw search is treated as a single `token` and searches event titles/messages.
 
@@ -52,11 +52,11 @@ Here are some examples of valid comparison operator searches:
 
 ### Using `OR` and `AND`
 
-<Note>
+<Alert>
 
 `OR` and `AND` search conditions are only available for [Discover](/product/explore/discover-queries/), [Performance](/product/performance/), and [Metric Alerts](/product/alerts-notifications/metric-alerts/).
 
-</Note>
+</Alert>
 
 Use `OR` and `AND` between tokens, and use parentheses `()` to group conditions. `AND` can also be used between non-aggregates and aggregates. However, `OR` cannot.
 
diff --git a/docs/concepts/search/searchable-properties/events.mdx b/docs/concepts/search/searchable-properties/events.mdx
index 16df7fa9634337..e85a36e59e3815 100644
--- a/docs/concepts/search/searchable-properties/events.mdx
+++ b/docs/concepts/search/searchable-properties/events.mdx
@@ -14,11 +14,11 @@ You can search by event properties in the following [sentry.io](https://sentry.i
 - Issues - as indicated in the list below
 - Alerts - when creating a metric alert
 
-<Note>
+<Alert>
 
 Please note that in Alerts only a limited number of properties are available for [filtering transaction events](/product/alerts/create-alerts/metric-alert-config/#tags--properties).
 
-</Note>
+</Alert>
 
 When searching on event properties within the **Issues** page, the search will return any issue that has _one or more events_ matching the supplied event properties filter.
 
diff --git a/docs/concepts/search/searchable-properties/issues.mdx b/docs/concepts/search/searchable-properties/issues.mdx
index e7d11d91063a42..e281dd17367e39 100644
--- a/docs/concepts/search/searchable-properties/issues.mdx
+++ b/docs/concepts/search/searchable-properties/issues.mdx
@@ -10,9 +10,9 @@ sidebar_order: 10
 
 Below is a list of keys and tokens that can be used in the issues search.
 
-<Note>
+<Alert>
 You'll only need to use query syntax for **datetime** and **relative time** searchable property types if you're using the Sentry [API](/api/).
-</Note>
+</Alert>
 
 <DefinitionList>
 
diff --git a/docs/contributing/approach/product-docs/write-index.mdx b/docs/contributing/approach/product-docs/write-index.mdx
index bf9840b6d5e44b..2357ef533b8c33 100644
--- a/docs/contributing/approach/product-docs/write-index.mdx
+++ b/docs/contributing/approach/product-docs/write-index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 10
 
 This guide to writing index pages is just that—a guide. It won’t answer every question you have about how to write a good index page, but it will help you make a good start.
 
-<Note>
+<Alert>
 
 While we use the term “index page” to refer to the top-level page about a feature in Docs, we don’t use this terminology in the actual Docs. Learn more in [Other Guidelines](#other-guidelines).
 
-</Note>
+</Alert>
 
 The index page:
 
diff --git a/docs/contributing/approach/sdk-docs/write-getting-started.mdx b/docs/contributing/approach/sdk-docs/write-getting-started.mdx
index 4c3609226830c7..afa64c1fcc6f99 100644
--- a/docs/contributing/approach/sdk-docs/write-getting-started.mdx
+++ b/docs/contributing/approach/sdk-docs/write-getting-started.mdx
@@ -28,11 +28,11 @@ Explain the SDK at a high level in these two parts:
 1. An italicized sentence that explains what the SDK enables (errors, or errors and transactions)
 2. A brief paragraph that provides technical insight and the versions supported
 
-   <Note>
+   <Alert>
 
    If the primer content isn't developed, this fallback will display "_Sentry's SDKs enable automatic reporting of errors and exceptions_."
 
-   </Note>
+   </Alert>
 
 Add the primer content to this directory:
 
@@ -54,11 +54,11 @@ Add the configuration code sample to this directory:
 
 - [`/platform-includes/getting-started-config/`](https://github.com/getsentry/sentry-docs/tree/master/platform-includes/getting-started-config)
 
-<Note >
+<Alert>
 
 If the SDK supports performance monitoring, add it to the list that links back into the SDK content from Product, stored in [`/docs/product/performance/getting-started.mdx`](https://github.com/getsentry/sentry-docs/blob/master/docs/product/performance/getting-started.mdx).
 
-</Note >
+</Alert>
 
 ## Verification Code Sample
 
diff --git a/docs/contributing/pages/components.mdx b/docs/contributing/pages/components.mdx
index bed2e3289b9f17..a47b7636db76d9 100644
--- a/docs/contributing/pages/components.mdx
+++ b/docs/contributing/pages/components.mdx
@@ -8,24 +8,62 @@ sidebar_order: 40
 
 Render an alert callout.
 
-<Alert level="info" title="Important">
+<Alert title="Watch out!">
+This is an info alert. Use these for information that's critical to know; it's important for users to read, but won't cause a catastrophic problem if they don't read it. These include versions that introduce breaking changes or feature limitations. Use infrequently.
+</Alert>
 
-This is an alert
+<Alert level="warning" title="Important">
+This is a warning alert. Use these for items that MUST be well understood before proceeding. These highlight information that could cause users to make catastrophic errors that break their applications in ways that are very difficult to fix or create liabilities for them, such as information needed to avoid leaking PII. These should be used very rarely.
+</Alert>
 
+<Alert level="success" title="Tip">
+This is a success alert. Use these when.... TODO?
 </Alert>
 
-```markdown {tabTitle:Example}
-<Alert level="info" title="Important">
+<Alert>
+This is an alert without title.
+</Alert>
+
+<Alert>
+This is a multi-line alert without title.  Use these for information that's critical to know; it's important for users to read, but won't cause a catastrophic problem if they don't read it. These include versions that introduce breaking changes or feature limitations. Use infrequently.
+</Alert>
+
+<Alert title="List">
+<ul>
+<li>Item 1</li>
+<li>Item 2</li>
+</ul>
+</Alert>
+
+
+```markdown {tabTitle:Info}
+<Alert title="Watch out!">
+This is an info alert.
+</Alert>
+```
 
-This is an alert
+```markdown {tabTitle:Warning}
+<Alert level="warning" title="Important">
+This is a warning alert.
+</Alert>
+```
 
+```markdown {tabTitle:Success}
+<Alert level="success" title="Tip">
+This is a success alert.
+</Alert>
+```
+
+```markdown {tabTitle:No Title}
+<Alert>
+This is an alert without title.
 </Alert>
 ```
 
 Attributes:
 
-- `title` (string)
-- `level` (string: `'info' | 'warning' | 'danger' | 'success'`)
+- `title` (string) - optional
+- `level` (string: `'info' | 'warning' | 'success') - optional, defaults to `'info'`
 
 Use this for these types of content:
 
@@ -34,9 +72,7 @@ Use this for these types of content:
 - **Warning:** Use these for items that MUST be well understood before proceeding. These highlight information that could cause users to make catastrophic errors that break their applications in ways that are very difficult to fix or create liabilities for them, such as information needed to avoid leaking PII. These should be used very rarely.
   - Use with the title "Important"; do not use the title "Warning"
 
-An Alert component with no level setting will render as a Note component.
-
-See also the [Note component](#note).
+You can also omit the title of the alert.
 
 ## Arcade embeds
 
@@ -56,12 +92,36 @@ Render an expandable section.
 
 <Expandable title="This is a title">This is some content</Expandable>
 
+<Expandable permalink title="With Permalink">This is some content</Expandable>
+
+<Expandable title="Warning" level="warning">This is some warning content</Expandable>
+
+<Expandable title="Success" level="success">This is some success content</Expandable>
+
 ```markdown {tabTitle:Example}
 <Expandable title="This is a title">
   This is some content
 </Expandable>
 ```
 
+```markdown {tabTitle:Permalink}
+<Expandable permalink title="With Permalink">
+  This is some content
+</Expandable>
+```
+
+```markdown {tabTitle:Warning}
+<Expandable level="warning" title="This is a title">
+  This is some content
+</Expandable>
+```
+
+```markdown {tabTitle:Success}
+<Expandable level="success" title="This is a title">
+  This is some content
+</Expandable>
+```
+
 Attributes:
 
 - `title` (string)
@@ -145,11 +205,11 @@ function foo() {
 
 Render a heading with a configuration key in the correctly cased format for a given platform.
 
-<Note>
+<Alert>
 
 If content is specified, it will automatically hide the content when the given `platform` is not selected in context.
 
-</Note>
+</Alert>
 
 ```markdown {tabTitle:Example}
 <ConfigKey name="send-default-pii" notSupported={["javascript"]}>
@@ -166,33 +226,6 @@ Attributes:
 - `supported` (string[])
 - `notSupported` (string[])
 
-## Note
-
-Render a note.
-
-<Note>
-
-Something important, but maybe not _that_ important.
-
-</Note>
-
-```markdown {tabTitle:Example}
-<Note>
-
-Something important, but maybe not _that_ important.
-
-</Note>
-```
-
-Use this for these types of content:
-
-- **Prerequisite(s):** Use these to list things that are required to finish. Place them prior to the procedure/process that follows so a user doesn't start and stop.
-- **Note:** to document information that's relevant to the topic, but isn't part of the larger point of the content. This might include a piece of information that should be highlighted, but isn't necessarily more important than other information. These include calling out early adopter features or providing clarification. Use sparingly.
-
-Don't use a title with this type of note.
-
-See also the [Alert component](#alert).
-
 ## PageGrid
 
 Render all `next_steps` of this document or default child pages, including their `description` if available.
diff --git a/docs/contributing/pages/images.mdx b/docs/contributing/pages/images.mdx
index df4a071b7cf030..2d9a6347a8f089 100644
--- a/docs/contributing/pages/images.mdx
+++ b/docs/contributing/pages/images.mdx
@@ -11,9 +11,9 @@ If an image is used in multiple places, it's best to put it in `includes/common-
 
 Alternatively, images can also be added to the `public` folder and referenced using their relative or full path within the folder. See [public images](#public-images)
 
-<Note>
+<Alert>
   Every image path that starts with `/` (instead of `./`) is considered to be in the `public` folder.
-</Note>
+</Alert>
 
 ### Examples
 
diff --git a/docs/contributing/pages/redirects.mdx b/docs/contributing/pages/redirects.mdx
index ebc01fdf4148f3..c3969ec2f5ecb3 100644
--- a/docs/contributing/pages/redirects.mdx
+++ b/docs/contributing/pages/redirects.mdx
@@ -13,9 +13,9 @@ There are two ways to add redirects in the Sentry docs:
 - [Add a New Redirect in `middleware.ts` (Recommended)](#add-a-new-redirect-in-middlewarets-recommended)
 - [Add a New Redirect in `redirects.js`](#example-redirect-in-redirectsjs)
 
-<Note>
+<Alert>
   Both files make the distinction between SDK docs (ie. end user docs) and developer docs.
-</Note>
+</Alert>
 
 Because Sentry has a limited number of `next.config.js` redirects, you should configure your redirects in `middleware.ts` whenever possible. You should only use `redirects.js` ie (`next.config.js`) if you need to use regular expressions and wildcard path segments in your redirects.
 
diff --git a/docs/contributing/platforms/index.mdx b/docs/contributing/platforms/index.mdx
index e2e54c65573a2b..ceb3ae6c2435d5 100644
--- a/docs/contributing/platforms/index.mdx
+++ b/docs/contributing/platforms/index.mdx
@@ -92,11 +92,11 @@ All of this content will be automatically duplicated within every guide. This le
 
 Sometimes a page may not make sense within the context of a given guide. To control this, you can use the `supported` and `notSupported` frontmatter on common pages in platforms.
 
-<Note>
+<Alert>
 
 Page visibility works similar to the supported/notSupported attributes in other platform components (such as `PlatformSection`).
 
-</Note>
+</Alert>
 
 For example, if you wanted to make hide the content for a platform by default, but enable it for a guide, you can do that like so:
 
diff --git a/docs/organization/authentication/sso/azure-sso.mdx b/docs/organization/authentication/sso/azure-sso.mdx
index 8aa49a1b9bfc6f..3865bf574c9cd7 100644
--- a/docs/organization/authentication/sso/azure-sso.mdx
+++ b/docs/organization/authentication/sso/azure-sso.mdx
@@ -80,11 +80,11 @@ If you change your organization slug, you'll need to make the same update in the
 
 ## SCIM Integration
 
-<Note>
+<Alert>
 
 This feature is only available if your organization is on a Business or Enterprise plan; it is not available on Trial plans.
 
-</Note>
+</Alert>
 
 <Alert level="warning">
 
@@ -133,8 +133,8 @@ As a result of these changes, users who are assigned will be sent an invitation
 
 You can use Use Group Provisioning to sync and assign groups in Azure; they will be reflected in Sentry teams.
 
-<Note>
+<Alert>
 
 Please see the [Microsoft AD tutorial](https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/sentry-provisioning-tutorial) for further documentation on Azure provisioning setup. If you are using a custom enterprise application, you **must** follow the instructions for only enabling attribute mappings that Sentry supports (Step 5).
 
-</Note>
+</Alert>
diff --git a/docs/organization/authentication/sso/index.mdx b/docs/organization/authentication/sso/index.mdx
index 0c31afe56f38a4..5f5263bfeb0421 100644
--- a/docs/organization/authentication/sso/index.mdx
+++ b/docs/organization/authentication/sso/index.mdx
@@ -34,7 +34,7 @@ Sessions last for [Django's default session length](https://docs.djangoproject.c
 
 Enabling the Google integration will ask you to authenticate against a Google Apps account. Once done, membership will be restricted to only members of the given Apps domain (i.e. `sentry.io`).
 
-<Alert level="info">
+<Alert>
 
 If you need to allow users across multiple domains to access your organization or change your Google domain, please contact our support team.
 
diff --git a/docs/organization/authentication/sso/okta-sso/okta-scim.mdx b/docs/organization/authentication/sso/okta-sso/okta-scim.mdx
index 84f0869be24c97..cc037e9c85d105 100644
--- a/docs/organization/authentication/sso/okta-sso/okta-scim.mdx
+++ b/docs/organization/authentication/sso/okta-sso/okta-scim.mdx
@@ -4,11 +4,11 @@ sidebar_order: 3
 description: "Set up Okta's SCIM Integration for Member and Team Provisioning"
 ---
 
-<Note>
+<Alert>
 
 This feature is only available if your organization is on a Business or Enterprise plan.
 
-</Note>
+</Alert>
 
 <Alert level="warning">
 
@@ -68,7 +68,7 @@ Once these changes have been made, newly assigned users will be sent an invitati
 
 You can use "Push Groups" to sync and assign groups in Okta; they'll be mirrored in Sentry teams.
 
-<Alert level="note">
+<Alert>
 
 If you use Okta to assign organization membership, you’ll be unable to make membership changes through Sentry and will need to continue using Okta. To remove these users, deprovision them in Okta.
 
@@ -116,13 +116,13 @@ Here's how to assign an organization-level role to an Okta group:
 - For security reasons, the "Owner" role cannot be provisioned through SCIM. However, you <i>can</i> deprovision users who have the "Owner" role in Sentry, but aren't provisioned through SCIM.
   - For self-hosted users with custom roles, this extends to any role with the `org:admin` permission
 
-<Alert level="note">
+<Alert>
 
 If a user is a member of multiple Okta groups, only the attributes set by the first group will be used.
 
 </Alert>
 
-<Alert level="note">
+<Alert>
 
 If you use Okta to assign organization-level roles, you’ll be unable to make membership changes through Sentry and will need to continue using Okta. To change a user's organization-level role, you will need to deprovision and then reprovision them with the new role.
 
diff --git a/docs/organization/getting-started/index.mdx b/docs/organization/getting-started/index.mdx
index c5cb26a80bce5b..896619b3f26bf5 100644
--- a/docs/organization/getting-started/index.mdx
+++ b/docs/organization/getting-started/index.mdx
@@ -81,11 +81,11 @@ For a list of all supported integrations, check out out our [full Integrations d
 
 You can set up automated issue management when you create alerts that route to [Azure DevOps](/organization/integrations/source-code-mgmt/azure-devops/#automatically) and [Jira](/organization/integrations/issue-tracking/jira/#automatically). External issues will be created for new Sentry issues on your behalf, and these issues will use the configured fields in your Azure DevOps or Jira workspace. For other issue tracking solutions, you can manually link Sentry issues.
 
-<Note>
+<Alert>
 
 Automatic issue management is available only if your organization is on a Business or Trial plan.
 
-</Note>
+</Alert>
 
 ## 4. Create Projects
 
diff --git a/docs/organization/integrations/cloud-monitoring/aws-lambda/index.mdx b/docs/organization/integrations/cloud-monitoring/aws-lambda/index.mdx
index 2a8be914d22f87..9c737ae060face 100644
--- a/docs/organization/integrations/cloud-monitoring/aws-lambda/index.mdx
+++ b/docs/organization/integrations/cloud-monitoring/aws-lambda/index.mdx
@@ -4,22 +4,22 @@ sidebar_order: 1
 description: "Learn more about Sentry's AWS Lambda integration and how you can automatically instrument your Node or Python Lambda functions with Sentry without changing your code."
 ---
 
-<Note>
+<Alert>
 
 This method of setting up Sentry in your Lambda functions only works if your Lambda functions are run in Node CommonJS (`require` syntax) or in Python.
 For all other setups, check out these docs for [Node](/platforms/javascript/guides/aws-lambda/) or [Python](/platforms/python/integrations/aws-lambda/) instead.
 
-</Note>
+</Alert>
 
 Connect Sentry to your AWS account to automatically add Sentry error and performance monitoring to your Node/Python Lambda functions.
 
 ## Install
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > AWS Lambda**.
 
@@ -49,11 +49,11 @@ Sentry owner, manager, or admin permissions are required to install this integra
 
    ![](./img/aws_account_2.png)
 
-<Note>
+<Alert>
 
 You need to create the CloudFormation stack only once per account, even when installing the integration in multiple regions. If you are setting up the integration in a second region, copy the externalId from the existing CloudFormation stack on the "Parameters" tab into the form shown above.
 
-</Note>
+</Alert>
 
 8. Select the Lambda functions to automatically add the Sentry layer and necessary environment variables when you **Finish Setup**. **Note:** You can enable or disable Sentry on Lambda functions after installation.
 
diff --git a/docs/organization/integrations/cloud-monitoring/cloudflare-workers/index.mdx b/docs/organization/integrations/cloud-monitoring/cloudflare-workers/index.mdx
index 382a4c2a4f5bb3..bdda1d71e46f48 100644
--- a/docs/organization/integrations/cloud-monitoring/cloudflare-workers/index.mdx
+++ b/docs/organization/integrations/cloud-monitoring/cloudflare-workers/index.mdx
@@ -10,11 +10,11 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Cloudflare Workers**
 
diff --git a/docs/organization/integrations/cloud-monitoring/gcp-cloud-run/index.mdx b/docs/organization/integrations/cloud-monitoring/gcp-cloud-run/index.mdx
index a7909cdb4fdd2c..7c7868fa6bd490 100644
--- a/docs/organization/integrations/cloud-monitoring/gcp-cloud-run/index.mdx
+++ b/docs/organization/integrations/cloud-monitoring/gcp-cloud-run/index.mdx
@@ -8,11 +8,11 @@ Cloud Run helps developers save time in building and deploying their application
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. [Create an account](https://sentry.io/signup/) (or [Login](https://sentry.io/auth/login/)) on Sentry
 
diff --git a/docs/organization/integrations/compliance/truto/index.mdx b/docs/organization/integrations/compliance/truto/index.mdx
index e3d6596a19fb43..7b492ad99bbcc0 100644
--- a/docs/organization/integrations/compliance/truto/index.mdx
+++ b/docs/organization/integrations/compliance/truto/index.mdx
@@ -8,11 +8,11 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry Owner, Manager, or Admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Truto**
 
diff --git a/docs/organization/integrations/compliance/vanta/index.mdx b/docs/organization/integrations/compliance/vanta/index.mdx
index 1d8a5211e4e0f9..9a8eb72b23b66b 100644
--- a/docs/organization/integrations/compliance/vanta/index.mdx
+++ b/docs/organization/integrations/compliance/vanta/index.mdx
@@ -8,11 +8,11 @@ Sentry's Vanta integration grants Vanta read-only access to verify that Sentry o
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Vanta**
 
diff --git a/docs/organization/integrations/data-visualization/amazon-sqs/index.mdx b/docs/organization/integrations/data-visualization/amazon-sqs/index.mdx
index 8d98716e5dc97f..9f3a0cef192132 100644
--- a/docs/organization/integrations/data-visualization/amazon-sqs/index.mdx
+++ b/docs/organization/integrations/data-visualization/amazon-sqs/index.mdx
@@ -10,11 +10,11 @@ This integration needs to be set up in each project for which you wish to use it
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 Navigate to **Settings > Integrations > Amazon SQS**
 
diff --git a/docs/organization/integrations/data-visualization/segment/index.mdx b/docs/organization/integrations/data-visualization/segment/index.mdx
index bd1cbbe7ec855b..082b9c455c8565 100644
--- a/docs/organization/integrations/data-visualization/segment/index.mdx
+++ b/docs/organization/integrations/data-visualization/segment/index.mdx
@@ -16,11 +16,11 @@ This integration needs to be set up in each project for which you wish to use it
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 Navigate to **Settings > Integrations > Segment**
 
diff --git a/docs/organization/integrations/data-visualization/splunk/index.mdx b/docs/organization/integrations/data-visualization/splunk/index.mdx
index 6c8dbc18472f51..c90c20fa1041d7 100644
--- a/docs/organization/integrations/data-visualization/splunk/index.mdx
+++ b/docs/organization/integrations/data-visualization/splunk/index.mdx
@@ -6,21 +6,21 @@ description: "Learn more about Sentry's Splunk integration, which allows you to
 
 Connect Splunk to Sentry with the [Data Forwarding](/concepts/data-management/data-forwarding/) feature.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This integration needs to be set up in each project for which you wish to use it. It is maintained and supported by the [Sentry community](https://open.sentry.io/).
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 Navigate to **Settings > Integrations > Splunk**
 
@@ -46,11 +46,11 @@ Change **All Tokens** to **Enabled**, and note the HTTP Port Number (`8088` by d
 
 ![Splunk global settings](./img/splunk-hec-global-settings.png)
 
-<Note>
+<Alert>
 
 If you’re running Splunk in a privileged environment, you may need to expose the HEC port.
 
-</Note>
+</Alert>
 
 ### Creating a Sentry Input
 
@@ -111,10 +111,10 @@ Once you’ve filled in the required fields, hit **Save Changes**:
 
 We’ll now begin forwarding all new events into your Splunk instance.
 
-<Note>
+<Alert>
 
 Sentry will internally limit the maximum number of events sent to your Splunk instance to 1000 per second.
 
-</Note>
+</Alert>
 
 ![Splunk page showing Sentry data](./img/splunk-search-sentry.png)
diff --git a/docs/organization/integrations/debugging/apigene/index.mdx b/docs/organization/integrations/debugging/apigene/index.mdx
index 8ae7eff29aa58a..bf243950b5b7e4 100644
--- a/docs/organization/integrations/debugging/apigene/index.mdx
+++ b/docs/organization/integrations/debugging/apigene/index.mdx
@@ -12,11 +12,11 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Apigene**
 
diff --git a/docs/organization/integrations/debugging/foamai/index.mdx b/docs/organization/integrations/debugging/foamai/index.mdx
index 2ca5a15b006c4a..13d0b742d77ae7 100644
--- a/docs/organization/integrations/debugging/foamai/index.mdx
+++ b/docs/organization/integrations/debugging/foamai/index.mdx
@@ -9,11 +9,11 @@ This integration is maintained and supported by Foam.ai. For more details, check
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Foam**
 
diff --git a/docs/organization/integrations/debugging/revisedev/index.mdx b/docs/organization/integrations/debugging/revisedev/index.mdx
index 4df4ba43f0a0d8..a59c329a39763a 100644
--- a/docs/organization/integrations/debugging/revisedev/index.mdx
+++ b/docs/organization/integrations/debugging/revisedev/index.mdx
@@ -11,11 +11,11 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Revise.dev**
 
diff --git a/docs/organization/integrations/debugging/rookout/index.mdx b/docs/organization/integrations/debugging/rookout/index.mdx
index 446a8eff64b503..51472f14d67a5d 100644
--- a/docs/organization/integrations/debugging/rookout/index.mdx
+++ b/docs/organization/integrations/debugging/rookout/index.mdx
@@ -10,13 +10,13 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
 Rookout **won't** work with self-hosted Sentry.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Rookout**
 
diff --git a/docs/organization/integrations/deployment/heroku/index.mdx b/docs/organization/integrations/deployment/heroku/index.mdx
index bc90faf51209b6..96fba91ac4f60b 100644
--- a/docs/organization/integrations/deployment/heroku/index.mdx
+++ b/docs/organization/integrations/deployment/heroku/index.mdx
@@ -18,11 +18,11 @@ Once done, you’ll be able to confirm that Sentry’s credentials are available
 heroku config:get SENTRY_DSN
 ```
 
-<Note>
+<Alert>
 
 If you’re not using the add-on, you can still bind the `SENTRY_DSN` environment variable which the SDK will automatically pick up.
 
-</Note>
+</Alert>
 
 ### Install the SDK
 
diff --git a/docs/organization/integrations/deployment/vercel/index.mdx b/docs/organization/integrations/deployment/vercel/index.mdx
index 17a9b460034644..905b4c6651f107 100644
--- a/docs/organization/integrations/deployment/vercel/index.mdx
+++ b/docs/organization/integrations/deployment/vercel/index.mdx
@@ -15,11 +15,11 @@ To learn more about using Sentry in your Next.js app, check out the [Next.js SDK
 
 ## Install
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Visit [https://vercel.com/integrations/sentry](https://vercel.com/integrations/sentry)
 
diff --git a/docs/organization/integrations/feature-flag/launchdarkly/index.mdx b/docs/organization/integrations/feature-flag/launchdarkly/index.mdx
index 1829324ff395ce..d714d215e2a54e 100644
--- a/docs/organization/integrations/feature-flag/launchdarkly/index.mdx
+++ b/docs/organization/integrations/feature-flag/launchdarkly/index.mdx
@@ -41,17 +41,17 @@ This integration is maintained and supported by the company that created it. For
 
 ### Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner or manager permissions are required to install this integration.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 The LaunchDarkly integration is only available to organizations with a Business or Enterprise plan.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > LaunchDarkly**
 
diff --git a/docs/organization/integrations/feature-flag/split/index.mdx b/docs/organization/integrations/feature-flag/split/index.mdx
index 8c6de468d477a8..1d2feefafe63bd 100644
--- a/docs/organization/integrations/feature-flag/split/index.mdx
+++ b/docs/organization/integrations/feature-flag/split/index.mdx
@@ -16,13 +16,13 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration. The Split integration is available only for organizations on the Business and Enterprise plans.
 
 Split **won't** work with self-hosted Sentry.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Split**
 
diff --git a/docs/organization/integrations/integration-platform/internal-integration.mdx b/docs/organization/integrations/integration-platform/internal-integration.mdx
index 76df2072577123..58d36a7a5fcfb2 100644
--- a/docs/organization/integrations/integration-platform/internal-integration.mdx
+++ b/docs/organization/integrations/integration-platform/internal-integration.mdx
@@ -4,11 +4,11 @@ sidebar_order: 2
 description: "Learn more about internal integrations, which are custom-made for your organization."
 ---
 
-<Note>
+<Alert>
 
 We've built an [example application](https://github.com/getsentry/integration-platform-example) to help you get started with building on Sentry's integration platform. Check it out for useful code snippets for adding these features in Python and TypeScript. See the [docs](/organization/integrations/integration-platform/#example-app) for more information.
 
-</Note>
+</Alert>
 
 Internal integrations are meant for custom integrations unique to your organization. They can also be as simple as an organization-wide token. Whether you are using just the API or all the integration platform features combined, internal integrations are for use within a single Sentry organization.
 
diff --git a/docs/organization/integrations/integration-platform/public-integration.mdx b/docs/organization/integrations/integration-platform/public-integration.mdx
index 13a9c873561be7..01168f231f5897 100644
--- a/docs/organization/integrations/integration-platform/public-integration.mdx
+++ b/docs/organization/integrations/integration-platform/public-integration.mdx
@@ -4,11 +4,11 @@ sidebar_order: 1
 description: "Learn more about public integrations, which are available to all Sentry users."
 ---
 
-<Note>
+<Alert>
 
 We've built an [example application](https://github.com/getsentry/integration-platform-example) to help you get started with building on Sentry's integration platform. Check it out for useful code snippets for adding these features in Python and TypeScript. See the [docs](/organization/integrations/integration-platform/#example-app) for more information.
 
-</Note>
+</Alert>
 
 Public integrations are for the "general public" of Sentry users. These start in an unpublished state for development purposes and can be submitted later for approval to publish. For more information, check out the [Publication section](#publication) of this page.
 
diff --git a/docs/organization/integrations/integration-platform/ui-components/index.mdx b/docs/organization/integrations/integration-platform/ui-components/index.mdx
index 703da3966b3aed..c498d51dfd6f4f 100644
--- a/docs/organization/integrations/integration-platform/ui-components/index.mdx
+++ b/docs/organization/integrations/integration-platform/ui-components/index.mdx
@@ -4,11 +4,11 @@ sidebar_order: 4
 description: "Learn more about Sentry's integration platform User Interface (UI) components."
 ---
 
-<Note>
+<Alert>
 
 We've built an [example application](https://github.com/getsentry/integration-platform-example) to help you get started with building on Sentry's integration platform! Check it out for useful code snippets for adding these features in Python and TypeScript. See the [docs](/organization/integrations/integration-platform/#example-app) for more information.
 
-</Note>
+</Alert>
 
 The Sentry integration platform provides developers with the ability to define components to render within specific parts of [sentry.io](https://sentry.io), through a JSON-based schema.
 
diff --git a/docs/organization/integrations/integration-platform/webhooks.mdx b/docs/organization/integrations/integration-platform/webhooks.mdx
index 7f42ce882da474..8f271e83efaa83 100644
--- a/docs/organization/integrations/integration-platform/webhooks.mdx
+++ b/docs/organization/integrations/integration-platform/webhooks.mdx
@@ -4,11 +4,11 @@ sidebar_order: 3
 description: "Learn more about Sentry's integration platform webhooks and how they allow your service to receive requests about specific resources, such as installation, issues, and alerts."
 ---
 
-<Note>
+<Alert>
 
 We've built an [example application](https://github.com/getsentry/integration-platform-example) to help you get started with building on Sentry's integration platform. Check it out for useful code snippets for adding these features in Python and TypeScript. See the [docs](/organization/integrations/integration-platform/#example-app) for more information.
 
-</Note>
+</Alert>
 
 Webhooks are a way for two applications or services to communicate over the web, allowing one application to send automatic notifications or data updates to another in near real-time.
 
diff --git a/docs/organization/integrations/integration-platform/webhooks/issue-alerts.mdx b/docs/organization/integrations/integration-platform/webhooks/issue-alerts.mdx
index f7fe6847591350..551d58a5dd4106 100644
--- a/docs/organization/integrations/integration-platform/webhooks/issue-alerts.mdx
+++ b/docs/organization/integrations/integration-platform/webhooks/issue-alerts.mdx
@@ -51,11 +51,11 @@ The interactive demo below shows how to set up an internal integration that can
 - type: string
 - description: the label of the rule that was triggered
 
-<Note>
+<Alert>
 
 The following two fields are for [alert rule action UI components](/organization/integrations/integration-platform/ui-components/alert-rule-action) only.
 
-</Note>
+</Alert>
 
 ### data['issue_alert']['title']
 
diff --git a/docs/organization/integrations/integration-platform/webhooks/metric-alerts.mdx b/docs/organization/integrations/integration-platform/webhooks/metric-alerts.mdx
index 2116300989a36f..66a8ab9f80fa58 100644
--- a/docs/organization/integrations/integration-platform/webhooks/metric-alerts.mdx
+++ b/docs/organization/integrations/integration-platform/webhooks/metric-alerts.mdx
@@ -56,11 +56,11 @@ The interactive demo below shows how to set up an internal integration that can
 - type: string
 - description: the api url for the incident
 
-<Note>
+<Alert>
 
 The following field is for [alert rule action UI components](/organization/integrations/integration-platform/ui-components/alert-rule-action) only.
 
-</Note>
+</Alert>
 
 ### data['metric_alert']['alert_rule']['triggers'][0]['actions'][0]['settings']
 
@@ -69,11 +69,11 @@ The following field is for [alert rule action UI components](/organization/integ
 
 ## Payload
 
-<Note>
+<Alert>
 
 Note: The webhook payload stack frame order lists the oldest frame to the most recent (where the exception happened).
 
-</Note>
+</Alert>
 
 ```json
 {
diff --git a/docs/organization/integrations/issue-tracking/asana/index.mdx b/docs/organization/integrations/issue-tracking/asana/index.mdx
index 5eababf9e82c75..9d28900982608b 100644
--- a/docs/organization/integrations/issue-tracking/asana/index.mdx
+++ b/docs/organization/integrations/issue-tracking/asana/index.mdx
@@ -8,11 +8,11 @@ This integration needs to be set up in each project for which you wish to use it
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Asana**
 
diff --git a/docs/organization/integrations/issue-tracking/clickup/index.mdx b/docs/organization/integrations/issue-tracking/clickup/index.mdx
index 4491fdf111b760..4448fae3d10140 100644
--- a/docs/organization/integrations/issue-tracking/clickup/index.mdx
+++ b/docs/organization/integrations/issue-tracking/clickup/index.mdx
@@ -10,13 +10,13 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
 ClickUp **won't** work with self-hosted Sentry.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > ClickUp**
 
diff --git a/docs/organization/integrations/issue-tracking/goast/index.mdx b/docs/organization/integrations/issue-tracking/goast/index.mdx
index 7399af100826ab..a5a788a376bfae 100644
--- a/docs/organization/integrations/issue-tracking/goast/index.mdx
+++ b/docs/organization/integrations/issue-tracking/goast/index.mdx
@@ -8,11 +8,11 @@ description: "Goast’s Sentry integration brings you an automated platform for
 This integration is maintained and supported by the company that created it. For more details, or questions, please feel free to reach out to support@goast.ai!
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Goast**
 
diff --git a/docs/organization/integrations/issue-tracking/height/index.mdx b/docs/organization/integrations/issue-tracking/height/index.mdx
index f74db9b6325158..594d00301c8d75 100644
--- a/docs/organization/integrations/issue-tracking/height/index.mdx
+++ b/docs/organization/integrations/issue-tracking/height/index.mdx
@@ -10,13 +10,13 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
 Height **won't** work with self-hosted Sentry.
 
-</Note>
+</Alert>
 
 To add the Height integration, navigate to **Settings > Integrations > Height** and click "Install".
 
diff --git a/docs/organization/integrations/issue-tracking/incidentio/index.mdx b/docs/organization/integrations/issue-tracking/incidentio/index.mdx
index 4f61d0e0174e40..3cbbf3189771e4 100644
--- a/docs/organization/integrations/issue-tracking/incidentio/index.mdx
+++ b/docs/organization/integrations/issue-tracking/incidentio/index.mdx
@@ -10,13 +10,13 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
 incident.io **won't** work with self-hosted Sentry.
 
-</Note>
+</Alert>
 
 The preferred way to install the incident.io integration is by sharing a Sentry link in your active incident Slack channel, which prompts you to add the integration:
 
diff --git a/docs/organization/integrations/issue-tracking/jira/index.mdx b/docs/organization/integrations/issue-tracking/jira/index.mdx
index d74bdeb4a603da..eaf6790ce8f801 100644
--- a/docs/organization/integrations/issue-tracking/jira/index.mdx
+++ b/docs/organization/integrations/issue-tracking/jira/index.mdx
@@ -6,11 +6,11 @@ description: "Learn more about Sentry's Jira integration and how it can help tra
 
 ## Install
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions, and Jira admin permissions are required to install this integration. This includes the following permissions: `read`, `write`, `act_as_user`, and `access_email_addresses`.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Jira**.
 
@@ -30,11 +30,11 @@ Jira should now be authorized for all projects under your Sentry organization.
 
 ### Jira Server
 
-<Note>
+<Alert>
 
 As of February 2024, Jira has discontinued support for Jira Server. Accordingly, we have stopped maintaining the docs for this integration. The instructions below may be out of date.
 
-</Note>
+</Alert>
 
 Sentry's Jira Server Integration is built using [Application Links](https://confluence.atlassian.com/adminjiraserver/link-to-other-applications-938846918.html) and should be able to integrate with Jira Data Center as well.
 
@@ -129,11 +129,11 @@ openssl x509 -pubkey -noout -in jira_publickey.cer  > jira_publickey.pem
 
 #### Connect your Jira Server application with Sentry
 
-<Note>
+<Alert>
 
 Confirm [Sentry's IP ranges](/security-legal-pii/security/ip-ranges/) are allowed.
 
-</Note>
+</Alert>
 
 1. Navigate to **Organization Settings > Integrations**.
 2. Next to Jira Server, click "Install".
@@ -143,6 +143,10 @@ Confirm [Sentry's IP ranges](/security-legal-pii/security/ip-ranges/) are allowe
 
 Jira should now be authorized for all projects under your Sentry organization.
 
+### Self-Hosted Sentry + Jira integration
+
+To install the Jira integration with a self-hosted Sentry instance, please follow our [develop-docs](https://develop.sentry.dev/integrations/jira/), skip to the "Installing Local Jira App" section.
+
 ## Configure
 
 Use Jira to leverage [issue management](#issue-management), [issue syncing](#issue-sync), and receive [notifications](#issue-notifications) about changes to issue status. Additionally, add [ignored fields](#ignored-fields) to hide specified fields in the issue creation form.
@@ -151,7 +155,7 @@ Use Jira to leverage [issue management](#issue-management), [issue syncing](#iss
 
 Issue tracking allows you to create Jira issues from within Sentry, and link Sentry issues to existing Jira Issues.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
   <p>
     Manual issue management is available to organizations on Team, Business, and
     Enterprise plans.
@@ -186,7 +190,7 @@ Here, you’ll be able to create or link Jira issues.
 
 To minimize duplication in issue tracking, you can sync comments, assignees, and status updates for Sentry issues to Jira tickets and vice versa. When you delegate an issue to an assignee or update a status on Jira, the updates will also populate in Sentry. When you resolve an issue in Sentry, the issue status will automatically update in Jira. When Jira tickets are marked Done, you can configure how the corresponding issue in Sentry should be resolved.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
   Issue sync is available for organizations on the Team, Business, and
   Enterprise plans.
 </Alert>
@@ -195,7 +199,7 @@ To configure Issue sync, navigate to **Organization Settings** > **Integrations*
 
 ![Sync Jira statuses to Sentry](./img/jira-sync.png)
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 If you hit a 4xx or 5xx error during or after setting up the Jira Server integration, see this [troubleshooting section](#receiving-a-4xx5xx-error-for-the-jira-server-integration).
 
diff --git a/docs/organization/integrations/issue-tracking/kitemaker/index.mdx b/docs/organization/integrations/issue-tracking/kitemaker/index.mdx
index 2cd0a0422c17a2..bc5ffb96c91db0 100644
--- a/docs/organization/integrations/issue-tracking/kitemaker/index.mdx
+++ b/docs/organization/integrations/issue-tracking/kitemaker/index.mdx
@@ -8,11 +8,11 @@ description: "Kitemaker’s integration with Sentry allows you to automatically
 This integration is maintained and supported by the company that created it. For more details, or questions, please feel free to reach out to hi@kitemaker.co!
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Kitemaker**
 
diff --git a/docs/organization/integrations/issue-tracking/linear/index.mdx b/docs/organization/integrations/issue-tracking/linear/index.mdx
index bc0d8e04e989ef..273e54ce62eff9 100644
--- a/docs/organization/integrations/issue-tracking/linear/index.mdx
+++ b/docs/organization/integrations/issue-tracking/linear/index.mdx
@@ -10,13 +10,13 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
 Linear **won't** work with self-hosted Sentry.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Linear**
 
diff --git a/docs/organization/integrations/issue-tracking/shortcut/index.mdx b/docs/organization/integrations/issue-tracking/shortcut/index.mdx
index 4bad40c0714b83..ae8c354f0657d7 100644
--- a/docs/organization/integrations/issue-tracking/shortcut/index.mdx
+++ b/docs/organization/integrations/issue-tracking/shortcut/index.mdx
@@ -10,13 +10,13 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
 Shortcut **won't** work with self-hosted Sentry.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Shortcut**
 
diff --git a/docs/organization/integrations/issue-tracking/teamwork/index.mdx b/docs/organization/integrations/issue-tracking/teamwork/index.mdx
index 079b7c38149c43..2114504c955a89 100644
--- a/docs/organization/integrations/issue-tracking/teamwork/index.mdx
+++ b/docs/organization/integrations/issue-tracking/teamwork/index.mdx
@@ -8,13 +8,13 @@ Teamwork needs to set up only once per organization, then it is available for _a
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
 Teamwork **won't** work with self-hosted Sentry.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Teamwork**
 
diff --git a/docs/organization/integrations/notification-incidents/blar/index.md b/docs/organization/integrations/notification-incidents/blar/index.md
index 064458d4e41ba5..1085e78852c3c8 100644
--- a/docs/organization/integrations/notification-incidents/blar/index.md
+++ b/docs/organization/integrations/notification-incidents/blar/index.md
@@ -11,11 +11,11 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Blar**
 
diff --git a/docs/organization/integrations/notification-incidents/discord/index.mdx b/docs/organization/integrations/notification-incidents/discord/index.mdx
index 02638632e4ef18..85a4eac6bfe38f 100644
--- a/docs/organization/integrations/notification-incidents/discord/index.mdx
+++ b/docs/organization/integrations/notification-incidents/discord/index.mdx
@@ -8,11 +8,11 @@ Set up a Discord integration so you can get notified about, then triage, resolve
 
 ## Install
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Discord** in [Sentry](https://sentry.io).
 
@@ -24,10 +24,10 @@ Sentry owner, manager, or admin permissions are required to install this integra
 
 4. Use the dropdown menu to select the Discord server you'd like to add Sentry to and click "Continue".
 
-   <Note>
+   <Alert>
      You'll need to have the "Manage Server" permission enabled for your Discord
      account in the server you're trying to add the bot to.
-   </Note>
+   </Alert>
 
    ![Select server](./img/discord-server-select.png)
 
diff --git a/docs/organization/integrations/notification-incidents/msteams/index.mdx b/docs/organization/integrations/notification-incidents/msteams/index.mdx
index e2a42bef286281..2702f4d3e16e65 100644
--- a/docs/organization/integrations/notification-incidents/msteams/index.mdx
+++ b/docs/organization/integrations/notification-incidents/msteams/index.mdx
@@ -10,11 +10,11 @@ Set this integration up once per organization, then it's available for _all_ pro
 
 ## Install
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Visit [the Microsoft Teams App Store](https://teams.microsoft.com/l/app/5adee720-30de-4006-a342-d454317db1d4)
 
@@ -39,11 +39,11 @@ Use Microsoft Teams for [alerts](/product/alerts/) regarding issues, environment
 
 ### Alert Rules
 
-<Note>
+<Alert>
 
 If Microsoft Teams is not appearing as an option in issue alert actions, re-install the integration using "Add to team".
 
-</Note>
+</Alert>
 
 Set up an alert rule by going to **Alerts** and clicking "Create Alert". From here, you can configure alerts to route notifications to your Microsoft Team's channels.
 
diff --git a/docs/organization/integrations/notification-incidents/opsgenie/index.mdx b/docs/organization/integrations/notification-incidents/opsgenie/index.mdx
index 8e3d0db159ab4a..67c42cf6f83714 100644
--- a/docs/organization/integrations/notification-incidents/opsgenie/index.mdx
+++ b/docs/organization/integrations/notification-incidents/opsgenie/index.mdx
@@ -10,11 +10,11 @@ The Opsgenie integration allows you to connect your Sentry organization with one
 
 ## Install
 
-<Note>
+<Alert>
 
 You'll need Sentry owner, manager, or admin-level permissions to be able to install this integration.
 
-</Note>
+</Alert>
 
 1. To get started, go to **Settings > Integrations > Opsgenie (Integration)** and click "Add Installation".
 
@@ -30,11 +30,11 @@ The Opsgenie integration should now be installed. Go to the configuration page t
 
 If you added an integration key during installation, it'll appear on the configuration page with the label 'my-first-key'. You can change this label at any time.
 
-<Note>
+<Alert>
 
 If you choose to create a key via the Opsgenie API, you will need to set "allowConfigurationAccess" to true. Integration keys are validated via the Opsgenie authentication endpoint, which requires a key to have configuration access.
 
-</Note>
+</Alert>
 
 ![Opsgenie configuration page](./img/opsgenie-config.png)
 
diff --git a/docs/organization/integrations/notification-incidents/pagerduty/index.mdx b/docs/organization/integrations/notification-incidents/pagerduty/index.mdx
index d08c8beae88226..5cb9fb7c646afc 100644
--- a/docs/organization/integrations/notification-incidents/pagerduty/index.mdx
+++ b/docs/organization/integrations/notification-incidents/pagerduty/index.mdx
@@ -8,11 +8,11 @@ The PagerDuty integration allows you to connect your Sentry organization with on
 
 ## Install
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > PagerDuty**
 
diff --git a/docs/organization/integrations/notification-incidents/pagertree/index.mdx b/docs/organization/integrations/notification-incidents/pagertree/index.mdx
index 08bc8f6396e004..1ee4b8bb1ba9eb 100644
--- a/docs/organization/integrations/notification-incidents/pagertree/index.mdx
+++ b/docs/organization/integrations/notification-incidents/pagertree/index.mdx
@@ -7,11 +7,11 @@ description: "Learn about Sentry's PagerTree integration, which can be used to s
 This integration is maintained and supported by the company that created it. For more details, or questions, please feel free to reach out to support@pagertree.com.
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > PagerTree**
 
diff --git a/docs/organization/integrations/notification-incidents/rootly/index.mdx b/docs/organization/integrations/notification-incidents/rootly/index.mdx
index a66741566e0f07..c6c38159f939b2 100644
--- a/docs/organization/integrations/notification-incidents/rootly/index.mdx
+++ b/docs/organization/integrations/notification-incidents/rootly/index.mdx
@@ -10,13 +10,13 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
 Rootly **won't** work with self-hosted Sentry.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Rootly**
 
diff --git a/docs/organization/integrations/notification-incidents/signl4/index.mdx b/docs/organization/integrations/notification-incidents/signl4/index.mdx
index b36d77287cb0bf..4fadf6d6ce083a 100644
--- a/docs/organization/integrations/notification-incidents/signl4/index.mdx
+++ b/docs/organization/integrations/notification-incidents/signl4/index.mdx
@@ -9,11 +9,11 @@ SIGNL4 is a mobile alerting, and incident response service. This integration is
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > SIGNL4**
 
diff --git a/docs/organization/integrations/notification-incidents/slack/index.mdx b/docs/organization/integrations/notification-incidents/slack/index.mdx
index d41f8a4eeff6b0..5a1cfc3862c56e 100644
--- a/docs/organization/integrations/notification-incidents/slack/index.mdx
+++ b/docs/organization/integrations/notification-incidents/slack/index.mdx
@@ -6,11 +6,11 @@ description: "Learn more about Sentry's Slack integration and how you can triage
 
 ## Install
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 Slack defaults to let any workspace member authorize apps, but they may have to request access. See this [Slack help article](https://get.slack.help/hc/en-us/articles/202035138-Add-an-app-to-your-workspace) for more details.
 
diff --git a/docs/organization/integrations/notification-incidents/spikesh/index.mdx b/docs/organization/integrations/notification-incidents/spikesh/index.mdx
index 696377b9d9a080..fff1b2bc790e3c 100644
--- a/docs/organization/integrations/notification-incidents/spikesh/index.mdx
+++ b/docs/organization/integrations/notification-incidents/spikesh/index.mdx
@@ -10,13 +10,13 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
 Spike.sh **won't** work with self-hosted Sentry.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Spike.sh**
 
diff --git a/docs/organization/integrations/session-replay/atlas/index.mdx b/docs/organization/integrations/session-replay/atlas/index.mdx
index 4eec26707a2028..90ecf231b87091 100644
--- a/docs/organization/integrations/session-replay/atlas/index.mdx
+++ b/docs/organization/integrations/session-replay/atlas/index.mdx
@@ -10,13 +10,13 @@ This integration is maintained and supported by the company that created it. For
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions are required to install this integration.
 
 Atlas **won't** work with self-hosted Sentry.
 
-</Note>
+</Alert>
 
 1. Navigate to **App Configuration > Sentry** in Atlas
 
diff --git a/docs/organization/integrations/session-replay/betterbugs.mdx b/docs/organization/integrations/session-replay/betterbugs.mdx
index 7894ed0bee4fb8..f011cde2bdd2c7 100644
--- a/docs/organization/integrations/session-replay/betterbugs.mdx
+++ b/docs/organization/integrations/session-replay/betterbugs.mdx
@@ -5,15 +5,15 @@ description: "Learn about Sentry's BetterBugs integration."
 ---
 
 BetterBugs + Sentry integration connects your Sentry infrastructure to your BetterBugs account. You get Sentry event logs (both frontend and backend) auto-attached to every bug report.
-This integration is maintained and supported by the company that created it. 
+This integration is maintained and supported by the company that created it.
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner or manager permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to Settings > Integrations > BetterBugs
 
diff --git a/docs/organization/integrations/session-replay/index.mdx b/docs/organization/integrations/session-replay/index.mdx
index 3338f39158baab..adfa928d581233 100644
--- a/docs/organization/integrations/session-replay/index.mdx
+++ b/docs/organization/integrations/session-replay/index.mdx
@@ -4,11 +4,11 @@ sidebar_order: 70
 description: "Learn more about third-party session replay integrations."
 ---
 
-<Note>
+<Alert>
 
 Looking for Sentry's built-in Session Replay product? Click <a class href="/product/explore/session-replay/">here</a> to learn more.
 
-</Note>
+</Alert>
 
 - [Atlas](/organization/integrations/session-replay/atlas/)
 - [BetterBugs](/organization/integrations/session-replay/betterbugs/)
diff --git a/docs/organization/integrations/session-replay/jam.mdx b/docs/organization/integrations/session-replay/jam.mdx
index 406e29c819aee8..70ebd323f997db 100644
--- a/docs/organization/integrations/session-replay/jam.mdx
+++ b/docs/organization/integrations/session-replay/jam.mdx
@@ -10,10 +10,10 @@ The Jam Sentry integration gives you visibility of a bug from the frontend (capt
 
 ## Install and Configure
 
-<Note>
+<Alert>
 
 Sentry owner or manager permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 You can find [installation instructions here](https://jam.dev/docs/integrations/sentry).
diff --git a/docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx b/docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx
index 18e6ba771f6358..02e5fc7e72cc44 100644
--- a/docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx
+++ b/docs/organization/integrations/source-code-mgmt/azure-devops/index.mdx
@@ -38,7 +38,7 @@ You’ll also see that the author of the suspect commit will be listed as a sugg
 
 Issue tracking allows you to create Azure DevOps issues from within Sentry, and link Sentry issues to existing Azure DevOps Issues.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
   <p>
     Manual issue management is available to organizations on Team, Business, and
     Enterprise plans.
@@ -69,7 +69,7 @@ Once you’ve navigated to a specific issue, you’ll find the **Linked Issues**
 
 Sync comments, assignees, and status updates for issues in Sentry to Azure DevOps, to minimize duplication. When you delegate an issue to an assignee or update a status on Azure DevOps, the updates will also populate in Sentry. When you resolve an issue in Sentry, the issue status will automatically update in Azure DevOps.
 
-<Alert title="Note" level="info">
+<Alert title="Note">
   Issue sync is available for organizations on the Team, Business, and
   Enterprise plans.
 </Alert>
@@ -92,11 +92,11 @@ When Sentry sees this, we’ll automatically annotate the matching issue with re
 
 ### Stack Trace Linking
 
-<Note>
+<Alert>
 
 This feature is currently only supported for Ruby, Python, Php, Node, JavaScript, Go and Elixir.
 
-</Note>
+</Alert>
 
 Stack trace linking takes you from a file in your Sentry stack trace to that same file in your source code. If you have commit tracking set up in Sentry, we can take you to the exact version (using the commit associated with the event) of the source code when the error occurred. Otherwise we'll link you to the current state of the source code (using the default branch).
 
@@ -117,11 +117,11 @@ Stack trace linking takes you from a file in your Sentry stack trace to that sam
 
 #### Stack Trace Root and Source Code Root
 
-<Note>
+<Alert>
 
 The following information is only valid for platforms which use traditional file paths. Platforms with package names require additional steps. For **Java**, read more in the [page on source context](/platforms/java/source-context#setting-up-code-mappings).
 
-</Note>
+</Alert>
 
 First, navigate to a stack trace that you wish to map. Find an **In App** frame, which is denoted by a bubble on the right side of the frame. The filename will be shown as the first piece of text at the left hand side of the frame header. In this example, it is `src/main.py`.
 
@@ -158,8 +158,8 @@ If you reach the account selection page during the Azure Devops installation pro
 - For single sign-on, see [Azure Active Directory SSO](/organization/authentication/sso/azure-sso/).
 - If you have multiple accounts in Azure DevOps, open [this link to Azure DevOps](https://aex.dev.azure.com) in another tab, select the correct account, then reinstall.
 
-<Note>
+<Alert>
   If reinstallation solves the problem, please upvote [that solution in
   GitHub](https://github.com/getsentry/sentry/issues/14357), which is where
   we're tracking this improvement.
-</Note>
+</Alert>
diff --git a/docs/organization/integrations/source-code-mgmt/bitbucket/index.mdx b/docs/organization/integrations/source-code-mgmt/bitbucket/index.mdx
index b196b00f5df3e4..30e991b0fbe6c4 100644
--- a/docs/organization/integrations/source-code-mgmt/bitbucket/index.mdx
+++ b/docs/organization/integrations/source-code-mgmt/bitbucket/index.mdx
@@ -6,11 +6,11 @@ description: "Learn more about Sentry's Bitbucket integration and how it can tra
 
 ## Install
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions, and Bitbucket admin permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > Bitbucket**.
 
@@ -168,11 +168,11 @@ When Sentry sees this, we’ll automatically annotate the matching issue with re
 
 ### Stack Trace Linking
 
-<Note>
+<Alert>
 
 This feature is currently only supported for Ruby, Python, Php, Node, JavaScript, Go and Elixir.
 
-</Note>
+</Alert>
 
 Stack trace linking takes you from a file in your Sentry stack trace to that same file in your source code. If you have commit tracking set up in Sentry, we can take you to the exact version (using the commit associated with the event) of the source code when the error occurred. Otherwise we'll link you to the current state of the source code (using the default branch).
 
@@ -193,11 +193,11 @@ Stack trace linking takes you from a file in your Sentry stack trace to that sam
 
 #### Stack Trace Root and Source Code Root
 
-<Note>
+<Alert>
 
 The following information is only valid for platforms which use traditional file paths. Platforms with package names require additional steps. For **Java**, read more in the [page on source context](/platforms/java/source-context#setting-up-code-mappings).
 
-</Note>
+</Alert>
 
 First, navigate to a stack trace that you wish to map. Find an **In App** frame, which is denoted by a bubble on the right side of the frame. The filename will be shown as the first piece of text at the left hand side of the frame header. In this example, it is `src/main.py`.
 
diff --git a/docs/organization/integrations/source-code-mgmt/github/index.mdx b/docs/organization/integrations/source-code-mgmt/github/index.mdx
index 363f635fe3e871..ad285bf05ae155 100644
--- a/docs/organization/integrations/source-code-mgmt/github/index.mdx
+++ b/docs/organization/integrations/source-code-mgmt/github/index.mdx
@@ -10,11 +10,11 @@ Self-hosted GitHub Enterprise accounts typically have URLs that look more like `
 
 ## Install
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions, and GitHub owner permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > [GitHub](https://sentry.io/orgredirect/organizations/:orgslug/settings/integrations/github)**.
 
@@ -36,12 +36,12 @@ The GitHub integration is available for all projects under your Sentry organizat
 
 ## GitHub Enterprise
 
-<Note>
+<Alert>
 
 If your GitHub Enterprise instance is self-hosted/on-prem, follow the instructions below.
 If you're using GitHub Enterprise Cloud, follow the [instructions for GitHub](/organization/integrations/source-code-mgmt/github/#install).
 
-</Note>
+</Alert>
 
 #### Add new GitHub App
 
@@ -159,7 +159,7 @@ If you're using GitHub Enterprise Cloud, follow the [instructions for GitHub](/o
 
    ![Add Installation](./img/github-e-add-installation.png)
 
-4. Fill out the following form with information from your GitHub apps configuration page.
+4. Fill out the following form with information from your GitHub apps configuration page. The installation URL must be resolvable over the Internet.
 
    ![GitHub Enterprise configuration form](./img/github-e-form.png)
 
@@ -296,11 +296,11 @@ By default, this feature is automatically enabled once your GitHub integration h
 
 ### Stack Trace Linking
 
-<Note>
+<Alert>
 
 Sentry will automatically try to set up code mappings on C#, Go, JavaScript, Node.js, PHP, Python, and Ruby projects for organizations with the GitHub integration installed. If your project uses a different SDK, you can add code mappings manually. Support for other languages and other source code integrations is being worked on.
 
-</Note>
+</Alert>
 
 Stack trace linking takes you from a file in your Sentry stack trace to that same file in your source code. If you have commit tracking set up in Sentry, we can take you to the exact version (using the commit associated with the event) of the source code when the error occurred. Otherwise we'll link you to the current state of the source code (using the default **branch**).
 
@@ -321,11 +321,11 @@ Stack trace linking takes you from a file in your Sentry stack trace to that sam
 
 #### Stack Trace Root and Source Code Root
 
-<Note>
+<Alert>
 
 The following information is only valid for platforms which use traditional file paths. Platforms with package names require additional steps. For **Java**, read more in the [page on source context](/platforms/java/source-context#setting-up-code-mappings).
 
-</Note>
+</Alert>
 
 First, navigate to a stack trace that you wish to map. Find an **In App** frame, which is denoted by a bubble on the right side of the frame. The filename will be shown as the first piece of text at the left hand side of the frame header. In this example, it is `src/main.py`.
 
diff --git a/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx b/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx
index db81df23187b00..c5ce8ef7ec7286 100644
--- a/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx
+++ b/docs/organization/integrations/source-code-mgmt/gitlab/index.mdx
@@ -6,11 +6,11 @@ description: "Learn more about Sentry’s GitLab integration and how it helps yo
 
 ## Install
 
-<Note>
+<Alert>
 
 Sentry owner, manager, or admin permissions and GitLab owner or maintainer permissions are required to install this integration.
 
-</Note>
+</Alert>
 
 1. Navigate to **Settings > Integrations > GitLab**.
 
@@ -108,11 +108,11 @@ A `<SHORT-ID>` may look something like 'BACKEND-C' in the image below.
 
 ### Stack Trace Linking
 
-<Note>
+<Alert>
 
 This feature is currently only supported for Ruby, Python, Php, Node, JavaScript, Go and Elixir.
 
-</Note>
+</Alert>
 
 Stack trace linking takes you from a file in your Sentry stack trace to that same file in your source code. If you have commit tracking set up in Sentry, we can take you to the exact version (using the commit associated with the event) of the source code when the error occurred. Otherwise we'll link you to the current state of the source code (using the default **branch**).
 
@@ -133,11 +133,11 @@ Stack trace linking takes you from a file in your Sentry stack trace to that sam
 
 #### Stack Trace Root and Source Code Root
 
-<Note>
+<Alert>
 
 The following information is only valid for platforms which use traditional file paths. Platforms with package names (such as **Java**, **Cocoa**, and **Flutter**) require additional steps.
 
-</Note>
+</Alert>
 
 First, navigate to a stack trace that you wish to map. Find an **In App** frame, which is denoted by a bubble on the right side of the frame. The filename will be shown as the first piece of text at the left hand side of the frame header. In this example, it is `src/main.py`.
 
diff --git a/docs/organization/membership/index.mdx b/docs/organization/membership/index.mdx
index 9ee7d86eea0f0d..416658afdc17bb 100644
--- a/docs/organization/membership/index.mdx
+++ b/docs/organization/membership/index.mdx
@@ -18,11 +18,11 @@ All users and their organization-level roles are listed in **Settings > Members*
 - **Org Managers** have full management access to all teams and projects. They can also manage the organization's membership. Org Managers can perform Team Admin actions without needing to join the team.
 - **Org Owners** have full access to the organization, its data, and settings. Org Owners can perform Team Admin actions without needing to join the team.
 
-<Note>
+<Alert>
 
 For Business and Enterprise plans, the Org Admin role has been replaced by Team Admins and can no longer be assigned to new users. Existing users with Org Admin roles will retain their admin privileges.
 
-</Note>
+</Alert>
 
 ### Permissions
 
@@ -55,11 +55,11 @@ Organization-level roles enable broad access to the entire organization, as desc
 
 ## Team-level Roles
 
-<Note>
+<Alert>
 
 Team-level roles are only available for Business and Enterprise accounts.
 
-</Note>
+</Alert>
 
 All members of a specific team and their team-level roles are listed in **Settings > Teams > [Team] > Members**. Alternatively, go to **Settings > Members > [Member]** to see a specific member's teams and team-level roles.
 
@@ -118,9 +118,9 @@ Projects can only be accessed by that project's team(s). Team Admins, Org Manage
 Any Org Member can get access to a project by joining the team that's associated with that project. Once you've joined a project you'll also be able to edit [ownership rules](/product/issues/ownership-rules/) for that project.
 
 ### Adding New Members
-<Note>
+<Alert>
 This feature is currently only available for [Early Adopters](/organization/early-adopter-features/).
-</Note>
+</Alert>
 
 Users with Manager and Owner-level permissions can add, remove, and change members for a project or organization. They can also toggle on the "Let Members Invite Others" setting to allow any org member to freely invite anyone they like without needing org owner or manager approval.
 
diff --git a/docs/platforms/android/configuration/app-not-respond.mdx b/docs/platforms/android/configuration/app-not-respond.mdx
index f00da4975f680c..4072e8cf781778 100644
--- a/docs/platforms/android/configuration/app-not-respond.mdx
+++ b/docs/platforms/android/configuration/app-not-respond.mdx
@@ -17,11 +17,11 @@ The new implementation (v2) uses the same data source as Google Play Console. Th
 
 While the original Watchdog approach (v1) reports many false positives and is based on heuristics, it still has some advantages over v2, like capturing screenshots and transactions with profiles at the time of ANR.
 
-<Note>
+<Alert>
 
 We're considering SDK support for both approaches working alongside each other on Android 11 and up. Please upvote [this GitHub discussion](https://github.com/getsentry/sentry-java/discussions/2716) and share your feedback if you have a case for v1 and v2 working together.
 
-</Note>
+</Alert>
 
 Both ANR detection implementations are controlled by the same flag:
 
@@ -37,11 +37,11 @@ Whenever the main UI thread of the application is blocked for more than five sec
 
 The integration reports ANR events with `mechanism:ANR`.
 
-<Note>
+<Alert>
 
 Sentry does not report the ANR if the application is in debug mode.
 
-</Note>
+</Alert>
 
 You can also specify how long the thread should be blocked before the ANR is reported. Provide the duration in the attribute `io.sentry.anr.timeout-interval-millis` in your `AndroidManifest.xml`:
 
@@ -58,11 +58,11 @@ and asynchronously sends ANR events to Sentry for each ANR in the history, enric
 
 The integration reports ANR events with `mechanism:AppExitInfo`.
 
-<Note>
+<Alert>
 
 If [ApplicationExitInfo#getTraceInputStream](<https://developer.android.com/reference/android/app/ApplicationExitInfo#getTraceInputStream()>) returns `null`, the SDK will no longer report an ANR event, since these events won't be actionable without it.
 
-</Note>
+</Alert>
 
 ![ANR](./img/app-not-respond.png)
 
diff --git a/docs/platforms/android/configuration/gradle.mdx b/docs/platforms/android/configuration/gradle.mdx
index 380579fd53ccc8..e80574b090f380 100644
--- a/docs/platforms/android/configuration/gradle.mdx
+++ b/docs/platforms/android/configuration/gradle.mdx
@@ -35,11 +35,11 @@ plugins {
 }
 ```
 
-<Note>
+<Alert>
 
 The `io.sentry.android.gradle` >= `3.0.0` requires [Android Gradle Plugin >= 7.0.0](https://developer.android.com/studio/releases/gradle-plugin#7-0-0). For older versions of the Android Gradle Plugin, use `io.sentry.android.gradle:2.+`.
 
-</Note>
+</Alert>
 
 ### Configure
 
@@ -383,11 +383,11 @@ defaults.org=___ORG_SLUG___
 auth.token=___ORG_AUTH_TOKEN___
 ```
 
-<Note>
+<Alert>
 
 You can find your authentication token [on the Organization Auth Tokens](https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/) settings page. For more information about the available configuration options, check out the [full sentry-cli documentation](/cli/configuration/#configuration-values).
 
-</Note>
+</Alert>
 
 ## Native Debug Symbols and Sources
 
@@ -405,11 +405,11 @@ defaults.org=___ORG_SLUG___
 auth.token=___ORG_AUTH_TOKEN___
 ```
 
-<Note>
+<Alert>
 
 You can find your authentication token [on the Sentry API page](https://sentry.io/api/). For more information about the available configuration options, check out the [full sentry-cli documentation](/cli/configuration/#configuration-values).
 
-</Note>
+</Alert>
 
 ## Java/Kotlin Source Context
 
@@ -435,11 +435,11 @@ The plugin uses the [bytecode manipulation](https://www.infoq.com/articles/Livin
 that starts and finishes a [span](/concepts/key-terms/tracing/trace-view/#product-walkthrough-trace-view-page) for common operations that can cause performance bottlenecks.
 This way potentially heavy operations are automatically measured without the need to manually instrument them.
 
-<Note>
+<Alert>
 
 For this data to be captured, you must enable [tracing](/platforms/android/tracing/).
 
-</Note>
+</Alert>
 
 The plugin supports the following features for auto-instrumentation:
 
@@ -486,11 +486,11 @@ enum class InstrumentationFeature {
 
 Check [Integrations](/platforms/android/integrations/) page for more detailed explanation of each instrumentation feature.
 
-<Note>
+<Alert>
 
 To learn more about the internals of auto-instrumentation, check out this [blog post](https://blog.sentry.io/2021/12/14/bytecode-transformations-the-android-gradle-plugin).
 
-</Note>
+</Alert>
 
 ## Auto-Installation
 
diff --git a/docs/platforms/android/configuration/manual-init.mdx b/docs/platforms/android/configuration/manual-init.mdx
index 1a789ec974f7d9..14746fdac054c6 100644
--- a/docs/platforms/android/configuration/manual-init.mdx
+++ b/docs/platforms/android/configuration/manual-init.mdx
@@ -20,11 +20,11 @@ dependencies {
 }
 ```
 
-<Note>
+<Alert>
 
 The [NDK integration](/platforms/android/using-ndk/) comes packaged with the SDK and requires API level 16, though other levels are supported. If you're using multiple Sentry dependencies, you can add a [bill of materials](/platforms/android/configuration/bill-of-materials) to avoid specifying the version of each dependency.
 
-</Note>
+</Alert>
 
 ## Manual Initialization
 
diff --git a/docs/platforms/android/configuration/options.mdx b/docs/platforms/android/configuration/options.mdx
index c3cecad3b314f0..84c92f51d440c4 100644
--- a/docs/platforms/android/configuration/options.mdx
+++ b/docs/platforms/android/configuration/options.mdx
@@ -95,11 +95,11 @@ Grouping in Sentry is different for events with stack traces and without. As a r
 
 If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This option is turned off by default.
 
@@ -170,11 +170,11 @@ The default is `3000`.
 
 _(New in version 6.0.0)_
 
-<Note>
+<Alert>
 
 This only affects [user interaction transactions](/platforms/android/tracing/instrumentation/automatic-instrumentation/#user-interaction-instrumentation).
 
-</Note>
+</Alert>
 
 </ConfigKey>
 
diff --git a/docs/platforms/android/configuration/releases.mdx b/docs/platforms/android/configuration/releases.mdx
index 755f3d838912e0..1466da72764cdc 100644
--- a/docs/platforms/android/configuration/releases.mdx
+++ b/docs/platforms/android/configuration/releases.mdx
@@ -31,11 +31,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -64,11 +64,11 @@ After configuring your SDK, you can install a repository integration or manually
 
 Monitor the [health of releases](/product/releases/health/) by observing user adoption, usage of the application, percentage of [crashes](/product/releases/health/#crash), and [session data](/product/releases/health/#session). Release health will provide insight into the impact of crashes and bugs as it relates to user experience, and reveal trends with each new issue through the [Release Details](/product/releases/release-details/) graphs and filters.
 
-<Note>
+<Alert>
 
 Crash reporting and app hang detection are not available for watchOS.
 
-</Note>
+</Alert>
 
 In order to monitor release health, the SDK sends session data.
 
diff --git a/docs/platforms/android/configuration/sampling.mdx b/docs/platforms/android/configuration/sampling.mdx
index bc66495c366656..e714c315cfb2b9 100644
--- a/docs/platforms/android/configuration/sampling.mdx
+++ b/docs/platforms/android/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
diff --git a/docs/platforms/android/configuration/shared-environments.mdx b/docs/platforms/android/configuration/shared-environments.mdx
index 9d77cd5e950478..fed23e28a20237 100644
--- a/docs/platforms/android/configuration/shared-environments.mdx
+++ b/docs/platforms/android/configuration/shared-environments.mdx
@@ -4,17 +4,17 @@ description: "Learn how to use the Sentry SDK within a shared environment, e.g.
 sidebar_order: 2000
 ---
 
-<Note>
+<Alert>
 
 Using the Sentry SDK within another SDK is [discouraged](https://docs.sentry.io/platforms/). This can lead to unexpected behaviour and potential data leakage. If you need to use Sentry within another SDK, please follow the best practices outlined below.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 When setting up Sentry inside a library, the consuming app could use the Sentry SDK as well, thus you should **not use `Sentry.init()`**, as this will pollute the global state.
 
-</Note>
+</Alert>
 
 In order to not conflict with other Sentry instances, you should use the `Scopes` API to create a new instance of Sentry.
 The Scopes API works the same way as the global Sentry instance, but it is not global and can be used within your component. If you want to capture uncaught exceptions, you can use the `UncaughtExceptionHandlerIntegration` to capture them. As this will capture all uncaught exceptions within an app, you should use the `BeforeSendCallback` to only accept events that are relevant for your SDK.
diff --git a/docs/platforms/android/data-management/debug-files/file-formats/index.mdx b/docs/platforms/android/data-management/debug-files/file-formats/index.mdx
index dd5d74925a8b3a..36d5129dc617d3 100644
--- a/docs/platforms/android/data-management/debug-files/file-formats/index.mdx
+++ b/docs/platforms/android/data-management/debug-files/file-formats/index.mdx
@@ -180,11 +180,11 @@ while removing all debug information from the release binary.
 
 ## ProGuard Mappings
 
-<Note>
+<Alert>
 
 The recommended method for [Android users is to use the Gradle plugin](/platforms/android/configuration/gradle/).
 
-</Note>
+</Alert>
 
 ProGuard mapping files allow Sentry to resolve obfuscated Java classpaths and
 method names into their original form. In that sense, they act as debug
diff --git a/docs/platforms/android/data-management/debug-files/identifiers/index.mdx b/docs/platforms/android/data-management/debug-files/identifiers/index.mdx
index aebce9d77c7593..ea0293898bdd60 100644
--- a/docs/platforms/android/data-management/debug-files/identifiers/index.mdx
+++ b/docs/platforms/android/data-management/debug-files/identifiers/index.mdx
@@ -24,14 +24,14 @@ compute a _Debug Identifier_ for each uploaded file. This identifier is
 associated with executables and libraries as well as debug companions to ensure
 that they can be uniquely located via one common mechanism.
 
-<Note>
+<Alert>
 
 Debug information does not have to be associated with releases. The unique debug
 identifier ensures that Sentry can choose the right files for every crash
 report. However, it is still recommended to configure releases in the client to
 benefit from other features.
 
-</Note>
+</Alert>
 
 For native events, the issue details page displays a list of _Loaded Images_.
 This list contains the executable and all loaded dynamic libraries including
diff --git a/docs/platforms/android/data-management/debug-files/index.mdx b/docs/platforms/android/data-management/debug-files/index.mdx
index b5a401b9febf2e..76457d462212fa 100644
--- a/docs/platforms/android/data-management/debug-files/index.mdx
+++ b/docs/platforms/android/data-management/debug-files/index.mdx
@@ -24,12 +24,12 @@ the following formats:
 - [_ProGuard mappings_](./file-formats/#proguard-mappings) for
   Java and Android
 
-<Note>
+<Alert>
 
 Source maps, while also being debug information files, are handled
 differently in Sentry. For more information see [Source Maps in sentry-cli](/cli/releases/#sentry-cli-sourcemaps).
 
-</Note>
+</Alert>
 
 Sentry requires access to debug information files of your application as well as
 system libraries to provide fully symbolicated crash reports. You can either
@@ -46,11 +46,11 @@ for automatic downloads.
 From the [Project Details](/product/projects/project-details/) page, click into settings,
 then click on _Debug Files_ in the page navigation.
 
-<Note>
+<Alert>
 
 ProGuard files are listed separately, in the _ProGuard_ section of the project settings page.
 
-</Note>
+</Alert>
 
 ## Retention Policy
 
diff --git a/docs/platforms/android/data-management/debug-files/source-context/index.mdx b/docs/platforms/android/data-management/debug-files/source-context/index.mdx
index 17447f9a423a88..4cb76e20c496c4 100644
--- a/docs/platforms/android/data-management/debug-files/source-context/index.mdx
+++ b/docs/platforms/android/data-management/debug-files/source-context/index.mdx
@@ -20,11 +20,11 @@ needs to be uploaded alongside the debug information files.
 The recommended way to do this is by using `sentry-cli`.
 See [Creating Source Bundles](/cli/dif/#creating-source-bundles) for more information.
 
-<Note>
+<Alert>
 
 For Android, follow the instructions in the [Android Source Context](/platforms/android/enhance-errors/source-context) guide.
 
-</Note>
+</Alert>
 
 After they've been uploaded you can review and manage source bundles the same as
 any other debug information file. See [Managing Debug Information Files](../#managing-debug-information-files).
diff --git a/docs/platforms/android/data-management/debug-files/symbol-servers/index.mdx b/docs/platforms/android/data-management/debug-files/symbol-servers/index.mdx
index 70c5456cbe8c1c..2a17fe0c23bd73 100644
--- a/docs/platforms/android/data-management/debug-files/symbol-servers/index.mdx
+++ b/docs/platforms/android/data-management/debug-files/symbol-servers/index.mdx
@@ -42,7 +42,7 @@ Beware that these cause notifications to your team members.
 
 ## Custom Repositories
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 Custom repositories are available for organizations on the _Business_ and
 _Enterprise_ plans.
diff --git a/docs/platforms/android/data-management/sensitive-data/index.mdx b/docs/platforms/android/data-management/sensitive-data/index.mdx
index cf4de7c59a1190..f06150b89cbdd9 100644
--- a/docs/platforms/android/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/android/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 ## Personally Identifiable Information (PII)
 
diff --git a/docs/platforms/android/enhance-errors/kotlin-compiler-plugin.mdx b/docs/platforms/android/enhance-errors/kotlin-compiler-plugin.mdx
index ba4adaa0aa621f..b21b0fd544cb32 100644
--- a/docs/platforms/android/enhance-errors/kotlin-compiler-plugin.mdx
+++ b/docs/platforms/android/enhance-errors/kotlin-compiler-plugin.mdx
@@ -9,11 +9,11 @@ The [Sentry Kotlin Compiler Plugin](https://github.com/getsentry/sentry-android-
 - <PlatformLink to="/enriching-events/viewhierarchy">View Hierarchy</PlatformLink>
 - <PlatformLink to="/tracing/instrumentation/automatic-instrumentation/#user-interaction-instrumentation">User Interaction Tracing</PlatformLink>
 
-<Note>
+<Alert>
 
 The minimum supported Kotlin version is `1.8.20`.
 
-</Note>
+</Alert>
 
 ## How it works
 
diff --git a/docs/platforms/android/enhance-errors/proguard.mdx b/docs/platforms/android/enhance-errors/proguard.mdx
index 5a022d77398382..031e2aff24de22 100644
--- a/docs/platforms/android/enhance-errors/proguard.mdx
+++ b/docs/platforms/android/enhance-errors/proguard.mdx
@@ -12,11 +12,11 @@ If [Source Context](/platforms/android/enhance-errors/source-context) is enabled
 
 Support for Guardsquare's ProGuard and [DexGuard](https://www.guardsquare.com/dexguard) was added in version 3.0.0 of the [Sentry Android Gradle Plugin](/platforms/android/configuration/gradle/).
 
-<Note>
+<Alert>
 
 The Android SDK ships with ProGuard rules automatically defined; no further configuration is needed.
 
-</Note>
+</Alert>
 
 ## In-app Frames
 
diff --git a/docs/platforms/android/enriching-events/attachments/index.mdx b/docs/platforms/android/enriching-events/attachments/index.mdx
index f78a437c1032a9..353de637b81988 100644
--- a/docs/platforms/android/enriching-events/attachments/index.mdx
+++ b/docs/platforms/android/enriching-events/attachments/index.mdx
@@ -49,11 +49,11 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <PlatformContent includePath="enriching-events/attachment-upload" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/android/enriching-events/breadcrumbs/index.mdx b/docs/platforms/android/enriching-events/breadcrumbs/index.mdx
index 65ee11d1ef2c98..8c0e4e7c0e248d 100644
--- a/docs/platforms/android/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/android/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/android/enriching-events/context/index.mdx b/docs/platforms/android/enriching-events/context/index.mdx
index dd07e216bbb9f9..36da3d54f75935 100644
--- a/docs/platforms/android/enriching-events/context/index.mdx
+++ b/docs/platforms/android/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/android/enriching-events/identify-user/index.mdx b/docs/platforms/android/enriching-events/identify-user/index.mdx
index d20a55786a7597..242b1077788c41 100644
--- a/docs/platforms/android/enriching-events/identify-user/index.mdx
+++ b/docs/platforms/android/enriching-events/identify-user/index.mdx
@@ -9,11 +9,11 @@ Users consist of a few critical pieces of information that construct a unique id
 
 ### `id`
 
-<Note>
+<Alert>
 
 If you don't provide an `id`, the SDK falls back to `installationId`, which the SDK randomly generates once during an app's installation.
 
-</Note>
+</Alert>
 
 Your internal identifier for the user.
 
diff --git a/docs/platforms/android/enriching-events/scopes/index.mdx b/docs/platforms/android/enriching-events/scopes/index.mdx
index 17333239d2eace..cc78544b98c6e2 100644
--- a/docs/platforms/android/enriching-events/scopes/index.mdx
+++ b/docs/platforms/android/enriching-events/scopes/index.mdx
@@ -70,6 +70,26 @@ Sentry.captureException(new Exception("my error"));
 // --> Will have the following extra:
 // { shared: 'current', global: 'data', isolation: 'data', current: 'data' }
 ```
+```kotlin
+Sentry.configureScope(ScopeType.GLOBAL) { scope ->
+  scope.setExtra("shared", "global")
+  scope.setExtra("global", "data")
+}
+
+Sentry.configureScope(ScopeType.ISOLATION) { scope ->
+  scope.setExtra("shared", "isolation")
+  scope.setExtra("isolation", "data")
+}
+
+Sentry.configureScope(ScopeType.CURRENT) { scope ->
+  scope.setExtra("shared", "current")
+  scope.setExtra("current", "data")
+}
+
+Sentry.captureException(Exception("my error"))
+// --> Will have the following extra:
+// { shared: 'current', global: 'data', isolation: 'data', current: 'data' }
+```
 
 ## Configuring the Scope
 
@@ -105,7 +125,7 @@ made will stay isolated within the callback function. This allows you to
 more easily isolate pieces of context information to specific locations in your code or
 even call `clear` to briefly remove all context information.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 Any exceptions that occur within the callback function for configuring a local scope will not be
 caught, and all errors that occur will be silently ignored and **not** reported.
diff --git a/docs/platforms/android/enriching-events/scopes/index__v7.x.mdx b/docs/platforms/android/enriching-events/scopes/index__v7.x.mdx
new file mode 100644
index 00000000000000..e9e7092403833c
--- /dev/null
+++ b/docs/platforms/android/enriching-events/scopes/index__v7.x.mdx
@@ -0,0 +1,80 @@
+---
+title: Scopes and Hubs
+description: "SDKs will typically automatically manage the scopes for you in the framework integrations. Learn what a scope is and how you can use it to your advantage."
+---
+
+When an event is captured and sent to Sentry, SDKs will merge that event data with extra
+information from the current scope. SDKs will typically automatically manage the scopes
+for you in the framework integrations and you don't need to think about them. However,
+you should know what a scope is and how you can use it for your advantage.
+
+## What's a Scope, What's a Hub
+
+You can think of the hub as the central point that our SDKs use to route an
+event to Sentry. When you call `init()` a hub is created and a client and a
+blank scope are created on it. That hub is then associated with the current
+thread and will internally hold a stack of scopes.
+
+The scope will hold useful information that should be sent along with the
+event. For instance [contexts](../context/) or
+[breadcrumbs](../breadcrumbs/) are stored on
+the scope. When a scope is pushed, it inherits all data from the parent scope
+and when it pops all modifications are reverted.
+
+The default SDK integrations will push and pop scopes intelligently. For
+instance web framework integrations will create and destroy scopes around your
+routes or controllers.
+
+## How the Scope and Hub Work
+
+As you start using an SDK, a scope and hub are automatically created for you out
+of the box. It's unlikely that you'll interact with the hub directly unless you're
+writing an integration or you want to create or destroy scopes. Scopes, on the
+other hand are more user facing. You can call <PlatformIdentifier name="configure-scope" /> at any point in
+time to modify data stored on the scope. This is useful for doing things like
+[modifying the context](../context/).
+
+When you call a global function such as <PlatformIdentifier name="capture-event" /> internally Sentry
+discovers the current hub and asks it to capture an event. Internally the hub will
+then merge the event with the topmost scope's data.
+
+## Configuring the Scope
+
+The most useful operation when working with scopes is the <PlatformIdentifier name="configure-scope" /> function. It can be used to reconfigure the current scope.
+
+You can, for instance, add custom tags or inform Sentry about the currently authenticated user.
+
+<PlatformContent includePath="enriching-events/scopes/configure-scope" />
+
+You can also apply this configuration when unsetting a user at logout:
+
+<PlatformContent includePath="enriching-events/unset-user" />
+
+<PlatformContent includePath="enriching-events/scopes/scope-synchronization" />
+
+To learn what useful information can be associated with scopes see
+[the context documentation](../context/).
+
+## Local Scopes
+
+We also support pushing and configuring a scope within a single call. This is typically
+called <PlatformIdentifier name="with-scope" />, <PlatformIdentifier name="push-scope" /> or implemented as a function parameter on the capture methods, depending on the SDK. It's very helpful if
+you only want to send data for one specific event.
+
+### Using Scope Callback Parameter
+
+In the following example we use the scope callback parameter that is available for all `capture` methods to attach a `level` and a `tag` to only one specific error:
+
+<PlatformContent includePath="enriching-events/scopes/scope-callback-param" />
+
+Before the callback is invoked the SDK creates a clone of the current scope, and the changes
+made will stay isolated within the callback function. This allows you to
+more easily isolate pieces of context information to specific locations in your code or
+even call `clear` to briefly remove all context information.
+
+<Alert title="Important">
+
+Any exceptions that occur within the callback function for configuring a local scope will not be
+caught, and all errors that occur will be silently ignored and **not** reported.
+
+</Alert>
diff --git a/docs/platforms/android/enriching-events/tags/index.mdx b/docs/platforms/android/enriching-events/tags/index.mdx
index 5707e7b98110ca..9657816853afb2 100644
--- a/docs/platforms/android/enriching-events/tags/index.mdx
+++ b/docs/platforms/android/enriching-events/tags/index.mdx
@@ -17,11 +17,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/android/enriching-events/viewhierarchy/index.mdx b/docs/platforms/android/enriching-events/viewhierarchy/index.mdx
index c5aa49ed4a7295..72780cd02f9806 100644
--- a/docs/platforms/android/enriching-events/viewhierarchy/index.mdx
+++ b/docs/platforms/android/enriching-events/viewhierarchy/index.mdx
@@ -7,11 +7,11 @@ Sentry makes it possible to render a JSON representation of the view hierarchy o
 
 This feature only applies to SDKs with a user interface, such as the ones for mobile and desktop applications. In some environments like native iOS, rendering the view hierarchy requires the UI thread and in the event of a crash, that might not be available. Another example where the view hierarchy might not be available is when the event happens before the screen starts to load. So inherently, this feature is a best effort solution.
 
-<Note>
+<Alert>
 
 Deobfuscation for view hierarchies is fully supported for native SDKs, and React Native, but is currently not supported for Flutter.
 
-</Note>
+</Alert>
 
 ## Enabling View Hierarchy Attachments
 
@@ -25,11 +25,11 @@ View hierarchy debugging is an opt-in feature. You can enable it as shown below:
 
 ### Customize View Hierarchy Capturing
 
-<Note>
+<Alert>
 
 Requires SDK version `6.24.0` or higher.
 
-</Note>
+</Alert>
 
 Because capturing view hierarchy can be a resource-intensive operation on Android, it's limited to one view hierarchy every 2 seconds using a debouncing mechanism. This behavior can be overruled if you supply a `BeforeCaptureCallback` for view hierarchies in the `SentryAndroidOptions`.
 
@@ -81,11 +81,11 @@ SentryAndroid.init(this) { options ->
 
 ### Jetpack Compose Support using the Sentry Kotlin Compiler Plugin
 
-<Note>
+<Alert>
 
 The Sentry Kotlin Compiler plugin is considered _experimental_. Give it a try and provide early feedback [on GitHub](https://github.com/getsentry/sentry-android-gradle-plugin).
 
-</Note>
+</Alert>
 
 If your application uses Jetpack Compose, you can use the <PlatformLink to="/enhance-errors/kotlin-compiler-plugin/">Sentry Kotlin Compiler Plugin</PlatformLink> to see the function names of your `@Composable` elements. You must add the plugin to all modules that contain `@Composable` elements.
 
diff --git a/docs/platforms/android/index.mdx b/docs/platforms/android/index.mdx
index 52b39b1be027c7..29d5d6ea159d8f 100644
--- a/docs/platforms/android/index.mdx
+++ b/docs/platforms/android/index.mdx
@@ -14,11 +14,11 @@ keywords:
 
 On this page, we get you up and running with Sentry's Android SDK, automatically reporting errors and exceptions in your application.
 
-<Note>
+<Alert>
 
 If you don't already have an account and Sentry project established, head over to [sentry.io](https://sentry.io/signup/), then return to this page.
 
-</Note>
+</Alert>
 
 ## Features
 
diff --git a/docs/platforms/android/integrations/apollo/index.mdx b/docs/platforms/android/integrations/apollo/index.mdx
index a103762b5b8bd9..16ce5a748448ac 100644
--- a/docs/platforms/android/integrations/apollo/index.mdx
+++ b/docs/platforms/android/integrations/apollo/index.mdx
@@ -8,19 +8,19 @@ categories:
   - mobile
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already.
 
-</Note>
+</Alert>
 
 Sentry Apollo integration provides the `SentryApolloInterceptor`, which creates a span for each outgoing HTTP request executed with an [Apollo Android](https://github.com/apollographql/apollo-android) GraphQL client.
 
-<Note>
+<Alert>
 
 This integration supports Apollo 2.x. For Apollo 3.x use our <PlatformLink to="/integrations/apollo3/">Apollo3 integration</PlatformLink>.
 
-</Note>
+</Alert>
 
 ## Install
 
diff --git a/docs/platforms/android/integrations/apollo3/index.mdx b/docs/platforms/android/integrations/apollo3/index.mdx
index d4fe0d2ef8b8ab..20a1798a3b1c26 100644
--- a/docs/platforms/android/integrations/apollo3/index.mdx
+++ b/docs/platforms/android/integrations/apollo3/index.mdx
@@ -8,19 +8,19 @@ categories:
   - mobile
 ---
 
-<Note>
+<Alert>
 
 To be able to capture transactions, you'll need to first <PlatformLink to="/tracing/">set up tracing</PlatformLink>.
 
-</Note>
+</Alert>
 
 Sentry's Apollo3 integration provides both the `SentryApollo3Interceptor` and the `SentryApollo3HttpInterceptor`, which create a span for each outgoing HTTP request executed with an [Apollo Kotlin](https://github.com/apollographql/apollo-kotlin) GraphQL client. The integration also provides extension functions on the `ApolloClient.Builder`.
 
-<Note>
+<Alert>
 
 This integration supports Apollo 3.x. It does not yet support <Link to="https://github.com/apollographql/apollo-kotlin/releases/tag/v4.0.0">Apollo4</Link>. If you're using Apollo4 and are interested in an integration for it, please track and upvote the <Link to="https://github.com/getsentry/sentry-java/issues/3662">related issue</Link>.
 
-</Note>
+</Alert>
 
 ## Install
 
diff --git a/docs/platforms/android/integrations/file-io/index.mdx b/docs/platforms/android/integrations/file-io/index.mdx
index 77c161bb5abb8d..f7d2b09404224e 100644
--- a/docs/platforms/android/integrations/file-io/index.mdx
+++ b/docs/platforms/android/integrations/file-io/index.mdx
@@ -7,13 +7,13 @@ categories:
   - mobile
 ---
 
-<Note>
+<Alert>
 
 Supported in Sentry's Android SDK version `5.5.0` and above.
 
 Supported in Sentry Android Gradle Plugin version `3.0.0` and above.
 
-</Note>
+</Alert>
 
 The [Sentry Android Gradle Plugin](/platforms/android/configuration/gradle/) provides file I/O support through bytecode manipulation. The source can be found [on GitHub](https://github.com/getsentry/sentry-android-gradle-plugin/tree/main/plugin-build/src/main/kotlin/io/sentry/android/gradle/instrumentation).
 
@@ -35,11 +35,11 @@ plugins {
 }
 ```
 
-<Note>
+<Alert>
 
 Make sure, that [tracing](/platforms/android/tracing/#configure-the-sample-rate) is enabled.
 
-</Note>
+</Alert>
 
 ## Configure
 
@@ -107,11 +107,11 @@ To view the recorded transaction, log into [sentry.io](https://sentry.io) and op
 
 ![File I/O performance instrumentation](./img/file-io-instrumentation.png)
 
-<Note>
+<Alert>
 
 At the moment, we only support `java.io.FileInputStream`, `java.io.FileOutputStream`, `java.io.FileReader` and `java.io.FileWriter` classes for auto-instrumentation.
 
-</Note>
+</Alert>
 
 ## (Optional) Custom Instrumentation
 
diff --git a/docs/platforms/android/integrations/jetpack-compose/index.mdx b/docs/platforms/android/integrations/jetpack-compose/index.mdx
index 7b8f9058a4ed32..db81f1efe7ba0e 100644
--- a/docs/platforms/android/integrations/jetpack-compose/index.mdx
+++ b/docs/platforms/android/integrations/jetpack-compose/index.mdx
@@ -23,7 +23,7 @@ With Jetpack Compose performance metrics the Sentry Android SDK can automaticall
 
 ![Jetpack Compose Performance Metrics](./img/jetpack-compose-performance-metrics.png)
 
-<Note>
+<Alert>
 
 This feature requires an underlying transaction to attach it's spans to. Transactions can be created manually or automatically by configuring
 
@@ -31,7 +31,7 @@ This feature requires an underlying transaction to attach it's spans to. Transac
 - [Navigation Instrumentation](#jetpack-compose-navigation)
 - [User Interactions](#user-interactions)
 
-</Note>
+</Alert>
 
 Once performance metrics have been enabled, you'll see two spans inside your transactions:
 
@@ -131,18 +131,18 @@ fun LoginScreen() {
 }
 ```
 
-<Note>
+<Alert>
 
 If a `@Composable` doesn't have a `.sentryTag` or a `.testTag` modifier applied, both breadcrumbs and transactions won't be captured because they can't be uniquely identified.
 To automatically generate tags, refer to the docs about our <PlatformLink to="/enhance-errors/kotlin-compiler-plugin/">Sentry Kotlin Compiler Plugin</PlatformLink>.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 If you want to customize the recorded breadcrumbs/transactions, you can skip to [the section below](#customize-the-recorded-breadcrumbtransaction).
 
-</Note>
+</Alert>
 
 ## Jetpack Compose Navigation
 
@@ -170,11 +170,11 @@ plugins {
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more about the Sentry Android Gradle plugin in our [Gradle](/platforms/android/configuration/gradle/) documentation. Details about auto-installation can be found in the [Auto Instrumentation](/platforms/android/configuration/gradle/#tracing-auto-instrumentation) section.
 
-</Note>
+</Alert>
 
 #### Disable
 
diff --git a/docs/platforms/android/integrations/logcat/index.mdx b/docs/platforms/android/integrations/logcat/index.mdx
index 906cf4b29bfd43..02d0706a2492d6 100644
--- a/docs/platforms/android/integrations/logcat/index.mdx
+++ b/docs/platforms/android/integrations/logcat/index.mdx
@@ -7,13 +7,13 @@ categories:
   - mobile
 ---
 
-<Note>
+<Alert>
 
 Supported in Sentry's Android SDK version `6.17.0` and above.
 
 Supported in Sentry Android Gradle Plugin version `3.5.0` and above.
 
-</Note>
+</Alert>
 
 The Sentry Logcat integration adds support for automatically reporting log calls above a minimum logging level as breadcrumbs.
 Any matching `android.Log.*` calls inside your app package are captured as breadcrumbs, including `android.Log.*` calls originating from bundled third party libraries.
@@ -112,10 +112,10 @@ public class MyActivity extends AppCompatActivity {
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded message, log into [sentry.io](https://sentry.io) and open your project. Click on the error's title to open a page where you can see error details and mark errors as resolved.
diff --git a/docs/platforms/android/integrations/okhttp/index.mdx b/docs/platforms/android/integrations/okhttp/index.mdx
index d17fc2f51cfce3..8dd049424e68bc 100644
--- a/docs/platforms/android/integrations/okhttp/index.mdx
+++ b/docs/platforms/android/integrations/okhttp/index.mdx
@@ -12,11 +12,11 @@ The `sentry-okhttp` library provides [OkHttp](https://github.com/square/okhttp)
 
 On this page, we get you up and running with Sentry's OkHttp Integration, so that it will automatically add a breadcrumb and start a span out of the active span bound to the scope for each HTTP Request.
 
-<Note>
+<Alert>
 
 The minimum supported version of `okhttp` is `3.13.0` due to its [incompatibilities](https://medium.com/square-corner-blog/okhttp-3-13-requires-android-5-818bb78d07ce) with Android versions below 5.0. However, you are free to adapt our [SentryOkHttpInterceptor](https://github.com/getsentry/sentry-java/blob/main/sentry-okhttp/src/main/java/io/sentry/okhttp/SentryOkHttpInterceptor.kt) if you're using an older `okhttp` version.
 
-</Note>
+</Alert>
 
 ## Auto-Installation With the Sentry Android Gradle Plugin
 
@@ -68,11 +68,11 @@ sentry {
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more about the Sentry Android Gradle plugin in our [Gradle](/platforms/android/configuration/gradle/) documentation.
 
-</Note>
+</Alert>
 
 ## Manual Installation
 
@@ -87,11 +87,11 @@ implementation 'io.sentry:sentry-okhttp:{{@inject packages.version('sentry.java.
 
 ### Configure
 
-<Note>
+<Alert>
 
 The SentryOkHttpEventListener is available in Sentry's Android SDK version `6.20.0` and above.
 
-</Note>
+</Alert>
 
 Configuration should happen once you create your `OkHttpClient` instance.
 
@@ -176,11 +176,11 @@ String run(String url) throws IOException {
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message, in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded message, log into [sentry.io](https://sentry.io) and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
 
diff --git a/docs/platforms/android/integrations/room-and-sqlite/index.mdx b/docs/platforms/android/integrations/room-and-sqlite/index.mdx
index e385e36b0ad698..eaea636f002c0d 100644
--- a/docs/platforms/android/integrations/room-and-sqlite/index.mdx
+++ b/docs/platforms/android/integrations/room-and-sqlite/index.mdx
@@ -8,7 +8,7 @@ categories:
   - mobile
 ---
 
-<Note>
+<Alert>
 
 Supported in Sentry's Android SDK version `4.0.0` and above.
 
@@ -16,7 +16,7 @@ Supported in Sentry Android Gradle Plugin version `3.0.0` and above.
 
 Custom instrumentation is supported in Sentry's Android SDK, version `6.21.0` and above.
 
-</Note>
+</Alert>
 
 ## Auto-Installation With the Sentry Android Gradle Plugin
 
@@ -48,11 +48,11 @@ dependencies {
 }
 ```
 
-<Note>
+<Alert>
 
 Make sure, that [tracing](/platforms/android/tracing/#configure-the-sample-rate) is enabled.
 
-</Note>
+</Alert>
 
 ### Configure
 
@@ -83,11 +83,11 @@ sentry {
 
 ## Manual Installation
 
-<Note>
+<Alert>
 
 Supported in Sentry's Android SDK, version `6.21.0` and above.
 
-</Note>
+</Alert>
 
 ### Install
 
@@ -201,7 +201,7 @@ To view the recorded transaction, log into [sentry.io](https://sentry.io) and op
 
 ![Room and AndroidX SQLite performance instrumentation](./img/room-sqlite-instrumentation.png)
 
-<Note>
+<Alert>
 
 The Sentry Android Gradle plugin will report SQL queries for any `SupportSQLiteOpenHelper.Factory`, starting with version `3.11.0`.
 
@@ -209,12 +209,12 @@ Earlier versions will only support standard `androidx.room` usage and won't repo
 
 If you're having trouble with this SDK, we want to hear about it. Create an [issue on GitHub](https://github.com/getsentry/sentry-android-gradle-plugin/issues) and describe your experience.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 If you are directly using [SupportSQLiteDatabase#query](<https://developer.android.com/reference/androidx/sqlite/db/SupportSQLiteDatabase#query(java.lang.String)>) or [SupportSQLiteDatabase#execSQL](<https://developer.android.com/reference/androidx/sqlite/db/SupportSQLiteDatabase#execSQL(java.lang.String)>) methods through the Room's SQLiteOpenHelper, consider switching to their alternatives that accept `bindArgs` as a second parameter.
 
 Because Sentry captures SQL queries as Span description, there is a risk of leaking sensitive data when not using an SQL string with placeholders.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/android/integrations/timber/index.mdx b/docs/platforms/android/integrations/timber/index.mdx
index 5f505b4fe9e915..153c887bfdef6f 100644
--- a/docs/platforms/android/integrations/timber/index.mdx
+++ b/docs/platforms/android/integrations/timber/index.mdx
@@ -155,10 +155,10 @@ public class MyActivity extends AppCompatActivity {
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message, in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded message, log into [sentry.io](https://sentry.io) and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
diff --git a/docs/platforms/android/metrics/index.mdx b/docs/platforms/android/metrics/index.mdx
index dff345b6a8092f..1a6a884fb936a7 100644
--- a/docs/platforms/android/metrics/index.mdx
+++ b/docs/platforms/android/metrics/index.mdx
@@ -8,11 +8,11 @@ sidebar_hidden: true
 
 <Include name="metrics-api-change.mdx" />
 
-<Note>
+<Alert>
 
 Metrics are supported with Sentry Android SDK version `7.6.0` and above.
 
-</Note>
+</Alert>
 
 Sentry metrics help you pinpoint and solve issues that impact user experience and app performance by measuring the data points that are important to you. You can track things like processing time, event size, user signups, and conversion rates, then correlate them back to tracing data in order to get deeper insights and solve issues faster.
 
diff --git a/docs/platforms/android/migration/index.mdx b/docs/platforms/android/migration/index.mdx
index c9ddd85fe64588..0baa84bd4eff6a 100644
--- a/docs/platforms/android/migration/index.mdx
+++ b/docs/platforms/android/migration/index.mdx
@@ -181,11 +181,11 @@ The `sentry-android-okhttp`, `sentry-android-fragment`, and `sentry-android-timb
 
 This version is still compatible with Kotlin `1.4`.
 
-<Note>
+<Alert>
 
 This only affects integrations that are written in Kotlin, such as `timber`, `fragment`, `okhttp`, `navigation` and `compose`.
 
-</Note>
+</Alert>
 
 ## Migrating from `io.sentry:sentry-android 5.x` to `io.sentry:sentry-android 6.0.0`
 
@@ -245,11 +245,11 @@ There are more changes and refactors, but they are not user breaking changes.
 
 Starting from version `5.6.2`, the `Timber.tag` usage is no longer supported by our SDK (the tag will not be captured and reflected on Sentry). Please, vote on this [GitHub issue](https://github.com/getsentry/sentry-java/issues/1900) to let us know if we should provide support for that.
 
-<Note>
+<Alert>
 
 Support for `Timber.tag` has been brought back in version `5.7.2`.
 
-</Note>
+</Alert>
 
 ## Migrating from `io.sentry:sentry-android-gradle-plugin 2.x` to `io.sentry:sentry-android-gradle-plugin 3.0.0`
 
diff --git a/docs/platforms/android/profiling/index.mdx b/docs/platforms/android/profiling/index.mdx
index 33637f83349751..e8b376de45ab77 100644
--- a/docs/platforms/android/profiling/index.mdx
+++ b/docs/platforms/android/profiling/index.mdx
@@ -30,12 +30,12 @@ By default, some transactions will be created automatically for common operation
 
 ## Enable Profiling
 
-<Note>
+<Alert>
 
 Android profiling is available starting in SDK version `6.16.0` and is supported on API level 22 and up.
 App start profiling is available starting in SDK version `7.3.0`.
 
-</Note>
+</Alert>
 
 In `AndroidManifest.xml`:
 
@@ -49,11 +49,11 @@ In `AndroidManifest.xml`:
 </application>
 ```
 
-<Note>
+<Alert>
 
 The `io.sentry.traces.profiling.sample-rate` setting is _relative_ to the `io.sentry.traces.sample-rate` setting.
 
-</Note>
+</Alert>
 
 ## App Start Profiling
 
@@ -62,9 +62,9 @@ This includes all methods from any `ContentProvider`, the `Application` class, a
 App start profiling can be enabled with the manifest option `io.sentry.traces.profiling.enable-app-start` as shown above, and it will respect the `io.sentry.traces.sample-rate` and the `io.sentry.traces.profiling.sample-rate`.
 If you prefer to use a <PlatformLink to="/configuration/sampling/#setting-a-sampling-function">sampling function</PlatformLink>, the SDK sets the `isForNextAppStart` field on the `TransactionContext` to specify it will be used for the next app start profiling.
 
-<Note>
+<Alert>
 
 The SDK won't run app start profiling the very first time the app runs, as the SDK won't have read the options by the time the profile should run.
 The SDK will set the `isForNextAppStart` flag in `TransactionContext` if app start profiling is enabled.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/android/session-replay/index.mdx b/docs/platforms/android/session-replay/index.mdx
index 12becae926c168..8b0be5d28fdfc1 100644
--- a/docs/platforms/android/session-replay/index.mdx
+++ b/docs/platforms/android/session-replay/index.mdx
@@ -88,11 +88,11 @@ Sampling begins as soon as a session starts. `sessionSampleRate` is evaluated fi
 The SDK is recording and aggressively masking all text, images, and webviews by default. If your app has any sensitive data, you should only turn the default masking off after explicitly masking out the sensitive data, using the APIs described below.
 However, if you're working on a mobile app that's free of PII or other types of private data, you can opt out of the default text and image masking settings. To learn more about Session Replay privacy, [read our docs](/platforms/android/session-replay/privacy/).
 
-<Note>
+<Alert>
 
 If you find that any other data isn't being masked with the default settings, please let us know by creating a [GitHub issue](https://github.com/getsentry/sentry-java/issues/new?assignees=&labels=Platform%3A+Android%2CType%3A+Bug&projects=&template=bug_report_android.yml).
 
-</Note>
+</Alert>
 
 To disable masking altogether (not to be used on applications with sensitive data):
 
@@ -116,12 +116,19 @@ Errors that happen while a replay is running will be linked to the replay, makin
 
 ## FAQ
 
-Q: Why are parts of my replay not masked?
+Q: **Why are parts of my replay not masked?**
+
 A: Text fields, input fields, images, video players and webviews are all masked by default. Local assets, such as colors or vector drawables, aren't masked because the likelihood of these assets containing PII is low. If you encounter a view/component that should be masked by default, consider opening a [GitHub issue](https://github.com/getsentry/sentry-java/issues).
 
-Q: Does Session Replay work with Jetpack Compose?
+Q: **Does Session Replay work with Jetpack Compose?**
+
 A: Yes, by default, text, input field, and image composables should be masked. Masking within embedded Android views (`AndroidView`)
 in Compose isn't currently supported. If you encounter composables that aren't masked but should be, consider opening a [GitHub issue](https://github.com/getsentry/sentry-java/issues).
 
-Q: What's the lowest version of Android supported?
+Q: **What's the lowest version of Android supported?**
+
 A: Recording only happens on Android 8 (API level 26) or newer. For devices running an older version, SDK features other than recording work normally.
+
+Q: **Why is my issue missing a replay?**
+
+A: An issue may be missing a replay because the user's device was [offline](/product/explore/session-replay/mobile#frequently-asked-questions) while `sessionSampleRate` was specified, your project/organization was rate-limited, or (in rare cases) the device failed to capture the replay video.
diff --git a/docs/platforms/android/session-replay/performance-overhead.mdx b/docs/platforms/android/session-replay/performance-overhead.mdx
index b5af4e51996bcf..176c9a30c57819 100644
--- a/docs/platforms/android/session-replay/performance-overhead.mdx
+++ b/docs/platforms/android/session-replay/performance-overhead.mdx
@@ -5,7 +5,7 @@ notSupported:
 description: "Learn about how enabling Session Replay impacts the performance of your application."
 ---
 
-If you're considering enabling Session Replay, it's important to first understand the potential performance impact to your app. While accurate metrics require realistic testing where you apply typical access patterns and correlate the results with your business metrics, to provide a baseline, we measured the overhead using the open-source [Pocket Casts](https://github.com/Automattic/pocket-casts-android) app. 
+If you're considering enabling Session Replay, it's important to first understand the potential performance impact to your app. While accurate metrics require realistic testing where you apply typical access patterns and correlate the results with your business metrics, to provide a baseline, we measured the overhead using the open-source [Pocket Casts](https://github.com/Automattic/pocket-casts-android) app.
 
 You can learn more about the various optimizations implemented in the Android Replay SDK in the [Replay Performance Overhead](/product/explore/session-replay/mobile/performance-overhead/) docs.
 
@@ -29,12 +29,41 @@ Below are the results of the benchmarking tests, presented as median values to r
 | CPU                              | 36%             | 42%                 |
 | App Startup Time (Cold)          | 1533.35 ms      | 1539.55 ms          |
 | Main Thread Time                 | n/a             | 20ms                |
-| Network Bandwidth                | n/a             | 35 KB               |
+| Network Bandwidth                | n/a             | 7 KB/s of recording |
 
 
 
-<Note>
+<Alert>
 
 Jetpack Compose view hierarchies may be slower to snapshot initially due to ART optimizations, compared to the traditional Android View System. But their performance improves as execution progresses.
 
-</Note>
+</Alert>
+
+## Reducing Performance Overhead
+
+To minimize the performance impact of the Replay SDK, consider the following steps:
+
+### Change Replay quality
+
+Lowering the quality of captured screenshots and videos can significantly reduce CPU, memory, and network bandwidth usage. Here's how you can do it:
+
+```kotlin
+SentryAndroid.init(context) { options ->
+  // this will reduce screenshot compression to 10 and bitrate to 50kbps
+  options.sessionReplay.quality = SentryReplayQuality.LOW // defaults to MEDIUM
+}
+```
+
+### Disable Replay for Low-End Devices
+
+If the Replay SDK causes performance issues on lower-end devices (for example, [this](https://github.com/getsentry/relay/blob/695b459e03481f7d799f07b2b901b140e5d5753d/relay-event-schema/src/protocol/device_class.rs#L21-L37) is how Sentry determines the device class), you can disable it specifically for those devices:
+
+```kotlin
+SentryAndroid.init(context) { options ->
+  options.dsn = "___PUBLIC_DSN___"
+  options.isDebug = true
+
+  options.sessionReplay.onErrorSampleRate = if (isLowEnd()) 0.0 else 1.0
+  options.sessionReplay.sessionSampleRate = if (isLowEnd()) 0.0 else 0.1
+}
+```
diff --git a/docs/platforms/android/session-replay/privacy/index.mdx b/docs/platforms/android/session-replay/privacy/index.mdx
index 6f1c9f4cc7fa19..2eee5f2d998231 100644
--- a/docs/platforms/android/session-replay/privacy/index.mdx
+++ b/docs/platforms/android/session-replay/privacy/index.mdx
@@ -48,11 +48,11 @@ options.sessionReplay.addMaskViewClass("com.example.MyCustomView")
 options.sessionReplay.addUnmaskViewClass("com.example.MyCustomTextView")
 ```
 
-<Note>
+<Alert>
 
 If you're using a code obfuscation tool (R8/ProGuard), adjust your proguard rules accordingly so your custom view class names don't get minified.
 
-</Note>
+</Alert>
 
 ### Class Hierarchy
 
diff --git a/docs/platforms/android/tracing/index.mdx b/docs/platforms/android/tracing/index.mdx
index a71f872ec0b668..bc66662aa0b686 100644
--- a/docs/platforms/android/tracing/index.mdx
+++ b/docs/platforms/android/tracing/index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 4000
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 ## Configure
 
diff --git a/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx
index 4ef09201812d39..3606b6092c7c69 100644
--- a/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx
@@ -4,13 +4,13 @@ sidebar_order: 10
 description: "Learn what transactions are captured after tracing is enabled."
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already.
 
 Supported in Sentry's Android SDK version `4.3.0` and above.
 
-</Note>
+</Alert>
 
 ### Activity Instrumentation
 
@@ -133,11 +133,11 @@ The SDK sets the Span operation to `app.start.cold` for _Cold start_ and `app.st
 
 The SDK uses the `SentryPerformanceProvider` (ContentProvider) creation time as the beginning of the app start and the first frame drawn as the end.
 
-<Note>
+<Alert>
 
 The app start is only measured if the process is of the importance [RunningAppProcessInfo.IMPORTANCE_FOREGROUND](https://developer.android.com/reference/android/app/ActivityManager.RunningAppProcessInfo#IMPORTANCE_FOREGROUND), which means the process is running the foreground UI.
 
-</Note>
+</Alert>
 
 You can opt out of Activity Instrumentation and App Start Instrumentation using options:
 
@@ -151,11 +151,11 @@ Cold and warm start are Mobile Vitals, which you can learn about in the [full do
 
 ### Slow and Frozen Frames
 
-<Note>
+<Alert>
 
 Supported on Android OS version `7.0` and above.
 
-</Note>
+</Alert>
 
 Unresponsive UI and animation hitches annoy users and degrade the user experience. Two measurements to track these types of experiences are _slow frames_ and _frozen frames_. If you want your app to run smoothly, you should try to avoid both. The SDK adds these two measurements for the [Activity](/platforms/android/tracing/instrumentation/automatic-instrumentation/#activity-instrumentation) transactions.
 
@@ -268,11 +268,11 @@ _(New in version 6.0.0)_
 
 The SDK composes the transaction name out of the host `Activity` and the `id` of the view that captured the user interaction — for example, for `LoginActivity.login_button`. The transaction operation is set to `ui.action` plus the interaction type (one of `click`, `scroll`, or `swipe`).
 
-<Note>
+<Alert>
 
 If the view doesn't have the `id` assigned, the transaction won't be captured because it can't be uniquely identified otherwise.
 
-</Note>
+</Alert>
 
 #### User Interaction Instrumentation for Jetpack Compose
 
@@ -297,20 +297,20 @@ fun LoginScreen() {
 }
 ```
 
-<Note>
+<Alert>
 
 If the `@Composable` doesn't have a `sentryTag` modifier applied, the transaction won't be captured because it can't be uniquely identified.
 To capture a transaction for the `@Composable`, you must either add a `sentryTag` modifier or enable automatic `@Composable` tagging.
 
-</Note>
+</Alert>
 
 ##### Automatic `@Composable` tagging using the Sentry Kotlin Compiler Plugin
 
-<Note>
+<Alert>
 
 The Sentry Kotlin Compiler plugin is considered _experimental_. Give it a try and provide early feedback [on GitHub](https://github.com/getsentry/sentry-android-gradle-plugin).
 
-</Note>
+</Alert>
 
 The <PlatformLink to="/enhance-errors/kotlin-compiler-plugin/">Sentry Kotlin Compiler Plugin</PlatformLink> can automatically enrich your `@Composable` functions during compilation with a tag name,
 based on the function name of your `@Composable`.
@@ -332,11 +332,11 @@ plugins {
 
 The transaction finishes automatically after it reaches the specified [idleTimeout](/platforms/android/configuration/options/#idle-timeout) and all of its child spans are finished. The `idleTimeoout` defaults to `3000` milliseconds (three seconds). You can also disable the idle timeout by setting it to `null`, but the transaction must be finished manually in this case.
 
-<Note>
+<Alert>
 
 If the UI transaction has idled, but didn't have any child spans added, it will be dropped.
 
-</Note>
+</Alert>
 
 To finish the transaction manually, you can:
 
diff --git a/docs/platforms/android/tracing/instrumentation/custom-instrumentation.mdx b/docs/platforms/android/tracing/instrumentation/custom-instrumentation.mdx
index 88bc74b2387092..e9c41fe5aefee6 100644
--- a/docs/platforms/android/tracing/instrumentation/custom-instrumentation.mdx
+++ b/docs/platforms/android/tracing/instrumentation/custom-instrumentation.mdx
@@ -4,11 +4,11 @@ sidebar_order: 20
 description: "Learn how to enable trace and span data-capturing on any action in your app."
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
diff --git a/docs/platforms/android/tracing/instrumentation/perf-v2.mdx b/docs/platforms/android/tracing/instrumentation/perf-v2.mdx
index 503b828bccef27..a322d4b5c809b8 100644
--- a/docs/platforms/android/tracing/instrumentation/perf-v2.mdx
+++ b/docs/platforms/android/tracing/instrumentation/perf-v2.mdx
@@ -4,12 +4,12 @@ sidebar_order: 11
 description: "Learn how to get even more insights into Android app performance"
 ---
 
-<Note>
+<Alert>
 
 This feature is marked as _experimental_.
 Supported in Sentry's Android SDK version `7.4.0` and above.
 
-</Note>
+</Alert>
 
 Performance V2 is a set of features which enrich your existing instrumentation, giving you more insights into potential performance bottlenecks. These features tightly integrate with [Mobile Vitals](/product/insights/mobile-vitals/).
 
diff --git a/docs/platforms/android/troubleshooting/index.mdx b/docs/platforms/android/troubleshooting/index.mdx
index 81b775e23b4595..673b94205faa97 100644
--- a/docs/platforms/android/troubleshooting/index.mdx
+++ b/docs/platforms/android/troubleshooting/index.mdx
@@ -155,12 +155,12 @@ If you're using [Android App Bundle](https://developer.android.com/guide/app-bun
 In addition, `sentry-native` uses [tagged pointers](https://source.android.com/devices/tech/debug/tagged-pointers)
 internally. As a result, the Android SDK won't work out of the box on devices with a newer Android OS because they have their own conflicting pointer tagging.
 
-<Note>
+<Alert>
 
 If you're using a version of `sentry-android` before 3.1, you must manually disable the [`allowNativeHeapPointerTagging`](https://developer.android.com/guide/topics/manifest/application-element#allowNativeHeapPointerTagging) configuration option because `sentry-native` uses [tagged pointers](https://source.android.com/devices/tech/debug/tagged-pointers)
 internally. As a result, this option won't work out of the box on devices with a newer Android OS because they have their own conflicting pointer tagging. This is fixed in `sentry-android` versions 3.1 and above.
 
-</Note>
+</Alert>
 
 **Example AndroidManifest.xml**:
 
@@ -311,10 +311,10 @@ sentry {
 }
 ```
 
-<Note>
+<Alert>
 
 This problem is only relevant to these specific versions: `sentry-android-core` version `6.+` and `sentry-android-gradle-plugin` version `3.1.0`.
 
-</Note>
+</Alert>
 
 Check [this issue](https://github.com/getsentry/sentry-android-gradle-plugin/issues/329) for more details.
diff --git a/docs/platforms/android/usage/index.mdx b/docs/platforms/android/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/android/usage/index.mdx
+++ b/docs/platforms/android/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/apple/common/configuration/app-hangs.mdx b/docs/platforms/apple/common/configuration/app-hangs.mdx
index 862859fd3dbe39..dba29f68fabbe0 100644
--- a/docs/platforms/apple/common/configuration/app-hangs.mdx
+++ b/docs/platforms/apple/common/configuration/app-hangs.mdx
@@ -4,7 +4,7 @@ sidebar_order: 11
 description: "Learn about how to add app hang detection reporting."
 ---
 
-<Note>
+<Alert>
 
 We recommend disabling this feature for Widgets and Live Activities because it might detect false positives.
 
@@ -12,7 +12,7 @@ Furthermore, the Cocoa SDK might report app hangs when the OS opens a system dia
 such as whether the user wants to allow your app to paste from the clipboard. As we can't reliably detect these scenarios,
 we advise you to [pause and resume tracking app hangs](#pause-and-resume-app-hang-tracking) to circumvent this problem.
 
-</Note>
+</Alert>
 
 This integration tracks app hangs. This feature is available on iOS, tvOS, and macOS.
 
@@ -133,11 +133,11 @@ SentrySDK.resumeAppHangTracking()
 
 ### App Hangs V2
 
-<Note>
+<Alert>
 
 This feature is experimental and may have bugs.
 
-</Note>
+</Alert>
 
 As of version 8.39.0-beta.1, you can enable AppHangsV2, which is available on iOS and tvOS. The main difference is that AppHangsV2 differentiates between fully-blocking and non-fully-blocking app hangs, which you might choose to ignore. A fully-blocking app hang is when the main thread is stuck completely, and the app can't render a single frame. A non-fully-blocking app hang is when the app appears stuck to the user, but can still render a few frames. Fully-blocking app hangs are more actionable because the stacktrace shows the exact blocking location on the main thread. Non-fully-blocking app hangs can have a stacktrace that doesn't highlight the exact blocking location, since the main thread isn't completely blocked.
 
diff --git a/docs/platforms/apple/common/configuration/options.mdx b/docs/platforms/apple/common/configuration/options.mdx
index 68a691c4dd90d8..a937faec874821 100644
--- a/docs/platforms/apple/common/configuration/options.mdx
+++ b/docs/platforms/apple/common/configuration/options.mdx
@@ -104,11 +104,11 @@ It's crucial for developers to understand that the OS sends a SIGTERM to their a
 
 If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This option is turned off by default.
 
@@ -275,11 +275,11 @@ If <PlatformIdentifier name="trace-propagation-targets" /> is not provided, trac
 <ConfigKey name="enable-persisting-traces-when-crashing">
 
 
-<Note>
+<Alert>
 
 This feature is experimental, may have bugs and is new in [sentry-cocoa version 8.41.0](https://github.com/getsentry/sentry-cocoa/blob/main/CHANGELOG.md#8410).
 
-</Note>
+</Alert>
 
 When enabled, the SDK finishes the ongoing transaction bound to the scope and links them to the crash event when your app crashes. The SDK skips adding profiles to increase the chance of keeping the transaction. This option defaults to `false`.
 
diff --git a/docs/platforms/apple/common/configuration/releases.mdx b/docs/platforms/apple/common/configuration/releases.mdx
index 8d466776a0610b..ff35760df93f55 100644
--- a/docs/platforms/apple/common/configuration/releases.mdx
+++ b/docs/platforms/apple/common/configuration/releases.mdx
@@ -29,11 +29,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -62,11 +62,11 @@ After configuring your SDK, you can install a repository integration or manually
 
 Monitor the [health of releases](/product/releases/health/) by observing user adoption, usage of the application, percentage of [crashes](/product/releases/health/#crash), and [session data](/product/releases/health/#session). Release health will provide insight into the impact of crashes and bugs as it relates to user experience, and reveal trends with each new issue through the [Release Details](/product/releases/release-details/) graphs and filters.
 
-<Note>
+<Alert>
 
 Crash reporting and app hang detection are not available for watchOS.
 
-</Note>
+</Alert>
 
 In order to monitor release health, the SDK sends session data.
 
diff --git a/docs/platforms/apple/common/configuration/sampling.mdx b/docs/platforms/apple/common/configuration/sampling.mdx
index bc66495c366656..e714c315cfb2b9 100644
--- a/docs/platforms/apple/common/configuration/sampling.mdx
+++ b/docs/platforms/apple/common/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
diff --git a/docs/platforms/apple/common/configuration/watchdog-terminations.mdx b/docs/platforms/apple/common/configuration/watchdog-terminations.mdx
index 29eaef459a6a40..170391918ef2f7 100644
--- a/docs/platforms/apple/common/configuration/watchdog-terminations.mdx
+++ b/docs/platforms/apple/common/configuration/watchdog-terminations.mdx
@@ -4,21 +4,21 @@ sidebar_order: 10
 description: "Learn how to turn off Watchdog Termination tracking"
 ---
 
-<Note>
+<Alert>
   This integration is available since version 8.0.0 of Sentry Apple SDK. It was
   named{" "}
   <PlatformLink to="/configuration/out-of-memory/">Out of Memory</PlatformLink>{" "}
   before the 8.0.0 release.
-</Note>
+</Alert>
 
 This integration tracks [watchdog terminations](https://developer.apple.com/documentation/xcode/addressing-watchdog-terminations) based on heuristics. This feature is available for iOS, tvOS, and Mac Catalyst, works only if the application was in the foreground, and doesn't track watchdog terminations for unit tests.
 
 When a typical unhandled error occurs, the Apple SDK writes a report to disk before the app terminates. It includes the current state of your application with details like the stack trace, tags, breadcrumbs, and so on.
 
 The watchdog terminates your app without notice, which means the SDK can't write a report to disk.
-A common reason for the watchdog to terminate your app is an Out Of Memory problem. 
+A common reason for the watchdog to terminate your app is an Out Of Memory problem.
 
-Note, that there are some security-related types of crashes where the OS immediately terminates the app. These are usually infrequent, and include stack buffer overflows or exceptions with a termination reason related to code signing. Third-party libraries like Sentry can't report these incidents. 
+Note, that there are some security-related types of crashes where the OS immediately terminates the app. These are usually infrequent, and include stack buffer overflows or exceptions with a termination reason related to code signing. Third-party libraries like Sentry can't report these incidents.
 
 Those types of crashes can sometimes be visible in the [Xcode Organizer](https://developer.apple.com/documentation/xcode/acquiring-crash-reports-and-diagnostic-logs), though.
 If the app is terminated because it hangs, we won't create a watchdog termination event. An `AppHangs` event will be created instead.
diff --git a/docs/platforms/apple/common/data-management/apple-privacy-manifest.mdx b/docs/platforms/apple/common/data-management/apple-privacy-manifest.mdx
index dbd9209cde7e8f..7d1dfdbc1ccee6 100644
--- a/docs/platforms/apple/common/data-management/apple-privacy-manifest.mdx
+++ b/docs/platforms/apple/common/data-management/apple-privacy-manifest.mdx
@@ -4,15 +4,15 @@ description: "Troubleshoot and resolve common issues with the Apple Privacy Mani
 sidebar_order: 50
 ---
 
-<Note>
+<Alert>
 This guide requires [sentry-cocoa@8.25.0](https://github.com/getsentry/sentry-cocoa/releases/tag/8.25.0) or newer.
-</Note>
+</Alert>
 
 Sentry's SDKs provide error and tracing for mobile applications running on Apple devices. To do this, the SDK needs to access certain information about the device and the application. Some of the APIs required for this are considered privacy-relevant by Apple. In order to submit apps to the App Store, Apple requires all apps - and libraries used within these apps - to provide privacy manifest files stating which APIs are used under which allowed reasons. For more details, read Apple's guidelines on [Describing use of required reason API](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api).
 
-<Note>
+<Alert>
 The information and steps in this guide are still being worked on and might change because of new tools or updated [Apple requirements](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files).
-</Note>
+</Alert>
 
 If you are using dynamically linked frameworks, Apple will automatically process the SDK's privacy manifest. If you are using statically linked libraries, you need to provide the privacy manifest yourself. This guide will help you create the privacy manifest for your applications.
 
diff --git a/docs/platforms/apple/common/data-management/debug-files/identifiers/index.mdx b/docs/platforms/apple/common/data-management/debug-files/identifiers/index.mdx
index aebce9d77c7593..ea0293898bdd60 100644
--- a/docs/platforms/apple/common/data-management/debug-files/identifiers/index.mdx
+++ b/docs/platforms/apple/common/data-management/debug-files/identifiers/index.mdx
@@ -24,14 +24,14 @@ compute a _Debug Identifier_ for each uploaded file. This identifier is
 associated with executables and libraries as well as debug companions to ensure
 that they can be uniquely located via one common mechanism.
 
-<Note>
+<Alert>
 
 Debug information does not have to be associated with releases. The unique debug
 identifier ensures that Sentry can choose the right files for every crash
 report. However, it is still recommended to configure releases in the client to
 benefit from other features.
 
-</Note>
+</Alert>
 
 For native events, the issue details page displays a list of _Loaded Images_.
 This list contains the executable and all loaded dynamic libraries including
diff --git a/docs/platforms/apple/common/data-management/debug-files/index.mdx b/docs/platforms/apple/common/data-management/debug-files/index.mdx
index b5a401b9febf2e..76457d462212fa 100644
--- a/docs/platforms/apple/common/data-management/debug-files/index.mdx
+++ b/docs/platforms/apple/common/data-management/debug-files/index.mdx
@@ -24,12 +24,12 @@ the following formats:
 - [_ProGuard mappings_](./file-formats/#proguard-mappings) for
   Java and Android
 
-<Note>
+<Alert>
 
 Source maps, while also being debug information files, are handled
 differently in Sentry. For more information see [Source Maps in sentry-cli](/cli/releases/#sentry-cli-sourcemaps).
 
-</Note>
+</Alert>
 
 Sentry requires access to debug information files of your application as well as
 system libraries to provide fully symbolicated crash reports. You can either
@@ -46,11 +46,11 @@ for automatic downloads.
 From the [Project Details](/product/projects/project-details/) page, click into settings,
 then click on _Debug Files_ in the page navigation.
 
-<Note>
+<Alert>
 
 ProGuard files are listed separately, in the _ProGuard_ section of the project settings page.
 
-</Note>
+</Alert>
 
 ## Retention Policy
 
diff --git a/docs/platforms/apple/common/data-management/debug-files/symbol-servers/index.mdx b/docs/platforms/apple/common/data-management/debug-files/symbol-servers/index.mdx
index 70c5456cbe8c1c..2a17fe0c23bd73 100644
--- a/docs/platforms/apple/common/data-management/debug-files/symbol-servers/index.mdx
+++ b/docs/platforms/apple/common/data-management/debug-files/symbol-servers/index.mdx
@@ -42,7 +42,7 @@ Beware that these cause notifications to your team members.
 
 ## Custom Repositories
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 Custom repositories are available for organizations on the _Business_ and
 _Enterprise_ plans.
diff --git a/docs/platforms/apple/common/data-management/sensitive-data/index.mdx b/docs/platforms/apple/common/data-management/sensitive-data/index.mdx
index 8b5526b2680e96..bf5eb4dc35b6bd 100644
--- a/docs/platforms/apple/common/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/apple/common/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 If you _do not_ wish to use the default PII behavior, you can also choose to identify users in a more controlled manner, using our [user identity context](../../enriching-events/identify-user/).
 
diff --git a/docs/platforms/apple/common/enriching-events/attachments/index.mdx b/docs/platforms/apple/common/enriching-events/attachments/index.mdx
index 9cb01f9a02d9eb..3afb2712936447 100644
--- a/docs/platforms/apple/common/enriching-events/attachments/index.mdx
+++ b/docs/platforms/apple/common/enriching-events/attachments/index.mdx
@@ -45,19 +45,19 @@ The specific media content type that determines how the attachment is rendered i
 
 Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</PlatformLink>. You can either add an attachment on the global scope to be sent with every event or add it on the <PlatformLink to="/enriching-events/scopes/#local-scopes">local Scope</PlatformLink> to just send the attachment with one specific event.
 
-<Note>
+<Alert>
 
 Adding attachments to crashes is currently not supported.
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="enriching-events/attachment-upload" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/apple/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/apple/common/enriching-events/breadcrumbs/index.mdx
index 6dc26dd026ee57..8e7e926c06d48d 100644
--- a/docs/platforms/apple/common/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/apple/common/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/apple/common/enriching-events/context/index.mdx b/docs/platforms/apple/common/enriching-events/context/index.mdx
index dd07e216bbb9f9..36da3d54f75935 100644
--- a/docs/platforms/apple/common/enriching-events/context/index.mdx
+++ b/docs/platforms/apple/common/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/apple/common/enriching-events/identify-user/index.mdx b/docs/platforms/apple/common/enriching-events/identify-user/index.mdx
index e5649a7fcdfa40..83d730b5306a6f 100644
--- a/docs/platforms/apple/common/enriching-events/identify-user/index.mdx
+++ b/docs/platforms/apple/common/enriching-events/identify-user/index.mdx
@@ -9,11 +9,11 @@ Users consist of a few critical pieces of information that construct a unique id
 
 ### `userId`
 
-<Note>
+<Alert>
 
 If you don't provide a `userId`, the SDK falls back to `installationId`, which the SDK randomly generates once during an app's installation.
 
-</Note>
+</Alert>
 
 Your internal identifier for the user.
 
diff --git a/docs/platforms/apple/common/enriching-events/scopes/index.mdx b/docs/platforms/apple/common/enriching-events/scopes/index.mdx
index 6cc8f4c149b0fb..a3971c45144c01 100644
--- a/docs/platforms/apple/common/enriching-events/scopes/index.mdx
+++ b/docs/platforms/apple/common/enriching-events/scopes/index.mdx
@@ -70,7 +70,7 @@ made will stay isolated within the callback function. This allows you to
 more easily isolate pieces of context information to specific locations in your code or
 even call `clear` to briefly remove all context information.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 Any exceptions that occur within the callback function for configuring a local scope will not be
 caught, and all errors that occur will be silently ignored and **not** reported.
diff --git a/docs/platforms/apple/common/enriching-events/screenshots/index.mdx b/docs/platforms/apple/common/enriching-events/screenshots/index.mdx
index 79f9b0ce16cb33..eb07022c2ccda0 100644
--- a/docs/platforms/apple/common/enriching-events/screenshots/index.mdx
+++ b/docs/platforms/apple/common/enriching-events/screenshots/index.mdx
@@ -14,9 +14,9 @@ Sentry makes it possible to automatically take a screenshot and include it as an
 
 This feature is only available for SDKs with a user interface, like the ones for mobile and desktop applications. It's also limited by whether taking a screenshot is possible or not. For example, in some environments, like native iOS, taking a screenshot requires the UI thread, which often isn't available in the event of a crash. Another example where a screenshot might not be available is when the event happens before the screen starts to load. So inherently, this feature is a best effort solution.
 
-<Note>
+<Alert>
 App hang events won't have a screenshot because the main thread is blocked and Sentry can't interact with UI elements in a background view.
-</Note>
+</Alert>
 
 ## Enabling Screenshots
 
diff --git a/docs/platforms/apple/common/enriching-events/tags/index.mdx b/docs/platforms/apple/common/enriching-events/tags/index.mdx
index 5707e7b98110ca..9657816853afb2 100644
--- a/docs/platforms/apple/common/enriching-events/tags/index.mdx
+++ b/docs/platforms/apple/common/enriching-events/tags/index.mdx
@@ -17,11 +17,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/apple/common/enriching-events/viewhierarchy/index.mdx b/docs/platforms/apple/common/enriching-events/viewhierarchy/index.mdx
index 74f77e62fb3069..c477ded2b9c36a 100644
--- a/docs/platforms/apple/common/enriching-events/viewhierarchy/index.mdx
+++ b/docs/platforms/apple/common/enriching-events/viewhierarchy/index.mdx
@@ -14,15 +14,15 @@ Sentry makes it possible to render a JSON representation of the view hierarchy o
 
 This feature only applies to SDKs with a user interface, such as the ones for mobile and desktop applications. In some environments like native iOS, rendering the view hierarchy requires the UI thread and in the event of a crash, that might not be available. Another example where the view hierarchy might not be available is when the event happens before the screen starts to load. So inherently, this feature is a best effort solution.
 
-<Note>
+<Alert>
 App hang events will not have view hierarchy because the main thread is blocked and Sentry can't interact with UI elements in a background view.
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 Deobfuscation for view hierarchies is fully supported for native SDKs, and React Native, but is currently not supported for Flutter. View hierarchies are not supported for SwiftUI.
 
-</Note>
+</Alert>
 
 ## Enabling View Hierarchy Attachments
 
@@ -61,4 +61,4 @@ View hierarchies appear in the "Attachments" tab, where you can view all attachm
 
 On the **Issue Details** page, you can interact with the view hierarchy attachment in a section called "View Hierarchy". This section represents the state of your application at the time of an error event. There are three displays: a tree view, wireframe, and detailed view for a selected node. You can select nodes in either the tree or the wireframe to view the properties collected by the SDK. The SDK will report on the following keys for each node in the view: `alpha`, `visible`, `x`, `y`, `width`, `height`, `type`, and `identifier` if applicable, but there may be additional values specific to the SDK. This feature can be used as an exploratory tool to debug layout issues, visualize unnecessarily rendered content, or gain a better understanding of the relationship between views.
 
-<Include name="common-imgs/viewhierarchy-example" />
\ No newline at end of file
+<Include name="common-imgs/viewhierarchy-example" />
diff --git a/docs/platforms/apple/common/features/experimental-features.mdx b/docs/platforms/apple/common/features/experimental-features.mdx
index 40a7001e63a28c..bd175aa690dfc9 100644
--- a/docs/platforms/apple/common/features/experimental-features.mdx
+++ b/docs/platforms/apple/common/features/experimental-features.mdx
@@ -14,10 +14,10 @@ Do you want to try some new experimental features? On the latest version of the
 - If you use Swift concurrency, stitch together stack traces of your async code with the `swiftAsyncStacktraces` option. Note that you can enable this in your Objective-C project, but only async code written in Swift will be stitched together.
 - Enable <PlatformLink to="/configuration/app-hangs/#app-hangs-v2">AppHangsV2</PlatformLink> to get more detailed app hangs. The main difference is that AppHangsV2 differentiates between fully-blocking and non-fully-blocking app hangs.
 
-<Note>
+<Alert>
   Experimental features are still a work-in-progress and may have bugs. We
   recognize the irony.
-</Note>
+</Alert>
 
 ```swift {tabTitle:Swift}
 import Sentry
diff --git a/docs/platforms/apple/common/features/index.mdx b/docs/platforms/apple/common/features/index.mdx
index 755cd8a3f60303..737502658f08b3 100644
--- a/docs/platforms/apple/common/features/index.mdx
+++ b/docs/platforms/apple/common/features/index.mdx
@@ -6,11 +6,11 @@ description: "Here's a list of Sentry's Apple SDK features."
 
 Sentry's Apple SDK enables automatic reporting of errors and exceptions, and identifies performance issues in your application.
 
-<Note>
+<Alert>
 
 The SDK builds a crash report that persists to disk. While it attempts to send the report right after the crash, it may not always work because the environment may be unstable at the time of the crash. If this is the case, the report will be sent upon application start.
 
-</Note>
+</Alert>
 
 
 **Features:**
diff --git a/docs/platforms/apple/common/index.mdx b/docs/platforms/apple/common/index.mdx
index 78ba49ba5e5beb..87cc29217c1c19 100644
--- a/docs/platforms/apple/common/index.mdx
+++ b/docs/platforms/apple/common/index.mdx
@@ -1,10 +1,10 @@
 On this page, we get you up and running with Sentry's Apple SDK, which will automatically report errors and exceptions in your application.
 
-<Note>
+<Alert>
 
 If you don't already have an account and Sentry project established, head over to [sentry.io](https://sentry.io/signup/), then return to this page.
 
-</Note>
+</Alert>
 
 <PlatformSection supported={["apple.visionos"]}>
 
@@ -232,11 +232,11 @@ struct SwiftUIApp: App {
 
 Verify that your app is sending events to Sentry by adding the following snippet, which includes an intentional error. You should see the error reported in Sentry within a few minutes.
 
-<Note>
+<Alert>
 
 To verify crashes, ensure you run your application without a debugger attached. Otherwise, the SDK won't capture the crash.
 
-</Note>
+</Alert>
 
 ```swift {tabTitle:Swift}
 import Sentry
diff --git a/docs/platforms/apple/common/install/swift-package-manager.mdx b/docs/platforms/apple/common/install/swift-package-manager.mdx
index 6d9e346878220d..ddcc3d36b162c3 100644
--- a/docs/platforms/apple/common/install/swift-package-manager.mdx
+++ b/docs/platforms/apple/common/install/swift-package-manager.mdx
@@ -16,10 +16,10 @@ You will then be prompted to choose one of the options `Sentry`, `Sentry-Dynamic
 - `Sentry-Dynamic` is the dynamic framework.
 - `SentrySwiftUI` is used to track performance of SwiftUI views, see more information in the [docs](https://docs.sentry.io/platforms/apple/guides/ios/tracing/instrumentation/swiftui-instrumentation/).
 
-<Note>
+<Alert>
   Xcode allows you to choose many options, but you should choose only one of the
   options above.
-</Note>
+</Alert>
 
 Alternatively, when your project uses a `Package.swift` file to manage dependencies, you can specify the target with:
 
@@ -27,8 +27,8 @@ Alternatively, when your project uses a `Package.swift` file to manage dependenc
 .package(url: "https://github.com/getsentry/sentry-cocoa", from: "{{@inject packages.version('sentry.cocoa') }}"),
 ```
 
-<Note>
+<Alert>
 
 Version tags or branches need to have the Package.swift file in it or Xcode won't be able to install the package. This means versions previous to `4.4.3` _cannot_ be installed using SPM.
 
- </Note>
+ </Alert>
diff --git a/docs/platforms/apple/common/integrations/default.mdx b/docs/platforms/apple/common/integrations/default.mdx
index 5c7b4f435d8de9..d2baec5f868c4f 100644
--- a/docs/platforms/apple/common/integrations/default.mdx
+++ b/docs/platforms/apple/common/integrations/default.mdx
@@ -11,17 +11,17 @@ System integrations are enabled by default to integrate into the standard librar
 
 This integration is the core part of the SDK. It hooks into all signal and exception handlers to capture uncaught errors or crashes. This integration is also responsible for adding most of the device information to events. If it is disabled, you will not receive crash reports, nor will events contain much device data.
 
-<Note>
+<Alert>
 
 Crash detection is not available for watchOS, and Mach exceptions are not reported on tvOS.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 Signal and exception handlers can't be installed if a debugger is attached. To test crashes locally, ensure that you've unchecked the "Debug executable" option in the Xcode scheme's Run action for your app.
 
-</Note>
+</Alert>
 
 ### SentryAutoBreadcrumbTrackingIntegration
 
diff --git a/docs/platforms/apple/common/metrics/index.mdx b/docs/platforms/apple/common/metrics/index.mdx
index d72d189cdd736b..4df7068c206485 100644
--- a/docs/platforms/apple/common/metrics/index.mdx
+++ b/docs/platforms/apple/common/metrics/index.mdx
@@ -7,11 +7,11 @@ sidebar_hidden: true
 
 <Include name="metrics-api-change.mdx" />
 
-<Note>
+<Alert>
 
 Metrics are supported with Sentry Cocoa SDK version `8.23.0` and above.
 
-</Note>
+</Alert>
 
 Sentry metrics help you pinpoint and solve issues that impact user experience and app performance by measuring the data points that are important to you. You can track things like processing time, event size, user signups, and conversion rates, then correlate them back to tracing data in order to get deeper insights and solve issues faster.
 
diff --git a/docs/platforms/apple/common/migration/index.mdx b/docs/platforms/apple/common/migration/index.mdx
index 0ee4a263f6e403..f529d3aaa96ae2 100644
--- a/docs/platforms/apple/common/migration/index.mdx
+++ b/docs/platforms/apple/common/migration/index.mdx
@@ -101,7 +101,7 @@ SentrySDK.start { options in
 
 ## Migrating From 6.x to 7.x
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 We recommend updating to at least [7.5.3](https://github.com/getsentry/sentry-cocoa/releases/tag/7.5.3), because the HTTP instrumentation can lead to crashes. Alternatively, you can also <PlatformLink to="/tracing/instrumentation/automatic-instrumentation/#network-tracking">disable the feature</PlatformLink>.
 
diff --git a/docs/platforms/apple/common/profiling/index.mdx b/docs/platforms/apple/common/profiling/index.mdx
index 52803d47e39b1c..5600b12e2edb65 100644
--- a/docs/platforms/apple/common/profiling/index.mdx
+++ b/docs/platforms/apple/common/profiling/index.mdx
@@ -44,11 +44,11 @@ By default, some transactions will be created automatically for common operation
 
 ## Enable Profiling
 
-<Note>
+<Alert>
 
 iOS profiling is available starting in SDK version `8.12.0`.
 
-</Note>
+</Alert>
 
 
 ```swift {tabTitle:Swift}
@@ -73,19 +73,19 @@ SentrySDK.start { options in
 }];
 ```
 
-<Note>
+<Alert>
 
 The <PlatformIdentifier name="profiles-sample-rate" /> setting is _relative_ to the <PlatformIdentifier name="traces-sample-rate" /> setting.
 
-</Note>
+</Alert>
 
 ## Enable Launch Profiling
 
-<Note>
+<Alert>
 
 This feature is experimental and may have bugs.
 
-</Note>
+</Alert>
 
 _(New in version 8.21.0)_
 
@@ -99,17 +99,17 @@ Currently, launch profiles are attached to a special performance transaction ope
 
 ## Continuous Profiling
 
-<Note>
+<Alert>
 
 This feature is experimental and may have bugs.
 
-</Note>
+</Alert>
 
 _(New in version 8.36.0)_
 
 The current profiling implementation stops the profiler automatically after 30 seconds (unless you manually stop it earlier). Naturally, this limitation makes it difficult to get full coverage of your app's execution. We now offer an experimental continuous mode, where profiling data is periodically uploaded while running, with no limit to how long the profiler may run.
 
-Previously, profiles only ran in tandem with performance transactions that were started either automatically or manually with `SentrySDK.startTransaction`. Now, you can start and stop the profiler directly with `SentrySDK.startProfiler` and `SentrySDK.stopProfiler`. You can also start a profile at app launch by setting `SentryOptions.enableAppLaunchProfiling = true` in your call to `SentrySDK.startWithOptions`. 
+Previously, profiles only ran in tandem with performance transactions that were started either automatically or manually with `SentrySDK.startTransaction`. Now, you can start and stop the profiler directly with `SentrySDK.startProfiler` and `SentrySDK.stopProfiler`. You can also start a profile at app launch by setting `SentryOptions.enableAppLaunchProfiling = true` in your call to `SentrySDK.startWithOptions`.
 
 Continuous profiling mode is enabled by default, requiring no changes to `SentryOptions` when you start the SDK to opt in. If you had previously set `SentryOptions.profilesSampleRate` or `SentryOptions.profilesSampler` to use transaction-based profiling, then remove those lines of code from your configuration.
 
diff --git a/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx
index c392e27fcb05de..82510a39ea0711 100644
--- a/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx
@@ -4,7 +4,7 @@ sidebar_order: 10
 description: "Learn what transactions are captured after tracing is enabled."
 ---
 
-<Note>
+<Alert>
 
 Once you <PlatformLink to="/tracing/">set up tracing</PlatformLink>, the SDK enables the following features by default:
 
@@ -16,7 +16,7 @@ Once you <PlatformLink to="/tracing/">set up tracing</PlatformLink>, the SDK ena
 - Core Data Tracing
 - User Interaction Tracing
 
-</Note>
+</Alert>
 
 ## UIViewController Tracing
 
@@ -321,11 +321,11 @@ SentrySDK.start { options in
 
 The SDK composes the transaction name out of the host `UIViewController` and the method that the `UIView` is calling; for example, `YourApp_LoginUIViewController.loginButton`. The SDK sets the transaction operation to `ui.action`. If the SDK detects the interaction's origin was a click, it adds `click` as a suffix to the operation. The transaction finishes automatically after it reaches the specified [idleTimeout](/platforms/android/configuration/options/#idle-timeout) and all of its child spans are finished. The `idleTimeoout` defaults to `3000` milliseconds (three seconds).
 
-<Note>
+<Alert>
 
 If the UI transaction has idled but didn't have any child spans added, the SDK will drop it.
 
-</Note>
+</Alert>
 
 The SDK binds user interaction transactions to the `Scope` automatically if there's no other transaction set. Because of that, you can create spans using custom instrumentation, and those spans will be automatically associated with the running UI transaction.
 
@@ -355,11 +355,11 @@ When the user interaction transaction is not finished yet, but the user makes a
 
 ## Time to Initial Display
 
-<Note>
+<Alert>
 
 This feature only works for UIViewControllers and not for SwiftUI.
 
-</Note>
+</Alert>
 
 By adding a span for a view controller when it's loaded, time to initial display (TTID) provides insight into how long it takes for your view controller to launch and draw its first UI frame. The SDK sets the span operation to `ui.load.initial-display` and the span description to the view controller's name, followed by `initial display` - for example, `MainViewController initial display`.
 
@@ -371,11 +371,11 @@ Since Cocoa SDK version 8.33.0, the SDK doesn't create time to initial display (
 
 ## Time to Full Display
 
-<Note>
+<Alert>
 
 This feature only works for UIViewControllers and not for SwiftUI.
 
-</Note>
+</Alert>
 
 By adding a span for a view controller when it's loaded, time to full display (TTFD) provides insight into how long it takes your view controller to launch and load all of its content. The span starts when the view of a view controller is loaded, and there is no other view controller transaction happening at the moment. The SDK sets the span operation to `ui.load.full-display` and the span description to the view controllers' name, followed by `full display` - for example, `MainActivity full display`.
 
diff --git a/docs/platforms/apple/common/tracing/instrumentation/custom-instrumentation.mdx b/docs/platforms/apple/common/tracing/instrumentation/custom-instrumentation.mdx
index 2d9a41622d6106..74f9e8c3a1188e 100644
--- a/docs/platforms/apple/common/tracing/instrumentation/custom-instrumentation.mdx
+++ b/docs/platforms/apple/common/tracing/instrumentation/custom-instrumentation.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
diff --git a/docs/platforms/apple/common/tracing/instrumentation/swiftui-instrumentation.mdx b/docs/platforms/apple/common/tracing/instrumentation/swiftui-instrumentation.mdx
index 671f098388e061..08fce77d9e19a6 100644
--- a/docs/platforms/apple/common/tracing/instrumentation/swiftui-instrumentation.mdx
+++ b/docs/platforms/apple/common/tracing/instrumentation/swiftui-instrumentation.mdx
@@ -4,7 +4,9 @@ sidebar_order: 12
 description: "Learn how to monitor the performance of your SwiftUI views."
 ---
 
-<Note>This feature is stable since version 8.17.0.</Note>
+<Alert>
+This feature is stable since version 8.17.0.
+</Alert>
 
 You can monitor the performance of your views in a SwiftUI project with the SentrySwiftUI library, which you can install via <PlatformLink to="/install/swift-package-manager/">SPM (Swift package manager)</PlatformLink> or CocoaPods:
 
diff --git a/docs/platforms/apple/common/tracing/trace-propagation/index.mdx b/docs/platforms/apple/common/tracing/trace-propagation/index.mdx
index 4584f4b688ddff..cd3e3d36a4563b 100644
--- a/docs/platforms/apple/common/tracing/trace-propagation/index.mdx
+++ b/docs/platforms/apple/common/tracing/trace-propagation/index.mdx
@@ -40,9 +40,9 @@ this down to only specific URLs, add those URLs to the `tracePropagationTargets`
 string and regexes). The SDK will then only attach the `sentry-trace` and `baggage` headers to outgoing requests
 whose destination either contains a string or matches a regex in your allowlist.
 
-<Note>
+<Alert>
 The `tracePropagationTargets` option matches the entire request URL, not just the domain. Using stricter regex to match certain parts of the URL ensures that requests don't unnecessarily have additional headers attached.
-</Note>
+</Alert>
 
 Since the value of `tracePropagationTargets` is `['.*']` by default, tracing headers are attached to all requests unless otherwise specified.
 
diff --git a/docs/platforms/apple/common/usage/index.mdx b/docs/platforms/apple/common/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/apple/common/usage/index.mdx
+++ b/docs/platforms/apple/common/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/apple/guides/ios/session-replay/index.mdx b/docs/platforms/apple/guides/ios/session-replay/index.mdx
index 3caf4e36fef32a..4abad20e315e66 100644
--- a/docs/platforms/apple/guides/ios/session-replay/index.mdx
+++ b/docs/platforms/apple/guides/ios/session-replay/index.mdx
@@ -67,11 +67,11 @@ Sampling begins as soon as a session starts. `sessionSampleRate` is evaluated fi
 The SDK is recording and aggressively masking all text, images, and webviews by default. If your app has any sensitive data, you should only turn the default masking off after explicitly masking out the sensitive data, using the APIs described below.
 If you want to manually mask parts of your app's data, read our guide on [custom masking](/platforms/apple/guides/ios/session-replay/customredact).
 
-<Note>
+<Alert>
 
 If you encounter any data not being redacted with the default settings, please let us know through a [GitHub issue](https://github.com/getsentry/sentry-cocoa/issues/new?assignees=&labels=Platform%3A+Cocoa%2CType%3A+Bug&projects=&template=bug.yml).
 
-</Note>
+</Alert>
 
 To disable redaction altogether (not to be used on applications with sensitive data):
 
@@ -90,14 +90,18 @@ Errors that happen while a replay is running will be linked to the replay, makin
 
 ### FAQ
 
-Q: Does Session Replay work with SwiftUI?
+Q: **Does Session Replay work with SwiftUI?**
 
 A: Yes. It works with both UIKit and SwiftUI.
 
-Q: Why are parts of my replay not masked?
+Q: **Why are parts of my replay not masked?**
 
 A: Text views, input views, images, video players and webviews are all masked by default. Images with bundled assets aren't masked because the likelihood of these assets containing PII is low. If you encounter a view that should be masked by default, consider opening a [GitHub issue](https://github.com/getsentry/sentry-cocoa/issues).
 
-Q: What's the lowest version of iOS supported?
+Q: **What's the lowest version of iOS supported?**
 
 A: Session Replay recording happens even on the lowest version supported by the Sentry SDK, which is aligend with appstore support.
+
+Q: **Why is my issue missing a replay?**
+
+A: An issue may be missing a replay because the user's device was [offline](/product/explore/session-replay/mobile#frequently-asked-questions) while `sessionSampleRate` was specified, your project/organization was rate-limited, or (in rare cases) the device failed to capture the replay video.
diff --git a/docs/platforms/apple/guides/ios/session-replay/performance-overhead.mdx b/docs/platforms/apple/guides/ios/session-replay/performance-overhead.mdx
index 2ba8e35afe0377..854e56cb7aabbb 100644
--- a/docs/platforms/apple/guides/ios/session-replay/performance-overhead.mdx
+++ b/docs/platforms/apple/guides/ios/session-replay/performance-overhead.mdx
@@ -29,4 +29,33 @@ Below are the results of the benchmarking tests, presented as median values to r
 | CPU                              | 4%              | 13%                 |
 | App Startup Time (Cold)          | 1264.80 ms      | 1265 ms             |
 | Main Thread Time                 | n/a             | 43ms                |
-| Network Bandwidth                | n/a             | 50 KB               |
+| Network Bandwidth                | n/a             | 10 KB/s of recording|
+
+## Reducing Performance Overhead
+
+To minimize the performance impact of the Replay SDK, consider the following steps:
+
+### Change Replay quality
+
+Lowering the quality of captured screenshots and videos can significantly reduce CPU, memory, and network bandwidth usage. Here's how you can do it:
+
+```swift
+SentrySDK.start(configureOptions: { options in
+  // this will reduce screenshot compression to 10 and bitrate to 50kbps
+  options.sessionReplay.quality = .low // defaults to .medium
+})
+```
+
+### Disable Replay for Low-End Devices
+
+If the Replay SDK causes performance issues on lower-end devices (for example, [this](https://github.com/getsentry/relay/blob/695b459e03481f7d799f07b2b901b140e5d5753d/relay-event-schema/src/protocol/device_class.rs#L21-L37) is how Sentry determines the device class), you can disable it specifically for those devices:
+
+```kotlin
+SentrySDK.start(configureOptions: { options in
+  options.dsn = "___PUBLIC_DSN___"
+  options.debug = true
+
+  options.sessionReplay.onErrorSampleRate = if isLowEnd() { 0.0 } else { 1.0 }
+  options.sessionReplay.sessionSampleRate = if isLowEnd() { 0.0 } else { 0.1 }
+})
+```
diff --git a/docs/platforms/apple/guides/macos/features/index.mdx b/docs/platforms/apple/guides/macos/features/index.mdx
index 00b89913edf8be..4cb9cda04d447c 100644
--- a/docs/platforms/apple/guides/macos/features/index.mdx
+++ b/docs/platforms/apple/guides/macos/features/index.mdx
@@ -6,17 +6,17 @@ description: "Learn about Sentry's Apple SDK features for macOS."
 
 Sentry's Apple SDK for macOS enables automatic reporting of errors and exceptions, and identifies performance issues in your application. The minimum supported macOS version is 10.10. The below, is a list of features that are available as part of this SDK.
 
-<Note>
+<Alert>
 
 For macOS, a simple [manual setup](/platforms/apple/guides/macos/usage/#capturing-uncaught-exceptions) is required for the SDK to report uncaught exceptions.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 The SDK builds a crash report that persists to disk. While it attempts to send the report right after the crash, it may not always work because the environment may be unstable at the time of the crash. If this is the case, the report will be sent upon application start.
 
-</Note>
+</Alert>
 
 
 **Features:**
diff --git a/docs/platforms/dart/configuration/options.mdx b/docs/platforms/dart/configuration/options.mdx
index 45fcd1572fe886..ed71dd2713bb3f 100644
--- a/docs/platforms/dart/configuration/options.mdx
+++ b/docs/platforms/dart/configuration/options.mdx
@@ -89,11 +89,11 @@ Grouping in Sentry is different for events with stack traces and without. As a r
 
 If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This option is turned off by default.
 
diff --git a/docs/platforms/dart/configuration/releases.mdx b/docs/platforms/dart/configuration/releases.mdx
index da74a0d318c8f5..b0dc4726a7f5ab 100644
--- a/docs/platforms/dart/configuration/releases.mdx
+++ b/docs/platforms/dart/configuration/releases.mdx
@@ -29,11 +29,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -60,11 +60,10 @@ After configuring your SDK, you can install a repository integration or manually
 
 ## Release Health
 
-<Note>
+<Alert>
 
 Looking for Flutter release health? [See the Flutter documentation](/platforms/flutter/configuration/releases/#release-health).
 
-</Note>
+</Alert>
 
 Monitoring release health is currently not supported for pure Dart applications.
-
diff --git a/docs/platforms/dart/configuration/sampling.mdx b/docs/platforms/dart/configuration/sampling.mdx
index bc66495c366656..e714c315cfb2b9 100644
--- a/docs/platforms/dart/configuration/sampling.mdx
+++ b/docs/platforms/dart/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
diff --git a/docs/platforms/dart/data-management/sensitive-data/index.mdx b/docs/platforms/dart/data-management/sensitive-data/index.mdx
index 8712656e07c427..10a33925792646 100644
--- a/docs/platforms/dart/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/dart/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 If you _do not_ wish to use the default PII behavior, you can also choose to identify users in a more controlled manner, using our [user identity context](../../enriching-events/identify-user/).
 
diff --git a/docs/platforms/dart/enriching-events/attachments/index.mdx b/docs/platforms/dart/enriching-events/attachments/index.mdx
index 2985c7acf86b4a..df53d17d50821a 100644
--- a/docs/platforms/dart/enriching-events/attachments/index.mdx
+++ b/docs/platforms/dart/enriching-events/attachments/index.mdx
@@ -47,11 +47,11 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <PlatformContent includePath="enriching-events/attachment-upload" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/dart/enriching-events/breadcrumbs/index.mdx b/docs/platforms/dart/enriching-events/breadcrumbs/index.mdx
index 65ee11d1ef2c98..8c0e4e7c0e248d 100644
--- a/docs/platforms/dart/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/dart/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/dart/enriching-events/context/index.mdx b/docs/platforms/dart/enriching-events/context/index.mdx
index dd07e216bbb9f9..36da3d54f75935 100644
--- a/docs/platforms/dart/enriching-events/context/index.mdx
+++ b/docs/platforms/dart/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/dart/enriching-events/scopes/index.mdx b/docs/platforms/dart/enriching-events/scopes/index.mdx
index f3d63a85f351cc..95b3264402ef6b 100644
--- a/docs/platforms/dart/enriching-events/scopes/index.mdx
+++ b/docs/platforms/dart/enriching-events/scopes/index.mdx
@@ -72,7 +72,7 @@ made will stay isolated within the callback function. This allows you to
 more easily isolate pieces of context information to specific locations in your code or
 even call `clear` to briefly remove all context information.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 Any exceptions that occur within the callback function for configuring a local scope will not be
 caught, and all errors that occur will be silently ignored and **not** reported.
diff --git a/docs/platforms/dart/enriching-events/tags/index.mdx b/docs/platforms/dart/enriching-events/tags/index.mdx
index 5707e7b98110ca..9657816853afb2 100644
--- a/docs/platforms/dart/enriching-events/tags/index.mdx
+++ b/docs/platforms/dart/enriching-events/tags/index.mdx
@@ -17,11 +17,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/dart/index.mdx b/docs/platforms/dart/index.mdx
index cf6509d20dff5b..30f8f82331aa34 100644
--- a/docs/platforms/dart/index.mdx
+++ b/docs/platforms/dart/index.mdx
@@ -11,11 +11,11 @@ categories:
 
 On this page, we get you up and running with Sentry's Dart SDK.
 
-<Note>
+<Alert>
 
 If you don't already have an account and Sentry project established, head over to [sentry.io](https://sentry.io/signup/), then return to this page.
 
-</Note>
+</Alert>
 
 ## Features
 
diff --git a/docs/platforms/dart/integrations/http-integration.mdx b/docs/platforms/dart/integrations/http-integration.mdx
index 3d3fda4d05d63d..cb38871aedfaae 100644
--- a/docs/platforms/dart/integrations/http-integration.mdx
+++ b/docs/platforms/dart/integrations/http-integration.mdx
@@ -114,11 +114,11 @@ try {
 
 ## Tracing for HTTP Requests
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already.
 
-</Note>
+</Alert>
 
 The `SentryHttpClient` starts a span out of the active span bound to the scope for each HTTP Request.
 
diff --git a/docs/platforms/dart/integrations/logging.mdx b/docs/platforms/dart/integrations/logging.mdx
index 2524be3fbd20f2..ca2011cc078cd5 100644
--- a/docs/platforms/dart/integrations/logging.mdx
+++ b/docs/platforms/dart/integrations/logging.mdx
@@ -61,10 +61,10 @@ void main() async {
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message, in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded message, log into [sentry.io](https://sentry.io) and open your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
diff --git a/docs/platforms/dart/metrics/index.mdx b/docs/platforms/dart/metrics/index.mdx
index 88107f6898d909..7d63b8368a6885 100644
--- a/docs/platforms/dart/metrics/index.mdx
+++ b/docs/platforms/dart/metrics/index.mdx
@@ -7,11 +7,11 @@ sidebar_hidden: true
 
 <Include name="metrics-api-change.mdx" />
 
-<Note>
+<Alert>
 
 Metrics are supported with Sentry Dart SDK version `7.19.0` and above.
 
-</Note>
+</Alert>
 
 Sentry metrics help you pinpoint and solve issues that impact user experience and app performance by measuring the data points that are important to you. You can track things like processing time, event size, user signups, and conversion rates, then correlate them back to tracing data in order to get deeper insights and solve issues faster.
 
diff --git a/docs/platforms/dart/tracing/index.mdx b/docs/platforms/dart/tracing/index.mdx
index eabe7a6ef7e537..d0a773abd0c1a8 100644
--- a/docs/platforms/dart/tracing/index.mdx
+++ b/docs/platforms/dart/tracing/index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 4000
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 ## Configure
 
diff --git a/docs/platforms/dart/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/dart/tracing/instrumentation/automatic-instrumentation.mdx
index 3931d7911e1b08..a7678e2feb2b14 100644
--- a/docs/platforms/dart/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/dart/tracing/instrumentation/automatic-instrumentation.mdx
@@ -4,11 +4,11 @@ description: "Learn what transactions are captured after tracing is enabled."
 sidebar_order: 10
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already.
 
-</Note>
+</Alert>
 
 ### http.Client Library Instrumentation
 
diff --git a/docs/platforms/dart/tracing/instrumentation/custom-instrumentation.mdx b/docs/platforms/dart/tracing/instrumentation/custom-instrumentation.mdx
index ff29395a8e6d49..7dcbb97cc96997 100644
--- a/docs/platforms/dart/tracing/instrumentation/custom-instrumentation.mdx
+++ b/docs/platforms/dart/tracing/instrumentation/custom-instrumentation.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
diff --git a/docs/platforms/dart/usage/index.mdx b/docs/platforms/dart/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/dart/usage/index.mdx
+++ b/docs/platforms/dart/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/dotnet/common/configuration/msbuild.mdx b/docs/platforms/dotnet/common/configuration/msbuild.mdx
index 1380235fc20547..b490444a92aab0 100644
--- a/docs/platforms/dotnet/common/configuration/msbuild.mdx
+++ b/docs/platforms/dotnet/common/configuration/msbuild.mdx
@@ -17,7 +17,7 @@ NuGet package, and providing properties to enable it from your build.
 
 For this feature to work, you must authenticate to Sentry on the machine that is performing your release builds.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 The Sentry auth token (or legacy API key) should always be treated as secret. Be careful not to commit authentication information to source control,
 or use it in any way that it would be written to log files.
@@ -203,12 +203,12 @@ Controls whether source code files are uploaded to Sentry during the build. Defa
 Set this property to `true` to opt-in to sending source code to Sentry.
 This enables the display of [source context](../../data-management/debug-files/source-context/) when viewing stack traces.
 
-<Note>
+<Alert>
 
 If you are already embedding source code in your symbol files using [`EmbedAllSources`](https://github.com/dotnet/sourcelink/blob/main/docs/README.md#embedallsources),
 you do not need to upload them to Sentry separately. In other words, use _either_ `SentryUploadSources` or `EmbedAllSources`, not both.
 
-</Note>
+</Alert>
 
 </ConfigKey>
 
@@ -220,7 +220,7 @@ Set to `false` to disable the Sentry CLI completely, ignoring the settings of ea
 
 </ConfigKey>
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 There are two more properties, `SentryAuthToken` and `SentryApiKey`, that are available for authentication.
 However we recommend that they are used only for simple testing, and not for production. If you decide to use
diff --git a/docs/platforms/dotnet/common/configuration/options.mdx b/docs/platforms/dotnet/common/configuration/options.mdx
index d9e74610429150..e0b439d797b703 100644
--- a/docs/platforms/dotnet/common/configuration/options.mdx
+++ b/docs/platforms/dotnet/common/configuration/options.mdx
@@ -31,11 +31,11 @@ Learn more about [DSN utilization](/product/sentry-basics/dsn-explainer/#dsn-uti
 Before version 3.0.0 of the Sentry SDK for .NET, there was no special treatment for the stack trace. Sentry reported what .NET made available at runtime.
 This behavior now called `StackTraceMode.Original`. With the introduction of 3.0, a new default mode is `Enhanced`.
 
-<Note>
+<Alert>
 
 Changing this value will affect issue grouping. Since the frame significantly changes shape.
 
-</Note>
+</Alert>
 
 </ConfigKey>
 
@@ -135,11 +135,11 @@ Grouping in Sentry is different for events with stack traces and without. As a r
 
 If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This option is turned off by default.
 
diff --git a/docs/platforms/dotnet/common/configuration/releases.mdx b/docs/platforms/dotnet/common/configuration/releases.mdx
index 43f8984dc810b5..92d7d07e0a07ff 100644
--- a/docs/platforms/dotnet/common/configuration/releases.mdx
+++ b/docs/platforms/dotnet/common/configuration/releases.mdx
@@ -29,11 +29,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -62,11 +62,11 @@ After configuring your SDK, you can install a repository integration or manually
 
 Monitor the [health of releases](/product/releases/health/) by observing user adoption, usage of the application, percentage of [crashes](/product/releases/health/#crash), and [session data](/product/releases/health/#session). Release health will provide insight into the impact of crashes and bugs as it relates to user experience, and reveal trends with each new issue through the [Release Details](/product/releases/release-details/) graphs and filters.
 
-<Note>
+<Alert>
 
 Crash reporting and app hang detection are not available for watchOS.
 
-</Note>
+</Alert>
 
 In order to monitor release health, the SDK sends session data.
 
@@ -76,9 +76,9 @@ A session represents the interaction between the user and the application. Sessi
 
 <PlatformContent includePath="configuration/auto-session-tracking" />
 
-<Note>
+<Alert>
 
 Release health support for .NET is currently limited to single-instance **client** applications only. This means it can be used with WPF, Xamarin, WinForms and similar app models.
 Support for server frameworks such as ASP.NET is planned.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/dotnet/common/configuration/sampling.mdx b/docs/platforms/dotnet/common/configuration/sampling.mdx
index bc66495c366656..e714c315cfb2b9 100644
--- a/docs/platforms/dotnet/common/configuration/sampling.mdx
+++ b/docs/platforms/dotnet/common/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
diff --git a/docs/platforms/dotnet/common/crons/index.mdx b/docs/platforms/dotnet/common/crons/index.mdx
index f6298ca18aef2a..bd8e27cf67f5e0 100644
--- a/docs/platforms/dotnet/common/crons/index.mdx
+++ b/docs/platforms/dotnet/common/crons/index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 5750
 
 Once implemented, it'll allow you to get alerts and metrics to help you solve errors, detect timeouts, and prevent disruptions to your service.
 
-<Note>
+<Alert>
 
 If you are using [Hangfire](https://www.hangfire.io/), please see <PlatformLink to="/crons/hangfire">how to setup monitoring for Hangfire jobs</PlatformLink>.
 
-</Note>
+</Alert>
 
 ## Requirements
 
diff --git a/docs/platforms/dotnet/common/data-management/debug-files/identifiers/index.mdx b/docs/platforms/dotnet/common/data-management/debug-files/identifiers/index.mdx
index aebce9d77c7593..ea0293898bdd60 100644
--- a/docs/platforms/dotnet/common/data-management/debug-files/identifiers/index.mdx
+++ b/docs/platforms/dotnet/common/data-management/debug-files/identifiers/index.mdx
@@ -24,14 +24,14 @@ compute a _Debug Identifier_ for each uploaded file. This identifier is
 associated with executables and libraries as well as debug companions to ensure
 that they can be uniquely located via one common mechanism.
 
-<Note>
+<Alert>
 
 Debug information does not have to be associated with releases. The unique debug
 identifier ensures that Sentry can choose the right files for every crash
 report. However, it is still recommended to configure releases in the client to
 benefit from other features.
 
-</Note>
+</Alert>
 
 For native events, the issue details page displays a list of _Loaded Images_.
 This list contains the executable and all loaded dynamic libraries including
diff --git a/docs/platforms/dotnet/common/data-management/debug-files/index.mdx b/docs/platforms/dotnet/common/data-management/debug-files/index.mdx
index b5a401b9febf2e..76457d462212fa 100644
--- a/docs/platforms/dotnet/common/data-management/debug-files/index.mdx
+++ b/docs/platforms/dotnet/common/data-management/debug-files/index.mdx
@@ -24,12 +24,12 @@ the following formats:
 - [_ProGuard mappings_](./file-formats/#proguard-mappings) for
   Java and Android
 
-<Note>
+<Alert>
 
 Source maps, while also being debug information files, are handled
 differently in Sentry. For more information see [Source Maps in sentry-cli](/cli/releases/#sentry-cli-sourcemaps).
 
-</Note>
+</Alert>
 
 Sentry requires access to debug information files of your application as well as
 system libraries to provide fully symbolicated crash reports. You can either
@@ -46,11 +46,11 @@ for automatic downloads.
 From the [Project Details](/product/projects/project-details/) page, click into settings,
 then click on _Debug Files_ in the page navigation.
 
-<Note>
+<Alert>
 
 ProGuard files are listed separately, in the _ProGuard_ section of the project settings page.
 
-</Note>
+</Alert>
 
 ## Retention Policy
 
diff --git a/docs/platforms/dotnet/common/data-management/debug-files/source-context/index.mdx b/docs/platforms/dotnet/common/data-management/debug-files/source-context/index.mdx
index 52e3fd63e78746..a9e733560b3be6 100644
--- a/docs/platforms/dotnet/common/data-management/debug-files/source-context/index.mdx
+++ b/docs/platforms/dotnet/common/data-management/debug-files/source-context/index.mdx
@@ -20,7 +20,7 @@ needs to be uploaded alongside the debug information files.
 The recommended way to do this is by using `sentry-cli`.
 See [Creating Source Bundles](/cli/dif/#creating-source-bundles) for more information.
 
-<Note>
+<Alert>
 
 For .NET projects, you can [configure MSBuild](../../../configuration/msbuild/) to
 call `sentry-cli` automatically. Enable the `SentryUploadSources` property to
@@ -34,7 +34,7 @@ extracted from them automatically.
 Also note that the similar `EmbedUntrackedSources` option is not yet supported, but may be added
 in the future. Referer to [this issue](https://github.com/getsentry/symbolic/issues/735) for details.
 
-</Note>
+</Alert>
 
 After they've been uploaded you can review and manage source bundles the same as
 any other debug information file. See [Managing Debug Information Files](../#managing-debug-information-files).
diff --git a/docs/platforms/dotnet/common/data-management/debug-files/symbol-servers/index.mdx b/docs/platforms/dotnet/common/data-management/debug-files/symbol-servers/index.mdx
index d5402e77097d86..a69e2582280c60 100644
--- a/docs/platforms/dotnet/common/data-management/debug-files/symbol-servers/index.mdx
+++ b/docs/platforms/dotnet/common/data-management/debug-files/symbol-servers/index.mdx
@@ -42,7 +42,7 @@ Beware that these cause notifications to your team members.
 
 ## Custom Repositories
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 Custom repositories are available for organizations on the _Business_ and
 _Enterprise_ plans.
diff --git a/docs/platforms/dotnet/common/data-management/debug-files/upload/index.mdx b/docs/platforms/dotnet/common/data-management/debug-files/upload/index.mdx
index 1ea1bb85c4ee8f..60d5ad430b1e89 100644
--- a/docs/platforms/dotnet/common/data-management/debug-files/upload/index.mdx
+++ b/docs/platforms/dotnet/common/data-management/debug-files/upload/index.mdx
@@ -11,7 +11,7 @@ application:
 
 <Include name="common-imgs/debug-files-workflow" />
 
-<Note>
+<Alert>
 
 Depending on application type, target platform, and build configuration, the
 Sentry support for .NET may require uploading debug files in order to show a
@@ -26,7 +26,7 @@ Refer to [msbuild configuration](/platforms/dotnet/configuration/msbuild) for de
 
 The remaining information on this page describes invoking the Sentry CLI manually.
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="debug-files">
 
diff --git a/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx b/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx
index cf4de7c59a1190..f06150b89cbdd9 100644
--- a/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/dotnet/common/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 ## Personally Identifiable Information (PII)
 
diff --git a/docs/platforms/dotnet/common/enriching-events/attachments/index.mdx b/docs/platforms/dotnet/common/enriching-events/attachments/index.mdx
index 57b07ad1937119..533c94eba7c6c7 100644
--- a/docs/platforms/dotnet/common/enriching-events/attachments/index.mdx
+++ b/docs/platforms/dotnet/common/enriching-events/attachments/index.mdx
@@ -3,11 +3,11 @@ title: Attachments
 description: "Learn more about how Sentry can store additional files in the same request as event attachments."
 ---
 
-<Note>
+<Alert>
 
 This feature is supported in version 3.0 and higher of Sentry's .NET SDK.
 
-</Note>
+</Alert>
 
 Sentry can enrich your events for further investigation by storing additional files, such as config or log files, as attachments.
 
@@ -53,11 +53,11 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <PlatformContent includePath="enriching-events/attachment-upload" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/dotnet/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/dotnet/common/enriching-events/breadcrumbs/index.mdx
index e65703cd2ddbcf..909b014f6d0e87 100644
--- a/docs/platforms/dotnet/common/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/dotnet/common/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/dotnet/common/enriching-events/context/index.mdx b/docs/platforms/dotnet/common/enriching-events/context/index.mdx
index 3fa1c3fffd8af4..3c36bc77e1f8bd 100644
--- a/docs/platforms/dotnet/common/enriching-events/context/index.mdx
+++ b/docs/platforms/dotnet/common/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/dotnet/common/enriching-events/identify-user/index.mdx b/docs/platforms/dotnet/common/enriching-events/identify-user/index.mdx
index d20a55786a7597..242b1077788c41 100644
--- a/docs/platforms/dotnet/common/enriching-events/identify-user/index.mdx
+++ b/docs/platforms/dotnet/common/enriching-events/identify-user/index.mdx
@@ -9,11 +9,11 @@ Users consist of a few critical pieces of information that construct a unique id
 
 ### `id`
 
-<Note>
+<Alert>
 
 If you don't provide an `id`, the SDK falls back to `installationId`, which the SDK randomly generates once during an app's installation.
 
-</Note>
+</Alert>
 
 Your internal identifier for the user.
 
diff --git a/docs/platforms/dotnet/common/enriching-events/scopes/index.mdx b/docs/platforms/dotnet/common/enriching-events/scopes/index.mdx
index 751b9de56294df..c70db4f1f633c3 100644
--- a/docs/platforms/dotnet/common/enriching-events/scopes/index.mdx
+++ b/docs/platforms/dotnet/common/enriching-events/scopes/index.mdx
@@ -72,7 +72,7 @@ made will stay isolated within the callback function. This allows you to
 more easily isolate pieces of context information to specific locations in your code or
 even call `clear` to briefly remove all context information.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 Any exceptions that occur within the callback function for configuring a local scope will not be
 caught, and all errors that occur will be silently ignored and **not** reported.
diff --git a/docs/platforms/dotnet/common/enriching-events/tags/index.mdx b/docs/platforms/dotnet/common/enriching-events/tags/index.mdx
index 5707e7b98110ca..9657816853afb2 100644
--- a/docs/platforms/dotnet/common/enriching-events/tags/index.mdx
+++ b/docs/platforms/dotnet/common/enriching-events/tags/index.mdx
@@ -17,11 +17,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/dotnet/common/index.mdx b/docs/platforms/dotnet/common/index.mdx
index 7f8d93896bc7f7..992ee7b79fdbaf 100644
--- a/docs/platforms/dotnet/common/index.mdx
+++ b/docs/platforms/dotnet/common/index.mdx
@@ -2,7 +2,7 @@
 
 On this page, we get you up and running with Sentry's SDK.
 
-<Alert level="info" title="Using a framework?">
+<Alert title="Using a framework?">
 
 Check out the other SDKs we support in the left-hand dropdown.
 
@@ -28,10 +28,10 @@ This snippet includes an intentional error, so you can test that everything is w
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
diff --git a/docs/platforms/dotnet/common/profiling/index.mdx b/docs/platforms/dotnet/common/profiling/index.mdx
index c77888bc35fe88..805786ec638c9d 100644
--- a/docs/platforms/dotnet/common/profiling/index.mdx
+++ b/docs/platforms/dotnet/common/profiling/index.mdx
@@ -8,7 +8,7 @@ sidebar_order: 5000
 
 With [profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real user devices in production to give you a complete picture of how your application performs in a variety of environments.
 
-<Note>
+<Alert>
 
 Sentry profiling for .NET is available in _Alpha_ on .NET 6.0+ (tested on .NET 7.0 & .NET 8.0 as well) for:
 
@@ -18,7 +18,7 @@ Sentry profiling for .NET is available in _Alpha_ on .NET 6.0+ (tested on .NET 7
 - iOS
 - Mac Catalyst
 
-</Note>
+</Alert>
 
 ## Enable Profiling
 
diff --git a/docs/platforms/dotnet/common/tracing/index.mdx b/docs/platforms/dotnet/common/tracing/index.mdx
index 3e546f2bbeefb9..ab0235950858a5 100644
--- a/docs/platforms/dotnet/common/tracing/index.mdx
+++ b/docs/platforms/dotnet/common/tracing/index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 4000
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 ## Configure
 
diff --git a/docs/platforms/dotnet/common/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/dotnet/common/tracing/instrumentation/automatic-instrumentation.mdx
index 1a82c3110ad05e..809deac7185e87 100644
--- a/docs/platforms/dotnet/common/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/dotnet/common/tracing/instrumentation/automatic-instrumentation.mdx
@@ -6,11 +6,11 @@ sidebar_order: 20
 
 ## Propagating a Trace
 
-<Note>
+<Alert>
 
 If you are using Sentry's ASP.NET Core integration, trace propagation is enabled automatically on all clients created by an HTTP client factory. Read more about it <Link to="/platforms/dotnet/guides/aspnetcore/tracing/instrumentation/automatic-instrumentation">here</Link>.
 
-</Note>
+</Alert>
 
 Sentry SDK provides a custom HTTP handler, `SentryHttpMessageHandler`. This handler can be used inside `HttpClient` to automatically propagate traces and create spans to track outgoing requests.
 
diff --git a/docs/platforms/dotnet/common/tracing/instrumentation/custom-instrumentation/index.mdx b/docs/platforms/dotnet/common/tracing/instrumentation/custom-instrumentation/index.mdx
index a9e53aaa98de73..1ccb9b0eb02be4 100644
--- a/docs/platforms/dotnet/common/tracing/instrumentation/custom-instrumentation/index.mdx
+++ b/docs/platforms/dotnet/common/tracing/instrumentation/custom-instrumentation/index.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
diff --git a/docs/platforms/dotnet/common/usage/index.mdx b/docs/platforms/dotnet/common/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/dotnet/common/usage/index.mdx
+++ b/docs/platforms/dotnet/common/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/dotnet/common/user-feedback/index.mdx b/docs/platforms/dotnet/common/user-feedback/index.mdx
index c3ee3df48b1c1c..988f8f41f6d43f 100644
--- a/docs/platforms/dotnet/common/user-feedback/index.mdx
+++ b/docs/platforms/dotnet/common/user-feedback/index.mdx
@@ -8,11 +8,11 @@ When a user experiences an error, Sentry provides the ability to collect additio
 
 ## Use the .NET SDK
 
-<Note>
+<Alert>
 
 User Feedback for **[ASP.NET](/platforms/dotnet/guides/aspnet/user-feedback/#integration)** or **[ASP.NET Core](/platforms/dotnet/guides/aspnetcore/user-feedback/#integration)** supply integrations specific to supporting those SDKs.
 
-</Note>
+</Alert>
 
 You can create a form to collect the user input in your preferred framework, and use the SDK's API to send the information to Sentry. You can also use the widget, as described below. If you'd prefer an alternative to the widget or do not have a JavaScript frontend, you can use this API:
 
diff --git a/docs/platforms/dotnet/guides/aspnet/tracing/included-instrumentation.mdx b/docs/platforms/dotnet/guides/aspnet/tracing/included-instrumentation.mdx
index cfa08436a50d1b..5317a7f52e7e83 100644
--- a/docs/platforms/dotnet/guides/aspnet/tracing/included-instrumentation.mdx
+++ b/docs/platforms/dotnet/guides/aspnet/tracing/included-instrumentation.mdx
@@ -4,11 +4,11 @@ sidebar_order: 20
 description: "Learn what transactions are captured after tracing is enabled."
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already. You'll also need to enable the <PlatformLink to="/">base Sentry integration</PlatformLink>.
 
-</Note>
+</Alert>
 
 ASP.NET integration, once enabled, captures each incoming HTTP request and turns it into a transaction with the help of a custom middleware. To enable tracing on ASP.NET, you need to update your `Global.asax.cs` file like this:
 
diff --git a/docs/platforms/dotnet/guides/aspnetcore/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/dotnet/guides/aspnetcore/tracing/instrumentation/automatic-instrumentation.mdx
index 92bf14b84a9e45..91eceee63b0c77 100644
--- a/docs/platforms/dotnet/guides/aspnetcore/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/dotnet/guides/aspnetcore/tracing/instrumentation/automatic-instrumentation.mdx
@@ -4,11 +4,11 @@ sidebar_order: 20
 description: "Learn what transactions are captured after tracing is enabled."
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already. You'll also need to enable the <PlatformLink to="/">base Sentry integration for ASP.NET Core</PlatformLink>.
 
-</Note>
+</Alert>
 
 ### Server Integration
 
diff --git a/docs/platforms/dotnet/guides/azure-functions-worker/index.mdx b/docs/platforms/dotnet/guides/azure-functions-worker/index.mdx
index 95d9c34c1345cf..8a0a44c1fa1bae 100644
--- a/docs/platforms/dotnet/guides/azure-functions-worker/index.mdx
+++ b/docs/platforms/dotnet/guides/azure-functions-worker/index.mdx
@@ -34,11 +34,11 @@ This package extends [Sentry.Extensions.Logging](/platforms/dotnet/guides/extens
 Sentry integration with Azure Functions is done by calling `.UseSentry()` and specifying the options, for example:
 
 
-<Note>
+<Alert>
 
 If using the ASP.NET Core integration add `UseSentry` to the `ConfigureFunctionsWebApplication` call instead.
 
-</Note>
+</Alert>
 
 ```csharp {"onboardingOptions": {"performance": "11-13"}}
 using Sentry.Azure.Functions.Worker;
diff --git a/docs/platforms/dotnet/guides/extensions-logging/index.mdx b/docs/platforms/dotnet/guides/extensions-logging/index.mdx
index 4fb36bfd3ad3ad..944e253829c5a0 100644
--- a/docs/platforms/dotnet/guides/extensions-logging/index.mdx
+++ b/docs/platforms/dotnet/guides/extensions-logging/index.mdx
@@ -33,11 +33,11 @@ dotnet add package Sentry.Extensions.Logging -v {{@inject packages.version('sent
 
 This package extends `Sentry` main SDK. That means that besides the logging related features, through this package you'll also get access to all API and features available in the main `Sentry` SDK.
 
-<Note>
+<Alert>
 
 Messages logged from assemblies with the name starting with `Sentry` will not generate events.
 
-</Note>
+</Alert>
 
 ## Configure
 
@@ -119,11 +119,11 @@ More settings can be passed via the callback configuring the `SentryOptions`.
 
 In cases where `AddSentry` is called without arguments, it's worth noting that an overload exists where `SentryOptions` can be configured just like if `SentrySdk.Init` had been called.
 
-<Note>
+<Alert>
 
 The SDK needs to be initialized only once. If the `DSN` is made available to this integration, by default it **will** initialize the SDK. If you do not wish to initialize the SDK via this configuration, set the `InitializeSdk` flag to **false**. Not providing a DSN or leaving it as an _empty string_ will disable the SDK.
 
-</Note>
+</Alert>
 
 For example:
 
diff --git a/docs/platforms/dotnet/guides/log4net/index.mdx b/docs/platforms/dotnet/guides/log4net/index.mdx
index 5c6d087f1f0ea3..bb169eb4f02439 100644
--- a/docs/platforms/dotnet/guides/log4net/index.mdx
+++ b/docs/platforms/dotnet/guides/log4net/index.mdx
@@ -37,11 +37,11 @@ This can be done, for example, via the `app.config` for console and desktop apps
   </appender>
 ```
 
-<Note>
+<Alert>
 
 Only a subset of the options are exposed via the log4net appender configuration. If you wish to access an [SDK option](/platforms/dotnet/configuration/options/) which is not listed below, you'll need to initialize the SDK via [SentrySdk.Init](/platforms/dotnet/) instead of doing it via this integration as described below.
 
-</Note>
+</Alert>
 
 ### SendIdentity
 
diff --git a/docs/platforms/dotnet/guides/nlog/configuration/advanced-configuration-example.mdx b/docs/platforms/dotnet/guides/nlog/configuration/advanced-configuration-example.mdx
index ff09d773c7064a..4d0fe3d5432780 100644
--- a/docs/platforms/dotnet/guides/nlog/configuration/advanced-configuration-example.mdx
+++ b/docs/platforms/dotnet/guides/nlog/configuration/advanced-configuration-example.mdx
@@ -4,7 +4,7 @@ sidebar_order: 20
 description: "Review an advanced example of configuration for NLog."
 ---
 
-<Alert level="" title="NLog Layouts">
+<Alert title="NLog Layouts">
 
 For more information on how to dynamically set event data via `NLog.config`, see NLog's [layout renderer documentation](https://nlog-project.org/config/?tab=layout-renderers).
 
diff --git a/docs/platforms/dotnet/guides/nlog/index.mdx b/docs/platforms/dotnet/guides/nlog/index.mdx
index 93edc6653f5250..b17176d4ced468 100644
--- a/docs/platforms/dotnet/guides/nlog/index.mdx
+++ b/docs/platforms/dotnet/guides/nlog/index.mdx
@@ -41,7 +41,7 @@ Messages logged from assemblies with the name starting with `Sentry` will not ge
 
 ## Configure
 
-<Alert level="" title="NLog Layouts">
+<Alert title="NLog Layouts">
 
 For more information on how to dynamically set event data via `NLog.config`, see NLog's [layout renderer documentation](https://nlog-project.org/config/?tab=layout-renderers).
 
diff --git a/docs/platforms/dotnet/guides/serilog/index.mdx b/docs/platforms/dotnet/guides/serilog/index.mdx
index 19563e98f00e8c..bb96fcf6236a73 100644
--- a/docs/platforms/dotnet/guides/serilog/index.mdx
+++ b/docs/platforms/dotnet/guides/serilog/index.mdx
@@ -64,11 +64,11 @@ Log.Logger = new LoggerConfiguration()
   .CreateLogger();
 ```
 
-<Note>
+<Alert>
 
 The SDK only needs to be initialized once. If a `DSN` is made available to this integration, by default it **will** initialize the SDK. If you do not wish to initialize the SDK via this integration, set the `InitializeSdk` flag to **false**. Not providing a DSN or leaving it as `null` instructs the integration not to initialize the SDK and unless another integration initializes it or you call `SentrySdk.Init`, the SDK will stay disabled.
 
-</Note>
+</Alert>
 
 ### Options
 
diff --git a/docs/platforms/dotnet/guides/uwp/index.mdx b/docs/platforms/dotnet/guides/uwp/index.mdx
index ac0b502fad23ac..e109d9c452bc72 100644
--- a/docs/platforms/dotnet/guides/uwp/index.mdx
+++ b/docs/platforms/dotnet/guides/uwp/index.mdx
@@ -21,11 +21,11 @@ Select which Sentry features you'd like to install in addition to Error Monitori
 
 In addition to [initializing the SDK with `SentrySdk.Init`](/platforms/dotnet/), you must configure the UWP specific `Application.UnhandledException` and `Application.Suspending` events.
 
-<Note>
+<Alert>
 
 The SDK should be initialized in the constructor of your application class (usually `App.xaml.cs`). Do not initialize the SDK in the `OnLaunched` event of the application or the `Hub` will not be initialized correctly.
 
-</Note>
+</Alert>
 
 
 ```csharp {"onboardingOptions": {"performance": "18-21"}}
diff --git a/docs/platforms/dotnet/guides/winui/index.mdx b/docs/platforms/dotnet/guides/winui/index.mdx
index f204fe00979734..a77b9dcdebf467 100644
--- a/docs/platforms/dotnet/guides/winui/index.mdx
+++ b/docs/platforms/dotnet/guides/winui/index.mdx
@@ -21,11 +21,11 @@ Select which Sentry features you'd like to install in addition to Error Monitori
 
 If you don't have [Trimming](https://learn.microsoft.com/en-us/dotnet/core/deploying/trimming/trimming-options?pivots=dotnet-8-0) enabled when publishing your application then all you need to do is [initialize the SDK with `SentrySdk.Init`](/platforms/dotnet/) in the constructor of your application class (usually `App.xaml.cs`). Sentry's integration for WinUI will automatically capture any unhandled exceptions in your application and send these to Sentry.
 
-<Note>
+<Alert>
 
 Do not initialize the SDK in the `OnLaunched` event of the application or the `Hub` will not be initialized correctly.
 
-</Note>
+</Alert>
 
 
 In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/).
@@ -72,11 +72,11 @@ sealed partial class App : Application
 
 If you have [Trimming](https://learn.microsoft.com/en-us/dotnet/core/deploying/trimming/trimming-options?pivots=dotnet-8-0) enabled when publishing your application then, in addition to [initializing the SDK with `SentrySdk.Init`](/platforms/dotnet/), you must also configure an UnhandledException handler in the constructor of your application class (usually `App.xaml.cs`).
 
-<Note>
+<Alert>
 
 Do not initialize the SDK in the `OnLaunched` event of the application or the `Hub` will not be initialized correctly.
 
-</Note>
+</Alert>
 
 
 ```csharp
diff --git a/docs/platforms/dotnet/guides/wpf/index.mdx b/docs/platforms/dotnet/guides/wpf/index.mdx
index 10f67a71770f06..0a15066c38737d 100644
--- a/docs/platforms/dotnet/guides/wpf/index.mdx
+++ b/docs/platforms/dotnet/guides/wpf/index.mdx
@@ -21,11 +21,11 @@ Select which Sentry features you'd like to install in addition to Error Monitori
 
 In addition to [initializing the SDK with `SentrySdk.Init`](/platforms/dotnet/), you must configure the WPF specific error handler.
 
-<Note>
+<Alert>
 
 The SDK should be initialized in the constructor of your application class (usually `App.xaml.cs`). Do not initialize the SDK in the `OnStartup()` event of the application or the `Hub` will not be initialized correctly.
 
-</Note>
+</Alert>
 
 The SDK automatically handles `AppDomain.UnhandledException`. On WPF, for production apps (when no debugger is attached), WPF catches exception to show the dialog to the user. You can also configure your app to capture those exceptions before the dialog shows up:
 
diff --git a/docs/platforms/dotnet/guides/xamarin/data-management/apple-privacy-manifest.mdx b/docs/platforms/dotnet/guides/xamarin/data-management/apple-privacy-manifest.mdx
index 19f96a54510890..cabb53ef660b6f 100644
--- a/docs/platforms/dotnet/guides/xamarin/data-management/apple-privacy-manifest.mdx
+++ b/docs/platforms/dotnet/guides/xamarin/data-management/apple-privacy-manifest.mdx
@@ -4,15 +4,15 @@ description: "Troubleshoot and resolve common issues with the Apple Privacy Mani
 sidebar_order: 50
 ---
 
-<Note>
+<Alert>
 This guide requires [@sentry/xamarin@2.1.0](https://github.com/getsentry/sentry-xamarin/releases/tag/2.1.0) or newer.
-</Note>
+</Alert>
 
 Sentry's SDKs provide error and tracing for mobile applications running on Apple devices. To do this, the SDK needs to access certain information about the device and the application. Some of the APIs required for this are considered privacy-relevant by Apple. In order to submit apps to the App Store, Apple requires all apps - and libraries used within these apps - to provide privacy manifest files stating which APIs are used under which allowed reasons. For more details, read Apple's guidelines on [Describing use of required reason API](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api).
 
-<Note>
+<Alert>
 The information and steps in this guide are still being worked on and might change because of new tools or updated [Apple requirements](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files).
-</Note>
+</Alert>
 
 During the build process, the SDK will provide your project a privacy manifest file containing only the required information used by the SDK. If you are providing your own privacy manifest, you'll need to include the below rules in your `privacyinfo.xcprivacy` file. This guide will help you create the privacy manifest for your Xamarin applications.
 
diff --git a/docs/platforms/dotnet/guides/xamarin/troubleshooting.mdx b/docs/platforms/dotnet/guides/xamarin/troubleshooting.mdx
index df4a25607bd99b..7261a538b740c6 100644
--- a/docs/platforms/dotnet/guides/xamarin/troubleshooting.mdx
+++ b/docs/platforms/dotnet/guides/xamarin/troubleshooting.mdx
@@ -35,10 +35,10 @@ To solve this, you will need to follow the steps below:
 - `Visual Studio (Mac)`: Right-click on your iOS project and at the bottom, select the option `Edit Project File`.
 - `Visual Studio (Windows)`: Right-click on your iOS project, select the option `Unload Project`. By doing that action, it'll open your raw project solution, otherwise, right-click your iOS project and select the option `Edit project file`.
 
-<Note>
+<Alert>
   You can also use an external text editor or another IDE to edit your iOS
   project.
-</Note>
+</Alert>
 
 2. Locate the `ItemGroup` that contains `PackageReference`.
 
@@ -50,12 +50,12 @@ To solve this, you will need to follow the steps below:
 <PackageReference Include="System.Memory" Version="4.5.4" IncludeAssets="None" />
 ```
 
-<Note>
+<Alert>
   It's important to add the `IncludeAssets` as `None`, or this fix will not
   work.
-</Note>
+</Alert>
 
-<Note>Using Reference will not work, it must be PackageReference.</Note>
+<Alert>sing Reference will not work, it must be PackageReference.</Alert>
 
 4. Save the edited `csproj` file and reload your project if it was unloaded:
 
diff --git a/docs/platforms/dotnet/index.mdx b/docs/platforms/dotnet/index.mdx
index 06be7c279f3f41..328b93aceecbfb 100644
--- a/docs/platforms/dotnet/index.mdx
+++ b/docs/platforms/dotnet/index.mdx
@@ -8,11 +8,11 @@ aliases:
   - C#
 ---
 
-<Note>
+<Alert>
 
 If you don't already have an account and Sentry project established, head over to [sentry.io](https://sentry.io/signup/), then return to this page.
 
-</Note>
+</Alert>
 
 You can use these instructions to run Sentry in an app running on:
 
@@ -54,11 +54,11 @@ Install the **NuGet** package to add the Sentry dependency:
 
 <OnboardingOption optionId="profiling">
 
-  <Note>
+  <Alert>
 
   Sentry profiling for .NET is available in Alpha on .NET 6.0 and newer.
 
-  </Note>
+  </Alert>
 
   ```shell {tabTitle:.NET Core CLI}
   dotnet add package Sentry -v {{@inject packages.version('sentry.dotnet') }}
@@ -66,7 +66,7 @@ Install the **NuGet** package to add the Sentry dependency:
   ```
 
   ```powershell {tabTitle:Package Manager}
-  Install-Package Sentry -Version {{@inject packages.version('sentry.dotnet') }}  
+  Install-Package Sentry -Version {{@inject packages.version('sentry.dotnet') }}
   Install-Package Sentry.Profiling -Version {{@inject packages.version('sentry.dotnet.profiling') }}
   ```
 
diff --git a/docs/platforms/elixir/configuration/releases.mdx b/docs/platforms/elixir/configuration/releases.mdx
index babb58d14dcbdf..3040ef122baf1d 100644
--- a/docs/platforms/elixir/configuration/releases.mdx
+++ b/docs/platforms/elixir/configuration/releases.mdx
@@ -29,11 +29,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
diff --git a/docs/platforms/elixir/data-management/sensitive-data/index.mdx b/docs/platforms/elixir/data-management/sensitive-data/index.mdx
index 8712656e07c427..10a33925792646 100644
--- a/docs/platforms/elixir/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/elixir/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 If you _do not_ wish to use the default PII behavior, you can also choose to identify users in a more controlled manner, using our [user identity context](../../enriching-events/identify-user/).
 
diff --git a/docs/platforms/elixir/enriching-events/breadcrumbs/index.mdx b/docs/platforms/elixir/enriching-events/breadcrumbs/index.mdx
index d09de40983e636..8af656caaa6a46 100644
--- a/docs/platforms/elixir/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/elixir/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/elixir/enriching-events/context/index.mdx b/docs/platforms/elixir/enriching-events/context/index.mdx
index 491b30006b8067..58466e0238a1ea 100644
--- a/docs/platforms/elixir/enriching-events/context/index.mdx
+++ b/docs/platforms/elixir/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/elixir/enriching-events/identify-user/index.mdx b/docs/platforms/elixir/enriching-events/identify-user/index.mdx
index 6d5e03315faeeb..739f85c1647aff 100644
--- a/docs/platforms/elixir/enriching-events/identify-user/index.mdx
+++ b/docs/platforms/elixir/enriching-events/identify-user/index.mdx
@@ -9,11 +9,11 @@ Users consist of a few critical pieces of information that construct a unique id
 
 ### `id`
 
-<Note>
+<Alert>
 
 If you don't provide an `id`, the SDK falls back to `installationId`, which the SDK randomly generates once during an app's installation.
 
-</Note>
+</Alert>
 
 Your internal identifier for the user.
 
diff --git a/docs/platforms/elixir/enriching-events/tags/index.mdx b/docs/platforms/elixir/enriching-events/tags/index.mdx
index 8035c211bf7cd3..d0595213f5689d 100644
--- a/docs/platforms/elixir/enriching-events/tags/index.mdx
+++ b/docs/platforms/elixir/enriching-events/tags/index.mdx
@@ -15,11 +15,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/elixir/index.mdx b/docs/platforms/elixir/index.mdx
index dd86c1a4f67841..8b721803cfcc83 100644
--- a/docs/platforms/elixir/index.mdx
+++ b/docs/platforms/elixir/index.mdx
@@ -9,9 +9,9 @@ showIntegrationsInSearch: true
 
 On this page, we get you up and running with Sentry's SDK.
 
-<Note>
+<Alert>
   You don't have an account and Sentry project established? Head over to [sentry.io](https://sentry.io/signup/), then return to this page.
-</Note>
+</Alert>
 
 ## Install
 
@@ -31,10 +31,10 @@ This snippet includes an intentional error, so you can test that everything is w
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
diff --git a/docs/platforms/elixir/integrations/oban/index.mdx b/docs/platforms/elixir/integrations/oban/index.mdx
index eec0c5832ac3ab..daad53002a50c2 100644
--- a/docs/platforms/elixir/integrations/oban/index.mdx
+++ b/docs/platforms/elixir/integrations/oban/index.mdx
@@ -33,7 +33,7 @@ config :sentry,
 
 This configuration will report failed Oban jobs to Sentry. It will also report started, completed, and failed jobs, as well as their duration. It will use the worker name as the `monitor_slug` of the reported cron.
 
-<Alert level="info" title="Perform Errors">
+<Alert title="Perform Errors">
 Oban wraps *unhandled* crashes, exits, and throws in jobs inside [`Oban.CrashError`](https://hexdocs.pm/oban/2.18.0/Oban.CrashError.html) exceptions. However, if jobs return errors manually (such as by returning `{:error, reason}` tuples) then Oban will wrap those inside [`Oban.PerformError`](https://hexdocs.pm/oban/2.18.0/Oban.PerformError.html) exceptions. If you only want to report crashes to Sentry, you can either configure an event filter that doesn't report `Oban.PerformError` events, or that inspects its `:reason` field to determine whether to report them. For example:
 
 ```elixir
diff --git a/docs/platforms/elixir/usage/index.mdx b/docs/platforms/elixir/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/elixir/usage/index.mdx
+++ b/docs/platforms/elixir/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/flutter/configuration/options.mdx b/docs/platforms/flutter/configuration/options.mdx
index ef94188d858a05..17fd8a345bd129 100644
--- a/docs/platforms/flutter/configuration/options.mdx
+++ b/docs/platforms/flutter/configuration/options.mdx
@@ -95,11 +95,11 @@ Grouping in Sentry is different for events with stack traces and without. As a r
 
 If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This option is turned off by default.
 
@@ -320,10 +320,10 @@ Set this boolean to `false` to disable auto [tracing](/product/performance/) tra
 
 <ConfigKey name="enableWatchdogTerminationTracking">
 
-<Note>
+<Alert>
   Available since version 8.0.0 of Sentry Apple SDK. It was named
   `enableOutOfMemoryTracking` before the 8.0.0 release.
-</Note>
+</Alert>
 
 Set this boolean to `false` to disable [watchdog termination](/platforms/apple/guides/ios/configuration/watchdog-terminations/) tracking on iOS.
 
diff --git a/docs/platforms/flutter/configuration/releases.mdx b/docs/platforms/flutter/configuration/releases.mdx
index 7e60fca65b4029..c74240c30745f6 100644
--- a/docs/platforms/flutter/configuration/releases.mdx
+++ b/docs/platforms/flutter/configuration/releases.mdx
@@ -29,11 +29,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -64,11 +64,11 @@ Monitor the [health of releases](/product/releases/health/) by observing user ad
 
 In order to monitor release health, the SDK sends session data.
 
-<Note>
+<Alert>
 
 Release health in Flutter is only available for Android, iOS, and macOS.
 
-</Note>
+</Alert>
 
 ### Sessions
 
diff --git a/docs/platforms/flutter/configuration/sampling.mdx b/docs/platforms/flutter/configuration/sampling.mdx
index 322d5ba1034f72..9e06bc53fd237b 100644
--- a/docs/platforms/flutter/configuration/sampling.mdx
+++ b/docs/platforms/flutter/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
diff --git a/docs/platforms/flutter/data-management/apple-privacy-manifest.mdx b/docs/platforms/flutter/data-management/apple-privacy-manifest.mdx
index 98e5d58a3ffca8..661c23cf49b459 100644
--- a/docs/platforms/flutter/data-management/apple-privacy-manifest.mdx
+++ b/docs/platforms/flutter/data-management/apple-privacy-manifest.mdx
@@ -4,15 +4,15 @@ description: "Troubleshoot and resolve common issues with the Apple Privacy Mani
 sidebar_order: 50
 ---
 
-<Note>
+<Alert>
 This guide requires [@sentry/dart@7.20.1](https://github.com/getsentry/sentry-dart/releases/tag/7.20.1) or newer.
-</Note>
+</Alert>
 
 Sentry's SDKs provide error and tracing for mobile applications running on Apple devices. To do this, the SDK needs to access certain information about the device and the application. Some of the APIs required for this are considered privacy-relevant by Apple. In order to submit apps to the App Store, Apple requires all apps - and libraries used within these apps - to provide privacy manifest files stating which APIs are used under which allowed reasons. For more details, read Apple's guidelines on [Describing use of required reason API](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api).
 
-<Note>
+<Alert>
 The information and steps in this guide are still being worked on and might change because of new tools or updated [Apple requirements](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files).
-</Note>
+</Alert>
 
 If you are using dynamically linked frameworks, which is the default for Flutter applications, Apple will automatically process the SDK's privacy manifest. If you are using statically linked libraries, you need to provide the privacy manifest yourself. This guide will help you create the privacy manifest for your Flutter applications.
 
diff --git a/docs/platforms/flutter/data-management/debug-files/file-formats/index.mdx b/docs/platforms/flutter/data-management/debug-files/file-formats/index.mdx
index dd5d74925a8b3a..36d5129dc617d3 100644
--- a/docs/platforms/flutter/data-management/debug-files/file-formats/index.mdx
+++ b/docs/platforms/flutter/data-management/debug-files/file-formats/index.mdx
@@ -180,11 +180,11 @@ while removing all debug information from the release binary.
 
 ## ProGuard Mappings
 
-<Note>
+<Alert>
 
 The recommended method for [Android users is to use the Gradle plugin](/platforms/android/configuration/gradle/).
 
-</Note>
+</Alert>
 
 ProGuard mapping files allow Sentry to resolve obfuscated Java classpaths and
 method names into their original form. In that sense, they act as debug
diff --git a/docs/platforms/flutter/data-management/debug-files/identifiers/index.mdx b/docs/platforms/flutter/data-management/debug-files/identifiers/index.mdx
index aebce9d77c7593..ea0293898bdd60 100644
--- a/docs/platforms/flutter/data-management/debug-files/identifiers/index.mdx
+++ b/docs/platforms/flutter/data-management/debug-files/identifiers/index.mdx
@@ -24,14 +24,14 @@ compute a _Debug Identifier_ for each uploaded file. This identifier is
 associated with executables and libraries as well as debug companions to ensure
 that they can be uniquely located via one common mechanism.
 
-<Note>
+<Alert>
 
 Debug information does not have to be associated with releases. The unique debug
 identifier ensures that Sentry can choose the right files for every crash
 report. However, it is still recommended to configure releases in the client to
 benefit from other features.
 
-</Note>
+</Alert>
 
 For native events, the issue details page displays a list of _Loaded Images_.
 This list contains the executable and all loaded dynamic libraries including
diff --git a/docs/platforms/flutter/data-management/debug-files/index.mdx b/docs/platforms/flutter/data-management/debug-files/index.mdx
index b5a401b9febf2e..76457d462212fa 100644
--- a/docs/platforms/flutter/data-management/debug-files/index.mdx
+++ b/docs/platforms/flutter/data-management/debug-files/index.mdx
@@ -24,12 +24,12 @@ the following formats:
 - [_ProGuard mappings_](./file-formats/#proguard-mappings) for
   Java and Android
 
-<Note>
+<Alert>
 
 Source maps, while also being debug information files, are handled
 differently in Sentry. For more information see [Source Maps in sentry-cli](/cli/releases/#sentry-cli-sourcemaps).
 
-</Note>
+</Alert>
 
 Sentry requires access to debug information files of your application as well as
 system libraries to provide fully symbolicated crash reports. You can either
@@ -46,11 +46,11 @@ for automatic downloads.
 From the [Project Details](/product/projects/project-details/) page, click into settings,
 then click on _Debug Files_ in the page navigation.
 
-<Note>
+<Alert>
 
 ProGuard files are listed separately, in the _ProGuard_ section of the project settings page.
 
-</Note>
+</Alert>
 
 ## Retention Policy
 
diff --git a/docs/platforms/flutter/data-management/debug-files/source-context/index.mdx b/docs/platforms/flutter/data-management/debug-files/source-context/index.mdx
index 0e3997027df095..df195309dc364a 100644
--- a/docs/platforms/flutter/data-management/debug-files/source-context/index.mdx
+++ b/docs/platforms/flutter/data-management/debug-files/source-context/index.mdx
@@ -20,11 +20,11 @@ needs to be uploaded alongside the debug information files.
 The recommended way to do this is by using `sentry-cli`.
 See [Creating Source Bundles](/cli/dif/#creating-source-bundles) for more information.
 
-<Note>
+<Alert>
 
 For Flutter Android, iOS, and macOS, follow the instructions in the [Debug Symbols](/platforms/flutter/upload-debug/#uploading-source-code-context-for-flutter-android-ios-and-macos) guide.
 
-</Note>
+</Alert>
 
 After they've been uploaded you can review and manage source bundles the same as
 any other debug information file. See [Managing Debug Information Files](../#managing-debug-information-files).
diff --git a/docs/platforms/flutter/data-management/debug-files/symbol-servers/index.mdx b/docs/platforms/flutter/data-management/debug-files/symbol-servers/index.mdx
index 70c5456cbe8c1c..2a17fe0c23bd73 100644
--- a/docs/platforms/flutter/data-management/debug-files/symbol-servers/index.mdx
+++ b/docs/platforms/flutter/data-management/debug-files/symbol-servers/index.mdx
@@ -42,7 +42,7 @@ Beware that these cause notifications to your team members.
 
 ## Custom Repositories
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 Custom repositories are available for organizations on the _Business_ and
 _Enterprise_ plans.
diff --git a/docs/platforms/flutter/data-management/sensitive-data/index.mdx b/docs/platforms/flutter/data-management/sensitive-data/index.mdx
index 8712656e07c427..10a33925792646 100644
--- a/docs/platforms/flutter/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/flutter/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 If you _do not_ wish to use the default PII behavior, you can also choose to identify users in a more controlled manner, using our [user identity context](../../enriching-events/identify-user/).
 
diff --git a/docs/platforms/flutter/enriching-events/attachments/index.mdx b/docs/platforms/flutter/enriching-events/attachments/index.mdx
index 2985c7acf86b4a..df53d17d50821a 100644
--- a/docs/platforms/flutter/enriching-events/attachments/index.mdx
+++ b/docs/platforms/flutter/enriching-events/attachments/index.mdx
@@ -47,11 +47,11 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <PlatformContent includePath="enriching-events/attachment-upload" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/flutter/enriching-events/breadcrumbs/index.mdx b/docs/platforms/flutter/enriching-events/breadcrumbs/index.mdx
index 65ee11d1ef2c98..8c0e4e7c0e248d 100644
--- a/docs/platforms/flutter/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/flutter/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/flutter/enriching-events/context/index.mdx b/docs/platforms/flutter/enriching-events/context/index.mdx
index dd07e216bbb9f9..36da3d54f75935 100644
--- a/docs/platforms/flutter/enriching-events/context/index.mdx
+++ b/docs/platforms/flutter/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/flutter/enriching-events/scopes/index.mdx b/docs/platforms/flutter/enriching-events/scopes/index.mdx
index 773027b863d423..e9e7092403833c 100644
--- a/docs/platforms/flutter/enriching-events/scopes/index.mdx
+++ b/docs/platforms/flutter/enriching-events/scopes/index.mdx
@@ -72,7 +72,7 @@ made will stay isolated within the callback function. This allows you to
 more easily isolate pieces of context information to specific locations in your code or
 even call `clear` to briefly remove all context information.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 Any exceptions that occur within the callback function for configuring a local scope will not be
 caught, and all errors that occur will be silently ignored and **not** reported.
diff --git a/docs/platforms/flutter/enriching-events/tags/index.mdx b/docs/platforms/flutter/enriching-events/tags/index.mdx
index 5707e7b98110ca..9657816853afb2 100644
--- a/docs/platforms/flutter/enriching-events/tags/index.mdx
+++ b/docs/platforms/flutter/enriching-events/tags/index.mdx
@@ -17,11 +17,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/flutter/enriching-events/viewhierarchy/index.mdx b/docs/platforms/flutter/enriching-events/viewhierarchy/index.mdx
index ba601c80a9b085..4752546ea382d5 100644
--- a/docs/platforms/flutter/enriching-events/viewhierarchy/index.mdx
+++ b/docs/platforms/flutter/enriching-events/viewhierarchy/index.mdx
@@ -9,11 +9,11 @@ Sentry makes it possible to render a JSON representation of the view hierarchy o
 
 This feature only applies to SDKs with a user interface, such as the ones for mobile and desktop applications. In some environments like native iOS, rendering the view hierarchy requires the UI thread and in the event of a crash, that might not be available. Another example where the view hierarchy might not be available is when the event happens before the screen starts to load. So inherently, this feature is a best effort solution.
 
-<Note>
+<Alert>
 
 Deobfuscation for view hierarchies is fully supported for native SDKs, and React Native, but is currently not supported for Flutter.
 
-</Note>
+</Alert>
 
 ## Enabling View Hierarchy Attachments
 
@@ -23,11 +23,11 @@ View hierarchy debugging is an opt-in feature. You can enable it as shown below:
 
 ### Customize View Hierarchy Capturing
 
-<Note>
+<Alert>
 
 Requires SDK version `8.13.0` or higher.
 
-</Note>
+</Alert>
 
 Capturing view hierarchies on Flutter is limited to once every 2 seconds by default to minimize performance impact. While this debounce interval is fixed, you can override individual capture decisions by implementing the `beforeCaptureViewHierarchy` option in your `SentryFlutterOptions`.
 
diff --git a/docs/platforms/flutter/index.mdx b/docs/platforms/flutter/index.mdx
index 195ab2adccf56a..a7b4b0143e7223 100644
--- a/docs/platforms/flutter/index.mdx
+++ b/docs/platforms/flutter/index.mdx
@@ -13,11 +13,11 @@ categories:
 
 On this page, we get you up and running with Sentry's Flutter SDK.
 
-<Note>
+<Alert>
 
 If you don't already have an account and Sentry project established, head over to [sentry.io](https://sentry.io/signup/), then return to this page.
 
-</Note>
+</Alert>
 
 ## Features
 
diff --git a/docs/platforms/flutter/integrations/app-start-instrumentation.mdx b/docs/platforms/flutter/integrations/app-start-instrumentation.mdx
index 23f7f85e9873a9..c4654a5059cc61 100644
--- a/docs/platforms/flutter/integrations/app-start-instrumentation.mdx
+++ b/docs/platforms/flutter/integrations/app-start-instrumentation.mdx
@@ -10,11 +10,11 @@ categories:
 
 Sentry's app start instrumentation provides insight into how long your application takes to launch.
 
-<Note>
+<Alert>
 
 App start instrumentation is available on **iOS** and **Android**.
 
-</Note>
+</Alert>
 
 ## Instrumentation Behaviour
 
@@ -27,11 +27,11 @@ When the SDK receives the start and end times of the app launch, the SDK:
 - Attaches a span with either `app.start.cold` or `app.start.warm` operation
 - Adds app start metrics to the transaction
 
-<Note>
+<Alert>
 
 While the SDK differentiates between cold and warm starts, it doesn't track hot starts/resumes.
 
-</Note>
+</Alert>
 
 ## Prerequisites
 
diff --git a/docs/platforms/flutter/integrations/routing-instrumentation.mdx b/docs/platforms/flutter/integrations/routing-instrumentation.mdx
index d95e5173770c9b..c7103143a8de7d 100644
--- a/docs/platforms/flutter/integrations/routing-instrumentation.mdx
+++ b/docs/platforms/flutter/integrations/routing-instrumentation.mdx
@@ -11,11 +11,11 @@ categories:
 Sentry's routing instrumentation for Flutter automatically tracks and reports page navigation events in your app.
 It supports both [traditional Flutter routing](https://docs.flutter.dev/ui/navigation) and the [GoRouter](https://pub.dev/packages/go_router) package.
 
-<Note>
+<Alert>
 
 The routing instrumentation feature is shipped with Sentry's Flutter SDK automatically.
 
-</Note>
+</Alert>
 
 ## Prerequisites
 
diff --git a/docs/platforms/flutter/integrations/slow-and-frozen-frames-instrumentation.mdx b/docs/platforms/flutter/integrations/slow-and-frozen-frames-instrumentation.mdx
index f4a79aa9527114..112887b3b771b1 100644
--- a/docs/platforms/flutter/integrations/slow-and-frozen-frames-instrumentation.mdx
+++ b/docs/platforms/flutter/integrations/slow-and-frozen-frames-instrumentation.mdx
@@ -12,11 +12,11 @@ Unresponsive UI and animation hitches annoy users and degrade the user experienc
 This integration can help. Set it up and identify these problems in your app by tracking and showing **slow frames**, **frozen frames**, and **frame delay** metrics for spans.
 Learn more about frame delay [here](https://develop.sentry.dev/sdk/performance/frames-delay/).
 
-<Note>
+<Alert>
 
 Frames tracking instrumentation is available on **iOS**, **macOS** and **Android**.
 
-</Note>
+</Alert>
 
 ## Instrumentation Behaviour
 
diff --git a/docs/platforms/flutter/metrics/index.mdx b/docs/platforms/flutter/metrics/index.mdx
index b9ab11be0d4744..f12931e2ccfc42 100644
--- a/docs/platforms/flutter/metrics/index.mdx
+++ b/docs/platforms/flutter/metrics/index.mdx
@@ -7,11 +7,11 @@ sidebar_hidden: true
 
 <Include name="metrics-api-change.mdx" />
 
-<Note>
+<Alert>
 
 Metrics are supported with Sentry Flutter SDK version `7.19.0` and above.
 
-</Note>
+</Alert>
 
 Sentry metrics help you pinpoint and solve issues that impact user experience and app performance by measuring the data points that are important to you. You can track things like processing time, event size, user signups, and conversion rates, then correlate them back to tracing data in order to get deeper insights and solve issues faster.
 
diff --git a/docs/platforms/flutter/profiling/index.mdx b/docs/platforms/flutter/profiling/index.mdx
index 74fcb42a6144f7..13a20a62d21e7c 100644
--- a/docs/platforms/flutter/profiling/index.mdx
+++ b/docs/platforms/flutter/profiling/index.mdx
@@ -9,11 +9,11 @@ sidebar_order: 5000
 
 The profiling feature captures profiles across multiple language layers, including native languages (such as Swift and Objective-C) as well as Dart.
 
-<Note>
+<Alert>
 
 Flutter Profiling alpha is available for **iOS** and **macOS** since SDK version `7.12.0`.
 
-</Note>
+</Alert>
 
 ## Enable Tracing
 
diff --git a/docs/platforms/flutter/session-replay/index.mdx b/docs/platforms/flutter/session-replay/index.mdx
index e5c1fbef33f86d..f25ebcbf102885 100644
--- a/docs/platforms/flutter/session-replay/index.mdx
+++ b/docs/platforms/flutter/session-replay/index.mdx
@@ -5,11 +5,11 @@ notSupported:
 description: "Learn how to enable Session Replay in your mobile app."
 ---
 
-<Note>
+<Alert>
 
 Flutter Session Replay is available on **iOS** and **Android**. This SDK support is still experimental as we iron out any bugs that are reported. If you encounter any issues please let us know via a GitHub ticket.
 
-</Note>
+</Alert>
 
 [Session Replay](/product/explore/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a reproduction of what was happening in the user's device before, during, and after the issue. You can rewind and replay your application's state and see key user interactions, like taps, swipes, network requests, and console entries, in a single UI.
 
diff --git a/docs/platforms/flutter/tracing/index.mdx b/docs/platforms/flutter/tracing/index.mdx
index 3c8f0ff00637c7..cb90064ed57b21 100644
--- a/docs/platforms/flutter/tracing/index.mdx
+++ b/docs/platforms/flutter/tracing/index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 4000
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 ## Configure
 
diff --git a/docs/platforms/flutter/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/flutter/tracing/instrumentation/automatic-instrumentation.mdx
index 45134cbb4ddf85..9e869e4ab3be94 100644
--- a/docs/platforms/flutter/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/flutter/tracing/instrumentation/automatic-instrumentation.mdx
@@ -4,11 +4,11 @@ description: "Learn what transactions are captured after tracing is enabled."
 sidebar_order: 10
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already.
 
-</Note>
+</Alert>
 
 ### Routing
 
diff --git a/docs/platforms/flutter/tracing/instrumentation/custom-instrumentation.mdx b/docs/platforms/flutter/tracing/instrumentation/custom-instrumentation.mdx
index ff29395a8e6d49..7dcbb97cc96997 100644
--- a/docs/platforms/flutter/tracing/instrumentation/custom-instrumentation.mdx
+++ b/docs/platforms/flutter/tracing/instrumentation/custom-instrumentation.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
diff --git a/docs/platforms/flutter/upload-debug.mdx b/docs/platforms/flutter/upload-debug.mdx
index 1ef2ee76c73be9..4b26b317d3b5a5 100644
--- a/docs/platforms/flutter/upload-debug.mdx
+++ b/docs/platforms/flutter/upload-debug.mdx
@@ -10,11 +10,11 @@ We offer a range of methods to provide Sentry with debug symbols so that you can
 
 With default settings, complete stack traces are available in your Dart error, out of the box, unless you use [`split-debug-info`](https://flutter.dev/docs/perf/app-size#reducing-app-size) and [`obfuscate`](https://flutter.dev/docs/deployment/obfuscate). In those cases, you need to upload the debug information files generated by the `flutter` build, so Sentry can show you proper stack traces.
 
-<Note>
+<Alert>
 
 For Flutter Desktop (Windows/Linux) `split-debug-info` and `obfuscate` flags are not supported yet. See this [issue](https://github.com/getsentry/sentry-dart/issues/433).
 
-</Note>
+</Alert>
 
 Errors raised from the native layer in Flutter apps require certain debug information files to be uploaded. For example, an Android app can use `proguard` for minification and obfuscation. And when using NDK, dwarf debug files need to be uploaded. Flutter Web requires sourcemaps and iOS apps also require dwarf debug information files.
 
@@ -44,11 +44,11 @@ sentry:
   auth_token: ___ORG_AUTH_TOKEN___
 ```
 
-<Note>
+<Alert>
 
 The option `upload_debug_symbols` is enabled by default. That means the plugin will automatically upload debug symbols for all platforms except Flutter Web.
 
-</Note>
+</Alert>
 
 #### Source Maps
 
@@ -75,12 +75,12 @@ sentry:
 
 ```
 
-<Note>
+<Alert>
 
 This uploads the source files of the Dart/Flutter code, not the native code.
 If you want to use source context for native code, you need to setup source context in the respective native platform.
 
-</Note>
+</Alert>
 
 In addition to configuring the plugin in the `pubspec.yaml` file, the plugin supports using a properties file or environment variables.
 For more information, read the [Sentry Dart Plugin README](https://github.com/getsentry/sentry-dart-plugin/tree/main?tab=readme-ov-file#configuration-optional).
@@ -100,11 +100,11 @@ For an obfuscated build:
 - `flutter build ios --obfuscate --split-debug-info=<output-directory>`
 - `flutter build macos --obfuscate --split-debug-info=<output-directory>`
 
-<Note>
+<Alert>
 
 For Flutter web run `flutter build web --release --source-maps` to generate source maps.
 
-</Note>
+</Alert>
 
 ### 4. Run
 
@@ -114,11 +114,11 @@ Now we can run the plugin to upload the debug symbols, source maps, and sources
 flutter packages pub run sentry_dart_plugin
 ```
 
-<Note>
+<Alert>
 
 If you choose not to obfuscate your build, the plugin will not upload debug symbols but will still configure source context if enabled.
 
-</Note>
+</Alert>
 
 ### Proguard
 
@@ -167,11 +167,11 @@ See our docs on uploading [Debug Information Files](/cli/dif/#uploading-files) m
 
 If you're using a version of `sentry_flutter` earlier than 5.1, native symbolication on Android requires a specific configuration. Refer to [Troubleshooting](/platforms/flutter/troubleshooting/#native-symbolication-on-android) for more information.
 
-<Note>
+<Alert>
 
 Sentry's Flutter SDK doesn't currently support the `uploadNativeSymbols` flag from the [Sentry Gradle Plugin](/platforms/android/configuration/gradle/).
 
-</Note>
+</Alert>
 
 ### Web
 
diff --git a/docs/platforms/flutter/usage/index.mdx b/docs/platforms/flutter/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/flutter/usage/index.mdx
+++ b/docs/platforms/flutter/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/go/common/configuration/releases.mdx b/docs/platforms/go/common/configuration/releases.mdx
index babb58d14dcbdf..3040ef122baf1d 100644
--- a/docs/platforms/go/common/configuration/releases.mdx
+++ b/docs/platforms/go/common/configuration/releases.mdx
@@ -29,11 +29,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
diff --git a/docs/platforms/go/common/configuration/sampling.mdx b/docs/platforms/go/common/configuration/sampling.mdx
index bc66495c366656..e714c315cfb2b9 100644
--- a/docs/platforms/go/common/configuration/sampling.mdx
+++ b/docs/platforms/go/common/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
diff --git a/docs/platforms/go/common/data-management/sensitive-data/index.mdx b/docs/platforms/go/common/data-management/sensitive-data/index.mdx
index 8712656e07c427..10a33925792646 100644
--- a/docs/platforms/go/common/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/go/common/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 If you _do not_ wish to use the default PII behavior, you can also choose to identify users in a more controlled manner, using our [user identity context](../../enriching-events/identify-user/).
 
diff --git a/docs/platforms/go/common/enriching-events/attachments/index.mdx b/docs/platforms/go/common/enriching-events/attachments/index.mdx
index c963923aca4d85..71226bde55ed97 100644
--- a/docs/platforms/go/common/enriching-events/attachments/index.mdx
+++ b/docs/platforms/go/common/enriching-events/attachments/index.mdx
@@ -3,11 +3,11 @@ title: Attachments
 description: "Learn more about how Sentry can store additional files in the same request as event attachments."
 ---
 
-<Note>
+<Alert>
 
 Attachments are supported in `sentry-go` version `0.23.0` and above.
 
-</Note>
+</Alert>
 
 Sentry can enrich your events for further investigation by storing additional files, such as config or log files, as attachments.
 
@@ -15,11 +15,11 @@ Sentry can enrich your events for further investigation by storing additional fi
 
 <PlatformContent includePath="enriching-events/add-attachment" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/go/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/go/common/enriching-events/breadcrumbs/index.mdx
index 65ee11d1ef2c98..8c0e4e7c0e248d 100644
--- a/docs/platforms/go/common/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/go/common/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/go/common/enriching-events/context/index.mdx b/docs/platforms/go/common/enriching-events/context/index.mdx
index dd07e216bbb9f9..36da3d54f75935 100644
--- a/docs/platforms/go/common/enriching-events/context/index.mdx
+++ b/docs/platforms/go/common/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/go/common/enriching-events/tags/index.mdx b/docs/platforms/go/common/enriching-events/tags/index.mdx
index 5707e7b98110ca..9657816853afb2 100644
--- a/docs/platforms/go/common/enriching-events/tags/index.mdx
+++ b/docs/platforms/go/common/enriching-events/tags/index.mdx
@@ -17,11 +17,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/go/common/index.mdx b/docs/platforms/go/common/index.mdx
index 5eee98f614226d..4179c4a200eee8 100644
--- a/docs/platforms/go/common/index.mdx
+++ b/docs/platforms/go/common/index.mdx
@@ -26,10 +26,10 @@ This snippet includes an intentional error, so you can test that everything is w
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
diff --git a/docs/platforms/go/common/tracing/index.mdx b/docs/platforms/go/common/tracing/index.mdx
index b8dac419bd1ec0..910426706976bc 100644
--- a/docs/platforms/go/common/tracing/index.mdx
+++ b/docs/platforms/go/common/tracing/index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 4000
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 <Include name="opentelemetry-available.mdx" />
 
diff --git a/docs/platforms/go/common/tracing/instrumentation/custom-instrumentation/index.mdx b/docs/platforms/go/common/tracing/instrumentation/custom-instrumentation/index.mdx
index a9e53aaa98de73..1ccb9b0eb02be4 100644
--- a/docs/platforms/go/common/tracing/instrumentation/custom-instrumentation/index.mdx
+++ b/docs/platforms/go/common/tracing/instrumentation/custom-instrumentation/index.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
diff --git a/docs/platforms/go/common/tracing/instrumentation/custom-instrumentation/queues-module.mdx b/docs/platforms/go/common/tracing/instrumentation/custom-instrumentation/queues-module.mdx
index 4f515d5f2b9792..36da51567ef07c 100644
--- a/docs/platforms/go/common/tracing/instrumentation/custom-instrumentation/queues-module.mdx
+++ b/docs/platforms/go/common/tracing/instrumentation/custom-instrumentation/queues-module.mdx
@@ -31,7 +31,7 @@ messageId := "abc123"
 // Create transaction
 transaction := sentry.StartTransaction(
     ctx,
-    "queue_producer_transaction,
+    "queue_producer_transaction",
     options...,
 )
 defer transaction.Finish()
diff --git a/docs/platforms/go/common/usage/index.mdx b/docs/platforms/go/common/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/go/common/usage/index.mdx
+++ b/docs/platforms/go/common/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/index.mdx b/docs/platforms/index.mdx
index 2211c96d30bfdb..80cc8ca4d4f540 100644
--- a/docs/platforms/index.mdx
+++ b/docs/platforms/index.mdx
@@ -8,7 +8,7 @@ Sentry provides code-level observability that makes it easy to diagnose issues a
 
 If your use case is very specific, or not covered by Sentry, you'll find documentation on how to report events on your own using our [SDK API](https://develop.sentry.dev/sdk/overview/).
 
-<Note>
+<Alert>
 
 It's considered bad practice to use Sentry SDKs in third-party plugins, packages, and libraries (such as payment SDKs or embeddable widgets) meant to be consumed by other apps. If an app uses a Sentry SDK in addition to a third-party package with its own Sentry SDK installed, the following issues can occur:
 
@@ -18,7 +18,7 @@ It's considered bad practice to use Sentry SDKs in third-party plugins, packages
 
 We also <Link to="https://sentry.zendesk.com/hc/en-us/articles/23961784367387">discourage using Sentry alongside other APM tools</Link> because it can lead to a number of side-effects that negatively impact performance and stability of the application.
 
-</Note>
+</Alert>
 
 <PlatformFilter />
 
diff --git a/docs/platforms/java/common/configuration/options.mdx b/docs/platforms/java/common/configuration/options.mdx
index 80356f85d070b2..a139e9da4f1db2 100644
--- a/docs/platforms/java/common/configuration/options.mdx
+++ b/docs/platforms/java/common/configuration/options.mdx
@@ -95,11 +95,11 @@ Grouping in Sentry is different for events with stack traces and without. As a r
 
 If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This option is turned off by default.
 
diff --git a/docs/platforms/java/common/configuration/releases.mdx b/docs/platforms/java/common/configuration/releases.mdx
index bbf6336dae8e67..a504eaa942740f 100644
--- a/docs/platforms/java/common/configuration/releases.mdx
+++ b/docs/platforms/java/common/configuration/releases.mdx
@@ -31,11 +31,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
diff --git a/docs/platforms/java/common/configuration/sampling.mdx b/docs/platforms/java/common/configuration/sampling.mdx
index b11df278e4715c..7ee9e905297451 100644
--- a/docs/platforms/java/common/configuration/sampling.mdx
+++ b/docs/platforms/java/common/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
diff --git a/docs/platforms/java/common/data-management/sensitive-data/index.mdx b/docs/platforms/java/common/data-management/sensitive-data/index.mdx
index cf4de7c59a1190..f06150b89cbdd9 100644
--- a/docs/platforms/java/common/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/java/common/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 ## Personally Identifiable Information (PII)
 
diff --git a/docs/platforms/java/common/enriching-events/attachments/index.mdx b/docs/platforms/java/common/enriching-events/attachments/index.mdx
index 8bf58e602c1efc..3c2242b4620913 100644
--- a/docs/platforms/java/common/enriching-events/attachments/index.mdx
+++ b/docs/platforms/java/common/enriching-events/attachments/index.mdx
@@ -49,11 +49,11 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <PlatformContent includePath="enriching-events/attachment-upload" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/java/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/java/common/enriching-events/breadcrumbs/index.mdx
index 65ee11d1ef2c98..8c0e4e7c0e248d 100644
--- a/docs/platforms/java/common/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/java/common/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/java/common/enriching-events/context/index.mdx b/docs/platforms/java/common/enriching-events/context/index.mdx
index dd07e216bbb9f9..36da3d54f75935 100644
--- a/docs/platforms/java/common/enriching-events/context/index.mdx
+++ b/docs/platforms/java/common/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/java/common/enriching-events/scopes/index.mdx b/docs/platforms/java/common/enriching-events/scopes/index.mdx
index 9670dedfb47d20..58e678cad75df4 100644
--- a/docs/platforms/java/common/enriching-events/scopes/index.mdx
+++ b/docs/platforms/java/common/enriching-events/scopes/index.mdx
@@ -21,7 +21,7 @@ routes or request handlers.
 
 ## How Scopes Work
 
-Scopes are basically a stacks of data that are attached to events. When an event is captured, the SDK will merge the data from the active scopes into the event. This allows you to attach data to events that is relevant to the context in which the event was captured.
+Scopes are basically stacks of data that are attached to events. When an event is captured, the SDK will merge the data from the active scopes into the event. This allows you to attach data to events that is relevant to the context in which the event was captured.
 
 A scope is generally valid inside of a callback or an execution context. This means that multiple parts of your application may have different scopes active at the same time. For instance, a web server might handle multiple requests at the same time, and each request may have different scope data to apply to its events.
 
@@ -54,6 +54,13 @@ Sentry.configureScope(ScopeType.ISOLATION, scope -> {
   scope.setTag("my-tag", "my value");
 });
 ```
+```kotlin
+Sentry.setTag("my-tag", "my value")
+// Is identical to:
+Sentry.configureScope(ScopeType.ISOLATION) { scope ->
+  scope.setTag("my-tag", "my value")
+}
+```
 
 ### Current Scope
 
@@ -70,6 +77,17 @@ Sentry.withScope(scope -> {
 // this event will not have the tag:
 Sentry.captureException(new Exception("my other error"));
 ```
+```kotlin
+Sentry.withScope { scope ->
+  // scope is the current scope inside of this callback!
+  scope.setTag("my-tag", "my value")
+  // this tag will only be applied to events captured inside of this callback
+  // the following event will have the tag:
+  Sentry.captureException(Exception("my error"))
+}
+// this event will not have the tag:
+Sentry.captureException(Exception("my other error"))
+```
 
 You can modify the current scope via `Sentry.configureScope(ScopeType.CURRENT, scope -> { ... })`, but usually you should use `Sentry.withScope()` to interact with local scopes instead.
 
@@ -100,6 +118,26 @@ Sentry.captureException(new Exception("my error"));
 // --> Will have the following extra:
 // { shared: 'current', global: 'data', isolation: 'data', current: 'data' }
 ```
+```kotlin
+Sentry.configureScope(ScopeType.GLOBAL) { scope ->
+  scope.setExtra("shared", "global")
+  scope.setExtra("global", "data")
+}
+
+Sentry.configureScope(ScopeType.ISOLATION) { scope ->
+  scope.setExtra("shared", "isolation")
+  scope.setExtra("isolation", "data")
+}
+
+Sentry.configureScope(ScopeType.CURRENT) { scope ->
+  scope.setExtra("shared", "current")
+  scope.setExtra("current", "data")
+}
+
+Sentry.captureException(Exception("my error"))
+// --> Will have the following extra:
+// { shared: 'current', global: 'data', isolation: 'data', current: 'data' }
+```
 
 ## Configuring the Scope
 
@@ -149,7 +187,7 @@ made will stay isolated within the callback function. This allows you to
 more easily isolate pieces of context information to specific locations in your code or
 even call `clear` to briefly remove all context information.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 Any exceptions that occur within the callback function for configuring a local scope will not be
 caught, and all errors that occur will be silently ignored and **not** reported.
diff --git a/docs/platforms/java/common/enriching-events/scopes/index__v7.x.mdx b/docs/platforms/java/common/enriching-events/scopes/index__v7.x.mdx
new file mode 100644
index 00000000000000..3cdf3c1937d755
--- /dev/null
+++ b/docs/platforms/java/common/enriching-events/scopes/index__v7.x.mdx
@@ -0,0 +1,130 @@
+---
+title: Scopes and Hubs
+description: "SDKs will typically automatically manage the scopes for you in the framework integrations. Learn what a scope is and how you can use it to your advantage."
+---
+
+When an event is captured and sent to Sentry, SDKs will merge that event data with extra
+information from the current scope. SDKs will typically automatically manage the scopes
+for you in the framework integrations and you don't need to think about them. However,
+you should know what a scope is and how you can use it for your advantage.
+
+## What's a Scope, What's a Hub
+
+You can think of the hub as the central point that our SDKs use to route an
+event to Sentry. When you call `init()` a hub is created and a client and a
+blank scope are created on it. That hub is then associated with the current
+thread and will internally hold a stack of scopes.
+
+The scope will hold useful information that should be sent along with the
+event. For instance [contexts](../context/) or
+[breadcrumbs](../breadcrumbs/) are stored on
+the scope. When a scope is pushed, it inherits all data from the parent scope
+and when it pops all modifications are reverted.
+
+The default SDK integrations will push and pop scopes intelligently. For
+instance web framework integrations will create and destroy scopes around your
+routes or controllers.
+
+## How the Scope and Hub Work
+
+As you start using an SDK, a scope and hub are automatically created for you out
+of the box. It's unlikely that you'll interact with the hub directly unless you're
+writing an integration or you want to create or destroy scopes. Scopes, on the
+other hand are more user facing. You can call <PlatformIdentifier name="configure-scope" /> at any point in
+time to modify data stored on the scope. This is useful for doing things like
+[modifying the context](../context/).
+
+When you call a global function such as <PlatformIdentifier name="capture-event" /> internally Sentry
+discovers the current hub and asks it to capture an event. Internally the hub will
+then merge the event with the topmost scope's data.
+
+## Configuring the Scope
+
+The most useful operation when working with scopes is the <PlatformIdentifier name="configure-scope" /> function. It can be used to reconfigure the current scope.
+
+You can, for instance, add custom tags or inform Sentry about the currently authenticated user.
+
+<PlatformContent includePath="enriching-events/scopes/configure-scope" />
+
+You can also apply this configuration when unsetting a user at logout:
+
+<PlatformContent includePath="enriching-events/unset-user" />
+
+To learn what useful information can be associated with scopes see
+[the context documentation](../context/).
+
+## Local Scopes
+
+We also support pushing and configuring a scope within a single call. This is typically
+called <PlatformIdentifier name="with-scope" />, <PlatformIdentifier name="push-scope" /> or implemented as a function parameter on the capture methods, depending on the SDK. It's very helpful if
+you only want to send data for one specific event.
+
+### Using <PlatformIdentifier name="with-scope" />
+
+In the following example we use <PlatformIdentifier name="with-scope" /> to attach a `level` and a `tag` to only one specific error:
+
+<PlatformContent includePath="enriching-events/scopes/with-scope" />
+
+While this example looks similar to <PlatformIdentifier name="configure-scope" />, it is actually very different.
+Calls to <PlatformIdentifier name="configure-scope" /> change the current active scope; all successive calls to <PlatformIdentifier name="configure-scope" /> will maintain previously set changes unless they are explicitly unset.
+
+On the other hand, <PlatformIdentifier name="with-scope" /> creates a clone of the current scope, and the changes
+made will stay isolated within the <PlatformIdentifier name="with-scope" /> callback function. This allows you to
+more easily isolate pieces of context information to specific locations in your code or
+even call <PlatformIdentifier name="clear" /> to briefly remove all context information.
+
+### Using Scope Callback Parameter
+
+In the following example we use the scope callback parameter that is available for all `capture` methods to attach a `level` and a `tag` to only one specific error:
+
+<PlatformContent includePath="enriching-events/scopes/scope-callback-param" />
+
+Before the callback is invoked the SDK creates a clone of the current scope, and the changes
+made will stay isolated within the callback function. This allows you to
+more easily isolate pieces of context information to specific locations in your code or
+even call `clear` to briefly remove all context information.
+
+<Alert title="Important">
+
+Any exceptions that occur within the callback function for configuring a local scope will not be
+caught, and all errors that occur will be silently ignored and **not** reported.
+
+</Alert>
+
+## Kotlin Coroutines
+
+Sentry's SDK for Java stores the scope and the context in a thread-local variable. To make sure that a coroutine has access to the correct Sentry context, an instance of `SentryContext` must be provided when launching a coroutine.
+
+### Installation
+
+```xml {tabTitle:Maven}
+<dependency>
+    <groupId>io.sentry</groupId>
+    <artifactId>sentry-kotlin-extensions</artifactId>
+    <version>{{@inject packages.version('sentry.java.kotlin-extensions', '5.0.0') }}</version>
+</dependency>
+```
+
+```groovy {tabTitle:Gradle}
+implementation 'io.sentry:sentry-kotlin-extensions:{{@inject packages.version('sentry.java.kotlin-extensions', '5.0.0') }}'
+```
+
+```scala {tabTitle: SBT}
+libraryDependencies += "io.sentry" % "sentry-kotlin-extensions" % "{{@inject packages.version('sentry.java.kotlin-extensions', '5.0.0') }}"
+```
+
+### Usage
+
+```kotlin
+import io.sentry.kotlin.SentryContext
+import io.sentry.Sentry
+
+launch(SentryContext()) {
+  // tag set in parent coroutine is visible to child coroutine
+  Sentry.setTag("parent-tag", "value")
+  launch() {
+    // tag set in child coroutine is not visible in parent coroutine
+    Sentry.setTag("child-tag", "value")
+  }
+}
+```
diff --git a/docs/platforms/java/common/enriching-events/tags/index.mdx b/docs/platforms/java/common/enriching-events/tags/index.mdx
index 5707e7b98110ca..9657816853afb2 100644
--- a/docs/platforms/java/common/enriching-events/tags/index.mdx
+++ b/docs/platforms/java/common/enriching-events/tags/index.mdx
@@ -17,11 +17,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/java/common/gradle/index.mdx b/docs/platforms/java/common/gradle/index.mdx
index 22658a88101e3b..8311b483d83d7d 100644
--- a/docs/platforms/java/common/gradle/index.mdx
+++ b/docs/platforms/java/common/gradle/index.mdx
@@ -29,11 +29,11 @@ plugins {
 }
 ```
 
-<Note>
+<Alert>
 
 For non-Android projects, the plugin only collects external dependencies and uploads <PlatformLink to="/source-context/">Source Context</PlatformLink>.
 
-</Note>
+</Alert>
 
 ### Configure
 
diff --git a/docs/platforms/java/common/index.mdx b/docs/platforms/java/common/index.mdx
index 29537b01815ea0..ba80d3abb72b21 100644
--- a/docs/platforms/java/common/index.mdx
+++ b/docs/platforms/java/common/index.mdx
@@ -26,10 +26,10 @@ This snippet includes an intentional error, so you can test that everything is w
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
diff --git a/docs/platforms/java/common/integrations/graphql.mdx b/docs/platforms/java/common/integrations/graphql.mdx
index 7296b10388e6c7..d9867c203bf228 100644
--- a/docs/platforms/java/common/integrations/graphql.mdx
+++ b/docs/platforms/java/common/integrations/graphql.mdx
@@ -14,11 +14,11 @@ Sentry's [GraphQL Java](https://github.com/graphql-java/graphql-java/) integrati
 
 Our GraphQL integration can be configured automatically if you're using `spring-graphql` with either the `sentry-spring-boot-starter` or the `sentry-spring-boot-jakarta-starter` integration.
 
-<Note>
+<Alert>
 
 If you're using version 22 of `graphql-java`, please refer to <PlatformLink to="/integrations/graphql22/">GraphQL 22 docs</PlatformLink>.
 
-</Note>
+</Alert>
 
 ## Install
 
@@ -98,11 +98,11 @@ val graphql = GraphQL.newGraphQL()
   .build()
 ```
 
-<Note>
+<Alert>
 
 The `SentryDataFetcherExceptionHandler` has been deprecated. Please upgrade to `SentryGenericDataFetcherExceptionHandler` and make sure `SentryInstrumentation` is configured to have more exceptions captured, more detailed exceptions, breadcrumbs, and better hub propagation. You may want to filter the errors by using `beforeSend` or an `EventProcessor` (read more about <PlatformLink to="/configuration/filtering/">Filters</PlatformLink>).
 
-</Note>
+</Alert>
 
 ## Capture Tracing Information
 
diff --git a/docs/platforms/java/common/integrations/graphql22.mdx b/docs/platforms/java/common/integrations/graphql22.mdx
index 0299e9efd06dd8..24d06a8b836103 100644
--- a/docs/platforms/java/common/integrations/graphql22.mdx
+++ b/docs/platforms/java/common/integrations/graphql22.mdx
@@ -14,11 +14,11 @@ Sentry's [GraphQL Java](https://github.com/graphql-java/graphql-java/) integrati
 
 Our GraphQL integration can be configured automatically if you're using `spring-graphql` with either the `sentry-spring-boot-starter` or the `sentry-spring-boot-jakarta-starter` integration.
 
-<Note>
+<Alert>
 
 If you're using version 21 or older of `graphql-java`, please refer to <PlatformLink to="/integrations/graphql/">GraphQL docs</PlatformLink>.
 
-</Note>
+</Alert>
 
 ## Install
 
@@ -98,11 +98,11 @@ val graphql = GraphQL.newGraphQL()
   .build()
 ```
 
-<Note>
+<Alert>
 
 The `SentryDataFetcherExceptionHandler` has been deprecated. Please upgrade to `SentryGenericDataFetcherExceptionHandler` and make sure `SentryInstrumentation` is configured to have more exceptions captured, more detailed exceptions, breadcrumbs, and better hub propagation. You may want to filter the errors by using `beforeSend` or an `EventProcessor` (read more about <PlatformLink to="/configuration/filtering/">Filters</PlatformLink>).
 
-</Note>
+</Alert>
 
 ## Capture Tracing Information
 
diff --git a/docs/platforms/java/common/integrations/quartz.mdx b/docs/platforms/java/common/integrations/quartz.mdx
index 9a443a48258fa6..32e6f49cbbf6c7 100644
--- a/docs/platforms/java/common/integrations/quartz.mdx
+++ b/docs/platforms/java/common/integrations/quartz.mdx
@@ -58,14 +58,14 @@ SimpleTriggerFactoryBean trigger = new SimpleTriggerFactoryBean();
 trigger.setJobDataAsMap(Collections.singletonMap(SENTRY_SLUG_KEY, "monitor_slug_simple_trigger"));
 ```
 
-<Note>
+<Alert>
 
 Setting the monitor slug on the `Trigger` will override what is set on the `JobDetail`. This also means you can set up a separate monitor per `Trigger`.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 Setting a global job listener using a `SchedulerFactoryBeanCustomizer` in Spring Boot, will override the listener set by Sentry. For Sentry to work properly, you need to add a new `SentryJobListener` instance to the global job listeners.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/java/common/tracing/index.mdx b/docs/platforms/java/common/tracing/index.mdx
index 24288935b24295..71cf9229d22454 100644
--- a/docs/platforms/java/common/tracing/index.mdx
+++ b/docs/platforms/java/common/tracing/index.mdx
@@ -10,11 +10,11 @@ supported:
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 <Include name="opentelemetry-available.mdx" />
 
diff --git a/docs/platforms/java/common/tracing/instrumentation/apollo.mdx b/docs/platforms/java/common/tracing/instrumentation/apollo.mdx
index 7c21921928c13d..1e1ea47b6d82f6 100644
--- a/docs/platforms/java/common/tracing/instrumentation/apollo.mdx
+++ b/docs/platforms/java/common/tracing/instrumentation/apollo.mdx
@@ -9,19 +9,19 @@ notSupported:
   - java.jul
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already.
 
-</Note>
+</Alert>
 
 Sentry Apollo integration provides the `SentryApolloInterceptor`, which creates a span for each outgoing HTTP request executed with an [Apollo Android](https://github.com/apollographql/apollo-android) GraphQL client.
 
-<Note>
+<Alert>
 
 This integration supports Apollo 2.x. For Apollo 3.x use our <PlatformLink to="/tracing/instrumentation/apollo3">Apollo3 integration</PlatformLink>.
 
-</Note>
+</Alert>
 
 ## Install
 
@@ -81,11 +81,11 @@ Sentry.init(options -> {
 }, true)
 ```
 
-<Note>
+<Alert>
 
 In Global Hub Mode, all threads use the same Hub.
 
-</Note>
+</Alert>
 
 ## Using With Kotlin Coroutines
 
diff --git a/docs/platforms/java/common/tracing/instrumentation/apollo3.mdx b/docs/platforms/java/common/tracing/instrumentation/apollo3.mdx
index b1446f366552c5..706d99e101077a 100644
--- a/docs/platforms/java/common/tracing/instrumentation/apollo3.mdx
+++ b/docs/platforms/java/common/tracing/instrumentation/apollo3.mdx
@@ -9,19 +9,19 @@ notSupported:
   - java.jul
 ---
 
-<Note>
+<Alert>
 
 To be able to capture transactions, you'll need to first <PlatformLink to="/tracing/">set up tracing</PlatformLink>.
 
-</Note>
+</Alert>
 
 Sentry's Apollo3 integration provides both the `SentryApollo3Interceptor` and the `SentryApollo3HttpInterceptor`, which create a span for each outgoing HTTP request executed with an [Apollo Kotlin](https://github.com/apollographql/apollo-kotlin) GraphQL client. The integration also provides extension functions on the `ApolloClient.Builder`.
 
-<Note>
+<Alert>
 
 This integration supports Apollo 3.x. It does not yet support <Link to="https://github.com/apollographql/apollo-kotlin/releases/tag/v4.0.0">Apollo4</Link>. If you're using Apollo4 and are interested in an integration for it, please track and upvote the <Link to="https://github.com/getsentry/sentry-java/issues/3662">related issue</Link>.
 
-</Note>
+</Alert>
 
 ## Install
 
@@ -105,7 +105,7 @@ val apollo = ApolloClient.builder()
     .build()
 ```
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 Apollo Kotlin is built with Kotlin coroutines. This means that `SentryApolloInterceptor` can be used with Java using only Global Hub Mode (single Hub used by all threads), with Kotlin using single Hub mode, or with <PlatformLink to="/enriching-events/scopes/#kotlin-coroutines">Sentry's coroutines support</PlatformLink>.
 
@@ -123,11 +123,11 @@ Sentry.init(options -> {
 }, true)
 ```
 
-<Note>
+<Alert>
 
 In Global Hub Mode, all threads use the same Hub.
 
-</Note>
+</Alert>
 
 ## Using With Kotlin Coroutines
 
diff --git a/docs/platforms/java/common/tracing/instrumentation/custom-instrumentation/index.mdx b/docs/platforms/java/common/tracing/instrumentation/custom-instrumentation/index.mdx
index 54eec878909f69..abdcb15057f356 100644
--- a/docs/platforms/java/common/tracing/instrumentation/custom-instrumentation/index.mdx
+++ b/docs/platforms/java/common/tracing/instrumentation/custom-instrumentation/index.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
diff --git a/docs/platforms/java/common/tracing/instrumentation/file-io.mdx b/docs/platforms/java/common/tracing/instrumentation/file-io.mdx
index fc58082918fb8c..9a0f8640ee7cfb 100644
--- a/docs/platforms/java/common/tracing/instrumentation/file-io.mdx
+++ b/docs/platforms/java/common/tracing/instrumentation/file-io.mdx
@@ -8,11 +8,11 @@ notSupported:
   - java.jul
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already.
 
-</Note>
+</Alert>
 
 Sentry file I/O integration provides the `SentryFileInputStream`/`SentryFileOutputStream` and `SentryFileReader`/`SentryFileWriter`, which create a span for each File read/write operation.
 
diff --git a/docs/platforms/java/common/tracing/instrumentation/jdbc.mdx b/docs/platforms/java/common/tracing/instrumentation/jdbc.mdx
index b019ab18b86669..126a58363c60c2 100644
--- a/docs/platforms/java/common/tracing/instrumentation/jdbc.mdx
+++ b/docs/platforms/java/common/tracing/instrumentation/jdbc.mdx
@@ -9,11 +9,11 @@ notSupported:
   - java.jul
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already.
 
-</Note>
+</Alert>
 
 Sentry JDBC integration provides the `SentryJdbcEventListener` for [P6Spy](https://github.com/p6spy/p6spy/) database activity interceptor, which creates a span for each JDBC statement executed over a proxied instance of `javax.sql.DataSource`.
 
diff --git a/docs/platforms/java/common/tracing/instrumentation/okhttp.mdx b/docs/platforms/java/common/tracing/instrumentation/okhttp.mdx
index 6b69cfdfd30cea..7bc2c3f5937b56 100644
--- a/docs/platforms/java/common/tracing/instrumentation/okhttp.mdx
+++ b/docs/platforms/java/common/tracing/instrumentation/okhttp.mdx
@@ -9,11 +9,11 @@ notSupported:
   - java.jul
 ---
 
-<Note>
+<Alert>
 
 To be able to capture transactions, you'll need to first <PlatformLink to="/tracing/">set up tracing</PlatformLink>.
 
-</Note>
+</Alert>
 
 The `sentry-okhttp` library provides [OkHttp](https://github.com/square/okhttp) support for Sentry via the `SentryOkHttpInterceptor` and the `SentryOkHttpEventListener`, which create a span for each outgoing HTTP request executed with an OkHttp client. The source can be found [on GitHub](https://github.com/getsentry/sentry-java/tree/main/sentry-okhttp).
 
diff --git a/docs/platforms/java/common/tracing/instrumentation/open-feign.mdx b/docs/platforms/java/common/tracing/instrumentation/open-feign.mdx
index 4480b247668d7c..447d2e0f8735a3 100644
--- a/docs/platforms/java/common/tracing/instrumentation/open-feign.mdx
+++ b/docs/platforms/java/common/tracing/instrumentation/open-feign.mdx
@@ -9,11 +9,11 @@ notSupported:
   - java.jul
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already.
 
-</Note>
+</Alert>
 
 Sentry OpenFeign integration provides the `SentryFeignClient`, which creates a span for each outgoing HTTP request executed with a [Feign](https://github.com/OpenFeign/feign)-based HTTP client.
 
diff --git a/docs/platforms/java/common/usage/index.mdx b/docs/platforms/java/common/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/java/common/usage/index.mdx
+++ b/docs/platforms/java/common/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/java/guides/spring-boot/logging-frameworks.mdx b/docs/platforms/java/guides/spring-boot/logging-frameworks.mdx
index 446b26caf9943c..de323b6ac636c8 100644
--- a/docs/platforms/java/guides/spring-boot/logging-frameworks.mdx
+++ b/docs/platforms/java/guides/spring-boot/logging-frameworks.mdx
@@ -50,20 +50,20 @@ If you decide to opt-out from the `application.properties` based Spring Boot log
 
   <appender name="SENTRY" class="io.sentry.logback.SentryAppender" />
 
-  <root level="info">
+  <root>
     <appender-ref ref="CONSOLE" />
     <appender-ref ref="SENTRY" />
   </root>
 </configuration>
 ```
 
-<Note>
+<Alert>
 
 You do not need to configure your DSN in the Logback configuration file since Sentry is configured from the Spring Boot integration.
 
 However, if errors that may appear during startup should to be sent to Sentry, the DSN must be provided to <i>both</i> the Logback and Spring Boot configurations.
 
-</Note>
+</Alert>
 
 ### Log4j 2
 
@@ -110,10 +110,10 @@ Then [follow the guide on configuring Log4j 2 with Spring Boot](https://docs.spr
 </Configuration>
 ```
 
-<Note>
+<Alert>
 
 You do not need to configure your DSN in the Log4j 2 configuration file since Sentry is configured from the Spring Boot integration.
 
 However, if errors that may appear during startup should to be sent to Sentry, the DSN must be provided to <i>both</i> the Log4j 2 and Spring Boot configurations.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/java/guides/spring-boot/record-user.mdx b/docs/platforms/java/guides/spring-boot/record-user.mdx
index 6166ec00dcfbd9..2bfd90a7635a5d 100644
--- a/docs/platforms/java/guides/spring-boot/record-user.mdx
+++ b/docs/platforms/java/guides/spring-boot/record-user.mdx
@@ -4,9 +4,9 @@ sidebar_order: 7
 description: "Learn about how you can record or customize the capture of user information."
 ---
 
-<Note>
+<Alert>
   Recording user information is available only in the Spring MVC integration.
-</Note>
+</Alert>
 
 Record user information from an HTTP request or by registering a Spring bean for custom user information capture.
 
diff --git a/docs/platforms/java/guides/spring-boot/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/java/guides/spring-boot/tracing/instrumentation/automatic-instrumentation.mdx
index c09767b03044d6..c655ab760ffa0f 100644
--- a/docs/platforms/java/guides/spring-boot/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/java/guides/spring-boot/tracing/instrumentation/automatic-instrumentation.mdx
@@ -4,11 +4,11 @@ sidebar_order: 20
 description: "Learn what transactions are captured after tracing is enabled."
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already.
 
-</Note>
+</Alert>
 
 ### Spring MVC Integration
 
diff --git a/docs/platforms/java/guides/spring/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/java/guides/spring/tracing/instrumentation/automatic-instrumentation.mdx
index cee7fd1feb5c22..82efdfa2ff622f 100644
--- a/docs/platforms/java/guides/spring/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/java/guides/spring/tracing/instrumentation/automatic-instrumentation.mdx
@@ -4,11 +4,11 @@ sidebar_order: 20
 description: "Learn what transactions we capture after tracing is enabled."
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already.
 
-</Note>
+</Alert>
 
 ### Spring MVC Integration
 
diff --git a/docs/platforms/javascript/common/best-practices/micro-frontends.mdx b/docs/platforms/javascript/common/best-practices/micro-frontends.mdx
index 6094889f64ac40..b72d0929810595 100644
--- a/docs/platforms/javascript/common/best-practices/micro-frontends.mdx
+++ b/docs/platforms/javascript/common/best-practices/micro-frontends.mdx
@@ -32,16 +32,16 @@ If your app uses micro frontends, it's very useful to be able to track which one
 
 Below you'll find setup instructions for both an automatic and a manual way to route errors to different Sentry projects.
 
-<Note>
+<Alert>
   In all cases `Sentry.init()` must never be called more than once, doing so
   will result in undefined behavior.
-</Note>
+</Alert>
 
 ## Automatically Route Errors to Different Projects
 
 `ModuleMetadata` and `makeMultiplexedTransport` can be used together to automatically route events to specific Sentry projects that represent your micro frontend services. Events will be routed once the service where the error occurred has been identified, ensuring errors are tracked in the correct project.
 
-<Note>
+<Alert>
   <ul>
     <li>
       Requires version `2.18.0` or higher of `@sentry/webpack-plugin`,
@@ -50,7 +50,7 @@ Below you'll find setup instructions for both an automatic and a manual way to r
     </li>
     <li>Requires SDK version `7.59.0` or higher.</li>
   </ul>
-</Note>
+</Alert>
 
 To identify the source of an error, you must first inject metadata that helps identify
 which bundles were responsible for the error. You can do this with any of the
@@ -134,19 +134,19 @@ init({
 
 Once this is set up, errors - both handled and unhandled - will be automatically routed to the right project.
 
-<Note>
+<Alert>
 
 By default, `args.getEvent` returns only error events. You can match against other event types like so: `args.getEvent(['event', 'transaction', 'replay_event'])`. This `getEvent` snippet
 will return matches for errors, transactions, and replays.
 
-</Note>
+</Alert>
 
 ## Manually Route Errors to Different Projects
 
 If you want more control to be able to explicitly specify the destination for each individual `captureException`,
 you can use the more advanced interface multiplexed transport offers.
 
-<Note>Requires SDK version `7.59.0` or higher.</Note>
+<Alert>equires SDK version `7.59.0` or higher.</Alert>
 
 The example below uses a `feature` tag to determine which Sentry project to
 send the event to. If the event doesn't have a `feature` tag, we send it to the
@@ -179,7 +179,7 @@ init({
 
 You can then set tags/contexts on events in individual micro-frontends to decide which Sentry project to send the event to as follows:
 
-<Note>
+<Alert>
   It's important to always use a local scope when setting the tag (either as
   shown below or using{" "}
   <PlatformLink to="/enriching-events/scopes/#local-scopes">
@@ -188,7 +188,7 @@ You can then set tags/contexts on events in individual micro-frontends to decide
   ). Using a global scope, for example, through `Sentry.setTag()` will result in
   all subsequent events being routed to the same DSN regardless of where they
   originated.
-</Note>
+</Alert>
 
 ```typescript
 captureException(new Error("oh no!"), (scope) => {
@@ -204,9 +204,9 @@ Starting with version [8.7.0](https://github.com/getsentry/sentry-javascript/rel
 However, for use cases like micro frontends, where you might _want_ SDK interaction across multiple micro frontends or child applications, you'll need to ensure that all SDKs are using the same version.
 For example, if you initialize the SDK in a host or skeleton application, but make Sentry SDK calls (like `Sentry.captureException` or `Sentry.setTag`) in micro frontend child applications, you need to ensure that the SDK packages in the host and child applications are aligned to the same version.
 
-<Note>
+<Alert>
 
 If you can't get all your micro frontends aligned on the same SDK version, you can [follow this workaround](https://github.com/getsentry/sentry-javascript/discussions/10576#discussioncomment-11446422).
 However, interoperability isn't guaranteed and you could run into some unexpected behavior.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/javascript/common/best-practices/multiple-sentry-instances.mdx b/docs/platforms/javascript/common/best-practices/multiple-sentry-instances.mdx
index d2fc2efe087a7b..4d91b6fae23e0a 100644
--- a/docs/platforms/javascript/common/best-practices/multiple-sentry-instances.mdx
+++ b/docs/platforms/javascript/common/best-practices/multiple-sentry-instances.mdx
@@ -16,11 +16,11 @@ notSupported:
 keywords: ["multiple clients", "BrowserClient", "NodeClient", "monorepo"]
 ---
 
-<Note>
+<Alert>
 
 Creating multiple Sentry clients is **not recommended** in general, as it can lead to unexpected behavior. In case you are using Micro Frontends or similar, multiplexing might be a better solution than using multiple clients. Check out [Micro Frontends](/platforms/javascript/best-practices/micro-frontends) in the Best Practices for more information.
 
-</ Note>
+</ Alert>
 
 To be able to manage several Sentry instances without any conflicts between them you need to create your own `Client`.
 This also helps to prevent tracking of any parent application errors in case your application is integrated
diff --git a/docs/platforms/javascript/common/best-practices/shared-environments.mdx b/docs/platforms/javascript/common/best-practices/shared-environments.mdx
index 064d7dfb7be660..9bbfdc07333f5a 100644
--- a/docs/platforms/javascript/common/best-practices/shared-environments.mdx
+++ b/docs/platforms/javascript/common/best-practices/shared-environments.mdx
@@ -24,11 +24,11 @@ keywords:
   ]
 ---
 
-<Note>
+<Alert>
 
 We recommend using JavaScript SDK `8.x` and above when using the SDK with shared environments. Check out our [migration docs](https://docs.sentry.io/platforms/javascript/migration/) to upgrade from an older SDK version to `8.x` and above.
 
-</Note>
+</Alert>
 
 These best practices are relevant for you if you set up Sentry in one of the following use-cases:
 
@@ -39,7 +39,7 @@ These best practices are relevant for you if you set up Sentry in one of the fol
 - Libraries
 - Any other scenario where you might have multiple Sentry instances running in the same environment
 
-<Alert level="danger">
+<Alert level="warning">
 
 When setting up Sentry in a shared environment where multiple Sentry instances may run, you should **not use `Sentry.init()`**, as this will pollute the global state. If your browser extension uses `Sentry.init()`, and a website also uses Sentry, the extension may send events to the website's Sentry project, or vice versa.
 
@@ -121,7 +121,7 @@ Sentry.init({
 });
 ```
 
-<Alert level="danger">
+<Alert level="warning">
 
 You shouldn't use this option if you're in fact using the SDK in a browser extension or another shared environment.
 Initializing the SDK via `Sentry.init` has no advantages over manually setting up the client and scope as described on this page.
diff --git a/docs/platforms/javascript/common/configuration/application-not-responding.mdx b/docs/platforms/javascript/common/configuration/application-not-responding.mdx
index 5bc59597a36980..548e4a4340b581 100644
--- a/docs/platforms/javascript/common/configuration/application-not-responding.mdx
+++ b/docs/platforms/javascript/common/configuration/application-not-responding.mdx
@@ -34,17 +34,17 @@ Application Not Responding (ANR) errors, or Event Loop Stall errors, are trigger
 
 <Include name="feature-stage-beta.mdx" />
 
-<Note>
+<Alert>
 
 ANR detection is not supported for [Node.js clusters](https://nodejs.org/api/cluster.html).
 
-</Note>
+</Alert>
 
 _(Available in version 7.91.0 and above)_
 
 To enable ANR detection, add the `Anr` integration from the `@sentry/node` package.
 
-<Alert level="info">
+<Alert>
 
 ANR detection requires Node 16 or higher and can only be used in the Node.js runtime.
 
diff --git a/docs/platforms/javascript/common/configuration/filtering.mdx b/docs/platforms/javascript/common/configuration/filtering.mdx
index 51731aadb05479..684006a14723ad 100644
--- a/docs/platforms/javascript/common/configuration/filtering.mdx
+++ b/docs/platforms/javascript/common/configuration/filtering.mdx
@@ -90,11 +90,11 @@ _Available in browser-based SDKs from version 8.10.0_
 The `thirdPartyErrorFilterIntegration` allows you to filter out errors originating from third parties, such as browser extensions, code-injecting browsers, or widgets from third-party services that also use Sentry.
 This integration can be very helpful in reducing noise that's not related to your own application code.
 
-<Note>
+<Alert>
 
 **Prerequisite**: To use the `thirdPartyErrorFilterIntegration`, ensure you are using a bundler and one of [Sentry's bundler plugins](https://github.com/getsentry/sentry-javascript-bundler-plugins).
 
-</Note>
+</Alert>
 
 This integration works by "marking" your JavaScript files with an "application key" during the build process.
 At runtime, if an error occurs, this integration checks application keys for each stack frame in the stack trace.
@@ -190,12 +190,12 @@ There are four modes you can choose from:
 
 If you choose a mode to only apply tags, the tags can then be used in Sentry to filter your issue stream with the `third_party_code` tag in the issue search bar.
 
-<Note>
+<Alert>
 
 The `thirdPartyErrorFilterIntegration` will not work with the [Sentry Loader Script or CDN Bundles](https://docs.sentry.io/platforms/javascript/install/loader/).
 This is the case because the Sentry Loader Script and CDN Bundles are detected as "third party" by the integration. This makes it apply the chosen behavior to almost all events, since the Sentry SDK wraps many browser-native APIs.
 
-</Note>
+</Alert>
 
 ## Filtering Transaction Events
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/amqplib.mdx b/docs/platforms/javascript/common/configuration/integrations/amqplib.mdx
index 09ceb02b7b471c..6717cc94405b21 100644
--- a/docs/platforms/javascript/common/configuration/integrations/amqplib.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/amqplib.mdx
@@ -25,7 +25,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes. Requires SDK version `8.32.0` or higher.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/anr.mdx b/docs/platforms/javascript/common/configuration/integrations/anr.mdx
index 5ea6a3249136a3..07c87f0fbe3096 100644
--- a/docs/platforms/javascript/common/configuration/integrations/anr.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/anr.mdx
@@ -22,7 +22,7 @@ supported:
   - javascript.astro
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js runtime.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/breadcrumbs.mdx b/docs/platforms/javascript/common/configuration/integrations/breadcrumbs.mdx
index 693a1fb4a9c381..b39cc28cd700a1 100644
--- a/docs/platforms/javascript/common/configuration/integrations/breadcrumbs.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/breadcrumbs.mdx
@@ -18,7 +18,7 @@ notSupported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/browserapierrors.mdx b/docs/platforms/javascript/common/configuration/integrations/browserapierrors.mdx
index 47c38351d0d9e0..890f8f9c9eeebd 100644
--- a/docs/platforms/javascript/common/configuration/integrations/browserapierrors.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/browserapierrors.mdx
@@ -18,7 +18,7 @@ notSupported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx b/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx
index 8ca9211b7bcec6..11bf6db1c56607 100644
--- a/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx
@@ -19,7 +19,7 @@ notSupported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/browsersession.mdx b/docs/platforms/javascript/common/configuration/integrations/browsersession.mdx
index 42d9e8679fd4be..daf840962651dc 100644
--- a/docs/platforms/javascript/common/configuration/integrations/browsersession.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/browsersession.mdx
@@ -18,7 +18,7 @@ notSupported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment.
 
@@ -27,7 +27,7 @@ This integration only works inside a browser environment.
 _Import name: `Sentry.browserSessionIntegration`_
 
 Sentry's [Release Health](/product/releases/health/) feature allows you to track user adoption and your application's crash-free rate.
-When the BrowserSession integration is enabled, it automatically creates a session each time a user loads your page or application. These sessions are used to track your release health. If an error is captured during an active session, the session will be flagged as faulty. 
+When the BrowserSession integration is enabled, it automatically creates a session each time a user loads your page or application. These sessions are used to track your release health. If an error is captured during an active session, the session will be flagged as faulty.
 Read more about <PlatformLink to="/configuration/releases/#sessions">Sessions</PlatformLink>.
 
 ```JavaScript
diff --git a/docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx b/docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx
index b4051cb614f07d..fe851a0dae22df 100644
--- a/docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx
@@ -18,7 +18,7 @@ notSupported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/bunserver.mdx b/docs/platforms/javascript/common/configuration/integrations/bunserver.mdx
index e0ee3269da18ad..4c302c920a4338 100644
--- a/docs/platforms/javascript/common/configuration/integrations/bunserver.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/bunserver.mdx
@@ -5,7 +5,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Bun runtime.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/childProcess.mdx b/docs/platforms/javascript/common/configuration/integrations/childProcess.mdx
index 18831fc7c94b1f..149fccca16eeb8 100644
--- a/docs/platforms/javascript/common/configuration/integrations/childProcess.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/childProcess.mdx
@@ -21,7 +21,7 @@ supported:
   - javascript.astro
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in Node.js and requires SDK version `8.39.0` or higher.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/connect.mdx b/docs/platforms/javascript/common/configuration/integrations/connect.mdx
index c9cecb167de19c..da243706406de8 100644
--- a/docs/platforms/javascript/common/configuration/integrations/connect.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/connect.mdx
@@ -8,7 +8,7 @@ supported:
 
 For more information on setting up Sentry Connect support, see the [Connect Sentry documentation](/platforms/javascript/guides/connect/).
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/console.mdx b/docs/platforms/javascript/common/configuration/integrations/console.mdx
index 11efb15a93f00d..d471cff1287b4e 100644
--- a/docs/platforms/javascript/common/configuration/integrations/console.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/console.mdx
@@ -26,7 +26,7 @@ supported:
   - javascript.cloudflare
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside server environments (Node.js, Bun, Deno).
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/dataloader.mdx b/docs/platforms/javascript/common/configuration/integrations/dataloader.mdx
index c96962e3ce1f06..1276477891ebec 100644
--- a/docs/platforms/javascript/common/configuration/integrations/dataloader.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/dataloader.mdx
@@ -22,7 +22,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes. Requires SDK version `8.31.0` or higher.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/denocontext.mdx b/docs/platforms/javascript/common/configuration/integrations/denocontext.mdx
index a5ef3ad099189e..c7e7b4f5eb2aa9 100644
--- a/docs/platforms/javascript/common/configuration/integrations/denocontext.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/denocontext.mdx
@@ -5,7 +5,7 @@ supported:
   - javascript.deno
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Deno runtime.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/denocron.mdx b/docs/platforms/javascript/common/configuration/integrations/denocron.mdx
index 6b02917461acec..74d7875ac43c39 100644
--- a/docs/platforms/javascript/common/configuration/integrations/denocron.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/denocron.mdx
@@ -5,7 +5,7 @@ supported:
   - javascript.deno
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Deno runtime.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/fastify.mdx b/docs/platforms/javascript/common/configuration/integrations/fastify.mdx
index eb2b35d38bda8f..18dcb7bf47e6df 100644
--- a/docs/platforms/javascript/common/configuration/integrations/fastify.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/fastify.mdx
@@ -8,7 +8,7 @@ supported:
 
 For more information on setting up Sentry Fastify support, see the [Fastify Sentry documentation](/platforms/javascript/guides/fastify/).
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/featureflags.mdx b/docs/platforms/javascript/common/configuration/integrations/featureflags.mdx
index 0316b480dc2280..f2d62e74c9b449 100644
--- a/docs/platforms/javascript/common/configuration/integrations/featureflags.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/featureflags.mdx
@@ -23,7 +23,7 @@ notSupported:
 
 <PlatformContent includePath="feature-flags/prerelease-alert" />
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment. It is only available from a package-based install (e.g. `npm` or `yarn`).
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/fs.mdx b/docs/platforms/javascript/common/configuration/integrations/fs.mdx
index 3cd1d3121a18e3..b9c0651f6f9989 100644
--- a/docs/platforms/javascript/common/configuration/integrations/fs.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/fs.mdx
@@ -22,7 +22,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/genericpool.mdx b/docs/platforms/javascript/common/configuration/integrations/genericpool.mdx
index 70dd20faff1b1d..dd351398b971ad 100644
--- a/docs/platforms/javascript/common/configuration/integrations/genericpool.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/genericpool.mdx
@@ -22,7 +22,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes. Requires SDK version `8.29.0` or higher.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/globalhandlers.mdx b/docs/platforms/javascript/common/configuration/integrations/globalhandlers.mdx
index c6b8afefaea869..227fcd17187d86 100644
--- a/docs/platforms/javascript/common/configuration/integrations/globalhandlers.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/globalhandlers.mdx
@@ -16,7 +16,7 @@ notSupported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Browser and Deno runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/graphql.mdx b/docs/platforms/javascript/common/configuration/integrations/graphql.mdx
index 436381afcfb631..7777fbb5d54b54 100644
--- a/docs/platforms/javascript/common/configuration/integrations/graphql.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/graphql.mdx
@@ -23,7 +23,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/hapi.mdx b/docs/platforms/javascript/common/configuration/integrations/hapi.mdx
index a79b89fe2734d2..1889a578bf93fd 100644
--- a/docs/platforms/javascript/common/configuration/integrations/hapi.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/hapi.mdx
@@ -8,7 +8,7 @@ supported:
 
 For more information on setting up Sentry Hapi support, see the [Hapi Sentry documentation](/platforms/javascript/guides/hapi/).
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/http.mdx b/docs/platforms/javascript/common/configuration/integrations/http.mdx
index c4c40fa2506941..a574567f3eb111 100644
--- a/docs/platforms/javascript/common/configuration/integrations/http.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/http.mdx
@@ -23,7 +23,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside server environments (Node.js, Bun, Deno).
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/httpclient.mdx b/docs/platforms/javascript/common/configuration/integrations/httpclient.mdx
index ac0577c0edc46b..87fe24f8adea25 100644
--- a/docs/platforms/javascript/common/configuration/integrations/httpclient.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/httpclient.mdx
@@ -17,7 +17,7 @@ notSupported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/httpcontext.mdx b/docs/platforms/javascript/common/configuration/integrations/httpcontext.mdx
index 4a3decca775179..2552f72a23f4f6 100644
--- a/docs/platforms/javascript/common/configuration/integrations/httpcontext.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/httpcontext.mdx
@@ -18,7 +18,7 @@ notSupported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/inboundfilters.mdx b/docs/platforms/javascript/common/configuration/integrations/inboundfilters.mdx
index 476ef86287752d..95e4e608607a47 100644
--- a/docs/platforms/javascript/common/configuration/integrations/inboundfilters.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/inboundfilters.mdx
@@ -21,11 +21,11 @@ Sentry.init({
 
 ## Options
 
-<Note>
+<Alert>
 
 Remember to pass these options to the root Sentry.init call, not the integration!
 
-</Note>{" "}
+</Alert>{" "}
 
 ### `ignoreErrors`
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/kafka.mdx b/docs/platforms/javascript/common/configuration/integrations/kafka.mdx
index 172bab14e6b17f..c0a1b0f64d5693 100644
--- a/docs/platforms/javascript/common/configuration/integrations/kafka.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/kafka.mdx
@@ -22,7 +22,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes. Requires SDK version `8.30.0` or higher.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/knex.mdx b/docs/platforms/javascript/common/configuration/integrations/knex.mdx
index e1fb4f9fb8af92..34cb01f760eee1 100644
--- a/docs/platforms/javascript/common/configuration/integrations/knex.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/knex.mdx
@@ -22,7 +22,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes. Requires SDK version `8.38.0` or higher.
 
@@ -34,7 +34,7 @@ The `knexIntegration` adds instrumentation for the `knex` library to capture spa
 
 ```javascript
 Sentry.init({
-  integrations: [new Sentry.knexIntegration()],
+  integrations: [Sentry.knexIntegration()],
 });
 ```
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/koa.mdx b/docs/platforms/javascript/common/configuration/integrations/koa.mdx
index 4b7ec379be2783..a64bfa5d911358 100644
--- a/docs/platforms/javascript/common/configuration/integrations/koa.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/koa.mdx
@@ -8,7 +8,7 @@ supported:
 
 For more information on setting up Sentry Koa support, see the [Koa Sentry documentation](/platforms/javascript/guides/koa/).
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/launchdarkly.mdx b/docs/platforms/javascript/common/configuration/integrations/launchdarkly.mdx
index 5dcbfda7256c5f..142f810bfbab99 100644
--- a/docs/platforms/javascript/common/configuration/integrations/launchdarkly.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/launchdarkly.mdx
@@ -23,7 +23,7 @@ notSupported:
 
 <PlatformContent includePath="feature-flags/prerelease-alert" />
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment. It is only available from a package-based install (e.g. `npm` or `yarn`).
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/localvariables.mdx b/docs/platforms/javascript/common/configuration/integrations/localvariables.mdx
index e74cc4e12310ed..f063d9860b4446 100644
--- a/docs/platforms/javascript/common/configuration/integrations/localvariables.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/localvariables.mdx
@@ -25,7 +25,7 @@ supported:
   - javascript.deno
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js runtime.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/lrumemoizer.mdx b/docs/platforms/javascript/common/configuration/integrations/lrumemoizer.mdx
index 8bed1557a11327..bd57da0d919154 100644
--- a/docs/platforms/javascript/common/configuration/integrations/lrumemoizer.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/lrumemoizer.mdx
@@ -25,7 +25,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes. Requires SDK version `8.33.0` or higher.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/modulemetadata.mdx b/docs/platforms/javascript/common/configuration/integrations/modulemetadata.mdx
index 958eaaa7feb302..4e56b4ddb90005 100644
--- a/docs/platforms/javascript/common/configuration/integrations/modulemetadata.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/modulemetadata.mdx
@@ -18,7 +18,7 @@ notSupported:
   - javascript.cloudflare
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/modules.mdx b/docs/platforms/javascript/common/configuration/integrations/modules.mdx
index 9704496b79fc5a..1897dca51d3cb0 100644
--- a/docs/platforms/javascript/common/configuration/integrations/modules.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/modules.mdx
@@ -25,7 +25,7 @@ supported:
   - javascript.cloudflare
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside server environments (Node.js, Bun, Deno).
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/mongo.mdx b/docs/platforms/javascript/common/configuration/integrations/mongo.mdx
index a4f7828b403eb3..236b1f243e70c9 100644
--- a/docs/platforms/javascript/common/configuration/integrations/mongo.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/mongo.mdx
@@ -23,7 +23,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/mongoose.mdx b/docs/platforms/javascript/common/configuration/integrations/mongoose.mdx
index 563be350673a77..168576d4950d24 100644
--- a/docs/platforms/javascript/common/configuration/integrations/mongoose.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/mongoose.mdx
@@ -22,7 +22,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/mysql.mdx b/docs/platforms/javascript/common/configuration/integrations/mysql.mdx
index 3685b1bc67d900..c22db613230157 100644
--- a/docs/platforms/javascript/common/configuration/integrations/mysql.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/mysql.mdx
@@ -23,7 +23,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/mysql2.mdx b/docs/platforms/javascript/common/configuration/integrations/mysql2.mdx
index 81f6aea2319e20..fdd4069b44acc0 100644
--- a/docs/platforms/javascript/common/configuration/integrations/mysql2.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/mysql2.mdx
@@ -23,7 +23,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/nest.mdx b/docs/platforms/javascript/common/configuration/integrations/nest.mdx
index 9068794f2d69e5..64f777c5598eca 100644
--- a/docs/platforms/javascript/common/configuration/integrations/nest.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/nest.mdx
@@ -8,7 +8,7 @@ supported:
 
 For more information on setting up Sentry Nest.js support, see the [Nest.js Sentry documentation](/platforms/javascript/guides/nestjs/).
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/nodecontext.mdx b/docs/platforms/javascript/common/configuration/integrations/nodecontext.mdx
index 53fcf33a5caa53..ad1747d6d2d82f 100644
--- a/docs/platforms/javascript/common/configuration/integrations/nodecontext.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/nodecontext.mdx
@@ -23,7 +23,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js runtime.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/nodefetch.mdx b/docs/platforms/javascript/common/configuration/integrations/nodefetch.mdx
index 5c08d40bf1c1ce..0966331c2be499 100644
--- a/docs/platforms/javascript/common/configuration/integrations/nodefetch.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/nodefetch.mdx
@@ -24,7 +24,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx b/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx
index cb5cf471a8b69a..506f016e2fe02e 100644
--- a/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx
@@ -22,7 +22,7 @@ supported:
   - javascript.astro
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js runtime.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/normalizepath.mdx b/docs/platforms/javascript/common/configuration/integrations/normalizepath.mdx
index 70f0c668124558..b022bdbf89d6ac 100644
--- a/docs/platforms/javascript/common/configuration/integrations/normalizepath.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/normalizepath.mdx
@@ -5,7 +5,7 @@ supported:
   - javascript.deno
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Deno runtime.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/onuncaughtexception.mdx b/docs/platforms/javascript/common/configuration/integrations/onuncaughtexception.mdx
index d20afc7f50cc62..cd2b17a84d9550 100644
--- a/docs/platforms/javascript/common/configuration/integrations/onuncaughtexception.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/onuncaughtexception.mdx
@@ -25,7 +25,7 @@ supported:
   - javascript.cloudflare
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside server environments (Node.js, Bun, Deno).
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/openfeature.mdx b/docs/platforms/javascript/common/configuration/integrations/openfeature.mdx
index e542ac08d8f6bd..1a2f0cec583ed7 100644
--- a/docs/platforms/javascript/common/configuration/integrations/openfeature.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/openfeature.mdx
@@ -23,7 +23,7 @@ notSupported:
 
 <PlatformContent includePath="feature-flags/prerelease-alert" />
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment. It is only available from a package-based install (e.g. `npm` or `yarn`).
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/postgres.mdx b/docs/platforms/javascript/common/configuration/integrations/postgres.mdx
index 2fa7aa9cae3506..95aa4eb35e68ac 100644
--- a/docs/platforms/javascript/common/configuration/integrations/postgres.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/postgres.mdx
@@ -23,7 +23,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/prisma.mdx b/docs/platforms/javascript/common/configuration/integrations/prisma.mdx
index 73ceb892373c4b..1461d9e8fe4dd1 100644
--- a/docs/platforms/javascript/common/configuration/integrations/prisma.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/prisma.mdx
@@ -22,9 +22,9 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
-This integration only works in the Node.js and Bun runtimes. This integration only supports Prisma v5 at the current time. If you're interested in Prisma v6 support, please leave your thoughts on the [Prisma v6 tracking issue for the Sentry SDK](https://github.com/getsentry/sentry-javascript/issues/14793).
+This integration only works in the Node.js and Bun runtimes.
 
 </Alert>
 
@@ -34,7 +34,31 @@ Sentry supports tracing [Prisma ORM](https://www.prisma.io/) queries with the Pr
 
 The Prisma Integrations creates a spans for each query and reports to Sentry with relevant details inside `description` if available.
 
-To install the integration, first enable the `tracing` feature flag in the `generator` block of your Prisma schema:
+## Prisma Version 6
+
+The Sentry Prisma Integration comes with Prisma version 5 support by default. For Prisma version 6 compatibility we need to pass a specific version of the Prisma instrumentation to the Sentry Prisma integration.
+
+To use the integration with Prisma version 6, first install the `@prisma/instrumentation` package on version 6 (ideally the exact same version as your `prisma` and `@prisma/client` packages).
+
+Then, add the `prismaIntegration` to your Sentry initialization as follows:
+
+```javascript {1,6-9}
+import { PrismaInstrumentation } from "@prisma/instrumentation";
+
+Sentry.init({
+  tracesSampleRate: 1.0,
+  integrations: [
+    Sentry.prismaIntegration({
+      // Override the default instrumentation that Sentry uses
+      prismaInstrumentation: new PrismaInstrumentation(),
+    }),
+  ],
+});
+```
+
+## Prisma Version 5
+
+To install the integration for Prisma version 5, first enable the `tracing` feature flag in the `generator` block of your Prisma schema:
 
 ```txt {tabTitle: Prisma Schema} {filename: schema.prisma} {3}
 generator client {
@@ -52,7 +76,14 @@ Sentry.init({
 });
 ```
 
+## Options
+
+### `prismaInstrumentation`
+
+_Type: `Instrumentation`_ (An OpenTelemetry type)
+
+Overrides the instrumentation used by the Sentry SDK with the passed in instrumentation instance.
 
 ## Supported Versions
 
-- `prisma`: `>=5 <6`
+- `prisma`: `>=5`
diff --git a/docs/platforms/javascript/common/configuration/integrations/processThreadsBreadcrumb.mdx b/docs/platforms/javascript/common/configuration/integrations/processThreadsBreadcrumb.mdx
index d783c2d517b5b1..a65b8935bfe6e9 100644
--- a/docs/platforms/javascript/common/configuration/integrations/processThreadsBreadcrumb.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/processThreadsBreadcrumb.mdx
@@ -27,7 +27,7 @@ This integration is deprecated and has been replaced with the <PlatformLink to="
 
 </Alert>
 
-<Alert level="info">
+<Alert>
 
 This integration only works in Node.js and requires SDK version `8.36.0` or higher.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/redis.mdx b/docs/platforms/javascript/common/configuration/integrations/redis.mdx
index 392ca10f72c237..aff67f075ec9f4 100644
--- a/docs/platforms/javascript/common/configuration/integrations/redis.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/redis.mdx
@@ -23,7 +23,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/replay.mdx b/docs/platforms/javascript/common/configuration/integrations/replay.mdx
index 90029b8a1ee89b..17c4953f35cd7e 100644
--- a/docs/platforms/javascript/common/configuration/integrations/replay.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/replay.mdx
@@ -19,7 +19,7 @@ notSupported:
   - javascript.cloudflare
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/replaycanvas.mdx b/docs/platforms/javascript/common/configuration/integrations/replaycanvas.mdx
index 73c3f1df02ab79..4fd21fde57e236 100644
--- a/docs/platforms/javascript/common/configuration/integrations/replaycanvas.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/replaycanvas.mdx
@@ -19,7 +19,7 @@ notSupported:
   - javascript.cloudflare
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/reportingobserver.mdx b/docs/platforms/javascript/common/configuration/integrations/reportingobserver.mdx
index 961ffe884895af..903fc36f72a65c 100644
--- a/docs/platforms/javascript/common/configuration/integrations/reportingobserver.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/reportingobserver.mdx
@@ -17,7 +17,7 @@ notSupported:
   - javascript.cloudflare
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside a browser environment.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/requestdata.mdx b/docs/platforms/javascript/common/configuration/integrations/requestdata.mdx
index 557d8e0270c965..75f115a115bb27 100644
--- a/docs/platforms/javascript/common/configuration/integrations/requestdata.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/requestdata.mdx
@@ -24,7 +24,7 @@ supported:
   - javascript.cloudflare
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside server environments (Node.js, Bun, Deno).
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/tedious.mdx b/docs/platforms/javascript/common/configuration/integrations/tedious.mdx
index 1e7d86f71be9ee..3e84cd69a9ce98 100644
--- a/docs/platforms/javascript/common/configuration/integrations/tedious.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/tedious.mdx
@@ -25,7 +25,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes. Requires SDK version `8.38.0` or higher.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/trpc.mdx b/docs/platforms/javascript/common/configuration/integrations/trpc.mdx
index 9e613642ad54a7..934a5378e27173 100644
--- a/docs/platforms/javascript/common/configuration/integrations/trpc.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/trpc.mdx
@@ -25,7 +25,7 @@ supported:
   - javascript.cloudflare
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside server environments (Node.js, Bun, Deno).
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/unhandledrejection.mdx b/docs/platforms/javascript/common/configuration/integrations/unhandledrejection.mdx
index a876b28a96cace..b11c855bb9c88c 100644
--- a/docs/platforms/javascript/common/configuration/integrations/unhandledrejection.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/unhandledrejection.mdx
@@ -25,7 +25,7 @@ supported:
   - javascript.cloudflare
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works inside server environments (Node.js, Bun, Deno).
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/unleash.mdx b/docs/platforms/javascript/common/configuration/integrations/unleash.mdx
new file mode 100644
index 00000000000000..765f61b3f24408
--- /dev/null
+++ b/docs/platforms/javascript/common/configuration/integrations/unleash.mdx
@@ -0,0 +1,40 @@
+---
+title: Unleash
+description: "Learn how to use Sentry with Unleash."
+notSupported:
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.bun
+  - javascript.capacitor
+  - javascript.cloudflare
+  - javascript.connect
+  - javascript.cordova
+  - javascript.deno
+  - javascript.electron
+  - javascript.express
+  - javascript.fastify
+  - javascript.gcp-functions
+  - javascript.hapi
+  - javascript.koa
+  - javascript.nestjs
+  - javascript.nodejs
+  - javascript.wasm
+---
+
+<PlatformContent includePath="feature-flags/prerelease-alert" />
+
+<Alert level="info">
+
+This integration only works inside a browser environment. It is only available from a package-based install (e.g. `npm` or `yarn`).
+
+</Alert>
+
+The [Unleash](https://www.getunleash.io/) integration tracks feature flag evaluations produced by the Unleash SDK. These evaluations are held in memory, and in the event an error occurs, sent to Sentry for review and analysis. **At the moment, we only support boolean flag evaluations.** This integration is available in Sentry SDK **versions 8.51.0 or higher.**
+
+_Import names: `Sentry.unleashIntegration`_
+
+<PlatformContent includePath="/configuration/unleash" />
+
+Visit the Sentry website and confirm that your error event has recorded the feature flag "test-flag" and its value "false".
+
+<PlatformContent includePath="feature-flags/next-steps" />
diff --git a/docs/platforms/javascript/common/configuration/integrations/vercelai.mdx b/docs/platforms/javascript/common/configuration/integrations/vercelai.mdx
index b6f14e96cd1b20..86dbe724576f4f 100644
--- a/docs/platforms/javascript/common/configuration/integrations/vercelai.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/vercelai.mdx
@@ -21,7 +21,7 @@ supported:
   - javascript.bun
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Node.js and Bun runtimes. Requires SDK version `8.43.0` or higher.
 
diff --git a/docs/platforms/javascript/common/configuration/integrations/vue.mdx b/docs/platforms/javascript/common/configuration/integrations/vue.mdx
index 4aab792453ec61..ea39b8c5bb5d26 100644
--- a/docs/platforms/javascript/common/configuration/integrations/vue.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/vue.mdx
@@ -5,7 +5,7 @@ supported:
   - javascript.vue
 ---
 
-<Alert level="info">
+<Alert>
 
   This integration is enabled by default (recommended) but can also be added manually.
 
@@ -38,4 +38,3 @@ const app = createApp({
 
 Sentry.addIntegration(Sentry.vueIntegration({ app }));
 `
-
diff --git a/docs/platforms/javascript/common/configuration/integrations/wintercgfetch.mdx b/docs/platforms/javascript/common/configuration/integrations/wintercgfetch.mdx
index d8eb8bafc80d76..c52e1ded61265c 100644
--- a/docs/platforms/javascript/common/configuration/integrations/wintercgfetch.mdx
+++ b/docs/platforms/javascript/common/configuration/integrations/wintercgfetch.mdx
@@ -6,7 +6,7 @@ supported:
   - javascript.nuxt
 ---
 
-<Alert level="info">
+<Alert>
 
 This integration only works in the Edge runtime.
 
diff --git a/docs/platforms/javascript/common/configuration/options.mdx b/docs/platforms/javascript/common/configuration/options.mdx
index 0fca67939aa861..9e02d380436878 100644
--- a/docs/platforms/javascript/common/configuration/options.mdx
+++ b/docs/platforms/javascript/common/configuration/options.mdx
@@ -14,12 +14,12 @@ initialized.
 
 The list of common options across SDKs. These work more or less the same in all SDKs, but some subtle differences will exist to better support the platform. Options that can be read from an environment variable (`SENTRY_DSN`, `SENTRY_ENVIRONMENT`, `SENTRY_RELEASE`) are read automatically.
 
-<Note>
+<Alert>
 
 If you are using a framework or runtime that requires a prefix to expose environment variables to the client, you must set these options in the `init()` function. These options will not be read into the client side automatically.
 This applies to `NEXT_PUBLIC_` in [Next.js](https://nextjs.org/docs/app/building-your-application/configuring/environment-variables) and `VITE_` in [Vite](https://vitejs.dev/guide/env-and-mode.html#env-files), among others.
 
-</Note>
+</Alert>
 
 <ConfigKey name="dsn">
 
diff --git a/docs/platforms/javascript/common/configuration/releases.mdx b/docs/platforms/javascript/common/configuration/releases.mdx
index 755f3d838912e0..1466da72764cdc 100644
--- a/docs/platforms/javascript/common/configuration/releases.mdx
+++ b/docs/platforms/javascript/common/configuration/releases.mdx
@@ -31,11 +31,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -64,11 +64,11 @@ After configuring your SDK, you can install a repository integration or manually
 
 Monitor the [health of releases](/product/releases/health/) by observing user adoption, usage of the application, percentage of [crashes](/product/releases/health/#crash), and [session data](/product/releases/health/#session). Release health will provide insight into the impact of crashes and bugs as it relates to user experience, and reveal trends with each new issue through the [Release Details](/product/releases/release-details/) graphs and filters.
 
-<Note>
+<Alert>
 
 Crash reporting and app hang detection are not available for watchOS.
 
-</Note>
+</Alert>
 
 In order to monitor release health, the SDK sends session data.
 
diff --git a/docs/platforms/javascript/common/configuration/sampling.mdx b/docs/platforms/javascript/common/configuration/sampling.mdx
index 0bb775bea4b774..da132f6a716609 100644
--- a/docs/platforms/javascript/common/configuration/sampling.mdx
+++ b/docs/platforms/javascript/common/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 <PlatformSection notSupported={["javascript.electron"]}>
 
diff --git a/docs/platforms/javascript/common/configuration/tree-shaking.mdx b/docs/platforms/javascript/common/configuration/tree-shaking.mdx
index ac89d6049d938d..68df1ea4da0d96 100644
--- a/docs/platforms/javascript/common/configuration/tree-shaking.mdx
+++ b/docs/platforms/javascript/common/configuration/tree-shaking.mdx
@@ -17,7 +17,7 @@ If you want to minimize the bundle size of the Sentry SDK, we recommend reading
 
 The Sentry SDK ships with code that is not strictly required for it to collect your errors. This includes code to debug your Sentry configuration or code to enable tracing, for example. While debug code can be very useful in development environments, it's not typically necessary to include it in your production bundles where it takes up valuable space. The JavaScript SDK includes special flags in its CommonJS and ESM distributions, which can be used to facilitate tree shaking (removal) of this kind of code during the build process.
 
-<Note>
+<Alert>
   Anything that you don't import and use will <i>automatically</i> be tree
   shaken away when using any modern bundler like Webpack, Rollup, Vite, or
   similar. This means that optional integrations like Replay, BrowserTracing,
@@ -25,7 +25,7 @@ The Sentry SDK ships with code that is not strictly required for it to collect y
   bundle unless you import and use them yourself. The rest of this page relates
   to ways to tree shake internal SDK code, which isn't strictly required unless
   you use certain features.
-</Note>
+</Alert>
 
 <PlatformSection notSupported={["javascript.nextjs", "javascript.nuxt", "javascript.solidstart", "javascript.sveltekit", "javascript.remix", "javascript.astro"]}>
 
@@ -118,9 +118,9 @@ Replacing this flag with `false` will tree shake any SDK code that's related to
 
 Replacing this flag with `false` will tree shake any SDK code that's related to tracing.
 
-<Note>
+<Alert>
 `__SENTRY_TRACING__` must not be replaced with `false` when you're using any tracing-related SDK features (for example,`Sentry.startTransaction()`). This flag is intended to be used in combination with packages like `@sentry/next` or `@sentry/sveltekit`, which automatically include the tracing functionality.
-</Note>
+</Alert>
 
 <PlatformCategorySection supported={['browser']}>
 This has no effect if you did not add `browserTracingIntegration`.
@@ -284,12 +284,12 @@ getCurrentScope().setClient(client);
 client.init();
 ```
 
-<Note>
+<Alert>
 
 In contrast to `Sentry.init`, the `Client` constructor expects options of type `ClientOptions` instead of `Options`.
 This means that the `ClientOptions.integrations` property is the final array of all integrations that will be used.
 
-</Note>
+</Alert>
 </PlatformCategorySection>
 
 <PlatformSection supported={[
diff --git a/docs/platforms/javascript/common/crons/index.mdx b/docs/platforms/javascript/common/crons/index.mdx
index e22726f7301bed..4444b3073a1942 100644
--- a/docs/platforms/javascript/common/crons/index.mdx
+++ b/docs/platforms/javascript/common/crons/index.mdx
@@ -85,11 +85,11 @@ GET /api/___PROJECT_ID___/cron/<monitor_slug>/___PUBLIC_KEY___/?status=error HTT
 Host: ___ORG_INGEST_DOMAIN___
 ```
 
-<Note>
+<Alert>
 
 If you expect your scheduled jobs to overlap, read about [Overlapping Jobs](#overlapping-jobs-optional) below.
 
-</Note>
+</Alert>
 
 ### Specifying monitor environments (Optional)
 
@@ -99,7 +99,7 @@ environments.
 
 If you don't specify an environment with your check-ins the default is `production`.
 
-<Alert level="info">
+<Alert>
 
 Monitor environments are still early in development. Currently, after a check-in
 occurs for a specific environment, you must continue sending check-ins on
@@ -173,11 +173,11 @@ This is an object specifying a `schedule_type` of either `crontab` or `interval`
 
 The amount of time (in minutes) Sentry should wait for your check-in before it's considered missed ("grace period"). Optional.
 
-<Note>
+<Alert>
 
 We recommend that your check-in margin be less than or equal to your interval.
 
-</Note>
+</Alert>
 
 `max_runtime`:
 
diff --git a/docs/platforms/javascript/common/data-management/debug-files/identifiers/index.mdx b/docs/platforms/javascript/common/data-management/debug-files/identifiers/index.mdx
index 20115c925e77e5..63098b550cf60e 100644
--- a/docs/platforms/javascript/common/data-management/debug-files/identifiers/index.mdx
+++ b/docs/platforms/javascript/common/data-management/debug-files/identifiers/index.mdx
@@ -27,14 +27,14 @@ compute a _Debug Identifier_ for each uploaded file. This identifier is
 associated with executables and libraries as well as debug companions to ensure
 that they can be uniquely located via one common mechanism.
 
-<Note>
+<Alert>
 
 Debug information does not have to be associated with releases. The unique debug
 identifier ensures that Sentry can choose the right files for every crash
 report. However, it is still recommended to configure releases in the client to
 benefit from other features.
 
-</Note>
+</Alert>
 
 For native events, the issue details page displays a list of _Loaded Images_.
 This list contains the executable and all loaded dynamic libraries including
diff --git a/docs/platforms/javascript/common/data-management/debug-files/index.mdx b/docs/platforms/javascript/common/data-management/debug-files/index.mdx
index f2806f21db4bdc..b17c55f2273cb5 100644
--- a/docs/platforms/javascript/common/data-management/debug-files/index.mdx
+++ b/docs/platforms/javascript/common/data-management/debug-files/index.mdx
@@ -27,12 +27,12 @@ the following formats:
 - [_ProGuard mappings_](./file-formats/#proguard-mappings) for
   Java and Android
 
-<Note>
+<Alert>
 
 Source maps, while also being debug information files, are handled
 differently in Sentry. For more information see [Source Maps in sentry-cli](/cli/releases/#sentry-cli-sourcemaps).
 
-</Note>
+</Alert>
 
 Sentry requires access to debug information files of your application as well as
 system libraries to provide fully symbolicated crash reports. You can either
@@ -49,11 +49,11 @@ for automatic downloads.
 From the [Project Details](/product/projects/project-details/) page, click into settings,
 then click on _Debug Files_ in the page navigation.
 
-<Note>
+<Alert>
 
 ProGuard files are listed separately, in the _ProGuard_ section of the project settings page.
 
-</Note>
+</Alert>
 
 ## Retention Policy
 
diff --git a/docs/platforms/javascript/common/data-management/debug-files/symbol-servers/index.mdx b/docs/platforms/javascript/common/data-management/debug-files/symbol-servers/index.mdx
index d4a3b208a94cdb..4a89178f4519ce 100644
--- a/docs/platforms/javascript/common/data-management/debug-files/symbol-servers/index.mdx
+++ b/docs/platforms/javascript/common/data-management/debug-files/symbol-servers/index.mdx
@@ -45,7 +45,7 @@ Beware that these cause notifications to your team members.
 
 ## Custom Repositories
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 Custom repositories are available for organizations on the _Business_ and
 _Enterprise_ plans.
diff --git a/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx b/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx
index e1484770d884d7..71236d14386856 100644
--- a/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx
@@ -24,13 +24,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 If you _do not_ wish to use the default PII behavior, you can also choose to identify users in a more controlled manner, using our [user identity context](../../enriching-events/identify-user/).
 
diff --git a/docs/platforms/javascript/common/enriching-events/attachments/index.mdx b/docs/platforms/javascript/common/enriching-events/attachments/index.mdx
index 1b6bebddcc4abb..3a2ed2fd7cd61e 100644
--- a/docs/platforms/javascript/common/enriching-events/attachments/index.mdx
+++ b/docs/platforms/javascript/common/enriching-events/attachments/index.mdx
@@ -13,11 +13,11 @@ You'll first need to import the SDK, as usual:
 
 <PlatformContent includePath="enriching-events/add-attachment" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/javascript/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/javascript/common/enriching-events/breadcrumbs/index.mdx
index 2c84f0ffac7dbe..b3a0d840fa1683 100644
--- a/docs/platforms/javascript/common/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/javascript/common/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/javascript/common/enriching-events/context/index.mdx b/docs/platforms/javascript/common/enriching-events/context/index.mdx
index f28b365f281fe3..c39a461affdf33 100644
--- a/docs/platforms/javascript/common/enriching-events/context/index.mdx
+++ b/docs/platforms/javascript/common/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
@@ -90,11 +90,11 @@ Sentry.captureException(new Error("something went wrong"), () => scope);
 Context is held in the current scope and thus is cleared when the scope is removed ("popped"). You can push and pop your own scopes to apply context data to a specific code block or function.
 
 <PlatformCategorySection supported={['server', 'serverless']}>
-<Note>
+<Alert>
 
 For Node.js backend frameworks, the SDK will create a separate scope for each incoming request. Modifying the context of the current scope in a request handler will therefore only affect events related to the request being handled.
 
-</Note>
+</Alert>
 </PlatformCategorySection>
 
 Sentry supports two different ways for unsetting context:
diff --git a/docs/platforms/javascript/common/enriching-events/tags/index.mdx b/docs/platforms/javascript/common/enriching-events/tags/index.mdx
index 9f70cfb7d967b3..0b5321e0ae8557 100644
--- a/docs/platforms/javascript/common/enriching-events/tags/index.mdx
+++ b/docs/platforms/javascript/common/enriching-events/tags/index.mdx
@@ -21,11 +21,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx b/docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
index fa2c9714ebeab5..9096d38425ae33 100644
--- a/docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
+++ b/docs/platforms/javascript/common/enriching-events/transaction-name/index.mdx
@@ -115,9 +115,9 @@ Sentry.init({
 });
 ```
 
-<Note>
+<Alert>
   Only do this if you can't set the root span name earlier using other options.
-</Note>
+</Alert>
 
 ## Further Information
 
diff --git a/docs/platforms/javascript/common/index.mdx b/docs/platforms/javascript/common/index.mdx
index 3b0cae9c6bcd6b..ca1c07e5a3bac1 100644
--- a/docs/platforms/javascript/common/index.mdx
+++ b/docs/platforms/javascript/common/index.mdx
@@ -2,7 +2,7 @@
 
 <PlatformSection noGuides>
 
-<Alert level="info" title="Using a framework?">
+<Alert title="Using a framework?">
 
 Check out the other SDKs we support in the left-hand dropdown.
 
@@ -102,11 +102,11 @@ This snippet includes an intentional error, so you can test that everything is w
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
 
diff --git a/docs/platforms/javascript/common/install/index.mdx b/docs/platforms/javascript/common/install/index.mdx
index fb65f1d213feff..c3cf995910f306 100644
--- a/docs/platforms/javascript/common/install/index.mdx
+++ b/docs/platforms/javascript/common/install/index.mdx
@@ -74,11 +74,11 @@ Using the Loader Script is the easiest way to start using Sentry. Add a script t
 
 - **Lazy-loading**: If you just want to use Sentry for errors, we'll only load the SDK when an error occurs, reducing the amount of JavaScript loaded on your page until then.
 
-  <Note>
+  <Alert>
     Note that when enabling Session Replay and/or Tracing, the SDK will be
     loaded immediately because we need to capture what's happening on the page
     as early as possible.
-  </Note>
+  </Alert>
 
 ### Why Choose NPM Over the Loader Script
 
diff --git a/docs/platforms/javascript/common/install/late-initialization.mdx b/docs/platforms/javascript/common/install/late-initialization.mdx
index 2f9285fe9139a2..1dbf1f36de4afa 100644
--- a/docs/platforms/javascript/common/install/late-initialization.mdx
+++ b/docs/platforms/javascript/common/install/late-initialization.mdx
@@ -21,11 +21,11 @@ In order for auto-instrumentation to work, it is generally required to run `Sent
 
 However, in some cases this may not be possible to do—for example, if you are fetching your DSN from an external source. In this case, you can use the `@sentry/node/preload` hook to ensure modules are wrapped early, which allows you to call `Sentry.init()` later at a time of your choosing.
 
-<Note>
+<Alert>
   We recommend to only use this method if strictly necessary. In most cases, it
   is better to find a way to run `Sentry.init()` early in your application, in
   order to ensure that no error can go unreported.
-</Note>
+</Alert>
 
 This initialization method is available starting in version **8.5.0**.
 
diff --git a/docs/platforms/javascript/common/opentelemetry/custom-setup.mdx b/docs/platforms/javascript/common/opentelemetry/custom-setup.mdx
index 35d4a6240b58ed..f2f716ef942923 100644
--- a/docs/platforms/javascript/common/opentelemetry/custom-setup.mdx
+++ b/docs/platforms/javascript/common/opentelemetry/custom-setup.mdx
@@ -24,13 +24,13 @@ notSupported:
 sidebar_order: 0
 ---
 
-<Note>
+<Alert>
 
 Use this guide when you already have a completely custom OpenTelemetry setup or when you intend to add a custom OpenTelemetry setup next to the Sentry SDK.
 
 If you are looking to simply add individual OpenTelemetry instrumentation to your Sentry setup, you should read <PlatformLink to="/opentelemetry/using-opentelemetry-apis/#adding-additional-opentelemetry-instrumentation">Adding Additional OpenTelemetry Instrumentation</PlatformLink> instead.
 
-</Note>
+</Alert>
 
 To use an existing OpenTelemetry setup, set `skipOpenTelemetrySetup: true` in your `init({})` config, then set up all the components that Sentry needs yourself. Finish by installing `@sentry/opentelemetry` and adding the following:
 
@@ -93,7 +93,7 @@ In order for the Sentry SDK to work as expected, and for it to be in sync with O
 
 - **SentrySpanProcessor**: Ensures that spans are correctly sent to Sentry.
 
-<Note>
+<Alert>
   Trace propagation is needed for Sentry to automatically connect services
   together. (For example, if you want to connect the frontend and backend, or
   different backend services.) This makes it possible to see related errors
@@ -101,7 +101,7 @@ In order for the Sentry SDK to work as expected, and for it to be in sync with O
   <PlatformLink to="/tracing/trace-propagation">
     Learn more about Trace Propagation.
   </PlatformLink>
-</Note>
+</Alert>
 
 The following code snippet shows how to set up Sentry for error monitoring only:
 
@@ -165,14 +165,14 @@ If tracing is not enabled (no `tracesSampleRate` is defined in the SDK configura
 <PlatformSection
   notSupported={["javascript.aws-lambda", "javascript.gcp-functions"]}
 >
-  <Note>
+  <Alert>
     If tracing is not enabled, performance instrumentations will not be
     registered but they will still be included in the bundle. If you want to
     reduce the bundle size or used dependencies, you can also{" "}
     <PlatformLink to="/configuration/tree-shaking/#setting-up-sentry-without-performance-integrations">
       Set up Sentry without Performance Integrations
     </PlatformLink>
-  </Note>
+  </Alert>
 </PlatformSection>
 
 These are needed to make sure that trace propagation works correctly.
@@ -267,7 +267,7 @@ Sentry.init({
 });
 ```
 
-<Alert level="info" title="Why is it recommended to register loader hooks yourself?">
+<Alert title="Why is it recommended to register loader hooks yourself?">
 
 It is recommended registering your own ESM loader hooks when you have a complete custom OpenTelemetry setup, first and foremost because it makes the most sense architecturally.
 You likely went through the effort to set up OpenTelemetry by itself and now you want to add Sentry to your application without messing with your OpenTelemetry setup.
diff --git a/docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx b/docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx
index 4ea751284fd04b..6f5e7b343dc0c5 100644
--- a/docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx
+++ b/docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx
@@ -47,7 +47,7 @@ Sentry.init({
 });
 ```
 
-<Note>
+<Alert>
   It is possible to add instrumentations via `registerInstrumentations()` from
   `@opentelemetry/instrumentation`. However, with ESM (`import`/`export` syntax)
   you need to be careful to do so before importing any modules that should be
@@ -55,7 +55,7 @@ Sentry.init({
 
 As a rule of thumb, `registerInstrumentations()` should be called right after, and in the same context as registering <PlatformLink to="/opentelemetry/custom-setup/#esm-loaders">ESM Loaders</PlatformLink>.
 
-</Note>
+</Alert>
 
 ## Using an OpenTelemetry Tracer
 
diff --git a/docs/platforms/javascript/common/profiling/browser-profiling.mdx b/docs/platforms/javascript/common/profiling/browser-profiling.mdx
index 88ef66583980c6..134e4890581fea 100644
--- a/docs/platforms/javascript/common/profiling/browser-profiling.mdx
+++ b/docs/platforms/javascript/common/profiling/browser-profiling.mdx
@@ -22,11 +22,11 @@ notSupported:
 description: "Collect & view performance insights for JavaScript programs with Sentry's JavaScript Profiling integration."
 ---
 
-<Note>
+<Alert>
 
 Browser Profiling is currently in beta. Beta features are still in progress and may have bugs. We recognize the irony.
 
-</Note>
+</Alert>
 
 The browser profiling integration is built using the [JS Self-Profiling API](https://wicg.github.io/js-self-profiling/) and will likely only move out of beta once the specification progresses and gains adoption. See [platform status](https://chromestatus.com/feature/5170190448852992).
 
diff --git a/docs/platforms/javascript/common/profiling/node-profiling.mdx b/docs/platforms/javascript/common/profiling/node-profiling.mdx
index 42ccf5fb0edd6e..da4ae6ccf6b4eb 100644
--- a/docs/platforms/javascript/common/profiling/node-profiling.mdx
+++ b/docs/platforms/javascript/common/profiling/node-profiling.mdx
@@ -21,11 +21,11 @@ supported:
 
 By default, Sentry error events will not get trace context unless you configure the scope with the transaction, as illustrated in the example below.
 
-<Note>
+<Alert>
 
 If you're adopting Profiling in a high-throughput environment, we recommend testing prior to deployment to ensure that your service's performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 ## Installation
 
diff --git a/docs/platforms/javascript/common/session-replay/configuration.mdx b/docs/platforms/javascript/common/session-replay/configuration.mdx
index d8a4c6ede5c41b..afd2c7703dd212 100644
--- a/docs/platforms/javascript/common/session-replay/configuration.mdx
+++ b/docs/platforms/javascript/common/session-replay/configuration.mdx
@@ -65,12 +65,12 @@ By default, Replay will capture basic information about all outgoing fetch and X
 
 To capture additional information such as request and response headers or bodies, you'll need to opt-in via `networkDetailAllowUrls` (requires SDK version >= [7.50.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.50.0)). This will make it possible for you to elect to only add URLs that are safe for capturing bodies and avoid any endpoints that may contain Personal Identifiable Information, (PII).
 
-<Note>
+<Alert>
 
 Content in bodies will be PII-sanitized server-side, based on object keys and values.
 Refer to our <PlatformLink to="/session-replay/privacy/#network-request-and-response-bodies-and-headers">Replay Privacy section</PlatformLink> for more details.
 
-</Note>
+</Alert>
 
 Any URL matching the given pattern(s) will then be captured with additional details:
 
@@ -102,7 +102,7 @@ replayIntegration({
 });
 ```
 
-<Note>Captured bodies will be truncated to 150k characters max.</Note>
+<Alert>aptured bodies will be truncated to 150k characters max.</Alert>
 
 ## Identifying Users
 
diff --git a/docs/platforms/javascript/common/session-replay/index.mdx b/docs/platforms/javascript/common/session-replay/index.mdx
index 78202a8b41026b..4090880f29a2d5 100644
--- a/docs/platforms/javascript/common/session-replay/index.mdx
+++ b/docs/platforms/javascript/common/session-replay/index.mdx
@@ -27,7 +27,7 @@ description: "Learn how to enable Session Replay in your app if it is not alread
 By default, our Session Replay SDK masks all DOM text content, images, and user input, giving you heightened confidence that no sensitive data will leave the browser. To learn more, see <PlatformLink to="/session-replay/privacy">Session Replay Privacy</PlatformLink>.
 
 <PlatformSection supported={["javascript.angular"]}>
-  <Alert level="danger">
+  <Alert level="warning">
     Angular's <a target="_blank" rel="noopener noreferrer" href="https://angular.dev/api/core/ChangeDetectionStrategy#Default">default "Change Detection" strategy</a> monkeypatches browser globals and can break or cause performance regressions in your application when using Session Replay. To avoid this, we recommend you use the `OnPush` strategy when using Angular.
   </Alert>
 </PlatformSection>
@@ -125,11 +125,11 @@ If you're unable to update your CSP policy to allow inline web workers, you can
 A user session starts when the Session Replay SDK is first loaded and initialized.
 The session will capture any pageloads, refreshes, or navigations as long as the SDK is re-initialized on the same domain, and in the same browser tab, each time. Sessions continue capturing data until 5 minutes pass without any user interactions **or** until a maximum of 60 minutes have elapsed. Closing the browser tab will end the session immediately, according to the rules for [SessionStorage](https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage).
 
-<Note>
+<Alert>
 
 An _interaction_ refers to either a mouse click or a browser navigation event.
 
-</Note>
+</Alert>
 
 ### Replay Captures on Errors Only
 
diff --git a/docs/platforms/javascript/common/session-replay/issue-types.mdx b/docs/platforms/javascript/common/session-replay/issue-types.mdx
index 270bafb9bacee1..ba3a0eb7c15684 100644
--- a/docs/platforms/javascript/common/session-replay/issue-types.mdx
+++ b/docs/platforms/javascript/common/session-replay/issue-types.mdx
@@ -32,10 +32,10 @@ You can configure which issue types are created by visiting Project Settings > R
 
 Sometimes rage or dead clicks will be detected on elements which are not expected to mutate the DOM, like a "Print" or "Download" button. In this case, you can configure `slowClickIgnoreSelectors`, which will prevent those buttons from generating new issues.
 
-<Note>
+<Alert>
   You'll need to have SDK version 7.60.1 or higher in order to be able to see
   **rage click issues**.
-</Note>
+</Alert>
 
 ## Configuring Hydration Errors
 
@@ -51,7 +51,7 @@ You can have your preferences configured in one of four ways:
 | disabled | enabled | Two issues created from both replay, and error data. The issues are duplicates. |
 | disabled | disabled | Issue created from captured error data. |
 
-<Note>
+<Alert>
   You'll need to have SDK version 7.87.0 or higher in order to be able to detect
   **hydration error issues** from replay data.
-</Note>
+</Alert>
diff --git a/docs/platforms/javascript/common/session-replay/understanding-sessions.mdx b/docs/platforms/javascript/common/session-replay/understanding-sessions.mdx
index 52dc0004d355b6..df15460b474908 100644
--- a/docs/platforms/javascript/common/session-replay/understanding-sessions.mdx
+++ b/docs/platforms/javascript/common/session-replay/understanding-sessions.mdx
@@ -190,8 +190,9 @@ If you want to skip capturing a Replay for certain errors, you can use the `befo
 
 ```javascript
 replayIntegration({
-  beforeErrorSampling: (error) => {
-    return error.message?.includes("drop me");
+  beforeErrorSampling: (event) => {
+    // Return false to skip capturing a Replay for this error
+    return !event.exception?.values?.[0]?.value?.includes("drop me");
   },
 });
 ```
diff --git a/docs/platforms/javascript/common/sourcemaps/uploading/angular-nx.mdx b/docs/platforms/javascript/common/sourcemaps/uploading/angular-nx.mdx
index ec66e95766ae6b..d03f70c0ea3c2c 100644
--- a/docs/platforms/javascript/common/sourcemaps/uploading/angular-nx.mdx
+++ b/docs/platforms/javascript/common/sourcemaps/uploading/angular-nx.mdx
@@ -45,13 +45,13 @@ Check out the example below: in your `project.json`, replace the default executo
 
 ## 2. Register the Sentry Bundler Plugin
 
-<Note>
+<Alert>
 
 This guide assumes you are using a Sentry SDK on version `7.47.0` or higher.
 
 If you are on an older version and you want to upload source maps we recommend upgrading your SDK to the newest version.
 
-</Note>
+</Alert>
 
 To upload source maps you have to configure an [Organization Auth Token](https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/).
 
@@ -167,9 +167,9 @@ To upload the source maps, build your Angular application:
 nx build
 ```
 
-<Note>
+<Alert>
 
 The Sentry webpack plugin doesn't upload source maps in watch-mode/development-mode.
 We recommend running a production build to test your implementation.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/javascript/common/sourcemaps/uploading/angular-webpack.mdx b/docs/platforms/javascript/common/sourcemaps/uploading/angular-webpack.mdx
index 103d3b64b8653e..aae85460f6c4c0 100644
--- a/docs/platforms/javascript/common/sourcemaps/uploading/angular-webpack.mdx
+++ b/docs/platforms/javascript/common/sourcemaps/uploading/angular-webpack.mdx
@@ -73,13 +73,13 @@ If you're using an Angular version below 13, only `ng build --prod` will leverag
 
 ### 2. Register the Sentry Webpack Plugin
 
-<Note>
+<Alert>
 
 This guide assumes you are using a Sentry SDK on version `7.47.0` or higher.
 
 If you are on an older version and you want to upload source maps we recommend upgrading your SDK to the newest version.
 
-</Note>
+</Alert>
 
 To upload source maps you have to configure an [Organization Auth Token](https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/).
 
@@ -123,12 +123,12 @@ To upload the source maps, build your Angular application:
 ng build # add --prod for Angular versions below 13
 ```
 
-<Note>
+<Alert>
 
 The Sentry webpack plugin doesn't upload source maps in watch-mode/development-mode.
 We recommend running a production build to test your implementation.
 
-</Note>
+</Alert>
 
 <Alert>
   Generating sourcemaps may expose them to the public, potentially causing your
diff --git a/docs/platforms/javascript/common/sourcemaps/uploading/create-react-app.mdx b/docs/platforms/javascript/common/sourcemaps/uploading/create-react-app.mdx
index e1bbfb041eed13..d238045c8a0e19 100644
--- a/docs/platforms/javascript/common/sourcemaps/uploading/create-react-app.mdx
+++ b/docs/platforms/javascript/common/sourcemaps/uploading/create-react-app.mdx
@@ -45,11 +45,11 @@ yarn add @sentry/cli --dev
 pnpm add @sentry/cli --save-dev
 ```
 
-<Note>
+<Alert>
 
 For more info on `sentry-cli` configuration visit the [Sentry CLI configuration docs](/cli/configuration/).
 
-</Note>
+</Alert>
 
 Use the below environment variables to make sure `sentry-cli` is configured for your project:
 
diff --git a/docs/platforms/javascript/common/sourcemaps/uploading/esbuild.mdx b/docs/platforms/javascript/common/sourcemaps/uploading/esbuild.mdx
index d489247a1a80b4..65820065b51eb0 100644
--- a/docs/platforms/javascript/common/sourcemaps/uploading/esbuild.mdx
+++ b/docs/platforms/javascript/common/sourcemaps/uploading/esbuild.mdx
@@ -4,11 +4,11 @@ description: "Upload your source maps with the Sentry esbuild Plugin."
 sidebar_order: 4
 ---
 
-<Note>
+<Alert>
 
 This guide assumes you're using a Sentry **SDK version `7.47.0` or higher**. If you're on an older version and you want to upload source maps, we recommend upgrading your SDK to the newest version.
 
-</Note>
+</Alert>
 
 <PlatformSection notSupported={[
   "javascript.nextjs",
@@ -21,7 +21,7 @@ This guide assumes you're using a Sentry **SDK version `7.47.0` or higher**. If
   "javascript.cordova",
 ]}>
 
-<Alert level="danger">
+<Alert level="warning">
 
 The Sentry esbuild plugin doesn't fully support esbuild configurations with `splitting: true`.
 If you rely on code splitting, use the esbuild plugin with <PlatformLink to="/sourcemaps/troubleshooting_js/legacy-uploading-methods/#uploading-using-sentry-bundler-plugins-on-version-2x">legacy source maps upload</PlatformLink>
@@ -100,9 +100,9 @@ require("esbuild").build({
   option to delete source maps after they've been uploaded to Sentry.
 </Alert>
 
-<Note>
+<Alert>
 
 The Sentry esbuild plugin doesn't upload source maps in watch-mode/development-mode.
 We recommend running a production build to test your configuration.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/javascript/common/sourcemaps/uploading/hosting-publicly.mdx b/docs/platforms/javascript/common/sourcemaps/uploading/hosting-publicly.mdx
index d4c097aea568f4..d4a1dfe3a8e939 100644
--- a/docs/platforms/javascript/common/sourcemaps/uploading/hosting-publicly.mdx
+++ b/docs/platforms/javascript/common/sourcemaps/uploading/hosting-publicly.mdx
@@ -15,11 +15,11 @@ notSupported:
   - javascript.nestjs
 ---
 
-<Note>
+<Alert>
 
 The most reliable way to provide your source maps to Sentry is to [upload them](..), because it cuts down on network traffic and ensures the correct version of the code and source maps will be used.
 
-</Note>
+</Alert>
 
 By default, Sentry will look for source map directives in your compiled JavaScript files. These directives are located on the last line and have the following format:
 
diff --git a/docs/platforms/javascript/common/sourcemaps/uploading/rollup.mdx b/docs/platforms/javascript/common/sourcemaps/uploading/rollup.mdx
index c9205fa53c3d1d..e3894ede340745 100644
--- a/docs/platforms/javascript/common/sourcemaps/uploading/rollup.mdx
+++ b/docs/platforms/javascript/common/sourcemaps/uploading/rollup.mdx
@@ -5,11 +5,11 @@ sidebar_order: 5
 customCanonicalTag: "/platforms/javascript/guides/koa/sourcemaps/uploading/rollup/"
 ---
 
-<Note>
+<Alert>
 
 This guide assumes you're using a **Sentry SDK version `7.47.0` or higher**. If you're on an older version and you want to upload source maps, we recommend upgrading your SDK to the newest version.
 
-</Note>
+</Alert>
 
 You can use the Sentry Rollup plugin to automatically create releases and upload source maps to Sentry when bundling your app.
 
diff --git a/docs/platforms/javascript/common/sourcemaps/uploading/typescript.mdx b/docs/platforms/javascript/common/sourcemaps/uploading/typescript.mdx
index 8cf1f0613a50b1..492239a61c5bc3 100644
--- a/docs/platforms/javascript/common/sourcemaps/uploading/typescript.mdx
+++ b/docs/platforms/javascript/common/sourcemaps/uploading/typescript.mdx
@@ -11,11 +11,11 @@ In this guide, you'll learn how to successfully upload source maps for TypeScrip
 
 <Include name="debug-id-requirement.mdx" />
 
-<Note>
+<Alert>
 
 This guide is only applicable if you're using `tsc` to compile your project. If you use another tool (such as webpack) in combination with TypeScript, you'll most likely want to follow that guide instead.
 
-</Note>
+</Alert>
 
 ## Automatic Setup
 
@@ -56,9 +56,9 @@ During compilation, TypeScript will inject some of its runtime dependencies into
 
 As a workaround, you'll need to tell the TypeScript compiler to use `tslib`, its own 3rd party package, (which is internally the part of a compiler) instead of injecting runtime dependencies. You'll only need to change what's inside the TypeScript config file, not your source code. Here's how:
 
-1. Make sure that `tslib` is listed as the dependency in your `package.json` file. 
+1. Make sure that `tslib` is listed as the dependency in your `package.json` file.
 2. Once that's done, add two entries in `compilerOptions` section of your `tsconfig.json`:
-- `"noEmitHelpers": true` and 
--`"importHelpers": true`. 
+- `"noEmitHelpers": true` and
+-`"importHelpers": true`.
 
 That's it! Now you should be able to correctly map the source maps for all your stack trace frames, including internal TypeScript compiler code snippets.
diff --git a/docs/platforms/javascript/common/sourcemaps/uploading/vite.mdx b/docs/platforms/javascript/common/sourcemaps/uploading/vite.mdx
index 41ccd84a26b10d..e3c6fbf23b45c1 100644
--- a/docs/platforms/javascript/common/sourcemaps/uploading/vite.mdx
+++ b/docs/platforms/javascript/common/sourcemaps/uploading/vite.mdx
@@ -5,11 +5,11 @@ customCanonicalTag: "/platforms/javascript/sourcemaps/uploading/vite/"
 sidebar_order: 3
 ---
 
-<Note>
+<Alert>
   This guide assumes you're using a Sentry **SDK version `7.47.0` or higher**.
   If you're on an older version and you want to upload source maps, we recommend
   upgrading your SDK to the newest version.
-</Note>
+</Alert>
 
 You can use the Sentry Vite plugin to automatically create releases and upload source maps to Sentry when bundling your app.
 
@@ -83,9 +83,9 @@ export default defineConfig({
   option to delete source maps after they've been uploaded to Sentry.
 </Alert>
 
-<Note>
+<Alert>
 
 The Sentry Vite plugin doesn't upload source maps in watch-mode/development-mode.
 We recommend running a production build to test your configuration.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/javascript/common/sourcemaps/uploading/webpack.mdx b/docs/platforms/javascript/common/sourcemaps/uploading/webpack.mdx
index 614f922c9064d3..a84f0f35652b03 100644
--- a/docs/platforms/javascript/common/sourcemaps/uploading/webpack.mdx
+++ b/docs/platforms/javascript/common/sourcemaps/uploading/webpack.mdx
@@ -5,10 +5,10 @@ customCanonicalTag: "/platforms/javascript/sourcemaps/uploading/webpack/"
 sidebar_order: 1
 ---
 
-<Note>
+<Alert>
 This guide assumes you're using a Sentry **SDK version `7.47.0` or higher**. If you're on an older version and you want to upload source maps, we recommend upgrading your SDK to the newest version.
 
-</Note>
+</Alert>
 
 You can use the Sentry webpack plugin to automatically create releases and upload source maps to Sentry when bundling your app.
 
@@ -106,15 +106,15 @@ exports.onCreateWebpackConfig = ({ actions }) => {
   option to delete source maps after they've been uploaded to Sentry.
 </Alert>
 
-<Note>
+<Alert>
 
 The Sentry webpack plugin doesn't upload source maps in watch-mode/development-mode.
 We recommend running a production build to test your configuration.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 If you use [SourceMapDevToolPlugin](https://webpack.js.org/plugins/source-map-dev-tool-plugin) for more fine-grained control of source map generation, turn off `noSources` so Sentry can display proper source code context in event stack traces.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/javascript/common/tracing/index.mdx b/docs/platforms/javascript/common/tracing/index.mdx
index 2d22db5fd4f219..42f0793ab20139 100644
--- a/docs/platforms/javascript/common/tracing/index.mdx
+++ b/docs/platforms/javascript/common/tracing/index.mdx
@@ -11,12 +11,12 @@ With [tracing](/product/performance/), Sentry tracks your software performance,
 </PlatformSection>
 
 <PlatformCategorySection supported={["server", "serverless"]}>
-  <Note>
+  <Alert>
     If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
-  </Note>
+  </Alert>
 
   <PlatformSection notSupported={["javascript.deno", "javascript.bun", "javascript.cloudflare"]}>
-    <Alert level="note">
+    <Alert>
       Sentry can integrate with <strong>OpenTelemetry</strong>. You can find more
       information about it
       <PlatformLink to="/opentelemetry/">here</PlatformLink>.
diff --git a/docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx
index 1014b7b4f2f27d..d3d6e17d2f4506 100644
--- a/docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx
@@ -6,11 +6,11 @@ notSupported:
   - javascript.cordova
 ---
 
-<Note>
+<Alert>
 
 Capturing spans requires that you first <PlatformLink to="/tracing/">set up tracing in your app</PlatformLink> if you haven't already.
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/automatic-instrumentation-intro" />
 
@@ -53,11 +53,11 @@ Supported options:
 
 ### tracePropagationTargets
 
-<Note>
+<Alert>
 
 The `tracingOrigins` option was renamed `tracePropagationTargets` and deprecated in [version `7.19.0`](https://github.com/getsentry/sentry-javascript/releases/tag/7.19.0) of the JavaScript SDK. `tracingOrigins` will be removed in version 8.
 
-</Note>
+</Alert>
 
 A list of strings and regular expressions. The JavaScript SDK will attach the `sentry-trace` and `baggage` headers to all outgoing XHR/fetch requests whose destination contains a string in the list or matches a regex in the list. If your frontend is making requests to a different domain, you'll need to add it there to propagate the `sentry-trace` and `baggage` headers to the backend services, which is required to link spans together as part of a single trace.
 
@@ -75,10 +75,10 @@ You will need to configure your web server [CORS](https://developer.mozilla.org/
 
 <PlatformContent includePath="performance/beforeNavigate-example" />
 
-<Note>
+<Alert>
   If you're using React, read our docs to learn how to set up your
   [React Router integration](/platforms/javascript/guides/react/configuration/integrations/react-router/).
-</Note>
+</Alert>
 
 ### shouldCreateSpanForRequest
 
@@ -131,9 +131,9 @@ This option determines whether spans for long tasks automatically get created.
 The default is `true`.
 
 ### enableLongAnimationFrame
-<Note>
+<Alert>
 The `enableLongAnimationFrame` option requires SDK [version 8.18.0](https://github.com/getsentry/sentry-javascript/releases/tag/8.18.0) or higher.
-</Note>
+</Alert>
 
 This option determines whether spans for long animation frames get created automatically. If both `enableLongAnimationFrame` and `enableLongTask` are enabled, Sentry will send long animation frames and fallback to long tasks (if long animation frames aren't supported by the browser).
 
@@ -141,19 +141,19 @@ The default is `true`.
 
 ### enableInp
 
-<Note>
+<Alert>
 The `enableInp` option requires SDK [version 7.104.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.104.0) or higher.
-</Note>
+</Alert>
 
 This option determines whether interactions spans automatically get created when an [Interaction to Next Paint (INP)](/product/insights/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp) event is detected. Interactions are scored and surfaced in the [Web Vitals](/product/insights/web-vitals/) module.
 
 The default is `true` in `8.x` of the SDK, and `false` in `7.x`.
 
-<Note>
+<Alert>
 INP samples currently incur no cost to enable at Sentry. Basic samples contain limited information such as the interaction target, latency, and user. You may wish to enrich your INP samples by setting up [Session Replays](/platforms/javascript/session-replay/) and/or setting up [Browser Profiling](/platforms/javascript/profiling/) instrumentation around your interactive elements to gain further insights into your slowest interactions.
 
 Please note that any Session Replays and Browser Profiles used this way will incur their [standard cost](/pricing/#per-category-pricing) depending on your plan and are subject to the sampling rates configured.
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-inp-example" />
 
diff --git a/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/index.mdx b/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/index.mdx
index c932c33236e383..afab97efc10a2f 100644
--- a/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/index.mdx
+++ b/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/index.mdx
@@ -1,14 +1,14 @@
 ---
-title: Custom Instrumentation
+title: Custom Span Instrumentation
 description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 To add custom performance data to your application, you need to add custom instrumentation in the form of spans. Spans are a way to measure the time it takes for a specific action to occur. For example, you can create a span to measure the time it takes for a function to execute.
 
@@ -225,6 +225,34 @@ if (span) {
 }
 ```
 
+### Adding attributes to all spans
+
+To add an attribute to all spans, use the `beforeSendTransaction` callback:
+
+```javascript
+Sentry.init({
+  // dsn, ...
+  beforeSendTransaction(event) {
+
+    // set the attribute on the root span
+    event.contexts.trace.data = {
+      ...event.contexts.trace.data,
+      myAttribute: "myValue",
+    }
+
+    // and on all child spans
+    event.spans.forEach(span => {
+      span.data = {
+        ...span.data,
+        myAttribute: "myValue",
+      }
+    });
+  }
+});
+```
+
+
+
 ### Adding Span Operations ("op")
 
 Spans can have an operation associated with them, which help activate Sentry identify additional context about the span. For example database related spans have the `db` span operation associated with them. The Sentry product offers additional controls, visualizations and filters for spans with known operations.
diff --git a/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/queues-module.mdx b/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/queues-module.mdx
index f48dac9b53bd72..c1fc2d28cb84ff 100644
--- a/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/queues-module.mdx
+++ b/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/queues-module.mdx
@@ -38,11 +38,11 @@ To start capturing performance metrics, use the `Sentry.startSpan` function to w
 
 You must also include trace headers in your message using `spanToTraceHeader` and `spanToBaggageHeader` so that your consumers can continue your trace once your message is picked up.
 
-<Note>
+<Alert>
 
 Your `queue.publish` span must exist as a child within a parent span in order to be recognized as a producer span. If you don't already have a parent producer span, you can start a new one using `Sentry.startSpan`.
 
-</Note>
+</Alert>
 
 ```javascript {filename:my-queue.js}
 app.post("/publish", async (req, res) => {
@@ -88,11 +88,11 @@ To start capturing performance metrics, use the `Sentry.startSpan` function to w
 
 Use `Sentry.continueTrace` to connect your consumer spans to their associated producer spans, and `setStatus` to mark the trace of your message as success or failed.
 
-<Note>
+<Alert>
 
 Your `queue.process` span must exist as a child within a parent span in order to be recognized as a consumer span. If you don't have a parent span, you can create one to wrap the consumer span with by using `Sentry.startSpan`.
 
-</Note>
+</Alert>
 
 ```javascript {filename:my-consumer.js}
 const message = JSON.parse(await redisClient.lPop(QUEUE_KEY));
diff --git a/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/requests-module.mdx b/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/requests-module.mdx
index 02225f82fca385..35ad1b71a37d9f 100644
--- a/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/requests-module.mdx
+++ b/docs/platforms/javascript/common/tracing/instrumentation/custom-instrumentation/requests-module.mdx
@@ -10,11 +10,11 @@ For detailed information about which data can be set, see the [Requests Module d
 
 ## Wrap HTTP Requests in a Span
 
-<Note>
+<Alert>
 
 Refer to [HTTP Span Data Conventions](https://develop.sentry.dev/sdk/performance/span-data-conventions/#http) for a full list of the span data attributes.
 
-</Note>
+</Alert>
 
 Here is an example of an instrumented function that makes HTTP requests:
 
diff --git a/docs/platforms/javascript/common/tracing/trace-propagation/custom-instrumentation/index.mdx b/docs/platforms/javascript/common/tracing/trace-propagation/custom-instrumentation/index.mdx
index fc574047ee80e5..f8add2ee45ec43 100644
--- a/docs/platforms/javascript/common/tracing/trace-propagation/custom-instrumentation/index.mdx
+++ b/docs/platforms/javascript/common/tracing/trace-propagation/custom-instrumentation/index.mdx
@@ -1,5 +1,5 @@
 ---
-title: Custom Instrumentation
+title: Custom Trace Propagation
 sidebar_order: 40
 notSupported:
   - javascript.cordova
diff --git a/docs/platforms/javascript/common/tracing/trace-propagation/index.mdx b/docs/platforms/javascript/common/tracing/trace-propagation/index.mdx
index b743eb65c30514..2003aaf5422c09 100644
--- a/docs/platforms/javascript/common/tracing/trace-propagation/index.mdx
+++ b/docs/platforms/javascript/common/tracing/trace-propagation/index.mdx
@@ -10,9 +10,7 @@ If the overall application landscape that you want to observe with Sentry consis
 
 ## What is Distributed Tracing?
 
-In the context of tracing events across a distributed system, distributed tracing acts as a powerful debugging tool. Imagine your application as a vast network of interconnected parts. For example, your system might be spread across different servers or your application might split into different backend and frontend services, each potentially having their own technology stack.
-
-When an error or performance issue occurs, it can be challenging to pinpoint the root cause due to the complexity of such a system. Distributed tracing helps you follow the path of an event as it travels through this intricate web, recording every step it takes. By examining these traces, you can reconstruct the sequence of events leading up to the event of interest, identify the specific components involved, and understand their interactions. This detailed visibility enables you to diagnose and resolve issues more effectively, ultimately improving the reliability and performance of your distributed system.
+<PlatformContent includePath="distributed-tracing/explanation" />
 
 ## Basic Example
 
@@ -57,7 +55,7 @@ If necessary, you can override the default trace duration by [manually starting
 
 <PlatformContent includePath="distributed-tracing/how-to-use/" />
 
-<Alert level="info" >
+<Alert >
 
 Remember that in order to propagate trace information through your whole distributed system, you have to use Sentry in all of the involved services and applications. Take a look at the respective SDK documentation to learn how distributed tracing can be enabled for each platform.
 
diff --git a/docs/platforms/javascript/common/troubleshooting/index.mdx b/docs/platforms/javascript/common/troubleshooting/index.mdx
index 40143b02f353e6..5bc1cd72e101d3 100644
--- a/docs/platforms/javascript/common/troubleshooting/index.mdx
+++ b/docs/platforms/javascript/common/troubleshooting/index.mdx
@@ -137,14 +137,11 @@ You can work around our CDN bundles being blocked by [using our NPM packages](#u
 
 <PlatformSection supported={["javascript.nextjs"]}>
 
-<Note>
-  The Sentry Next.js SDK has a separate option to make setting up tunnels very
-  straight-forward, allowing you to skip the setup below. See
-  <PlatformLink to="/manual-setup/#configure-tunneling-to-avoid-ad-blockers">
-    Configure Tunneling to avoid Ad-Blockers
-  </PlatformLink>
-  to learn how to set up tunneling on Next.js.
-</Note>
+The Sentry Next.js SDK has a separate option to make setting up tunnels very
+straight-forward, allowing you to skip the setup below. See <PlatformLink to="/manual-setup/#configure-tunneling-to-avoid-ad-blockers">
+Configure Tunneling to avoid Ad-Blockers</PlatformLink> to learn how to set up tunneling on Next.js.
+
+If you do not want to configure `tunnelRoute`, you can follow the guide below.
 
 </PlatformSection>
 
@@ -543,7 +540,7 @@ shamefully-hoist=true
 <PlatformSection supported={['javascript.nextjs']}>
   <Expandable permalink title="Out of Memory (OOM) errors during build">
     The problem here is related to memory consumption during the build process, especially when generating source maps. Here are some potential solutions and workarounds:
-    
+
     - Update your `@sentry/nextjs` package to the latest version.
     - Increase Node.js memory limit: You can try increasing the memory limit for Node.js during the build process. Add this to your build command: `NODE_OPTIONS="--max-old-space-size=8192" next build`. This flag will increase the memory available to the node process to 8 GB. We have found that Next.js consumes around 4 GB in most cases. Decrease the size depending on your memory availability.
     - Disable source maps entirely: As a last resort, you can disable source map generation completely:
diff --git a/docs/platforms/javascript/common/usage/index.mdx b/docs/platforms/javascript/common/usage/index.mdx
index 3858ed86c8b35b..eb64e6e57ff1a7 100644
--- a/docs/platforms/javascript/common/usage/index.mdx
+++ b/docs/platforms/javascript/common/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 4
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/javascript/common/user-feedback/configuration/index.mdx b/docs/platforms/javascript/common/user-feedback/configuration/index.mdx
index 05e33683e5ef92..1140bba3b630ec 100644
--- a/docs/platforms/javascript/common/user-feedback/configuration/index.mdx
+++ b/docs/platforms/javascript/common/user-feedback/configuration/index.mdx
@@ -362,9 +362,9 @@ document
 
 Because the `feedbackIntegration` is a user-facing integration, we offer two loading strategies that have bundle size implications.
 
-<Note>
+<Alert>
 For most users, we recommend using `feedbackIntegration` in your `Sentry.init` call. This will set up user feedback with good defaults, matching the environment.
-</Note>
+</Alert>
 
 All of the code examples on this page use `feedbackIntegration` as a default because it's available regardless of whether you've chosen the CDN or NPM installation method. However, the implementation of `feedbackIntegration` is different for the two installation methods. For NPM users, `feedbackIntegration` is an alias of `feedbackSyncIntegration`. For CDN users, `feedbackIntegration` is an alias of `feedbackAsyncIntegration`.
 
diff --git a/docs/platforms/javascript/common/user-feedback/index.mdx b/docs/platforms/javascript/common/user-feedback/index.mdx
index e1e18b0dfe6fe0..1feb8875db05cb 100644
--- a/docs/platforms/javascript/common/user-feedback/index.mdx
+++ b/docs/platforms/javascript/common/user-feedback/index.mdx
@@ -35,7 +35,7 @@ By default, this will insert the widget into the bottom right corner of your web
 
 On SDK version 8.0.0 and above, users can send screenshots with their feedback. If you're self-hosting, you also need release 24.4.2 and above. You can configure this using the `enableScreenshot` option, by default it is set to `true`. Screenshots aren't supported on mobile devices, so the screenshot button will be hidden automatically in this case.
 
-<Alert level="">
+<Alert>
   Screenshots use your [attachments
   quota](/pricing/quotas/manage-attachments-quota). All plans come with 1GB of
   attachments, which is approxiamately 2500 screenshots.
@@ -51,11 +51,12 @@ The User Feedback widget integrates easily with <PlatformLink to="/session-repla
 
 The user feedback API allows you to collect user feedback while utilizing your own UI. You can use the same programming language you have in your app to send user feedback. In this case, the SDK creates the HTTP request so you don't have to deal with posting data via HTTP.
 
-Sentry pairs the feedback with the original event, giving you additional insight into issues. Sentry needs the `eventId` to be able to associate the user feedback to the corresponding event. For example, to get the `eventId`, you can use <PlatformLink to="/configuration/options/#before-send"><PlatformIdentifier name="before-send" /></PlatformLink> or the return value of the method capturing an event.
+You can optionally pass in an `associatedEventId` to associate user feedback with an error event, giving you additional insight into issues. To get an event ID, you have 2 options:
+1. Use the return value of a method capturing an event.
+2. Use <PlatformLink to="/configuration/options/#before-send"><PlatformIdentifier name="before-send" /></PlatformLink>{' '}and `Sentry.lastEventId()`.
 
-<PlatformContent includePath="user-feedback/sdk-api-example/" />
 
-Alternatively, you can use the [User Feedback API endpoint](/api/projects/submit-user-feedback/) directly.
+<PlatformContent includePath="user-feedback/sdk-api-example/" />
 
 ## Crash-Report Modal
 
diff --git a/docs/platforms/javascript/guides/aws-lambda/index.mdx b/docs/platforms/javascript/guides/aws-lambda/index.mdx
index 4de8d75745ece9..c9a169c39c50a2 100644
--- a/docs/platforms/javascript/guides/aws-lambda/index.mdx
+++ b/docs/platforms/javascript/guides/aws-lambda/index.mdx
@@ -7,11 +7,11 @@ categories:
   - serverless
 ---
 
-<Note>
+<Alert>
 
 Looking for instructions on how to add Sentry without modifying your code? [Check out these docs instead](/organization/integrations/cloud-monitoring/aws-lambda/).
 
-</Note>
+</Alert>
 
 On this page you'll get an overview how to install, configure and use Sentry in your AWS Lambda functions. Once set up, our SDK will automatically report error and performance data from your Lambda Functions. Issues in Sentry will automatically include cloudwatch data, function details and execution time measurements.
 
diff --git a/docs/platforms/javascript/guides/aws-lambda/install/cjs-layer.mdx b/docs/platforms/javascript/guides/aws-lambda/install/cjs-layer.mdx
index fc10999fa1b80c..1aed72cc7b0ff3 100644
--- a/docs/platforms/javascript/guides/aws-lambda/install/cjs-layer.mdx
+++ b/docs/platforms/javascript/guides/aws-lambda/install/cjs-layer.mdx
@@ -8,11 +8,11 @@ The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](h
 If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code.
 To actually start the SDK, you can decide between setting up the SDK using environment variables or in your Lambda function code. We recommend using environment variables as it's the easiest way to get started. [Initializing the SDK in code](#alternative-initialize-the-sdk-in-code) instead of setting environment variables gives you more control over the SDK setup if you need it.
 
-<Note>
+<Alert>
 
 This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](../esm-npm).
 
-</Note>
+</Alert>
 
 ## 1. Prerequisites
 
diff --git a/docs/platforms/javascript/guides/aws-lambda/install/esm-npm.mdx b/docs/platforms/javascript/guides/aws-lambda/install/esm-npm.mdx
index 015b716e8bc126..e43936ded07dae 100644
--- a/docs/platforms/javascript/guides/aws-lambda/install/esm-npm.mdx
+++ b/docs/platforms/javascript/guides/aws-lambda/install/esm-npm.mdx
@@ -8,12 +8,12 @@ In this guide you will learn how to set up the `@sentry/aws-serverless` SDK for
 We recommend starting the SDK automatically via environment variables so that you only have to make minimal code changes to your lambda function.
 If you need more control over the SDK setup, you can also [initialize the SDK in in code](#alternative-initialize-the-sdk-in-code).
 
-<Note>
+<Alert>
 
 At this time, this guide shows the only way to use Sentry with ESM lambda functions. You cannot use the Sentry AWS Lambda Layer with ESM.
 We're working on an ESM lambda layer to provide a simpler setup but need to solve several OpenTelemetry-related limitations first.
 
-</Note>
+</Alert>
 
 ## 1. Prerequisites
 
@@ -139,7 +139,7 @@ export const handler = Sentry.wrapHandler(async (event, context) => {
 
 ### 4. Load the SDK
 
-To load the SDK before your function starts, you need to preload the `instrumentation.mjs` by setting the `NODE_OPTIONS` environment variable:
+To load the SDK before your function starts, you need to preload the `instrument.mjs` by setting the `NODE_OPTIONS` environment variable:
 
 ```bash
 NODE_OPTIONS="--import instrument.mjs"
diff --git a/docs/platforms/javascript/guides/cordova/upload-debug.mdx b/docs/platforms/javascript/guides/cordova/upload-debug.mdx
index d3b691c96a9c8b..a64e7d275864d7 100644
--- a/docs/platforms/javascript/guides/cordova/upload-debug.mdx
+++ b/docs/platforms/javascript/guides/cordova/upload-debug.mdx
@@ -6,11 +6,11 @@ description: "Learn more about uploading debug symbols when building your app."
 
 Debug symbols help provide you with readable stack traces, which Sentry displays on the **Issue Details** page, to help you triage an issue.
 
-<Note>
+<Alert>
 
 We do not currently support non-JavaScript automatic source map uploads or build scripts for Android. You must upload files manually [using our CLI](/cli/dif/#uploading-files).
 
-</Note>
+</Alert>
 
 ## JavaScript Source Maps
 
diff --git a/docs/platforms/javascript/guides/electron/configuration/application-not-responding.mdx b/docs/platforms/javascript/guides/electron/configuration/application-not-responding.mdx
index 376986723d2fe3..e643e6e6ca0c20 100644
--- a/docs/platforms/javascript/guides/electron/configuration/application-not-responding.mdx
+++ b/docs/platforms/javascript/guides/electron/configuration/application-not-responding.mdx
@@ -20,7 +20,7 @@ optionally attach a stack trace of the blocking code to the ANR event.
 
 _(Available in version 4.17.0 and above)_
 
-<Alert level="info">
+<Alert>
 
 ANR detection requires Electron v22 or higher.
 
diff --git a/docs/platforms/javascript/guides/electron/index.mdx b/docs/platforms/javascript/guides/electron/index.mdx
index 181dff6ebc950b..d5a65d1276dbc4 100644
--- a/docs/platforms/javascript/guides/electron/index.mdx
+++ b/docs/platforms/javascript/guides/electron/index.mdx
@@ -72,7 +72,9 @@ import { init as reactInit } from "@sentry/react";
 
 init(
   {
-    /* config */
+    dsn: "___PUBLIC_DSN___",
+    integrations: [ /* integrations */ ],
+    /* Other Electron and React SDK config */
   },
   reactInit
 );
diff --git a/docs/platforms/javascript/guides/express/index.mdx b/docs/platforms/javascript/guides/express/index.mdx
index 583d94c329e143..74dfe4983bd112 100644
--- a/docs/platforms/javascript/guides/express/index.mdx
+++ b/docs/platforms/javascript/guides/express/index.mdx
@@ -11,4 +11,11 @@ categories:
 
 This guide explains how to set up Sentry in your Express application.
 
+<Alert level="warning">
+  Sentry currently has limited support for Express v5.
+  While error monitoring will work, tracing auto-instrumentation will lack instrumented routes for the time being.
+  You may also see a warning log message in your console.
+  We are working on adding full support for Express v5 in the future. For the time being, see the [Express v5 issue](https://github.com/getsentry/sentry-javascript/issues/13674) for details and workarounds.
+</Alert>
+
 <PlatformContent includePath="getting-started-node" />
diff --git a/docs/platforms/javascript/guides/gatsby/index.mdx b/docs/platforms/javascript/guides/gatsby/index.mdx
index 4931c024b28e1e..f950d503c78ff4 100644
--- a/docs/platforms/javascript/guides/gatsby/index.mdx
+++ b/docs/platforms/javascript/guides/gatsby/index.mdx
@@ -33,11 +33,11 @@ yarn add @sentry/gatsby
 pnpm add @sentry/gatsby
 ```
 
-<Note>
+<Alert>
 
 `@sentry/gatsby` is a wrapper around the `@sentry/react` package, with added functionality related to Gatsby. All methods available in the `@sentry/react` package can also be imported from `@sentry/gatsby`.
 
-</Note>
+</Alert>
 
 Register the `@sentry/gatsby` plugin in your Gatsby configuration file (typically `gatsby-config.js`).
 
diff --git a/docs/platforms/javascript/guides/gcp-functions/index.mdx b/docs/platforms/javascript/guides/gcp-functions/index.mdx
index e8f9615ed407c2..84a6d49f8dedce 100644
--- a/docs/platforms/javascript/guides/gcp-functions/index.mdx
+++ b/docs/platforms/javascript/guides/gcp-functions/index.mdx
@@ -7,9 +7,9 @@ categories:
   - serverless
 ---
 
-<Note>
+<Alert>
   This guide is for version 8.0.0 and up of `@sentry/google-cloud-serverless`.
-</Note>
+</Alert>
 
 ## Features
 
diff --git a/docs/platforms/javascript/guides/nestjs/features/event-emitter.mdx b/docs/platforms/javascript/guides/nestjs/features/event-emitter.mdx
index eb381e5f0f31fd..8613f849cc76e6 100644
--- a/docs/platforms/javascript/guides/nestjs/features/event-emitter.mdx
+++ b/docs/platforms/javascript/guides/nestjs/features/event-emitter.mdx
@@ -3,9 +3,9 @@ title: NestJS Event Emitter
 description: "Learn about instrumenting NestJS event-based services."
 ---
 
-<Note>
+<Alert>
   The @nestjs/event-emitter module is auto-instrumented in `@sentry/nestjs` 8.39.0 and up.
-</Note>
+</Alert>
 
 The NestJS SDK wraps the `@OnEvent` decorator automatically to:
 
@@ -15,4 +15,4 @@ The NestJS SDK wraps the `@OnEvent` decorator automatically to:
 
 When an event handler is executed, a new span is created to track its performance, and any errors are automatically reported to Sentry while preserving the original error behavior.
 
-This instrumentation works transparently with existing NestJS event handlers without requiring any code changes to your application.
\ No newline at end of file
+This instrumentation works transparently with existing NestJS event handlers without requiring any code changes to your application.
diff --git a/docs/platforms/javascript/guides/nestjs/features/sentry-cron-decorator.mdx b/docs/platforms/javascript/guides/nestjs/features/sentry-cron-decorator.mdx
index ba28e5d7e276a5..9f9333bcca6499 100644
--- a/docs/platforms/javascript/guides/nestjs/features/sentry-cron-decorator.mdx
+++ b/docs/platforms/javascript/guides/nestjs/features/sentry-cron-decorator.mdx
@@ -3,18 +3,18 @@ title: SentryCron Decorator
 description: "Learn about Sentry's SentryCron decorator."
 ---
 
-<Note>
+<Alert>
   The `@SentryCron` decorator is available from version `@sentry/nestjs` 8.16.0 and up.
-</Note>
+</Alert>
 
 The NestJS SDK includes a `@SentryCron` decorator that can be used to augment the native NestJS `@Cron` decorator to
 send check-ins to Sentry before and after each cron job run.
 
 To get started, import `SentryCron` from `@sentry/nestjs` and use it to decorate a cron job function in your NestJS application.
 
-<Note>
+<Alert>
   The `@SentryCron` decorator needs to be applied after the `@Cron` decorator, or else the instrumentation does not work.
-</Note>
+</Alert>
 
 ```typescript
 import { Cron } from '@nestjs/schedule';
diff --git a/docs/platforms/javascript/guides/nestjs/features/sentry-traced-decorator.mdx b/docs/platforms/javascript/guides/nestjs/features/sentry-traced-decorator.mdx
index 2f77420d60a1f1..fd3842ce562bf4 100644
--- a/docs/platforms/javascript/guides/nestjs/features/sentry-traced-decorator.mdx
+++ b/docs/platforms/javascript/guides/nestjs/features/sentry-traced-decorator.mdx
@@ -3,9 +3,9 @@ title: SentryTraced Decorator
 description: "Learn about Sentry's SentryTraced decorator."
 ---
 
-<Note>
+<Alert>
   The `@SentryTraced` decorator is available from version `@sentry/nestjs` 8.15.0 and up.
-</Note>
+</Alert>
 
 The NestJS SDK includes a `@SentryTraced` decorator that will create spans whenever the method it decorates is invoked.
 This feature enables more granular performance monitoring and helps you gather detailed insights into the performance
diff --git a/docs/platforms/javascript/guides/nextjs/manual-setup.mdx b/docs/platforms/javascript/guides/nextjs/manual-setup.mdx
index 1967781879aca2..642166895b04ce 100644
--- a/docs/platforms/javascript/guides/nextjs/manual-setup.mdx
+++ b/docs/platforms/javascript/guides/nextjs/manual-setup.mdx
@@ -442,7 +442,7 @@ module.exports = withSentryConfig(nextConfig, {
 
 Alternatively, you can set the `SENTRY_AUTH_TOKEN` environment variable:
 
-<Alert level="danger">
+<Alert level="warning">
 
 Do not commit your auth token to version control.
 
@@ -646,11 +646,11 @@ module.exports = withSentryConfig(nextConfig, {
 
 You can set the `automaticVercelMonitors` option to automatically create [Cron Monitors](/product/crons/) in Sentry if you have configured [Vercel Cron Jobs](https://vercel.com/docs/cron-jobs).
 
-<Note>
+<Alert>
 
 Automatic instrumentation of Vercel cron jobs currently only works for the Pages Router. App Router route handlers are not yet supported.
 
-</Note>
+</Alert>
 
 ```javascript {tabTitle:ESM} {filename:next.config.mjs}
 export default withSentryConfig(nextConfig, {
diff --git a/docs/platforms/javascript/guides/nuxt/manual-setup.mdx b/docs/platforms/javascript/guides/nuxt/manual-setup.mdx
index 0d2f16b34a98a8..13a0fad8e62d74 100644
--- a/docs/platforms/javascript/guides/nuxt/manual-setup.mdx
+++ b/docs/platforms/javascript/guides/nuxt/manual-setup.mdx
@@ -148,7 +148,7 @@ This means that when you run a production build (`nuxt build`), source maps will
 To upload source maps, specify your Sentry auth token as well as your org and project slugs. Set them in the `sourceMapsUploadOptions` option
 inside the `sentry` options of your `nuxt.config.ts`.
 
-<Alert level="info">
+<Alert>
   The module options inside `sentry` are only affecting the **build-time** of the SDK.
 </Alert>
 
diff --git a/docs/platforms/javascript/guides/react-router/config.yml b/docs/platforms/javascript/guides/react-router/config.yml
index f62329f1af2bab..b8ec2fc458a220 100644
--- a/docs/platforms/javascript/guides/react-router/config.yml
+++ b/docs/platforms/javascript/guides/react-router/config.yml
@@ -1,5 +1,5 @@
-title: React Router
-description: React Router (v7) is a framework for building full-stack web apps and websites. Learn how to set it up with Sentry.
+title: React Router v7 (framework mode)
+description: React Router v7 is a framework for building full-stack web apps and websites. Learn how to set it up with Sentry.
 sdk: sentry.javascript.react-router
 categories:
   - javascript
diff --git a/docs/platforms/javascript/guides/react/features/react-router/index.mdx b/docs/platforms/javascript/guides/react/features/react-router/index.mdx
index 3a0c20cb7b2a53..4f80ebde0503be 100644
--- a/docs/platforms/javascript/guides/react/features/react-router/index.mdx
+++ b/docs/platforms/javascript/guides/react/features/react-router/index.mdx
@@ -7,7 +7,7 @@ _(Available in version 5.21.0 and above)_
 
 React Router support is included in the `@sentry/react` package since version `5.21.0`.
 
-<Alert level="info" title="Note">
+<Alert title="Note">
 
 The React Router integration is designed to work with Sentry Tracing. Please see [Set Up Tracing with React](/platforms/javascript/guides/react/tracing/) for more details on how to set up and install the SDK.
 
@@ -19,4 +19,4 @@ We support integrations for React Router 3, 4, 5, 6 and 7.
 
 
 
-<PageGrid />
\ No newline at end of file
+<PageGrid />
diff --git a/docs/platforms/javascript/guides/react/features/react-router/v6.mdx b/docs/platforms/javascript/guides/react/features/react-router/v6.mdx
index 806af8987bc0b9..f12af4ecd0a46b 100644
--- a/docs/platforms/javascript/guides/react/features/react-router/v6.mdx
+++ b/docs/platforms/javascript/guides/react/features/react-router/v6.mdx
@@ -4,7 +4,7 @@ description: "Learn about Sentry's React Router v6 integration."
 sidebar_order: 20
 ---
 
-<Alert level="info">
+<Alert>
   - React Router v6 support is included in the `@sentry/react` package since
   version `7`.
 </Alert>
@@ -119,7 +119,7 @@ This is only needed at the top level of your app, rather than how v4/v5 required
 
 ### Usage With `useRoutes` Hook
 
-<Alert level="info">
+<Alert>
   Available in `@sentry/react` version `7.12.1` and above.
 </Alert>
 
@@ -179,10 +179,10 @@ Now, Sentry should generate `pageload`/`navigation` transactions with parameteri
 
 When using `react-router`, errors thrown inside route elements will only be re-thrown in **development mode** while using [`strict mode`](https://react.dev/reference/react/StrictMode). In production, these errors won't be surfaced unless manually captured. If you **don't** have a custom error boundary in place, `react-router` will create a default one that "swallows" all errors.
 
-<Note>
+<Alert>
   Note, that this only applies to render method and lifecycle errors since React
   doesn't need error boundaries to handle errors in event handlers.
-</Note>
+</Alert>
 
 To send errors to Sentry while using a custom error boundary, use the `Sentry.captureException` method:
 
diff --git a/docs/platforms/javascript/guides/react/features/react-router/v7.mdx b/docs/platforms/javascript/guides/react/features/react-router/v7.mdx
index 4a3f50e97bd05d..5a46884fad80b6 100644
--- a/docs/platforms/javascript/guides/react/features/react-router/v7.mdx
+++ b/docs/platforms/javascript/guides/react/features/react-router/v7.mdx
@@ -1,13 +1,17 @@
 ---
-title: React Router v7
+title: React Router v7 (library mode)
 description: "Learn about Sentry's React Router v7 integration."
 sidebar_order: 10
 ---
 
+
+<Alert level="warning" title="Looking for framework mode?">
+  - React Router v7 (framework mode) is not yet supported, but we do provide a guide on how to set it up using existing SDKs [here](/platforms/javascript/guides/react-router/).
+</Alert>
+
 <Alert level="info">
-  - React Router v7 (library mode) support is included in the `@sentry/react`
-  package since version `8.42.0`. - React Router v7 (framework mode) is not yet
-  supported.
+  React Router v7 (library mode) support is included in the `@sentry/react`
+  package since version `8.42.0`.
 </Alert>
 
 Update your `Sentry.browserTracingIntegration` to `Sentry.reactRouterV7BrowserTracingIntegration` and provide the required React hooks and router functions:
@@ -176,10 +180,10 @@ Now, Sentry should generate `pageload`/`navigation` transactions with parameteri
 
 When using `react-router`, errors thrown inside route elements will only be re-thrown in **development mode** while using [`strict mode`](https://react.dev/reference/react/StrictMode). In production, these errors won't be surfaced unless manually captured. If you **don't** have a custom error boundary in place, `react-router` will create a default one that "swallows" all errors.
 
-<Note>
+<Alert>
   Note, that this only applies to render method and lifecycle errors since React
   doesn't need error boundaries to handle errors in event handlers.
-</Note>
+</Alert>
 
 To send errors to Sentry while using a custom error boundary, use the `Sentry.captureException` method:
 
diff --git a/docs/platforms/javascript/guides/react/features/tanstack-router.mdx b/docs/platforms/javascript/guides/react/features/tanstack-router.mdx
index 797dfe3e190b27..14c99f1b29a079 100644
--- a/docs/platforms/javascript/guides/react/features/tanstack-router.mdx
+++ b/docs/platforms/javascript/guides/react/features/tanstack-router.mdx
@@ -7,7 +7,7 @@ _(Available in version 8.7.0 and above)_
 
 TanStack Router support is included in the `@sentry/react` package since version `8.7.0` and is only compatible with version `1.34.5` of ` `@tanstack/router` and above.
 
-<Alert level="info" title="Note">
+<Alert title="Note">
 
 The TanStack Router integration is designed to work with Sentry Tracing. Please see <PlatformLink to="/tracing/#enable-tracing">Getting Started with React Performance</PlatformLink> for more details on how to set up and install the SDK.
 
diff --git a/docs/platforms/javascript/guides/remix/manual-setup.mdx b/docs/platforms/javascript/guides/remix/manual-setup.mdx
index 9f1eb67abe15aa..be4dae215dc66f 100644
--- a/docs/platforms/javascript/guides/remix/manual-setup.mdx
+++ b/docs/platforms/javascript/guides/remix/manual-setup.mdx
@@ -93,10 +93,10 @@ export const ErrorBoundary: V2_ErrorBoundaryComponent = () => {
 
 To catch React component errors (in Remix v1) and routing transactions (in all Remix versions), wrap your Remix root with `withSentry`.
 
-<Note>
+<Alert>
 
 If you use Remix v1 with the `v2_errorBoundary` future flag, you must also configure your `ErrorBoundary`.
-</Note>
+</Alert>
 
 ```typescript {filename: root.tsx}
 import {
@@ -130,11 +130,11 @@ function App() {
 export default withSentry(App);
 ```
 
-<Note>
+<Alert>
 
 If you use Remix v2, `wrapWithErrorBoundary` is disabled by default. You still need to wrap your root component with `withSentry` to capture routing transactions.
 
-</Note>
+</Alert>
 
 You can disable or configure `ErrorBoundary` using a second parameter to `withSentry`.
 
@@ -240,11 +240,11 @@ This snippet includes an intentional error, so you can test that everything is w
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 You can refer to [Remix Docs](https://remix.run/docs/en/main/guides/envvars#browser-environment-variables) to learn how to use your Sentry DSN with environment variables.
 
-</Note>
+</Alert>
 
 ## Custom Express Server
 
diff --git a/docs/platforms/javascript/guides/solid/features/index.mdx b/docs/platforms/javascript/guides/solid/features/index.mdx
index b3ec70bab9bad9..7f045ba78cf836 100644
--- a/docs/platforms/javascript/guides/solid/features/index.mdx
+++ b/docs/platforms/javascript/guides/solid/features/index.mdx
@@ -3,14 +3,14 @@ title: Solid Features
 description: "Learn how Sentry's Solid SDK exposes features for first class integration with Solid."
 ---
 
-<Note>
+<Alert>
 
   This SDK is currently in **beta**. Beta features are still in progress and may have bugs. Please reach out on
   [GitHub](https://github.com/getsentry/sentry-javascript/issues/new/choose) if you have any feedback or concerns.
   This SDK is for [Solid](https://www.solidjs.com/), for [SolidStart](https://start.solidjs.com/) see our
   [SolidStart SDK](/platforms/javascript/guides/solidstart).
 
-</Note>
+</Alert>
 
 The Sentry Solid SDK offers Solid-specific features for first class integration with the framework.
 
diff --git a/docs/platforms/javascript/guides/solid/features/solid-router.mdx b/docs/platforms/javascript/guides/solid/features/solid-router.mdx
index 2c7cb20dbbf820..5878bda6eb16a9 100644
--- a/docs/platforms/javascript/guides/solid/features/solid-router.mdx
+++ b/docs/platforms/javascript/guides/solid/features/solid-router.mdx
@@ -3,9 +3,9 @@ title: Solid Router
 description: "Learn about Sentry's Solid Router integration."
 ---
 
-<Note>
+<Alert>
   The routing instrumentation supports [Solid Router](https://docs.solidjs.com/solid-router) 0.13.4 and up.
-</Note>
+</Alert>
 
 The Sentry SDK provides a routing instrumentation for Solid Router to create navigation spans to ensure
 you collect meaningful performance data about the health of your page loads and associated requests.
diff --git a/docs/platforms/javascript/guides/solidstart/features/index.mdx b/docs/platforms/javascript/guides/solidstart/features/index.mdx
index fe5374a087858c..f29a1f38e35200 100644
--- a/docs/platforms/javascript/guides/solidstart/features/index.mdx
+++ b/docs/platforms/javascript/guides/solidstart/features/index.mdx
@@ -3,12 +3,12 @@ title: SolidStart Features
 description: "Learn how Sentry's SolidStart SDK exposes features for first class integration with Solid."
 ---
 
-<Note>
+<Alert>
 
   This SDK is currently in **beta**. Beta features are still in progress and may have bugs. Please reach out on
   [GitHub](https://github.com/getsentry/sentry-javascript/issues/new/choose) if you have any feedback or concerns.
 
-</Note>
+</Alert>
 
 The Sentry SolidStart SDK offers Solid-specific features for first class integration with the framework.
 
diff --git a/docs/platforms/javascript/guides/solidstart/features/solid-router.mdx b/docs/platforms/javascript/guides/solidstart/features/solid-router.mdx
index d8e7d5e49eb596..d571fe5cccf487 100644
--- a/docs/platforms/javascript/guides/solidstart/features/solid-router.mdx
+++ b/docs/platforms/javascript/guides/solidstart/features/solid-router.mdx
@@ -3,9 +3,9 @@ title: Solid Router
 description: "Learn about Sentry's Solid Router integration."
 ---
 
-<Note>
+<Alert>
   The routing instrumentation supports [Solid Router](https://docs.solidjs.com/solid-router) 0.13.4 and up.
-</Note>
+</Alert>
 
 The Sentry SDK provides a routing instrumentation for Solid Router to create navigation spans to ensure
 you collect meaningful performance data about the health of your page loads and associated requests.
diff --git a/docs/platforms/javascript/guides/sveltekit/manual-setup.mdx b/docs/platforms/javascript/guides/sveltekit/manual-setup.mdx
index 0d8e237f28360c..d0e4ed82d2f00f 100644
--- a/docs/platforms/javascript/guides/sveltekit/manual-setup.mdx
+++ b/docs/platforms/javascript/guides/sveltekit/manual-setup.mdx
@@ -209,12 +209,12 @@ The SDK primarily uses [SvelteKit's hooks](https://kit.svelte.dev/docs/hooks) to
 
 Auto-instrumentation is enabled by default when you add the `sentrySvelteKit()` function call to your `vite.config.(js|ts)`. However, you can customize the behavior, or disable it entirely. If you disable it you can still manually wrap specific `load` functions with the `withSentry` function.
 
-<Note>
+<Alert>
 
 The SDK will only auto-instrument `load` functions in `+page` or `+layout` files that don't contain any Sentry code.
 If you have custom Sentry code in these files, you'll have to [manually](#instrument-load-functions-manually) add the Sentry wrapper to your `load` functions.
 
-</Note>
+</Alert>
 
 #### Customize Auto-instrumentation
 
@@ -259,11 +259,11 @@ export default {
 
 #### Configure CSP for Client-side `fetch` Instrumentation
 
-<Note>
+<Alert>
 
 Available since version `7.91.0`
 
-</Note>
+</Alert>
 
 The `sentryHandle` function you added to your `handle` hook in `hooks.server.ts` during [server-side setup](#server-side-setup) injects an inline `<script>` tag into the HTML response of the server.
 This script attempts to proxy all client-side `fetch` calls, so that `fetch` calls inside your `load` functions are captured by the SDK.
@@ -293,14 +293,14 @@ For external CSP configurations, add the following hash to your `script-src` dir
 
 We will not make changes to this script any time soon (in fact, this script will be removed in version 9 of the SDK).
 
-<Note>
+<Alert>
 
 Previous versions of this documentation recommended setting a nonce in your `sentryHandle` options.
 We no longer recommend this approach due to security concerns with re-using nonces.
 Instead, we recommend setting the hash as outlined above.
 If you're currently setting `fetchProxyScriptNonce` in your `sentryHandle` options, it will continue to work as expected.
 
-</Note>
+</Alert>
 
 ##### Disable Client-side `fetch` Proxy Script
 
@@ -352,11 +352,11 @@ export const load = wrapServerLoadWithSentry(({ fetch }) => {
 
 #### Instrument Server Routes
 
-<Note>
+<Alert>
 
 Available since `8.25.0`
 
-</Note>
+</Alert>
 
 You can also manually instrument [server (API) routes ](https://kit.svelte.dev/docs/routing#server) with the SDK.
 This is useful if you have custom server routes that you want to trace or if you want to capture `error()` calls within your server routes:
diff --git a/docs/platforms/javascript/legacy-sdk/integrations.mdx b/docs/platforms/javascript/legacy-sdk/integrations.mdx
index cedb2260f2c149..3135cf4ecbb736 100644
--- a/docs/platforms/javascript/legacy-sdk/integrations.mdx
+++ b/docs/platforms/javascript/legacy-sdk/integrations.mdx
@@ -39,7 +39,7 @@ On its own, Raven.js will report any uncaught exceptions triggered from your app
 
 Additionally, the Raven.js AngularJS plugin will catch any AngularJS-specific exceptions reported through AngularJS’s `$exceptionHandler` interface.
 
-<Alert level="info" title="Note">
+<Alert title="Note">
 
 This documentation is for Angular 1.x. See also: [_Angular 2.x_](#angular).
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/configuration/releases.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/configuration/releases.mdx
index 5ebdfaf5227d70..39f7681059920a 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/configuration/releases.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/configuration/releases.mdx
@@ -31,11 +31,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/data-management/apple-privacy-manifest.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/data-management/apple-privacy-manifest.mdx
index b51300f0321fbd..06f89ac90a48a5 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/data-management/apple-privacy-manifest.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/data-management/apple-privacy-manifest.mdx
@@ -4,15 +4,15 @@ description: "Troubleshoot and resolve common issues with the Apple Privacy Mani
 sidebar_order: 50
 ---
 
-<Note>
+<Alert>
 This guide requires using [@sentry/cocoa@8.21.0](https://github.com/getsentry/sentry-cocoa/releases/tag/8.21.0) in combination with our Kotlin Multiplatform SDK.
-</Note>
+</Alert>
 
 Sentry's SDKs provide error and tracing for mobile applications running on Apple devices. To do this, the SDK needs to access certain information about the device and the application. Some of the APIs required for this are considered privacy-relevant by Apple. In order to submit apps to the App Store, Apple requires all apps - and libraries used within these apps - to provide privacy manifest files stating which APIs are used under which allowed reasons. For more details, read Apple's guidelines on [Describing use of required reason API](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api).
 
-<Note>
+<Alert>
 The information and steps in this guide are still being worked on and might change because of new tools or updated [Apple requirements](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files).
-</Note>
+</Alert>
 
 If you are using dynamically linked frameworks which is the default when creating a Kotlin Multiplatform framework, Apple will automatically process the SDK's privacy manifest. If you are using statically linked libraries, you need to provide the privacy manifest yourself. This guide will help you create the privacy manifest for your Kotlin Multiplatform applications.
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/data-management/sensitive-data/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/data-management/sensitive-data/index.mdx
index dc24987a5b9bd1..4a04734295c717 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/data-management/sensitive-data/index.mdx
@@ -23,12 +23,12 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 If you _do not_ wish to use the default PII behavior, you can also choose to identify users in a more controlled manner, using our [user identity context](../../enriching-events/identify-user/).
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/attachments/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/attachments/index.mdx
index 8bf58e602c1efc..3c2242b4620913 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/attachments/index.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/attachments/index.mdx
@@ -49,11 +49,11 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <PlatformContent includePath="enriching-events/attachment-upload" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/breadcrumbs/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/breadcrumbs/index.mdx
index e65703cd2ddbcf..909b014f6d0e87 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/context/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/context/index.mdx
index dd07e216bbb9f9..36da3d54f75935 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/context/index.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/scopes/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/scopes/index.mdx
index 6cc8f4c149b0fb..a3971c45144c01 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/scopes/index.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/scopes/index.mdx
@@ -70,7 +70,7 @@ made will stay isolated within the callback function. This allows you to
 more easily isolate pieces of context information to specific locations in your code or
 even call `clear` to briefly remove all context information.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 Any exceptions that occur within the callback function for configuring a local scope will not be
 caught, and all errors that occur will be silently ignored and **not** reported.
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/screenshots/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/screenshots/index.mdx
index e2da1f1dc0a773..f1462165f0c547 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/screenshots/index.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/screenshots/index.mdx
@@ -11,11 +11,11 @@ This feature is only available for SDKs with a user interface, like the ones for
 
 Because screenshots may contain <PlatformLink to="/data-management/sensitive-data/">PII</PlatformLink>, they are an opt-in feature. You can enable screenshots as shown below:
 
-<Note>
+<Alert>
 
 This feature is supported for iOS and Android only.
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="enriching-events/attach-screenshots" />
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/tags/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/tags/index.mdx
index 5707e7b98110ca..9657816853afb2 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/tags/index.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/tags/index.mdx
@@ -17,11 +17,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/viewhierarchy/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/viewhierarchy/index.mdx
index 231360b3340b19..ef8be403c37e42 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/viewhierarchy/index.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/viewhierarchy/index.mdx
@@ -7,11 +7,11 @@ Sentry makes it possible to render a JSON representation of the view hierarchy o
 
 This feature only applies to SDKs with a user interface, such as the ones for mobile and desktop applications. In some environments like native iOS, rendering the view hierarchy requires the UI thread and in the event of a crash, that might not be available. Another example where the view hierarchy might not be available is when the event happens before the screen starts to load. So inherently, this feature is a best effort solution.
 
-<Note>
+<Alert>
 
 Deobfuscation for view hierarchies is fully supported for native SDKs, and React Native, but is currently not supported for Flutter.
 
-</Note>
+</Alert>
 
 ## Enabling View Hierarchy Attachments
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/features/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/features/index.mdx
index d804b576a9ac8b..4b29304f539d93 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/features/index.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/features/index.mdx
@@ -11,11 +11,11 @@ Because the SDK provides a unified API for all supported platforms directly leve
 - [Android features](/platforms/android/features)
 - [Java features](/platforms/java)
 
-<Note>
+<Alert>
 Some functionality may not be available in the shared Kotlin Multiplatform layer yet. You may have to use the native SDKs directly, or write your own platform-specific code.
 
 To access the native SDK init options, use the [Native Platform Options initialization](/platforms/kotlin/guides/kotlin-multiplatform/initialization-strategies/#native-platform-options).
-</Note>
+</Alert>
 
 ## Supported Platforms
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/index.mdx
index 44b251c96c8087..856d3c362725a9 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/index.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/index.mdx
@@ -31,11 +31,11 @@ This snippet includes an intentional error, so you can test that everything is w
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/initialization-strategies.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/initialization-strategies.mdx
index 63008e43eeb95b..cce2f6eebe9fd2 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/initialization-strategies.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/initialization-strategies.mdx
@@ -49,13 +49,13 @@ struct SwiftUIApp: App {
 
 ## Native Platform Options
 
-<Note>
+<Alert>
 Requires Sentry SDK version `0.7.1` or higher.
-</Note>
-<Note>
+</Alert>
+<Alert>
 Available options are determined by the native SDK versions used in the build.
 For example, Kotlin Multiplatform SDK `0.10.0` uses Sentry Android `7.16.0` and Sentry Cocoa `8.38.0`, so it supports all options from these versions.
-</Note>
+</Alert>
 
 This approach involves initializing the SDK with the platform's specific options directly, using `PlatformOptionsConfiguration`. This strategy is ideal for projects that require configuring options that are not yet supported by the KMP SDK, such as experimental options.
 For example, if you configure your KMP application for Android, you will have access to every option that the Android SDK provides.
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/manual-setup/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/manual-setup/index.mdx
index 5411be1ff4b82d..b98f728d034156 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/manual-setup/index.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/manual-setup/index.mdx
@@ -73,11 +73,11 @@ This snippet includes an intentional error, so you can test that everything is w
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/troubleshooting.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/troubleshooting.mdx
index a8b70ae41917f0..2952063ee46596 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/troubleshooting.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/troubleshooting.mdx
@@ -16,9 +16,9 @@ Starting May 1, 2024, Apple requires all apps submitted to the App Store to prov
 
 If you configured the Sentry Kotlin Multiplatform SDK and tests are still failing with the following error: `ld: framework 'Sentry' not found` then follow these steps for the workaround:
 
-<Note>
+<Alert>
 This example shows you how to fix the issue for the iOS simulator target, but the same approach can be used for other targets.
-</Note>
+</Alert>
 
 **1. Download the Sentry xcframework**
 
diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/usage/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/usage/index.mdx
index efe373330daad4..aa044b25f2bdeb 100644
--- a/docs/platforms/kotlin/guides/kotlin-multiplatform/usage/index.mdx
+++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 5
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/native/common/configuration/releases.mdx b/docs/platforms/native/common/configuration/releases.mdx
index 8d466776a0610b..ff35760df93f55 100644
--- a/docs/platforms/native/common/configuration/releases.mdx
+++ b/docs/platforms/native/common/configuration/releases.mdx
@@ -29,11 +29,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -62,11 +62,11 @@ After configuring your SDK, you can install a repository integration or manually
 
 Monitor the [health of releases](/product/releases/health/) by observing user adoption, usage of the application, percentage of [crashes](/product/releases/health/#crash), and [session data](/product/releases/health/#session). Release health will provide insight into the impact of crashes and bugs as it relates to user experience, and reveal trends with each new issue through the [Release Details](/product/releases/release-details/) graphs and filters.
 
-<Note>
+<Alert>
 
 Crash reporting and app hang detection are not available for watchOS.
 
-</Note>
+</Alert>
 
 In order to monitor release health, the SDK sends session data.
 
diff --git a/docs/platforms/native/common/configuration/sampling.mdx b/docs/platforms/native/common/configuration/sampling.mdx
index 7e8264cec3b5e8..59e2139b0a94c1 100644
--- a/docs/platforms/native/common/configuration/sampling.mdx
+++ b/docs/platforms/native/common/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
@@ -68,11 +68,11 @@ When using custom instrumentation to create a transaction, you can add data to t
 
 <PlatformContent includePath="performance/custom-sampling-context" />
 
-<Note>
+<Alert>
 
 `sentry_transaction_start` takes ownership of the custom sampling context and frees it at the end, meaning you cannot reuse it.
 
-</Note>
+</Alert>
 
 ## Inheritance
 
@@ -107,7 +107,7 @@ When there's the potential for more than one of these to come into play, the fol
 1. If <PlatformIdentifier name="traces-sampler" /> is not defined, but there's a parent sampling decision, the parent sampling decision will be used.
 1. If <PlatformIdentifier name="traces-sampler" /> is not defined and there's no parent sampling decision, <PlatformIdentifier name="traces-sample-rate" /> will be used.
 
-<Alert level="info">
+<Alert>
 
 Forcing a sampling decision by passing it into <PlatformIdentifier name="start-transaction" /> is currently not supported by this platform.
 
diff --git a/docs/platforms/native/common/data-management/debug-files/identifiers/index.mdx b/docs/platforms/native/common/data-management/debug-files/identifiers/index.mdx
index a4ce5da0fdf22e..8bac409ce8fd3a 100644
--- a/docs/platforms/native/common/data-management/debug-files/identifiers/index.mdx
+++ b/docs/platforms/native/common/data-management/debug-files/identifiers/index.mdx
@@ -24,14 +24,14 @@ compute a _Debug Identifier_ for each uploaded file. This identifier is
 associated with executables and libraries as well as debug companions to ensure
 that they can be uniquely located via one common mechanism.
 
-<Note>
+<Alert>
 
 Debug information does not have to be associated with releases. The unique debug
 identifier ensures that Sentry can choose the right files for every crash
 report. However, it is still recommended to configure releases in the client to
 benefit from other features.
 
-</Note>
+</Alert>
 
 For native events, the issue details page displays a list of _Loaded Images_.
 This list contains the executable and all loaded dynamic libraries including
diff --git a/docs/platforms/native/common/data-management/debug-files/index.mdx b/docs/platforms/native/common/data-management/debug-files/index.mdx
index 0876114bc0b4cd..833378b447d4ed 100644
--- a/docs/platforms/native/common/data-management/debug-files/index.mdx
+++ b/docs/platforms/native/common/data-management/debug-files/index.mdx
@@ -12,12 +12,12 @@ can use some of this information and display it on the issue details page.
 
 <PlatformContent includePath="debug-information-files" />
 
-<Note>
+<Alert>
 
 Source maps, while also being debug information files, are handled
 differently in Sentry. For more information see [Source Maps in sentry-cli](/cli/releases/#sentry-cli-sourcemaps).
 
-</Note>
+</Alert>
 
 Sentry requires access to debug information files of your application as well as
 system libraries to provide fully symbolicated crash reports. You can either
@@ -34,11 +34,11 @@ for automatic downloads.
 From the [Project Details](/product/projects/project-details/) page, click into settings,
 then click on _Debug Files_ in the page navigation.
 
-<Note>
+<Alert>
 
 ProGuard files are listed separately, in the _ProGuard_ section of the project settings page.
 
-</Note>
+</Alert>
 
 ## Retention Policy
 
diff --git a/docs/platforms/native/common/data-management/debug-files/symbol-servers/index.mdx b/docs/platforms/native/common/data-management/debug-files/symbol-servers/index.mdx
index 70c5456cbe8c1c..2a17fe0c23bd73 100644
--- a/docs/platforms/native/common/data-management/debug-files/symbol-servers/index.mdx
+++ b/docs/platforms/native/common/data-management/debug-files/symbol-servers/index.mdx
@@ -42,7 +42,7 @@ Beware that these cause notifications to your team members.
 
 ## Custom Repositories
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 Custom repositories are available for organizations on the _Business_ and
 _Enterprise_ plans.
diff --git a/docs/platforms/native/common/data-management/sensitive-data/index.mdx b/docs/platforms/native/common/data-management/sensitive-data/index.mdx
index 59fd1f1adbb6c6..64809a29816a92 100644
--- a/docs/platforms/native/common/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/native/common/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="sensitive-data/pii" />
 
diff --git a/docs/platforms/native/common/enriching-events/attachments/index.mdx b/docs/platforms/native/common/enriching-events/attachments/index.mdx
index 82f84faf101e90..9b5e2bbf5cd6cc 100644
--- a/docs/platforms/native/common/enriching-events/attachments/index.mdx
+++ b/docs/platforms/native/common/enriching-events/attachments/index.mdx
@@ -17,13 +17,13 @@ To receive symbolicated stack traces, you have to upload debug information to Se
 
 <PlatformContent includePath="enriching-events/add-attachment" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
 Usually, native crash reports range from a few kilobytes to a few megabytes. This leaves sufficient space to add custom attachments. In case your application generates particularly large crash reports, consider to limit or avoid adding additional attachments in the SDK.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
@@ -41,7 +41,7 @@ By default, access is granted to all members when storage is enabled. If a membe
 
 <Include name="store-minidumps-as-attachments-intro" />
 
-<Alert level="note">☝ This feature is supported on Windows, Linux, and Android.</Alert>
+<Alert>☝ This feature is supported on Windows, Linux, and Android.</Alert>
 
 <Include name="store-minidumps-as-attachments-configuration" />
 
diff --git a/docs/platforms/native/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/native/common/enriching-events/breadcrumbs/index.mdx
index e5e5824ec1ccc4..0d358e424c91d1 100644
--- a/docs/platforms/native/common/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/native/common/enriching-events/breadcrumbs/index.mdx
@@ -12,7 +12,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/native/common/enriching-events/context/index.mdx b/docs/platforms/native/common/enriching-events/context/index.mdx
index 39a85e980104cd..4f1ffe56cf761f 100644
--- a/docs/platforms/native/common/enriching-events/context/index.mdx
+++ b/docs/platforms/native/common/enriching-events/context/index.mdx
@@ -12,11 +12,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/native/common/enriching-events/tags/index.mdx b/docs/platforms/native/common/enriching-events/tags/index.mdx
index 32e35ee82e7002..bbf0c42649cc6e 100644
--- a/docs/platforms/native/common/enriching-events/tags/index.mdx
+++ b/docs/platforms/native/common/enriching-events/tags/index.mdx
@@ -20,11 +20,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/native/common/index.mdx b/docs/platforms/native/common/index.mdx
index 780bf1c4b712a7..982b872dd61cbb 100644
--- a/docs/platforms/native/common/index.mdx
+++ b/docs/platforms/native/common/index.mdx
@@ -24,10 +24,10 @@ This snippet includes an intentional error, so you can test that everything is w
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
diff --git a/docs/platforms/native/common/tracing/index.mdx b/docs/platforms/native/common/tracing/index.mdx
index 820052d4a53907..a8377fa5eb1516 100644
--- a/docs/platforms/native/common/tracing/index.mdx
+++ b/docs/platforms/native/common/tracing/index.mdx
@@ -11,11 +11,11 @@ notSupported:
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 ## Configure
 
diff --git a/docs/platforms/native/common/tracing/instrumentation/custom-instrumentation.mdx b/docs/platforms/native/common/tracing/instrumentation/custom-instrumentation.mdx
index 15cfe5aa9f1dfd..120bef6bb31de7 100644
--- a/docs/platforms/native/common/tracing/instrumentation/custom-instrumentation.mdx
+++ b/docs/platforms/native/common/tracing/instrumentation/custom-instrumentation.mdx
@@ -9,11 +9,11 @@ notSupported:
   - native.wasm
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
@@ -38,6 +38,8 @@ When using these functions, you should ensure that the provided timestamps are c
 
 <PlatformContent includePath="performance/connect-errors-spans" />
 
+<PlatformContent includePath="performance/improving-data" />
+
 ## Distributed Tracing
 
 In order to use distributed tracing with the Native SDK, follow the <PlatformLink to="/tracing/trace-propagation/custom-instrumentation/">custom instrumentation</PlatformLink> steps.
diff --git a/docs/platforms/native/common/usage/index.mdx b/docs/platforms/native/common/usage/index.mdx
index 61549145dd2932..934661a947b9c8 100644
--- a/docs/platforms/native/common/usage/index.mdx
+++ b/docs/platforms/native/common/usage/index.mdx
@@ -11,7 +11,7 @@ notSupported:
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -20,7 +20,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/native/guides/minidumps/index.mdx b/docs/platforms/native/guides/minidumps/index.mdx
index 4e4871be2313b3..473e5f184fd7e1 100644
--- a/docs/platforms/native/guides/minidumps/index.mdx
+++ b/docs/platforms/native/guides/minidumps/index.mdx
@@ -34,7 +34,7 @@ and can later be uploaded to Sentry. A minidump typically includes:
   assertion message is also included in the dump.
 - Meta data about the CPU architecture and the user’s operating system.
 
-<Alert level="" title="A Word on Data Privacy">
+<Alert title="A Word on Data Privacy">
 
 Minidumps are memory dumps of the process at the moment it crashes. As such,
 they might contain sensitive information on the target system, such as
diff --git a/docs/platforms/native/guides/wasm/index.mdx b/docs/platforms/native/guides/wasm/index.mdx
index c131dea4da29e4..f76fef5a177c4e 100644
--- a/docs/platforms/native/guides/wasm/index.mdx
+++ b/docs/platforms/native/guides/wasm/index.mdx
@@ -10,13 +10,13 @@ WebAssembly allows you to compile native code into a platform-independent byteco
 Debugging support for WebAssembly is an ongoing effort by the WebAssembly community.
 Support for it in Sentry is limited by what's possible in that ecosystem.
 
-<Note>
+<Alert>
 
 Want to be an early adopter, but running into issues? Please reach out to us
 [on GitHub](https://github.com/getsentry/symbolicator/issues/new/choose), we
 would love to talk.
 
-</Note>
+</Alert>
 
 ## Requirements
 
diff --git a/docs/platforms/php/common/configuration/options.mdx b/docs/platforms/php/common/configuration/options.mdx
index 38d3fb2d72ff89..8c5ec9894a1b85 100644
--- a/docs/platforms/php/common/configuration/options.mdx
+++ b/docs/platforms/php/common/configuration/options.mdx
@@ -82,11 +82,11 @@ Grouping in Sentry is different for events with stack traces and without. As a r
 
 If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This option is turned off by default.
 
@@ -146,10 +146,10 @@ This parameter controls whether integrations should capture HTTP request bodies.
 
 The number of characters after which the values containing text in the event payload will be truncated (defaults to `1024`).
 
-<Note>
+<Alert>
   If the value you set for this is exceptionally large, the event may exceed 1
   MiB and will be dropped by Sentry.
-</Note>
+</Alert>
 
 </ConfigKey>
 
diff --git a/docs/platforms/php/common/configuration/releases.mdx b/docs/platforms/php/common/configuration/releases.mdx
index babb58d14dcbdf..3040ef122baf1d 100644
--- a/docs/platforms/php/common/configuration/releases.mdx
+++ b/docs/platforms/php/common/configuration/releases.mdx
@@ -29,11 +29,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
diff --git a/docs/platforms/php/common/configuration/sampling.mdx b/docs/platforms/php/common/configuration/sampling.mdx
index d54da6256658ad..95970896348e84 100644
--- a/docs/platforms/php/common/configuration/sampling.mdx
+++ b/docs/platforms/php/common/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
diff --git a/docs/platforms/php/common/data-management/sensitive-data/index.mdx b/docs/platforms/php/common/data-management/sensitive-data/index.mdx
index cf4de7c59a1190..f06150b89cbdd9 100644
--- a/docs/platforms/php/common/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/php/common/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 ## Personally Identifiable Information (PII)
 
diff --git a/docs/platforms/php/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/php/common/enriching-events/breadcrumbs/index.mdx
index 77705a3b49b90c..0770caef65c398 100644
--- a/docs/platforms/php/common/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/php/common/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/php/common/enriching-events/context/index.mdx b/docs/platforms/php/common/enriching-events/context/index.mdx
index dd07e216bbb9f9..36da3d54f75935 100644
--- a/docs/platforms/php/common/enriching-events/context/index.mdx
+++ b/docs/platforms/php/common/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/php/common/enriching-events/tags/index.mdx b/docs/platforms/php/common/enriching-events/tags/index.mdx
index 8035c211bf7cd3..d0595213f5689d 100644
--- a/docs/platforms/php/common/enriching-events/tags/index.mdx
+++ b/docs/platforms/php/common/enriching-events/tags/index.mdx
@@ -15,11 +15,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/php/common/metrics/index.mdx b/docs/platforms/php/common/metrics/index.mdx
index cfdc1661c79b3a..afefeb82e2b9d2 100644
--- a/docs/platforms/php/common/metrics/index.mdx
+++ b/docs/platforms/php/common/metrics/index.mdx
@@ -9,11 +9,11 @@ notSupported:
 
 <Include name="metrics-api-change.mdx" />
 
-<Note>
+<Alert>
 
 Metrics for PHP are supported with Sentry PHP SDK version `4.5.0` and above.
 
-</Note>
+</Alert>
 
 Sentry metrics help you pinpoint and solve issues that impact user experience and app performance by measuring the data points that are important to you. You can track things like processing time, event size, user signups, and conversion rates, then correlate them back to tracing data in order to get deeper insights and solve issues faster.
 
diff --git a/docs/platforms/php/common/profiling/index.mdx b/docs/platforms/php/common/profiling/index.mdx
index 0d3f374ccdad16..6c70656fe80d9d 100644
--- a/docs/platforms/php/common/profiling/index.mdx
+++ b/docs/platforms/php/common/profiling/index.mdx
@@ -4,22 +4,22 @@ description: "Learn more about how to configure our Profiling integration and st
 sidebar_order: 5000
 ---
 
-<Note>
+<Alert>
 
 Profiling for PHP is supported with Sentry PHP SDK version `3.15.0` and above.
 
-</Note>
+</Alert>
 
 With [profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments.
 
 Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer).
 The Excimer PHP extension supports PHP 7.2 and up.
 
-<Note>
+<Alert>
 
 Excimer requires Linux or macOS and doesn't support Windows.
 
-</Note>
+</Alert>
 
 ## Installation
 
diff --git a/docs/platforms/php/common/tracing/index.mdx b/docs/platforms/php/common/tracing/index.mdx
index 0c4f578a3dd063..27e972ef8f3b60 100644
--- a/docs/platforms/php/common/tracing/index.mdx
+++ b/docs/platforms/php/common/tracing/index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 4000
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 ## Configure
 
diff --git a/docs/platforms/php/common/tracing/instrumentation/custom-instrumentation.mdx b/docs/platforms/php/common/tracing/instrumentation/custom-instrumentation.mdx
index ed214a1912157c..2d6ccdb2d2e704 100644
--- a/docs/platforms/php/common/tracing/instrumentation/custom-instrumentation.mdx
+++ b/docs/platforms/php/common/tracing/instrumentation/custom-instrumentation.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
@@ -30,7 +30,7 @@ $transactionContext = \Sentry\Tracing\TransactionContext::make()
         'data_attribute_2' => true,
     ]);
 $transaction = \Sentry\startTransaction($transactionContext);
-    
+
 // ... or create a span and assign data attributes
 
 $spanContext = \Sentry\Tracing\SpanContext::make()
diff --git a/docs/platforms/php/common/usage/index.mdx b/docs/platforms/php/common/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/php/common/usage/index.mdx
+++ b/docs/platforms/php/common/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/php/guides/laravel/configuration/laravel-options.mdx b/docs/platforms/php/guides/laravel/configuration/laravel-options.mdx
index ecda2443cf4e88..efedea58cdc83a 100644
--- a/docs/platforms/php/guides/laravel/configuration/laravel-options.mdx
+++ b/docs/platforms/php/guides/laravel/configuration/laravel-options.mdx
@@ -72,11 +72,11 @@ If you want more control over which requests are monitored, you can use the [`tr
 },
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Closures and Config Caching](/platforms/php/guides/laravel/configuration/laravel-options/#closures-and-config-caching).
 
-</Note>
+</Alert>
 
 ### More Configuration
 
diff --git a/docs/platforms/php/guides/laravel/integrations/eloquent.mdx b/docs/platforms/php/guides/laravel/integrations/eloquent.mdx
index 259a57ccc0cdbd..272daffb5f1c3c 100644
--- a/docs/platforms/php/guides/laravel/integrations/eloquent.mdx
+++ b/docs/platforms/php/guides/laravel/integrations/eloquent.mdx
@@ -37,11 +37,11 @@ Model::handleLazyLoadingViolationUsing(
 
 ### Lazy Loading
 
-<Note>
+<Alert>
 
 Read more about preventing lazy loading in the [Laravel documentation](https://laravel.com/docs/11.x/eloquent-relationships#preventing-lazy-loading).
 
-</Note>
+</Alert>
 
 To capture lazy loading violations add the following code to the `boot` method of your `AppServiceProvider`:
 
@@ -61,11 +61,11 @@ if (app()->isProduction()) {
 
 ### Silently Discarding Attributes (Mass Assignment Protection)
 
-<Note>
+<Alert>
 
 Read more about preventing silently discarding attributes in the [Laravel documentation](https://laravel.com/docs/11.x/eloquent#configuring-eloquent-strictness).
 
-</Note>
+</Alert>
 
 To capture silently discarded attribute violations add the following code to the `boot` method of your `AppServiceProvider`:
 
diff --git a/docs/platforms/php/guides/laravel/metrics/index.mdx b/docs/platforms/php/guides/laravel/metrics/index.mdx
index b6c80e2faab7d2..19d6688a9481b6 100644
--- a/docs/platforms/php/guides/laravel/metrics/index.mdx
+++ b/docs/platforms/php/guides/laravel/metrics/index.mdx
@@ -7,11 +7,11 @@ sidebar_hidden: true
 
 <Include name="metrics-api-change.mdx" />
 
-<Note>
+<Alert>
 
 Metrics for Laravel are supported with Sentry Laravel SDK version `4.2.0` and above.
 
-</Note>
+</Alert>
 
 Sentry metrics help you pinpoint and solve issues that impact user experience and app performance by measuring the data points that are important to you. You can track things like processing time, event size, user signups, and conversion rates, then correlate them back to tracing data in order to get deeper insights and solve issues faster.
 
diff --git a/docs/platforms/php/guides/laravel/other-versions/laravel4.mdx b/docs/platforms/php/guides/laravel/other-versions/laravel4.mdx
index e0ce3bb12f48e0..d9a9aae5690094 100644
--- a/docs/platforms/php/guides/laravel/other-versions/laravel4.mdx
+++ b/docs/platforms/php/guides/laravel/other-versions/laravel4.mdx
@@ -4,11 +4,11 @@ description: "Learn about using Sentry with Laravel 4.x."
 sidebar_order: 400
 ---
 
-<Note>
+<Alert>
 
 Laravel 4.x is supported until version 0.8.x of the `sentry/sentry-laravel` package.
 
-</Note>
+</Alert>
 
 Laravel is supported using a native package: [sentry-laravel](https://github.com/getsentry/sentry-laravel).
 
diff --git a/docs/platforms/php/guides/laravel/other-versions/laravel5.mdx b/docs/platforms/php/guides/laravel/other-versions/laravel5.mdx
index 0031df89c205ed..9581ffd0bde1c7 100644
--- a/docs/platforms/php/guides/laravel/other-versions/laravel5.mdx
+++ b/docs/platforms/php/guides/laravel/other-versions/laravel5.mdx
@@ -4,11 +4,11 @@ description: "Learn about using Sentry with Laravel 5.x."
 sidebar_order: 300
 ---
 
-<Note>
+<Alert>
 
 Laravel 5.x is supported until version 2.14.x of the `sentry/sentry-laravel` package.
 
-</Note>
+</Alert>
 
 Laravel is supported using a native package: [sentry-laravel](https://github.com/getsentry/sentry-laravel).
 
diff --git a/docs/platforms/php/guides/laravel/other-versions/laravel8-10.mdx b/docs/platforms/php/guides/laravel/other-versions/laravel8-10.mdx
index 0da3cd6ea72201..c148802a35d669 100644
--- a/docs/platforms/php/guides/laravel/other-versions/laravel8-10.mdx
+++ b/docs/platforms/php/guides/laravel/other-versions/laravel8-10.mdx
@@ -29,11 +29,11 @@ public function register(): void
 }
 ```
 
-<Note>
+<Alert>
 
 Alternatively, you can configure Sentry in your [Laravel Log Channel](/platforms/php/guides/laravel/usage/#log-channels), allowing you to log `info` and `debug` as well.
 
-</Note>
+</Alert>
 
 ## Configure
 
diff --git a/docs/platforms/php/guides/laravel/profiling/index.mdx b/docs/platforms/php/guides/laravel/profiling/index.mdx
index 4afad9164a6f01..3d43cfffdcc3ac 100644
--- a/docs/platforms/php/guides/laravel/profiling/index.mdx
+++ b/docs/platforms/php/guides/laravel/profiling/index.mdx
@@ -4,22 +4,22 @@ description: "Learn more about how to configure our Profiling integration and st
 sidebar_order: 5000
 ---
 
-<Note>
+<Alert>
 
 Profiling for PHP is supported with Sentry Laravel SDK version `3.3.0` and above.
 
-</Note>
+</Alert>
 
 With [Profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments.
 
 Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer).
 The Excimer PHP extension supports PHP 7.2 and up.
 
-<Note>
+<Alert>
 
 Excimer requires Linux or macOS and doesn't support Windows.
 
-</Note>
+</Alert>
 
 ## Installation
 
diff --git a/docs/platforms/php/guides/laravel/usage/index.mdx b/docs/platforms/php/guides/laravel/usage/index.mdx
index 726b004b372b2d..e8de820066cff5 100644
--- a/docs/platforms/php/guides/laravel/usage/index.mdx
+++ b/docs/platforms/php/guides/laravel/usage/index.mdx
@@ -90,7 +90,7 @@ class SentryContext
 
 ### Log Channels
 
-<Alert level="info" title="Note">
+<Alert title="Note">
 
 If you're using log channels to log your exceptions and are also logging exceptions to Sentry in your exception handler, exceptions might show up in Sentry twice.
 
diff --git a/docs/platforms/php/guides/symfony/enriching-events/tags/index.mdx b/docs/platforms/php/guides/symfony/enriching-events/tags/index.mdx
index 18385d5296e08e..6f038e757e78e4 100644
--- a/docs/platforms/php/guides/symfony/enriching-events/tags/index.mdx
+++ b/docs/platforms/php/guides/symfony/enriching-events/tags/index.mdx
@@ -11,11 +11,11 @@ _Tag keys_ have a maximum length of 32 characters and can contain only letters (
 
 _Tag values_ have a maximum length of 200 characters and they cannot contain the newline (`\n`) character.
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/php/guides/symfony/metrics/index.mdx b/docs/platforms/php/guides/symfony/metrics/index.mdx
index 415fecc3b01035..f9fe3b07f1a0de 100644
--- a/docs/platforms/php/guides/symfony/metrics/index.mdx
+++ b/docs/platforms/php/guides/symfony/metrics/index.mdx
@@ -7,11 +7,11 @@ sidebar_hidden: true
 
 <Include name="metrics-api-change.mdx" />
 
-<Note>
+<Alert>
 
 Metrics for Symfony are supported with Sentry Symfony SDK version `5.0.0` and above.
 
-</Note>
+</Alert>
 
 Sentry metrics help you pinpoint and solve issues that impact user experience and app performance by measuring the data points that are important to you. You can track things like processing time, event size, user signups, and conversion rates, then correlate them back to tracing data in order to get deeper insights and solve issues faster.
 
diff --git a/docs/platforms/php/guides/symfony/profiling/index.mdx b/docs/platforms/php/guides/symfony/profiling/index.mdx
index 0f9cb22a6f63ca..4ac70a46553ae3 100644
--- a/docs/platforms/php/guides/symfony/profiling/index.mdx
+++ b/docs/platforms/php/guides/symfony/profiling/index.mdx
@@ -4,22 +4,22 @@ description: "Learn more about how to configure our Profiling integration and st
 sidebar_order: 5000
 ---
 
-<Note>
+<Alert>
 
 Profiling for PHP is supported with Sentry Symfony SDK version `4.7.0` and above.
 
-</Note>
+</Alert>
 
 With [Profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments.
 
 Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer).
 The Excimer PHP extension supports PHP 7.2 and up.
 
-<Note>
+<Alert>
 
 Excimer requires Linux or macOS and doesn't support Windows.
 
-</Note>
+</Alert>
 
 ## Installation
 
diff --git a/docs/platforms/php/legacy-sdk/usage.mdx b/docs/platforms/php/legacy-sdk/usage.mdx
index 64f9d84e1df1c1..b5ec18bb45f0ef 100644
--- a/docs/platforms/php/legacy-sdk/usage.mdx
+++ b/docs/platforms/php/legacy-sdk/usage.mdx
@@ -36,7 +36,7 @@ $error_handler->registerErrorHandler();
 $error_handler->registerShutdownFunction();
 ```
 
-<Alert level="info" title="Note">
+<Alert title="Note">
 
 Calling `install()` on a Raven_Client instance will automatically register these handlers.
 
diff --git a/docs/platforms/powershell/configuration/options.mdx b/docs/platforms/powershell/configuration/options.mdx
index 2644cfe71b6a1f..465975945a331e 100644
--- a/docs/platforms/powershell/configuration/options.mdx
+++ b/docs/platforms/powershell/configuration/options.mdx
@@ -101,11 +101,11 @@ Grouping in Sentry is different for events with stack traces and without. As a r
 
 If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This option is turned off by default.
 
diff --git a/docs/platforms/powershell/configuration/releases.mdx b/docs/platforms/powershell/configuration/releases.mdx
index bde5894a2e3037..638247fa808d16 100644
--- a/docs/platforms/powershell/configuration/releases.mdx
+++ b/docs/platforms/powershell/configuration/releases.mdx
@@ -24,16 +24,16 @@ The release name cannot:
 The value can be arbitrary, but we recommend either of these naming strategies:
 
 - **Semantic Versioning**: `package@version` or `package@version+build` (for example, `my.project.name@2.3.12+1234`)
-  - `package` is the unique identifier of the project/app 
-  - `version` is the semver-like structure `<major>.<minor?>.<patch?>.<revision?>-<prerelease?>` 
-  - `build` is the number that identifies an iteration of your app 
+  - `package` is the unique identifier of the project/app
+  - `version` is the semver-like structure `<major>.<minor?>.<patch?>.<revision?>-<prerelease?>`
+  - `build` is the number that identifies an iteration of your app
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -62,11 +62,11 @@ After configuring your SDK, you can install a repository integration or manually
 
 Monitor the [health of releases](/product/releases/health/) by observing user adoption, usage of the application, percentage of [crashes](/product/releases/health/#crash), and [session data](/product/releases/health/#session). Release health will provide insight into the impact of crashes and bugs as it relates to user experience, and reveal trends with each new issue through the [Release Details](/product/releases/release-details/) graphs and filters.
 
-<Note>
+<Alert>
 
 Crash reporting and app hang detection are not available for watchOS.
 
-</Note>
+</Alert>
 
 In order to monitor release health, the SDK sends session data.
 
diff --git a/docs/platforms/powershell/configuration/sampling.mdx b/docs/platforms/powershell/configuration/sampling.mdx
index 2c8aff45559ed2..ff7fc637ecca9a 100644
--- a/docs/platforms/powershell/configuration/sampling.mdx
+++ b/docs/platforms/powershell/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
diff --git a/docs/platforms/powershell/data-management/sensitive-data/index.mdx b/docs/platforms/powershell/data-management/sensitive-data/index.mdx
index cf4de7c59a1190..f06150b89cbdd9 100644
--- a/docs/platforms/powershell/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/powershell/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 ## Personally Identifiable Information (PII)
 
diff --git a/docs/platforms/powershell/enriching-events/attachments/index.mdx b/docs/platforms/powershell/enriching-events/attachments/index.mdx
index c0ecaa6ebf7251..30e9ab4abe6cd5 100644
--- a/docs/platforms/powershell/enriching-events/attachments/index.mdx
+++ b/docs/platforms/powershell/enriching-events/attachments/index.mdx
@@ -47,11 +47,11 @@ Attachments live on the <PlatformLink to="/enriching-events/scopes/">Scope</Plat
 
 <PlatformContent includePath="enriching-events/attachment-upload" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/powershell/enriching-events/breadcrumbs/index.mdx b/docs/platforms/powershell/enriching-events/breadcrumbs/index.mdx
index 032b4b2fafdb0a..c780b4de862d2c 100644
--- a/docs/platforms/powershell/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/powershell/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/powershell/enriching-events/context/index.mdx b/docs/platforms/powershell/enriching-events/context/index.mdx
index 3fa1c3fffd8af4..3c36bc77e1f8bd 100644
--- a/docs/platforms/powershell/enriching-events/context/index.mdx
+++ b/docs/platforms/powershell/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/powershell/enriching-events/identify-user/index.mdx b/docs/platforms/powershell/enriching-events/identify-user/index.mdx
index d20a55786a7597..242b1077788c41 100644
--- a/docs/platforms/powershell/enriching-events/identify-user/index.mdx
+++ b/docs/platforms/powershell/enriching-events/identify-user/index.mdx
@@ -9,11 +9,11 @@ Users consist of a few critical pieces of information that construct a unique id
 
 ### `id`
 
-<Note>
+<Alert>
 
 If you don't provide an `id`, the SDK falls back to `installationId`, which the SDK randomly generates once during an app's installation.
 
-</Note>
+</Alert>
 
 Your internal identifier for the user.
 
diff --git a/docs/platforms/powershell/enriching-events/scopes/index.mdx b/docs/platforms/powershell/enriching-events/scopes/index.mdx
index 751b9de56294df..c70db4f1f633c3 100644
--- a/docs/platforms/powershell/enriching-events/scopes/index.mdx
+++ b/docs/platforms/powershell/enriching-events/scopes/index.mdx
@@ -72,7 +72,7 @@ made will stay isolated within the callback function. This allows you to
 more easily isolate pieces of context information to specific locations in your code or
 even call `clear` to briefly remove all context information.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 Any exceptions that occur within the callback function for configuring a local scope will not be
 caught, and all errors that occur will be silently ignored and **not** reported.
diff --git a/docs/platforms/powershell/enriching-events/tags/index.mdx b/docs/platforms/powershell/enriching-events/tags/index.mdx
index 5707e7b98110ca..9657816853afb2 100644
--- a/docs/platforms/powershell/enriching-events/tags/index.mdx
+++ b/docs/platforms/powershell/enriching-events/tags/index.mdx
@@ -17,11 +17,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/powershell/index.mdx b/docs/platforms/powershell/index.mdx
index 47ee6201fe5837..bf25db93feda99 100644
--- a/docs/platforms/powershell/index.mdx
+++ b/docs/platforms/powershell/index.mdx
@@ -36,10 +36,10 @@ This snippet includes an intentional error, so you can test that everything is w
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
diff --git a/docs/platforms/powershell/tracing/index.mdx b/docs/platforms/powershell/tracing/index.mdx
index c18d9615ce653e..a0bcf61547c081 100644
--- a/docs/platforms/powershell/tracing/index.mdx
+++ b/docs/platforms/powershell/tracing/index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 4000
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 ## Configure
 
diff --git a/docs/platforms/powershell/tracing/instrumentation/custom-instrumentation.mdx b/docs/platforms/powershell/tracing/instrumentation/custom-instrumentation.mdx
index a9e53aaa98de73..1ccb9b0eb02be4 100644
--- a/docs/platforms/powershell/tracing/instrumentation/custom-instrumentation.mdx
+++ b/docs/platforms/powershell/tracing/instrumentation/custom-instrumentation.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
diff --git a/docs/platforms/powershell/usage/index.mdx b/docs/platforms/powershell/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/powershell/usage/index.mdx
+++ b/docs/platforms/powershell/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/python/configuration/options.mdx b/docs/platforms/python/configuration/options.mdx
index 98f6d0db7d7af6..6fd92e3dbd56d8 100644
--- a/docs/platforms/python/configuration/options.mdx
+++ b/docs/platforms/python/configuration/options.mdx
@@ -97,11 +97,11 @@ Grouping in Sentry is different for events with stack traces and without. As a r
 
 If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This option is turned off by default.
 
@@ -192,10 +192,10 @@ Please note that the Sentry server [limits HTTP request body size](https://devel
 
 The number of characters after which the values containing text in the event payload will be truncated (defaults to `1024`).
 
-<Note>
+<Alert>
   If the value you set for this is exceptionally large, the event may exceed 1
   MiB and will be dropped by Sentry.
-</Note>
+</Alert>
 
 </ConfigKey>
 
diff --git a/docs/platforms/python/data-management/sensitive-data/index.mdx b/docs/platforms/python/data-management/sensitive-data/index.mdx
index 1feccf7df6c5cc..cfdd5503868955 100644
--- a/docs/platforms/python/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/python/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 ## Personally Identifiable Information (PII)
 
diff --git a/docs/platforms/python/enriching-events/attachments/index.mdx b/docs/platforms/python/enriching-events/attachments/index.mdx
index 16aaade9389701..fd5e2b060238ff 100644
--- a/docs/platforms/python/enriching-events/attachments/index.mdx
+++ b/docs/platforms/python/enriching-events/attachments/index.mdx
@@ -9,11 +9,11 @@ Sentry can enrich your events for further investigation by storing additional fi
 
 <PlatformContent includePath="enriching-events/add-attachment" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/python/enriching-events/breadcrumbs/index.mdx b/docs/platforms/python/enriching-events/breadcrumbs/index.mdx
index 77705a3b49b90c..0770caef65c398 100644
--- a/docs/platforms/python/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/python/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/python/enriching-events/context/index.mdx b/docs/platforms/python/enriching-events/context/index.mdx
index dd07e216bbb9f9..36da3d54f75935 100644
--- a/docs/platforms/python/enriching-events/context/index.mdx
+++ b/docs/platforms/python/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/python/enriching-events/scopes/index.mdx b/docs/platforms/python/enriching-events/scopes/index.mdx
index 824c0c158e2a75..040acaf65197d6 100644
--- a/docs/platforms/python/enriching-events/scopes/index.mdx
+++ b/docs/platforms/python/enriching-events/scopes/index.mdx
@@ -25,11 +25,11 @@ We generally recommend using the top-level API to manage your scopes, since the
 
 However, if your use case requires direct access to the scope object, you can use the <PlatformIdentifier name="new-scope" /> context manager. <PlatformIdentifier name="new-scope" /> forks the current scope, allows you to modify the new scope while the context manager is active, and restores the original scope afterwards. Using <PlatformIdentifier name="new-scope" /> allows you to send data for only one specific event, such as [modifying the context](../context/). It is roughly equivalent to the <PlatformIdentifier name="push-scope" /> context manager in earlier (1.x) versions of the SDK.
 
-<Note>
+<Alert>
 
 Avoid calling top-level APIs inside the  <PlatformIdentifier name="new-scope" /> context manager. The top-level API might interact with a different scope from what <PlatformIdentifier name="new-scope" /> yields, causing unintended results. While within the <PlatformIdentifier name="new-scope" /> context manager, please call methods directly on the scope that <PlatformIdentifier name="new-scope" /> yields!
 
-</Note>
+</Alert>
 
 Using <PlatformIdentifier name="new-scope" /> allows you to attach additional information, such as adding custom tags or informing Sentry about the currently authenticated user.
 
diff --git a/docs/platforms/python/enriching-events/tags/index.mdx b/docs/platforms/python/enriching-events/tags/index.mdx
index 8606ad533d8aca..11c40af20bb92f 100644
--- a/docs/platforms/python/enriching-events/tags/index.mdx
+++ b/docs/platforms/python/enriching-events/tags/index.mdx
@@ -25,11 +25,11 @@ from sentry_sdk import set_tags
 set_tags({"page.locale": "de-at", "page.type": "article"})
 ```
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/python/index.mdx b/docs/platforms/python/index.mdx
index 1585c5fbe8e28c..4785844a1596d5 100644
--- a/docs/platforms/python/index.mdx
+++ b/docs/platforms/python/index.mdx
@@ -61,16 +61,16 @@ Add this intentional error to your application to test that everything is workin
 division_by_zero = 1 / 0
 ```
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
 
-<Note>
+<Alert>
 
 Not seeing your error in Sentry? Make sure you're running the above example from a file and not from a Python shell like IPython.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/python/integrations/anthropic/index.mdx b/docs/platforms/python/integrations/anthropic/index.mdx
index 13deba3a02744a..016bbebecd07bd 100644
--- a/docs/platforms/python/integrations/anthropic/index.mdx
+++ b/docs/platforms/python/integrations/anthropic/index.mdx
@@ -3,7 +3,7 @@ title: Anthropic
 description: "Learn about using Sentry for Anthropic."
 ---
 
-<Alert level="info" title="Beta">
+<Alert title="Beta">
 
 The support for **Anthropic** is in its beta phase.
 
diff --git a/docs/platforms/python/integrations/asgi/index.mdx b/docs/platforms/python/integrations/asgi/index.mdx
index 2ca7e8dad29107..7cd2fa15bb4963 100644
--- a/docs/platforms/python/integrations/asgi/index.mdx
+++ b/docs/platforms/python/integrations/asgi/index.mdx
@@ -5,11 +5,11 @@ description: "Learn about the ASGI integration and how it adds support for ASGI
 
 The ASGI middleware can be used to instrument any [ASGI](https://asgi.readthedocs.io/en/latest/)-compatible web framework to attach request data for your events.
 
-<Note>
+<Alert>
 
 Please check our list of [supported integrations](/platforms/python/integrations/) as there might already be a specific integration (like [FastAPI](/platforms/python/integrations/fastapi/) or [Sanic](/platforms/python/integrations/sanic/)) that is easier to use and captures more useful information than our generic ASGI middleware. If that's the case, you should use the specific integration instead of this middleware.
 
-</Note>
+</Alert>
 
 ## Install
 
diff --git a/docs/platforms/python/integrations/aws-lambda/manual-instrumentation/index.mdx b/docs/platforms/python/integrations/aws-lambda/manual-instrumentation/index.mdx
index df211dc279f26d..0fdc4abef65f03 100644
--- a/docs/platforms/python/integrations/aws-lambda/manual-instrumentation/index.mdx
+++ b/docs/platforms/python/integrations/aws-lambda/manual-instrumentation/index.mdx
@@ -66,7 +66,7 @@ def lambda_handler(event, context):
     # ...
 ```
 
-<Alert level="info" title="Note">
+<Alert title="Note">
 
 If you're using another web framework inside of AWS Lambda, that framework may catch exceptions before we see them. Make sure to enable the framework-specific integration if it exists. See [_the Python main page_](/platforms/python/) for more information.
 
diff --git a/docs/platforms/python/integrations/celery/crons.mdx b/docs/platforms/python/integrations/celery/crons.mdx
index 290a395b2afc7e..555c35adf537cc 100644
--- a/docs/platforms/python/integrations/celery/crons.mdx
+++ b/docs/platforms/python/integrations/celery/crons.mdx
@@ -9,9 +9,9 @@ Sentry Crons allows you to monitor the uptime and performance of any scheduled,
 
 Use the Celery integration to monitor your [Celery periodic tasks](https://docs.celeryq.dev/en/stable/userguide/periodic-tasks.html) and get notified when a task is missed (or doesn't start when expected), if it fails due to a problem in the runtime (such as an error), or if it fails by exceeding its maximum runtime.
 
-<Note>
+<Alert>
   Please note that a cron monitor will only be created the first time your task runs.
-</Note>
+</Alert>
 
 Get started by setting up your Celery beat schedule:
 
@@ -30,10 +30,10 @@ app.conf.beat_schedule = {
 }
 ```
 
-<Note>
+<Alert>
   Please note that only schedules that can be parsed by crontab will be successfully
   updated or inserted.
-</Note>
+</Alert>
 
 Next, initialize Sentry. Where to do this depends on how you run beat:
 
@@ -85,11 +85,11 @@ Start your Celery beat and worker services and see your tasks being monitored at
 
 In addition to the default Celery Beat scheduler, we also support [Redbeat](https://redbeat.readthedocs.io/en/latest).
 
-<Note>
+<Alert>
 
 You don't need to create Cron Monitors for your tasks on Sentry.io, we'll do it for you.
 
-</Note>
+</Alert>
 
 ### Excluding Celery Beat Tasks from Auto Discovery
 
@@ -118,11 +118,11 @@ For more information, see the documentation for <PlatformLink to="/#options">opt
 
 We provide a lightweight decorator to make monitoring individual tasks easier. To use it, add `@sentry_sdk.monitor` to your Celery task (or any function), then supply a `monitor_slug` of a monitor created previously on Sentry.io. Once this is done, every time the task (or function) is executed, telemetry data will be captured when a task is started, when it finishes, and when it fails.
 
-<Note>
+<Alert>
 
 Make sure the Sentry `@sentry_sdk.monitor` decorator is below Celery's `@app.task` decorator.
 
-</Note>
+</Alert>
 
 ```python {diff} {filename:tasks.py}
 # tasks.py
diff --git a/docs/platforms/python/integrations/celery/index.mdx b/docs/platforms/python/integrations/celery/index.mdx
index a597a5ce032e45..70e113501c5f3e 100644
--- a/docs/platforms/python/integrations/celery/index.mdx
+++ b/docs/platforms/python/integrations/celery/index.mdx
@@ -120,7 +120,7 @@ def debug_sentry():
     1/0
 ```
 
-<Alert level="info" title="Note on distributed tracing">
+<Alert title="Note on distributed tracing">
 
 Sentry uses custom message headers for distributed tracing. For Celery versions 4.x, with [message protocol of version 1](https://docs.celeryq.dev/en/stable/internals/protocol.html#version-1), this functionality is broken, and Celery fails to propagate custom headers to the worker. Protocol version 2, which is the default since Celery version 4.0, is not affected.
 
diff --git a/docs/platforms/python/integrations/cohere/index.mdx b/docs/platforms/python/integrations/cohere/index.mdx
index b585cfb9fec37b..4cbf8af23154d6 100644
--- a/docs/platforms/python/integrations/cohere/index.mdx
+++ b/docs/platforms/python/integrations/cohere/index.mdx
@@ -3,7 +3,7 @@ title: Cohere
 description: "Learn about using Sentry for Cohere."
 ---
 
-<Alert level="info" title="Beta">
+<Alert title="Beta">
 
 The support for **Cohere** is in its beta phase.
 
diff --git a/docs/platforms/python/integrations/django/index.mdx b/docs/platforms/python/integrations/django/index.mdx
index 286619a8222925..8b3f0449c02076 100644
--- a/docs/platforms/python/integrations/django/index.mdx
+++ b/docs/platforms/python/integrations/django/index.mdx
@@ -7,11 +7,11 @@ description: "Learn about using Sentry with Django."
 
 Sentry's [Django](https://www.djangoproject.com/) integration adds support for the Django framework. It enables automatic reporting of errors and exceptions as well as tracing. In order to get started using the integration, you should have a [Sentry account](https://sentry.io) and a project set up.
 
-<Note>
+<Alert>
 
 If you're using Python 3.7, Django applications with `channels` 2.0 will be correctly instrumented. Older versions of Python will require the installation of [aiocontextvars](https://pypi.org/project/aiocontextvars/).
 
-</Note>
+</Alert>
 
 ## Install
 
@@ -88,11 +88,11 @@ The following parts of your Django project are monitored:
 - Redis commands
 - Access to Django caches
 
-<Note>
+<Alert>
 
 The parameter `enable_tracing` needs to be set when initializing the Sentry SDK for performance measurements to be recorded.
 
-</Note>
+</Alert>
 
 ## Options
 
@@ -165,7 +165,7 @@ You can pass the following keyword arguments to `DjangoIntegration()`:
 
   (Note that `OPTIONS` and `HEAD` are missing by default.)
 
-  <Alert title="Added in 2.15.0" level="info">
+  <Alert title="Added in 2.15.0">
     The `http_methods_to_capture` option.
   </Alert>
 
diff --git a/docs/platforms/python/integrations/dramatiq/index.mdx b/docs/platforms/python/integrations/dramatiq/index.mdx
index 377caf3d201f26..59b084aea708ba 100644
--- a/docs/platforms/python/integrations/dramatiq/index.mdx
+++ b/docs/platforms/python/integrations/dramatiq/index.mdx
@@ -7,7 +7,7 @@ The Dramatiq integration adds support for the [Dramatiq](https://dramatiq.io/) b
 
 The Dramatiq integration only reports errors. Tracing is not yet supported. If you want to have more instrumentation, you need to do [custom instrumentation](/platforms/python/tracing/instrumentation/custom-instrumentation/).
 
-<Alert level="info">
+<Alert>
   This is the successor of the original `DramatiqIntegration` that can be found here: https://github.com/jacobsvante/sentry-dramatiq
 
   The original maintainer has [donated the integration to Sentry](https://github.com/getsentry/sentry-python/issues/3387), so we can take over maintenance.
diff --git a/docs/platforms/python/integrations/fastapi/index.mdx b/docs/platforms/python/integrations/fastapi/index.mdx
index 1f466ecb111d81..8ef55d442f582f 100644
--- a/docs/platforms/python/integrations/fastapi/index.mdx
+++ b/docs/platforms/python/integrations/fastapi/index.mdx
@@ -61,11 +61,11 @@ The following parts of your FastAPI project are monitored:
 
 ![Performance details are shown as waterfall diagram](./img/fastapi-performance-details.png)
 
-<Note>
+<Alert>
 
 The parameter `enable_tracing` needs to be set when initializing the Sentry SDK for performance measurements to be recorded.
 
-</Note>
+</Alert>
 
 ## Options
 
@@ -154,7 +154,7 @@ You can pass the following keyword arguments to `StarletteIntegration()` and `Fa
 
   (Note that `OPTIONS` and `HEAD` are missing by default.)
 
-  <Alert title="Added in 2.15.0" level="info">
+  <Alert title="Added in 2.15.0">
     The `http_methods_to_capture` option.
   </Alert>
 
diff --git a/docs/platforms/python/integrations/flask/index.mdx b/docs/platforms/python/integrations/flask/index.mdx
index 4441173e451d74..bc564c3f8bb71a 100644
--- a/docs/platforms/python/integrations/flask/index.mdx
+++ b/docs/platforms/python/integrations/flask/index.mdx
@@ -19,11 +19,11 @@ If you have the `flask` package in your dependencies, the Flask integration will
 
 <PlatformContent includePath="getting-started-config" />
 
-<Note>
+<Alert>
 
 Our Python SDK will install the Flask integration for all of your apps. It hooks into Flask’s signals, not anything on the app object.
 
-</Note>
+</Alert>
 
 ## Verify
 
@@ -101,7 +101,7 @@ You can pass the following keyword arguments to `FlaskIntegration()`:
 
   (Note that `OPTIONS` and `HEAD` are missing by default.)
 
-  <Alert title="Added in 2.15.0" level="info">
+  <Alert title="Added in 2.15.0">
     The `http_methods_to_capture` option.
   </Alert>
 
diff --git a/docs/platforms/python/integrations/gcp-functions/index.mdx b/docs/platforms/python/integrations/gcp-functions/index.mdx
index 1681bc684eef23..d2c123aa0955a7 100644
--- a/docs/platforms/python/integrations/gcp-functions/index.mdx
+++ b/docs/platforms/python/integrations/gcp-functions/index.mdx
@@ -11,13 +11,13 @@ Add the Sentry SDK to your `requirements.txt`:
  sentry-sdk>=0.17.1
 ```
 
-<Note>
+<Alert>
 
 The GCP integration currently supports only the Python `3.7` runtime environment. If you try to run it with a newer version (such as `3.9`), an error message will be displayed (with debug mode on).
 
 Limited Sentry support is available on newer Python runtimes by directly enabling [integrations for supported frameworks](/platforms/python/integrations) and/or using the generic [serverless integration](/platforms/python/integrations/serverless/).
 
-</Note>
+</Alert>
 
 ## Configure
 
@@ -57,7 +57,7 @@ def http_function_entrypoint(request):
     # ...
 ```
 
-<Alert level="info" title="Note">
+<Alert title="Note">
 
 If you are using a web framework inside of your Cloud Function, the framework might catch those exceptions before we get to see them. Make sure to enable the framework specific integration as well, if one exists. See [_the Python main page_](/platforms/python/) for more information.
 
diff --git a/docs/platforms/python/integrations/grpc/index.mdx b/docs/platforms/python/integrations/grpc/index.mdx
index 9dcc37069ab340..968389c8422a47 100644
--- a/docs/platforms/python/integrations/grpc/index.mdx
+++ b/docs/platforms/python/integrations/grpc/index.mdx
@@ -100,13 +100,13 @@ async with grpc.aio.insecure_channel("example.com:12345") as channel:
     ...
 ```
 
-<Note>
+<Alert>
 
 **Note:**
 
 In older versions of this integration you had to add the interceptors by hand. Since Python SDK version 1.35.0 you do not need to add any interceptors by hand but only add the GRPCIntegration as described above.
 
-</Note>
+</Alert>
 
 ## Verify
 
diff --git a/docs/platforms/python/integrations/huggingface_hub/index.mdx b/docs/platforms/python/integrations/huggingface_hub/index.mdx
index f85858269e4575..48dd63eb3be498 100644
--- a/docs/platforms/python/integrations/huggingface_hub/index.mdx
+++ b/docs/platforms/python/integrations/huggingface_hub/index.mdx
@@ -3,7 +3,7 @@ title: Huggingface Hub
 description: "Learn about using Sentry for Huggingface Hub."
 ---
 
-<Alert level="info" title="Beta">
+<Alert title="Beta">
 
 The support for **Huggingface Hub** is in its beta phase.
 
diff --git a/docs/platforms/python/integrations/langchain/index.mdx b/docs/platforms/python/integrations/langchain/index.mdx
index 61a1051a7cf51b..0659ed62596a0e 100644
--- a/docs/platforms/python/integrations/langchain/index.mdx
+++ b/docs/platforms/python/integrations/langchain/index.mdx
@@ -3,7 +3,7 @@ title: Langchain
 description: "Learn about using Sentry for Langchain."
 ---
 
-<Alert level="info" title="Beta">
+<Alert title="Beta">
 
 The support for **LangChain** is in its beta phase.
 
diff --git a/docs/platforms/python/integrations/logging/index.mdx b/docs/platforms/python/integrations/logging/index.mdx
index 9e6806f12d3cf2..d040fa2f5953d7 100644
--- a/docs/platforms/python/integrations/logging/index.mdx
+++ b/docs/platforms/python/integrations/logging/index.mdx
@@ -79,7 +79,7 @@ You can pass the following keyword arguments to `LoggingIntegration()`:
 
 - `event_level` (default `ERROR`): The Sentry Python SDK will report log records with a level higher than or equal to `event_level` as events as long as the logger itself is set to output records of those log levels (see note below). If a value of `None` occurs, the SDK won't send log records as events.
 
-<Alert level="info" title="Note">
+<Alert title="Note">
 
 The Sentry Python SDK will honor the configured level of each logger (set with `logger.setLevel(level)` or `logging.basicConfig(level=level)`). That means that you will not see any `INFO` or `DEBUG` events from a logger with the level set to `WARNING`, regardless of how you configure the integration. If not set explicitly, the logging level defaults to `WARNING`.
 
diff --git a/docs/platforms/python/integrations/openai/index.mdx b/docs/platforms/python/integrations/openai/index.mdx
index 1327596ca034e5..66996f2125711d 100644
--- a/docs/platforms/python/integrations/openai/index.mdx
+++ b/docs/platforms/python/integrations/openai/index.mdx
@@ -3,7 +3,7 @@ title: OpenAI
 description: "Learn about using Sentry for OpenAI."
 ---
 
-<Alert level="info" title="Beta">
+<Alert title="Beta">
 
 The support for **OpenAI** is in its beta phase.
 
diff --git a/docs/platforms/python/integrations/starlette/index.mdx b/docs/platforms/python/integrations/starlette/index.mdx
index 396de6001989a1..7b2e5e58e83ee6 100644
--- a/docs/platforms/python/integrations/starlette/index.mdx
+++ b/docs/platforms/python/integrations/starlette/index.mdx
@@ -117,7 +117,7 @@ You can pass the following keyword arguments to `StarletteIntegration()`:
 
   (Note that `OPTIONS` and `HEAD` are missing by default.)
 
-  <Alert title="Added in 2.15.0" level="info">
+  <Alert title="Added in 2.15.0">
     The `http_methods_to_capture` option.
   </Alert>
 
diff --git a/docs/platforms/python/integrations/sys_exit/index.mdx b/docs/platforms/python/integrations/sys_exit/index.mdx
index 39c234e5f6ee12..e3c59e8e4a9000 100644
--- a/docs/platforms/python/integrations/sys_exit/index.mdx
+++ b/docs/platforms/python/integrations/sys_exit/index.mdx
@@ -66,7 +66,7 @@ sys.exit(1)
 If you use `capture_successful_exits=True`, calling `sys.exit(0)` should also report a `SystemExit` exception to Sentry.
 
 
-<Alert level="info" title="Manually-raised SystemExit">
+<Alert title="Manually-raised SystemExit">
 
 Please note that the `SysExitIntegration` only captures `SystemExit` exceptions which are raised by calling `sys.exit`. If your code raises `SystemExit` without calling `sys.exit`, the exception will not be reported to Sentry.
 
diff --git a/docs/platforms/python/integrations/wsgi/index.mdx b/docs/platforms/python/integrations/wsgi/index.mdx
index 912ca3809e44aa..7e09a4f4e9336b 100644
--- a/docs/platforms/python/integrations/wsgi/index.mdx
+++ b/docs/platforms/python/integrations/wsgi/index.mdx
@@ -5,10 +5,10 @@ description: "Learn about the WSGI integration and how it adds support for WSGI
 
 If you use a WSGI framework not directly supported by the SDK, or wrote a raw WSGI app, you can use this generic WSGI middleware. It captures errors and attaches a basic amount of information for incoming requests.
 
-<Note>
+<Alert>
 
 Please check our list of [supported integrations](/platforms/python/integrations/) as there might already be a specific integration (like [Django](/platforms/python/integrations/django/) or [Flask](/platforms/python/integrations/flask/)) that is easier to use and captures more useful information than our generic WSGI middleware. If that's the case, you should use the specific integration instead of this middleware.
-</Note>
+</Alert>
 
 ## Install
 
diff --git a/docs/platforms/python/legacy-sdk/integrations.mdx b/docs/platforms/python/legacy-sdk/integrations.mdx
index 89925ef5766476..c0d3c5c1a13a7c 100644
--- a/docs/platforms/python/legacy-sdk/integrations.mdx
+++ b/docs/platforms/python/legacy-sdk/integrations.mdx
@@ -875,7 +875,7 @@ logger.error('There was an error, with a stack trace!', extra={
 })
 ```
 
-<Alert level="" title="Note on Python version">
+<Alert title="Note on Python version">
 
 Depending on the version of Python you’re using, `extra` might not be an acceptable keyword argument for a logger’s `.exception()` method (`.debug()`, `.info()`, `.warning()`, `.error()` and `.critical()` should work fine regardless of Python version). This should be fixed as of Python 2.7.4 and 3.2. Official issue here: [bugs.python.org/issue15541](https://bugs.python.org/issue15541).
 
@@ -1200,7 +1200,7 @@ class AsyncExceptionHandler(SentryMixin, tornado.web.RequestHandler):
         self.finish()
 ```
 
-<Alert level="" title="Tip">
+<Alert title="Tip">
 
 The value returned by the yield is a `HTTPResponse` object.
 
diff --git a/docs/platforms/python/metrics/index.mdx b/docs/platforms/python/metrics/index.mdx
index 8334b343aaa6c2..5d4a94528bd87f 100644
--- a/docs/platforms/python/metrics/index.mdx
+++ b/docs/platforms/python/metrics/index.mdx
@@ -7,11 +7,11 @@ sidebar_hidden: true
 
 <Include name="metrics-api-change.mdx" />
 
-<Note>
+<Alert>
 
 Metrics for Python are supported with Sentry Python SDK version `1.40.0` and above.
 
-</Note>
+</Alert>
 
 Sentry metrics help you pinpoint and solve issues that impact user experience and app performance by measuring the data points that are important to you. You can track things like processing time, event size, user signups, and conversion rates, then correlate them back to tracing data in order to get deeper insights and solve issues faster.
 
diff --git a/docs/platforms/python/profiling/index.mdx b/docs/platforms/python/profiling/index.mdx
index 722dba58f5934e..b1e4af71e009f7 100644
--- a/docs/platforms/python/profiling/index.mdx
+++ b/docs/platforms/python/profiling/index.mdx
@@ -9,11 +9,11 @@ sidebar_order: 5000
 
 ## Enable Profiling
 
-<Note>
+<Alert>
 
 Python profiling is stable as of SDK version `1.18.0`.
 
-</Note>
+</Alert>
 
 
 ```python
@@ -38,13 +38,13 @@ sentry_sdk.init(
 )
 ```
 
-<Note>
+<Alert>
 
 The <PlatformIdentifier name="profiles_sample_rate" /> setting is _relative_ to the <PlatformIdentifier name="traces_sample_rate" /> setting.
 
 For Profiling to work, you have to first enable Sentry’s tracing via `traces_sample_rate` (like in the example above). Read our <PlatformLink to="/tracing/">tracing setup documentation</PlatformLink> to learn how to configure sampling. If you set your sample rate to 1.0, all transactions will be captured.
 
-</Note>
+</Alert>
 
 ### Upgrading from older SDK versions
 
@@ -60,11 +60,11 @@ The current profiling implementation stops the profiler automatically after 30 s
 
 To get started with continuous profiling, you can start and stop the profiler directly with `sentry_sdk.profiler.start_profiler` and `sentry_sdk.profiler.stop_profiler`.
 
-<Note>
+<Alert>
 
 If you previously set `profiles_sample_rate` or `profilers_sampler` to use transaction-based profiling, you must remove those lines of code from your configuration in order to use continuous profiling.
 
-</Note>
+</Alert>
 
 ```python
 import sentry_sdk
diff --git a/docs/platforms/python/tracing/instrumentation/custom-instrumentation/index.mdx b/docs/platforms/python/tracing/instrumentation/custom-instrumentation/index.mdx
index 2234647999b896..78b30c376ef702 100644
--- a/docs/platforms/python/tracing/instrumentation/custom-instrumentation/index.mdx
+++ b/docs/platforms/python/tracing/instrumentation/custom-instrumentation/index.mdx
@@ -9,7 +9,7 @@ The Sentry SDK for Python does a very good job of auto instrumenting your applic
 
 Adding transactions will allow you to instrument and capture certain regions of your code.
 
-<Alert level="info">
+<Alert>
 
 If you're using one of Sentry's SDK integrations, transactions will be created for you automatically.
 
@@ -56,7 +56,7 @@ def eat_pizza(pizza):
                 eat_slice(pizza.slices.pop())
 ```
 
-<Alert title="Changed in 2.15.0" level="info">
+<Alert title="Changed in 2.15.0">
 
 The parameter `name` in `start_span()` used to be called `description`. In version 2.15.0 `description` was deprecated and from 2.15.0 on, only `name` should be used. `description` will be removed in `3.0.0`.
 
@@ -77,7 +77,7 @@ def eat_pizza(pizza):
             eat_slice(pizza.slices.pop())
 ```
 
-<Alert title="Static & Class Methods" level="info">
+<Alert title="Static & Class Methods">
 
 When tracing a static or class method, you **must** add the `@sentry_sdk.trace` decorator **after** the `@staticmethod` or `@classmethod` decorator (i.e., **closer** to the function definition). Otherwise, your function will break!
 
@@ -99,7 +99,7 @@ def eat_pizza(pizza):
             span.finish()
 ```
 
-<Alert title="Changed in 2.15.0" level="info">
+<Alert title="Changed in 2.15.0">
 
 The parameter `name` in `start_span()` used to be called `description`. In version 2.15.0 `description` was deprecated and from 2.15.0 on, only `name` should be used. `description` will be removed in `3.0.0`.
 
@@ -125,7 +125,7 @@ def eat_slice(slice):
             chew()
 ```
 
-<Alert title="Changed in 2.15.0" level="info">
+<Alert title="Changed in 2.15.0">
 
 The parameter `name` in `start_span()` used to be called `description`. In version 2.15.0 `description` was deprecated and from 2.15.0 on, only `name` should be used. `description` will be removed in `3.0.0`.
 
@@ -163,7 +163,7 @@ def eat_slice(slice):
     parent_span.finish()
 ```
 
-<Alert title="Changed in 2.15.0" level="info">
+<Alert title="Changed in 2.15.0">
 
 The parameter `name` in `start_span()` used to be called `description`. In version 2.15.0 `description` was deprecated and from 2.15.0 on, only `name` should be used. `description` will be removed in `3.0.0`.
 
@@ -196,7 +196,7 @@ sentry_sdk.init(
 
 Now, whenever a function specified in `functions_to_trace` will be executed, a span will be created and attached as a child to the currently running span.
 
-<Alert title="Important" level="info">
+<Alert title="Important">
 
 To enable performance monitoring for the functions specified in `functions_to_trace`, the SDK needs to load the function modules. Be aware, there may be code being executed in modules during module loading. To avoid this, use the method described above to trace your functions.
 
diff --git a/docs/platforms/python/usage/index.mdx b/docs/platforms/python/usage/index.mdx
index 7a0738aa75b523..81fb1850156166 100644
--- a/docs/platforms/python/usage/index.mdx
+++ b/docs/platforms/python/usage/index.mdx
@@ -6,7 +6,7 @@ description: "Use the SDK to manually capture errors and other events."
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/react-native/configuration/options.mdx b/docs/platforms/react-native/configuration/options.mdx
index e79eda75be5901..a7857b16127e36 100644
--- a/docs/platforms/react-native/configuration/options.mdx
+++ b/docs/platforms/react-native/configuration/options.mdx
@@ -83,11 +83,11 @@ Grouping in Sentry is different for events with stack traces and without. As a r
 
 If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This option is turned off by default.
 
diff --git a/docs/platforms/react-native/configuration/releases.mdx b/docs/platforms/react-native/configuration/releases.mdx
index 755f3d838912e0..1466da72764cdc 100644
--- a/docs/platforms/react-native/configuration/releases.mdx
+++ b/docs/platforms/react-native/configuration/releases.mdx
@@ -31,11 +31,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -64,11 +64,11 @@ After configuring your SDK, you can install a repository integration or manually
 
 Monitor the [health of releases](/product/releases/health/) by observing user adoption, usage of the application, percentage of [crashes](/product/releases/health/#crash), and [session data](/product/releases/health/#session). Release health will provide insight into the impact of crashes and bugs as it relates to user experience, and reveal trends with each new issue through the [Release Details](/product/releases/release-details/) graphs and filters.
 
-<Note>
+<Alert>
 
 Crash reporting and app hang detection are not available for watchOS.
 
-</Note>
+</Alert>
 
 In order to monitor release health, the SDK sends session data.
 
diff --git a/docs/platforms/react-native/configuration/sampling.mdx b/docs/platforms/react-native/configuration/sampling.mdx
index bc66495c366656..e714c315cfb2b9 100644
--- a/docs/platforms/react-native/configuration/sampling.mdx
+++ b/docs/platforms/react-native/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
diff --git a/docs/platforms/react-native/configuration/touchevents.mdx b/docs/platforms/react-native/configuration/touchevents.mdx
index 1b28078c8ae834..76d2c8b9f4a0bb 100644
--- a/docs/platforms/react-native/configuration/touchevents.mdx
+++ b/docs/platforms/react-native/configuration/touchevents.mdx
@@ -64,11 +64,11 @@ const YourCoolComponent = (props) => {
 };
 ```
 
-<Note>
+<Alert>
 
 You don't have to worry about Typescript errors when passing the `sentry-label` prop. [Typescript will not throw an error on props with the '-' character](https://www.typescriptlang.org/docs/handbook/jsx.html#attribute-type-checking).
 
-</Note>
+</Alert>
 
 ## Options
 
diff --git a/docs/platforms/react-native/data-management/apple-privacy-manifest.mdx b/docs/platforms/react-native/data-management/apple-privacy-manifest.mdx
index 1d76196ae54831..f2746300b86fe6 100644
--- a/docs/platforms/react-native/data-management/apple-privacy-manifest.mdx
+++ b/docs/platforms/react-native/data-management/apple-privacy-manifest.mdx
@@ -4,15 +4,15 @@ description: "Troubleshoot and resolve common issues with the Apple Privacy Mani
 sidebar_order: 50
 ---
 
-<Note>
+<Alert>
 This guide requires [@sentry/react-native@5.22.1](https://github.com/getsentry/sentry-react-native/releases/tag/5.22.1) or newer.
-</Note>
+</Alert>
 
 Sentry's SDKs provide error and performance monitoring for mobile applications running on Apple devices. To do this, the SDK needs to access certain information about the device and the application. Some of the APIs required for this are considered privacy-relevant by Apple. In order to submit apps to the App Store, Apple requires all apps - and libraries used within these apps - to provide privacy manifest files stating which APIs are used under which allowed reasons. For more details, read Apple's guidelines on [Describing use of required reason API](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api).
 
-<Note>
+<Alert>
 The information and steps in this guide are still being worked on and might change because of new tools or updated [Apple requirements](https://developer.apple.com/documentation/bundleresources/privacy_manifest_files).
-</Note>
+</Alert>
 
 If you are using dynamically linked frameworks, Apple will automatically process the SDK's privacy manifest. If you are using statically linked libraries, which is the default for React Native applications, you need to provide the privacy manifest yourself. This guide will help you create the privacy manifest for your React Native and Expo applications.
 
diff --git a/docs/platforms/react-native/data-management/debug-files/file-formats/index.mdx b/docs/platforms/react-native/data-management/debug-files/file-formats/index.mdx
index dd5d74925a8b3a..36d5129dc617d3 100644
--- a/docs/platforms/react-native/data-management/debug-files/file-formats/index.mdx
+++ b/docs/platforms/react-native/data-management/debug-files/file-formats/index.mdx
@@ -180,11 +180,11 @@ while removing all debug information from the release binary.
 
 ## ProGuard Mappings
 
-<Note>
+<Alert>
 
 The recommended method for [Android users is to use the Gradle plugin](/platforms/android/configuration/gradle/).
 
-</Note>
+</Alert>
 
 ProGuard mapping files allow Sentry to resolve obfuscated Java classpaths and
 method names into their original form. In that sense, they act as debug
diff --git a/docs/platforms/react-native/data-management/debug-files/identifiers/index.mdx b/docs/platforms/react-native/data-management/debug-files/identifiers/index.mdx
index aebce9d77c7593..ea0293898bdd60 100644
--- a/docs/platforms/react-native/data-management/debug-files/identifiers/index.mdx
+++ b/docs/platforms/react-native/data-management/debug-files/identifiers/index.mdx
@@ -24,14 +24,14 @@ compute a _Debug Identifier_ for each uploaded file. This identifier is
 associated with executables and libraries as well as debug companions to ensure
 that they can be uniquely located via one common mechanism.
 
-<Note>
+<Alert>
 
 Debug information does not have to be associated with releases. The unique debug
 identifier ensures that Sentry can choose the right files for every crash
 report. However, it is still recommended to configure releases in the client to
 benefit from other features.
 
-</Note>
+</Alert>
 
 For native events, the issue details page displays a list of _Loaded Images_.
 This list contains the executable and all loaded dynamic libraries including
diff --git a/docs/platforms/react-native/data-management/debug-files/index.mdx b/docs/platforms/react-native/data-management/debug-files/index.mdx
index b5a401b9febf2e..76457d462212fa 100644
--- a/docs/platforms/react-native/data-management/debug-files/index.mdx
+++ b/docs/platforms/react-native/data-management/debug-files/index.mdx
@@ -24,12 +24,12 @@ the following formats:
 - [_ProGuard mappings_](./file-formats/#proguard-mappings) for
   Java and Android
 
-<Note>
+<Alert>
 
 Source maps, while also being debug information files, are handled
 differently in Sentry. For more information see [Source Maps in sentry-cli](/cli/releases/#sentry-cli-sourcemaps).
 
-</Note>
+</Alert>
 
 Sentry requires access to debug information files of your application as well as
 system libraries to provide fully symbolicated crash reports. You can either
@@ -46,11 +46,11 @@ for automatic downloads.
 From the [Project Details](/product/projects/project-details/) page, click into settings,
 then click on _Debug Files_ in the page navigation.
 
-<Note>
+<Alert>
 
 ProGuard files are listed separately, in the _ProGuard_ section of the project settings page.
 
-</Note>
+</Alert>
 
 ## Retention Policy
 
diff --git a/docs/platforms/react-native/data-management/sensitive-data/index.mdx b/docs/platforms/react-native/data-management/sensitive-data/index.mdx
index 8712656e07c427..10a33925792646 100644
--- a/docs/platforms/react-native/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/react-native/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 If you _do not_ wish to use the default PII behavior, you can also choose to identify users in a more controlled manner, using our [user identity context](../../enriching-events/identify-user/).
 
diff --git a/docs/platforms/react-native/enriching-events/attachments/index.mdx b/docs/platforms/react-native/enriching-events/attachments/index.mdx
index a59fd799af9699..920e4c5e42e4c2 100644
--- a/docs/platforms/react-native/enriching-events/attachments/index.mdx
+++ b/docs/platforms/react-native/enriching-events/attachments/index.mdx
@@ -13,11 +13,11 @@ You'll first need to import the SDK, as usual:
 
 <PlatformContent includePath="enriching-events/add-attachment" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/react-native/enriching-events/breadcrumbs/index.mdx b/docs/platforms/react-native/enriching-events/breadcrumbs/index.mdx
index 2c84f0ffac7dbe..b3a0d840fa1683 100644
--- a/docs/platforms/react-native/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/react-native/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/react-native/enriching-events/context/index.mdx b/docs/platforms/react-native/enriching-events/context/index.mdx
index 343d4620d0969d..c89cf5697bf256 100644
--- a/docs/platforms/react-native/enriching-events/context/index.mdx
+++ b/docs/platforms/react-native/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/react-native/enriching-events/tags/index.mdx b/docs/platforms/react-native/enriching-events/tags/index.mdx
index 9f70cfb7d967b3..0b5321e0ae8557 100644
--- a/docs/platforms/react-native/enriching-events/tags/index.mdx
+++ b/docs/platforms/react-native/enriching-events/tags/index.mdx
@@ -21,11 +21,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/react-native/enriching-events/viewhierarchy/index.mdx b/docs/platforms/react-native/enriching-events/viewhierarchy/index.mdx
index 82b43f8aaa0e95..68dfa8645fe22b 100644
--- a/docs/platforms/react-native/enriching-events/viewhierarchy/index.mdx
+++ b/docs/platforms/react-native/enriching-events/viewhierarchy/index.mdx
@@ -7,11 +7,11 @@ Sentry makes it possible to render a JSON representation of the view hierarchy o
 
 This feature only applies to SDKs with a user interface, such as the ones for mobile and desktop applications. In some environments like native iOS, rendering the view hierarchy requires the UI thread and in the event of a crash, that might not be available. Another example where the view hierarchy might not be available is when the event happens before the screen starts to load. So inherently, this feature is a best effort solution.
 
-<Note>
+<Alert>
 
 Deobfuscation for view hierarchies is fully supported for native SDKs, and React Native, but is currently not supported for Flutter.
 
-</Note>
+</Alert>
 
 ## Enabling View Hierarchy Attachments
 
diff --git a/docs/platforms/react-native/index.mdx b/docs/platforms/react-native/index.mdx
index c31ec231b22662..116c3cbb565417 100644
--- a/docs/platforms/react-native/index.mdx
+++ b/docs/platforms/react-native/index.mdx
@@ -11,11 +11,11 @@ categories:
 
 Read on to find out how to set up Sentry's React Native SDK which will automatically report errors and exceptions in your application. If you prefer to follow video instructions, see [How to Install the Sentry React Native SDK in 60 Seconds](https://vimeo.com/899369012).
 
-<Note>
+<Alert>
 
 If you don't already have an account and Sentry project established, head over to [sentry.io](https://sentry.io/signup/), then return to this page.
 
-</Note>
+</Alert>
 
 ## Features
 
diff --git a/docs/platforms/react-native/manual-setup/hermes.mdx b/docs/platforms/react-native/manual-setup/hermes.mdx
index 419c5763e6a8b4..ce4a755733dde9 100644
--- a/docs/platforms/react-native/manual-setup/hermes.mdx
+++ b/docs/platforms/react-native/manual-setup/hermes.mdx
@@ -22,17 +22,17 @@ If you use `EXTRA_PACKAGER_ARGS`, you only need the packager source map. This is
 
 Our React Native [Source Maps](/platforms/react-native/sourcemaps/) documentation is based on [`react-native-xcode.sh`](https://github.com/facebook/react-native/blob/0.71-stable/scripts/react-native-xcode.sh) for iOS and on [`BundleHermesCTask.kt`](https://github.com/facebook/react-native/blob/0.71-stable/packages/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/tasks/BundleHermesCTask.kt) for Android. If you are having issues with the manually generated artifacts check the steps of your React Native tooling using the previous links.
 
-<Note>
+<Alert>
 
 React Native [`0.70`](https://github.com/facebook/react-native/blob/e3a5fbe72f966b27b967192317d7072db52d1c8c/scripts/react-native-xcode.sh#L141) and CodePush Update minifies the packager bundle by default.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 [`BundleHermesCTask.kt`](https://github.com/facebook/react-native/blob/0.71-stable/packages/react-native-gradle-plugin/src/main/kotlin/com/facebook/react/tasks/BundleHermesCTask.kt) is only available from version `0.71` on. For previous versions, use [`react.gradle`](https://github.com/facebook/react-native/blob/0.70-stable/react.gradle).
 
-</Note>
+</Alert>
 
 For more details see [this issue](https://github.com/facebook/react-native/issues/34043) in the React Native repository.
 
diff --git a/docs/platforms/react-native/manual-setup/native-init.mdx b/docs/platforms/react-native/manual-setup/native-init.mdx
index f2ae5781bbd97d..62055b5dd1bbfd 100644
--- a/docs/platforms/react-native/manual-setup/native-init.mdx
+++ b/docs/platforms/react-native/manual-setup/native-init.mdx
@@ -33,11 +33,11 @@ you have to [configure the sample rate](/platforms/apple/tracing/#configure-the-
 
 ## Android Configuration
 
-<Note>
+<Alert>
 
 Initializing with this method uses a Content Provider. Because the Javascript engine for React Native is also initialized using a Content Provider, we cannot guarantee that Sentry will always initialize before the JavaScript engine.
 
-</Note>
+</Alert>
 
 To use auto-init, add the following to your `AndroidManifest.xml`:
 
diff --git a/docs/platforms/react-native/manual-setup/ram-bundles.mdx b/docs/platforms/react-native/manual-setup/ram-bundles.mdx
index 60dbab52022820..6a351884d97d44 100644
--- a/docs/platforms/react-native/manual-setup/ram-bundles.mdx
+++ b/docs/platforms/react-native/manual-setup/ram-bundles.mdx
@@ -10,11 +10,11 @@ All the existing RAM bundle formats are explained in detail in the [Metro Bundle
 
 ## Enabling RAM Bundles
 
-<Note>
+<Alert>
 
 If you are using [Hermes](/platforms/react-native/manual-setup/hermes/), you should not have the RAM bundles feature enabled. In Hermes, when loading the bytecode, `mmap` ensures that the entire file is not loaded. Using Hermes with RAM bundles might lead to issues, because those mechanisms are not compatible with each other.
 
-</Note>
+</Alert>
 
 To enable RAM bundles for your app, please consult with the [official React Native documentation](https://reactnative.dev/docs/ram-bundles-inline-requires#enable-the-ram-format).
 
diff --git a/docs/platforms/react-native/migration/before-v5.mdx b/docs/platforms/react-native/migration/before-v5.mdx
index 86a3d81f29a593..ac49a5f3396505 100644
--- a/docs/platforms/react-native/migration/before-v5.mdx
+++ b/docs/platforms/react-native/migration/before-v5.mdx
@@ -241,11 +241,11 @@ This version of the SDK uses the [envelope endpoint](https://develop.sentry.dev/
 
 While the migration doesn't introduce breaking changes for iOS/MacOS on the React Native side, we recommend running `pod install` after the upgrade.
 
-<Note>
+<Alert>
 
 If you're using our Cocoa SDK directly, follow the [migration guide for 5.x to 6.x](/platforms/apple/migration/#migrating-from-5x-to-6x).
 
-</Note>
+</Alert>
 
 On iOS/MacOS, we now cache events in envelopes on the disk. As a result, you might lose a few cached events during the migration. Due to the high level of effort involved, the migration from 5.x to 6.x won't move these few cached events into envelopes.
 
@@ -275,13 +275,13 @@ import io.sentry.react.RNSentryPackage
 
 Other than the one line change noted above, the migration shouldn't cause breaking changes on the React Native side.
 
-<Note>
+<Alert>
 <markdown>
 
 If you use our Android SDK directly, you should follow its [migration guide for 2.x to 3.x](/platforms/android/migration/#migrating-from-iosentrysentry-android-2x-to-iosentrysentry-android-3x).
 
 </markdown>
-</Note>
+</Alert>
 
 ## From 0.x to 1.x
 
diff --git a/docs/platforms/react-native/profiling/index.mdx b/docs/platforms/react-native/profiling/index.mdx
index b1c73ac0d207ba..aefe21aca7acf7 100644
--- a/docs/platforms/react-native/profiling/index.mdx
+++ b/docs/platforms/react-native/profiling/index.mdx
@@ -25,11 +25,11 @@ Check out the <PlatformLink to="/tracing/">tracing setup documentation</Platform
 
 ## Enable Profiling
 
-<Note>
+<Alert>
 
 Profiling for React Native is available in SDK versions `5.32.0` and above.
 
-</Note>
+</Alert>
 
 To enable profiling, set the `profilesSampleRate`:
 
diff --git a/docs/platforms/react-native/session-replay/index.mdx b/docs/platforms/react-native/session-replay/index.mdx
index 172e5220ea9feb..785cbf67449ef9 100644
--- a/docs/platforms/react-native/session-replay/index.mdx
+++ b/docs/platforms/react-native/session-replay/index.mdx
@@ -68,11 +68,11 @@ Sampling begins as soon as a session starts. <PlatformIdentifier name="replays-s
 The SDK is recording and aggressively masking all text, images, and webviews by default. If your app has any sensitive data, you should only turn the default masking off after explicitly masking out any sensitive data, using the APIs described below.
 However, if you're working on a mobile app that doesn't contain any PII or private data, you can opt out of the default text and image-masking settings. To learn more about Session Replay privacy, [read our docs](/platforms/react-native/session-replay/privacy/).
 
-<Note>
+<Alert>
 
 If you encounter any data not being redacted with the default settings, please let us know through a [GitHub issue](https://github.com/getsentry/sentry-react-native/issues/new?assignees=&labels=Platform%3A+React-Native%2CType%3A+%F0%9F%AA%B2+Bug&projects=&template=BUG_REPORT.md).
 
-</Note>
+</Alert>
 
 To disable redaction altogether (not to be used on applications with sensitive data):
 
diff --git a/docs/platforms/react-native/session-replay/performance-overhead.mdx b/docs/platforms/react-native/session-replay/performance-overhead.mdx
index 921aeb36a4e896..7d9c1aa5b70c93 100644
--- a/docs/platforms/react-native/session-replay/performance-overhead.mdx
+++ b/docs/platforms/react-native/session-replay/performance-overhead.mdx
@@ -30,7 +30,7 @@ The benchmarks were run on an iPhone 14 Pro and a Pixel 2XL. Note that active Se
 | CPU                              | 4%              | 13%                 |
 | App Startup Time (Cold)          | 1264.80 ms      | 1265 ms             |
 | Main Thread Time                 | n/a             | 43ms                |
-| Network Bandwidth                | n/a             | 50 KB               |
+| Network Bandwidth                | n/a             | 10 KB/s of recording|
 
 
 
@@ -43,4 +43,4 @@ The benchmarks were run on an iPhone 14 Pro and a Pixel 2XL. Note that active Se
 | CPU                              | 36%             | 42%                 |
 | App Startup Time (Cold)          | 1533.35 ms      | 1539.55 ms          |
 | Main Thread Time                 | n/a             | 20ms                |
-| Network Bandwidth                | n/a             | 35 KB               |
+| Network Bandwidth                | n/a             | 7 KB/s of recording |
diff --git a/docs/platforms/react-native/sourcemaps/index.mdx b/docs/platforms/react-native/sourcemaps/index.mdx
index 646f0c5e196877..c92750929fd18f 100644
--- a/docs/platforms/react-native/sourcemaps/index.mdx
+++ b/docs/platforms/react-native/sourcemaps/index.mdx
@@ -4,13 +4,13 @@ description: "Learn more about how to upload your source maps to Sentry."
 sidebar_order: 95
 ---
 
-<Note>
+<Alert>
 
 This guide assumes you are using a Sentry React Native SDK on version `5.11.0` or higher.
 
 If you are on an older version and you want to upload source maps we recommend upgrading your SDK to the newest version.
 
-</Note>
+</Alert>
 
 To get unminified stack traces for JavaScript code, source maps must be generated and uploaded. The React Native SDK handles source maps _automatically_ for iOS with Xcode and Android with Gradle, if you do not use custom values.
 
@@ -53,4 +53,4 @@ sentry {
 
 ### Debug Builds
 
-Symbolication is handled directly by the Metro development server, automatically providing the symbolication needed to translate stack traces into readable source code in a development environment. There's no need to upload source maps for these types of builds which is why the automatic uploading of source maps is disabled. 
\ No newline at end of file
+Symbolication is handled directly by the Metro development server, automatically providing the symbolication needed to translate stack traces into readable source code in a development environment. There's no need to upload source maps for these types of builds which is why the automatic uploading of source maps is disabled.
diff --git a/docs/platforms/react-native/sourcemaps/troubleshooting/legacy-uploading-methods.mdx b/docs/platforms/react-native/sourcemaps/troubleshooting/legacy-uploading-methods.mdx
index 22a2d5a5cfbebb..8323dbc1d39a82 100644
--- a/docs/platforms/react-native/sourcemaps/troubleshooting/legacy-uploading-methods.mdx
+++ b/docs/platforms/react-native/sourcemaps/troubleshooting/legacy-uploading-methods.mdx
@@ -54,11 +54,11 @@ Pass your entry file to `--entry-file` for Android or iOS, respectively. By defa
 
 These files will output your bundle and source maps. By default, these files are named `index.android.bundle` and `index.android.bundle.map` for Android and `main.jsbundle` and `main.jsbundle.map` for iOS.
 
-<Note>
+<Alert>
 
 The source map's name must be the bundle's name appended with `.map` for source maps to correctly be detected.
 
-</Note>
+</Alert>
 
 ### 3. Upload the bundle and source maps
 
diff --git a/docs/platforms/react-native/sourcemaps/uploading/hermes.mdx b/docs/platforms/react-native/sourcemaps/uploading/hermes.mdx
index b33044c5ded5e1..a026f8497dd3e5 100644
--- a/docs/platforms/react-native/sourcemaps/uploading/hermes.mdx
+++ b/docs/platforms/react-native/sourcemaps/uploading/hermes.mdx
@@ -155,10 +155,10 @@ node_modules/@sentry/cli/bin/sentry-cli sourcemaps upload \
   main.jsbundle main.jsbundle.map
 ```
 
-<Note>
+<Alert>
 
 When uploaded, the `bundle` file will have a size of 0 bytes. This is expected with Hermes bytecode and won't affect the source maps resolution.
 
-</Note>
+</Alert>
 
 For more Hermes guides, see the [Hermes Throubleshooting](/platforms/react-native/manual-setup/hermes/#throubleshooting) docs section.
diff --git a/docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx
index 04ae6d0ac654f6..fd04bec5414ae4 100644
--- a/docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx
@@ -20,11 +20,11 @@ export default Sentry.wrap(App);
 
 ### Enable Routing Instrumentation
 
-<Note>
+<Alert>
 
 When no routing instrumentation is used, a transaction for `App Start` is automatically captured. However, that transaction stops being sent when one of the routing integrations below is added. Instead, the `App Start` information is included as a span in a transaction captured by the routing instrumentation.
 
-</Note>
+</Alert>
 
 We currently provide three routing instrumentations out of the box to instrument route changes for:
 
@@ -45,11 +45,11 @@ Sentry offers the following automatic instrumentation features.
 
 The App Start Instrumentation provides insight into how long your application takes to launch. It tracks the length of time from the **earliest native process initialization** until the **React Native root component mounts**.
 
-<Note>
+<Alert>
 
 If you don't [wrap your root component with Sentry](#wrap-your-root-component), the App Start measurement will finish when the JavaScript code is initialized instead of when the first component mount.
 
-</Note>
+</Alert>
 
 The SDK differentiates between a cold and a warm start, but doesn't track hot starts or resumes. The measurements are available under `measurements.app_start_warm` and `measurements.app_start_cold`.
 
@@ -61,11 +61,11 @@ Unresponsive UI and animation hitches annoy users and degrade the user experienc
 
 Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/insights/mobile-vitals).
 
-<Note>
+<Alert>
 
 React Native mobile apps will not report [Web Vitals](/product/insights/web-vitals/). These values depend on APIs provided by browsers, and are not available in this context.
 
-</Note>
+</Alert>
 
 #### AndroidX Support
 
diff --git a/docs/platforms/react-native/tracing/instrumentation/custom-instrumentation.mdx b/docs/platforms/react-native/tracing/instrumentation/custom-instrumentation.mdx
index 9ccca08a22c6a1..1ce2338e337017 100644
--- a/docs/platforms/react-native/tracing/instrumentation/custom-instrumentation.mdx
+++ b/docs/platforms/react-native/tracing/instrumentation/custom-instrumentation.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 To add custom performance data to your application, you need to add custom instrumentation in the form of spans. Spans are a way to measure the time it takes for a specific action to occur. For example, you can create a span to measure the time it takes for a function to execute.
 
diff --git a/docs/platforms/react-native/tracing/instrumentation/user-interaction-instrumentation.mdx b/docs/platforms/react-native/tracing/instrumentation/user-interaction-instrumentation.mdx
index fc8f890964841c..ce25ec17678843 100644
--- a/docs/platforms/react-native/tracing/instrumentation/user-interaction-instrumentation.mdx
+++ b/docs/platforms/react-native/tracing/instrumentation/user-interaction-instrumentation.mdx
@@ -12,11 +12,11 @@ The UI instrumentation captures transactions and adds breadcrumbs for touch inte
 
 Transaction names are composed from a combination of displayed screen names, (for example, `LoginScreen`), and the labels of the element users interacted with, (for example, `login_button`).
 
-<Note>
+<Alert>
   To capture UI transactions, you have to first set up {<Link to="/platforms/react-native/tracing/instrumentation/automatic-instrumentation/#enable-routing-instrumentation">
     routing instrumentation
   </Link>}.
-</Note>
+</Alert>
 
 UI instrumentation tracing is disabled by default, but you can enable it by setting the `enableUserInteractionTracing` options to `true` and wrapping your root component:
 
@@ -45,10 +45,10 @@ export default Sentry.wrap(App, {
 });
 ```
 
-<Note>
+<Alert>
   If the UI transaction idled, but didn't have any child spans, it'll be
   dropped.
-</Note>
+</Alert>
 
 Because transactions are automatically bound to scope, you can create child spans using [custom instrumentation](/platforms/react-native/tracing/instrumentation/custom-instrumentation/#retrieve-a-transaction). Note, that the `idleTimeoout` for running UI transactions defaults to `1000` milliseconds (one second).
 
@@ -56,9 +56,9 @@ Because transactions are automatically bound to scope, you can create child span
 
 To create UI transactions from React Native Gesture Handler, you need to wrap individual gestures using `sentryTraceGesture`. This will also automatically create breadcrumbs. The wrapper `sentryTraceGesture(label, gesture)` accepts `string` labels that uniquely identify the gesture in a screen as well as the gesture object being wrapped.
 
-<Note>
+<Alert>
   Only [RNGH API v2](https://docs.swmansion.com/react-native-gesture-handler/docs/gestures/gesture/) is supported.
-</Note>
+</Alert>
 
 ```javascript {10-11}
 import React from "react";
diff --git a/docs/platforms/react-native/troubleshooting/index.mdx b/docs/platforms/react-native/troubleshooting/index.mdx
index 10d0e70cdc4740..4675e56f16e97e 100644
--- a/docs/platforms/react-native/troubleshooting/index.mdx
+++ b/docs/platforms/react-native/troubleshooting/index.mdx
@@ -79,11 +79,11 @@ You don't need to perform the steps below if you don't disable [auto patching](#
 }
 ```
 
-<Note>
+<Alert>
 
 Package resolutions are currently only supporred by `yarn`. If you use `npm`, you can use a third-party package called [npm-force-resolutions](https://www.npmjs.com/package/npm-force-resolutions) to achieve this.
 
-</Note>
+</Alert>
 
 3. If the fix is successful, our SDK will no longer display the above warning and will indicate that promise rejections will be caught.
 
@@ -148,11 +148,11 @@ module.exports = {
 };
 ```
 
-<Note>
+<Alert>
 
 This setting applies to **all** class and function names — not just React components — and could increase your JS bundle size.
 
-</Note>
+</Alert>
 
 ## Missing Context on Android NDK Events
 
diff --git a/docs/platforms/react-native/usage/index.mdx b/docs/platforms/react-native/usage/index.mdx
index 91c3aead08e03d..9ac2b8c9c6b0bf 100644
--- a/docs/platforms/react-native/usage/index.mdx
+++ b/docs/platforms/react-native/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/ruby/common/configuration/options.mdx b/docs/platforms/ruby/common/configuration/options.mdx
index 46eb773c5b6537..3040e64d09127e 100644
--- a/docs/platforms/ruby/common/configuration/options.mdx
+++ b/docs/platforms/ruby/common/configuration/options.mdx
@@ -72,9 +72,9 @@ This lets you attach diagnostic client reports about dropped events to an existi
 ```ruby
 config.send_client_reports = false
 
-<Note>
+<Alert>
 This information isn't currently visible to users, but we're planning on adding it to the user-facing UI in the near future.
-</Note>
+</Alert>
 ```
 
 </ConfigKey>
diff --git a/docs/platforms/ruby/common/configuration/releases.mdx b/docs/platforms/ruby/common/configuration/releases.mdx
index 0d6bf7aa1a5309..2c4b50d83a5e5d 100644
--- a/docs/platforms/ruby/common/configuration/releases.mdx
+++ b/docs/platforms/ruby/common/configuration/releases.mdx
@@ -29,11 +29,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -62,11 +62,11 @@ After configuring your SDK, you can install a repository integration or manually
 
 Monitor the [health of releases](/product/releases/health/) by observing user adoption, usage of the application, percentage of [crashes](/product/releases/health/#crash), and [session data](/product/releases/health/#session). Release health will provide insight into the impact of crashes and bugs as it relates to user experience, and reveal trends with each new issue through the [Release Details](/product/releases/release-details/) graphs and filters.
 
-<Note>
+<Alert>
 
 Crash reporting and app hang detection are not available for watchOS.
 
-</Note>
+</Alert>
 
 In order to monitor release health, the SDK sends session data.
 
diff --git a/docs/platforms/ruby/common/configuration/sampling.mdx b/docs/platforms/ruby/common/configuration/sampling.mdx
index bc66495c366656..e714c315cfb2b9 100644
--- a/docs/platforms/ruby/common/configuration/sampling.mdx
+++ b/docs/platforms/ruby/common/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
diff --git a/docs/platforms/ruby/common/data-management/sensitive-data/index.mdx b/docs/platforms/ruby/common/data-management/sensitive-data/index.mdx
index 7e74b3275d5d69..5aadb9a9156656 100644
--- a/docs/platforms/ruby/common/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/ruby/common/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 If you _do not_ wish to use the default PII behavior, you can also choose to identify users in a more controlled manner, using our [user identity context](../../enriching-events/identify-user/).
 
diff --git a/docs/platforms/ruby/common/enriching-events/attachments/index.mdx b/docs/platforms/ruby/common/enriching-events/attachments/index.mdx
index 16aaade9389701..fd5e2b060238ff 100644
--- a/docs/platforms/ruby/common/enriching-events/attachments/index.mdx
+++ b/docs/platforms/ruby/common/enriching-events/attachments/index.mdx
@@ -9,11 +9,11 @@ Sentry can enrich your events for further investigation by storing additional fi
 
 <PlatformContent includePath="enriching-events/add-attachment" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
diff --git a/docs/platforms/ruby/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/ruby/common/enriching-events/breadcrumbs/index.mdx
index 77705a3b49b90c..0770caef65c398 100644
--- a/docs/platforms/ruby/common/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/ruby/common/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/ruby/common/enriching-events/context/index.mdx b/docs/platforms/ruby/common/enriching-events/context/index.mdx
index dd07e216bbb9f9..36da3d54f75935 100644
--- a/docs/platforms/ruby/common/enriching-events/context/index.mdx
+++ b/docs/platforms/ruby/common/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/ruby/common/enriching-events/tags/index.mdx b/docs/platforms/ruby/common/enriching-events/tags/index.mdx
index 5707e7b98110ca..9657816853afb2 100644
--- a/docs/platforms/ruby/common/enriching-events/tags/index.mdx
+++ b/docs/platforms/ruby/common/enriching-events/tags/index.mdx
@@ -17,11 +17,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/ruby/common/index.mdx b/docs/platforms/ruby/common/index.mdx
index ab91edea53f63f..ab5826dfd44569 100644
--- a/docs/platforms/ruby/common/index.mdx
+++ b/docs/platforms/ruby/common/index.mdx
@@ -31,10 +31,10 @@ This snippet includes an intentional error, so you can test that everything is w
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
diff --git a/docs/platforms/ruby/common/metrics/index.mdx b/docs/platforms/ruby/common/metrics/index.mdx
index 339e7a4a531095..79ca6952fb690a 100644
--- a/docs/platforms/ruby/common/metrics/index.mdx
+++ b/docs/platforms/ruby/common/metrics/index.mdx
@@ -7,11 +7,11 @@ sidebar_hidden: true
 
 <Include name="metrics-api-change.mdx" />
 
-<Note>
+<Alert>
 
 Metrics for Ruby are supported with Sentry Ruby SDK version `5.17.0` and above.
 
-</Note>
+</Alert>
 
 Sentry metrics help you pinpoint and solve issues that impact user experience and app performance by measuring the data points that are important to you. You can track things like processing time, event size, user signups, and conversion rates, then correlate them back to tracing data in order to get deeper insights and solve issues faster.
 
diff --git a/docs/platforms/ruby/common/migration.mdx b/docs/platforms/ruby/common/migration.mdx
index 0208d647b5488c..071d6b5d662b71 100644
--- a/docs/platforms/ruby/common/migration.mdx
+++ b/docs/platforms/ruby/common/migration.mdx
@@ -25,11 +25,11 @@ description: "Learn about how to migrate from the deprecated sentry-raven SDK."
 
 ## Major Changes
 
-<Note>
+<Alert>
 
 Ruby 2.3 and Rails 4 are no longer supported.
 
-</Note>
+</Alert>
 
 #### Integrations Were Extracted
 
diff --git a/docs/platforms/ruby/common/profiling/index.mdx b/docs/platforms/ruby/common/profiling/index.mdx
index 6c912a13c5f18d..998e37c41cb21f 100644
--- a/docs/platforms/ruby/common/profiling/index.mdx
+++ b/docs/platforms/ruby/common/profiling/index.mdx
@@ -9,11 +9,11 @@ sidebar_order: 5000
 
 ## Enable Profiling using StackProf
 
-<Note>
+<Alert>
 
 StackProf profiling beta is available starting in SDK version `5.9.0`.
 
-</Note>
+</Alert>
 
 We use the [`stackprof` gem](https://github.com/tmm1/stackprof) to collect profiles for Ruby.
 
@@ -39,27 +39,27 @@ Sentry.init do |config|
 end
 ```
 
-<Note>
+<Alert>
 
 The <PlatformIdentifier name="profiles_sample_rate" /> setting is _relative_ to the <PlatformIdentifier name="traces_sample_rate" /> setting.
 
 For Profiling to work, you have to first enable Sentry’s tracing via `traces_sample_rate` (like in the example above). Read our <PlatformLink to="/tracing/">tracing setup documentation</PlatformLink> to learn how to configure sampling. If you set your sample rate to 1.0, all transactions will be captured.
 
-</Note>
+</Alert>
 
 ## Enable Profiling using Vernier
 
-<Note>
+<Alert>
 
 Vernier profiling beta is available starting in SDK version `5.21.0`.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 Vernier requires Ruby 3.2.1+
 
-</Note>
+</Alert>
 
 You can have much better profiles if you're using multi-threaded servers like Puma now by leveraging Vernier.
 
diff --git a/docs/platforms/ruby/common/tracing/index.mdx b/docs/platforms/ruby/common/tracing/index.mdx
index 44ec42f6895b26..5e4cfdd0613c8d 100644
--- a/docs/platforms/ruby/common/tracing/index.mdx
+++ b/docs/platforms/ruby/common/tracing/index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 4000
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 <Include name="opentelemetry-available.mdx" />
 
diff --git a/docs/platforms/ruby/common/tracing/instrumentation/custom-instrumentation/index.mdx b/docs/platforms/ruby/common/tracing/instrumentation/custom-instrumentation/index.mdx
index 6f7441bf6becae..0d5c2d898d9968 100644
--- a/docs/platforms/ruby/common/tracing/instrumentation/custom-instrumentation/index.mdx
+++ b/docs/platforms/ruby/common/tracing/instrumentation/custom-instrumentation/index.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
diff --git a/docs/platforms/ruby/common/usage/index.mdx b/docs/platforms/ruby/common/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/ruby/common/usage/index.mdx
+++ b/docs/platforms/ruby/common/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/rust/common/configuration/options.mdx b/docs/platforms/rust/common/configuration/options.mdx
index f613ac76a7c4fe..ae6f2f4af87e99 100644
--- a/docs/platforms/rust/common/configuration/options.mdx
+++ b/docs/platforms/rust/common/configuration/options.mdx
@@ -71,11 +71,11 @@ Grouping in Sentry is different for events with stack traces and without. As a r
 
 If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This option is turned off by default.
 
diff --git a/docs/platforms/rust/common/configuration/releases.mdx b/docs/platforms/rust/common/configuration/releases.mdx
index 31f467ea6c5e5e..0a88c565271cd7 100644
--- a/docs/platforms/rust/common/configuration/releases.mdx
+++ b/docs/platforms/rust/common/configuration/releases.mdx
@@ -29,11 +29,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -62,11 +62,11 @@ After configuring your SDK, you can install a repository integration or manually
 
 Monitor the [health of releases](/product/releases/health/) by observing user adoption, usage of the application, percentage of [crashes](/product/releases/health/#crash), and [session data](/product/releases/health/#session). Release health will provide insight into the impact of crashes and bugs as it relates to user experience, and reveal trends with each new issue through the [Release Details](/product/releases/release-details/) graphs and filters.
 
-<Note>
+<Alert>
 
 Crash reporting and app hang detection are not available for watchOS.
 
-</Note>
+</Alert>
 
 In order to monitor release health, the SDK sends session data.
 
diff --git a/docs/platforms/rust/common/configuration/sampling.mdx b/docs/platforms/rust/common/configuration/sampling.mdx
index 79fb56a04d8066..5e61d677fbdf18 100644
--- a/docs/platforms/rust/common/configuration/sampling.mdx
+++ b/docs/platforms/rust/common/configuration/sampling.mdx
@@ -15,11 +15,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
@@ -47,7 +47,7 @@ The Sentry SDKs have two configuration options to control the volume of transact
 
 By default, none of these options are set, meaning no transactions will be sent to Sentry. You must set either one of the options to start sending transactions.
 
-<Alert level="info">
+<Alert>
 
 Sampling functions (<PlatformIdentifier name="traces-sampler" />) are currently not supported by this platform.
 
@@ -90,7 +90,7 @@ When there's the potential for more than one of these to come into play, the fol
 1. If <PlatformIdentifier name="traces-sampler" /> is not defined, but there's a parent sampling decision, the parent sampling decision will be used.
 1. If <PlatformIdentifier name="traces-sampler" /> is not defined and there's no parent sampling decision, <PlatformIdentifier name="traces-sample-rate" /> will be used.
 
-<Alert level="info">
+<Alert>
 
 Forcing a sampling decision by passing it into <PlatformIdentifier name="start-transaction" /> is currently not supported by this platform.
 
diff --git a/docs/platforms/rust/common/data-management/sensitive-data/index.mdx b/docs/platforms/rust/common/data-management/sensitive-data/index.mdx
index cf4de7c59a1190..f06150b89cbdd9 100644
--- a/docs/platforms/rust/common/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/rust/common/data-management/sensitive-data/index.mdx
@@ -23,13 +23,13 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 ## Personally Identifiable Information (PII)
 
diff --git a/docs/platforms/rust/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/rust/common/enriching-events/breadcrumbs/index.mdx
index 04082cdb3efd9c..d61b0079f3b2d3 100644
--- a/docs/platforms/rust/common/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/rust/common/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/rust/common/enriching-events/context/index.mdx b/docs/platforms/rust/common/enriching-events/context/index.mdx
index dd07e216bbb9f9..36da3d54f75935 100644
--- a/docs/platforms/rust/common/enriching-events/context/index.mdx
+++ b/docs/platforms/rust/common/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
diff --git a/docs/platforms/rust/common/enriching-events/tags/index.mdx b/docs/platforms/rust/common/enriching-events/tags/index.mdx
index 5707e7b98110ca..9657816853afb2 100644
--- a/docs/platforms/rust/common/enriching-events/tags/index.mdx
+++ b/docs/platforms/rust/common/enriching-events/tags/index.mdx
@@ -17,11 +17,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/rust/common/tracing/index.mdx b/docs/platforms/rust/common/tracing/index.mdx
index fc39d3d5b76b10..909a0e747c22a2 100644
--- a/docs/platforms/rust/common/tracing/index.mdx
+++ b/docs/platforms/rust/common/tracing/index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 4000
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 ## Configure
 
diff --git a/docs/platforms/rust/common/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/rust/common/tracing/instrumentation/automatic-instrumentation.mdx
index d600350068bf01..b337e6b2b49986 100644
--- a/docs/platforms/rust/common/tracing/instrumentation/automatic-instrumentation.mdx
+++ b/docs/platforms/rust/common/tracing/instrumentation/automatic-instrumentation.mdx
@@ -6,11 +6,11 @@ supported:
 description: "Learn what instrumentation automatically captures transactions."
 ---
 
-<Note>
+<Alert>
 
 Capturing transactions requires that you first <PlatformLink to="/tracing/">set up tracing</PlatformLink> if you haven't already.
 
-</Note>
+</Alert>
 
 ## `tracing` Integration
 
diff --git a/docs/platforms/rust/common/tracing/instrumentation/custom-instrumentation.mdx b/docs/platforms/rust/common/tracing/instrumentation/custom-instrumentation.mdx
index 2b3e549ec7ac16..50f48be8f767f9 100644
--- a/docs/platforms/rust/common/tracing/instrumentation/custom-instrumentation.mdx
+++ b/docs/platforms/rust/common/tracing/instrumentation/custom-instrumentation.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
diff --git a/docs/platforms/rust/common/usage/index.mdx b/docs/platforms/rust/common/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/rust/common/usage/index.mdx
+++ b/docs/platforms/rust/common/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/rust/index.mdx b/docs/platforms/rust/index.mdx
index 2445dd742861d2..619f00a0960b7f 100644
--- a/docs/platforms/rust/index.mdx
+++ b/docs/platforms/rust/index.mdx
@@ -7,11 +7,11 @@ supportLevel: production
 
 On this page, we get you up and running with Sentry's Rust SDK.
 
-<Note>
+<Alert>
 
 If you don't already have an account and Sentry project established, head over to [sentry.io](https://sentry.io/signup/), then return to this page.
 
-</Note>
+</Alert>
 
 Using a framework? Check out the other SDKs we support in the left-hand dropdown.
 
@@ -104,7 +104,7 @@ and libraries.
 A list of integrations and their feature flags can be found
 [in the integration API docs](https://docs.rs/sentry/0/sentry/integrations/index.html).
 
-<Note>
+<Alert>
 
 If you keep debug information files in the produced binary, rather than strip them down or split them,
 do not add the `debug_images` integration and the corresponding `debug-images` feature flag,
@@ -112,7 +112,7 @@ as it will collide with the built-in debug file processing.
 
 Conflicts could lead to UI warning messages in Sentry, as it can be interpreted as a problem with debug files and processing your error. See this [comment](https://github.com/getsentry/sentry-rust/issues/574#issuecomment-1534316787) and connected issue for more information.
 
-</Note>
+</Alert>
 
 ## More Information
 
diff --git a/docs/platforms/unity/configuration/options.mdx b/docs/platforms/unity/configuration/options.mdx
index 375c93d51e3374..8efed021d143b2 100644
--- a/docs/platforms/unity/configuration/options.mdx
+++ b/docs/platforms/unity/configuration/options.mdx
@@ -31,11 +31,11 @@ Learn more about [DSN utilization](/product/sentry-basics/dsn-explainer/#dsn-uti
 Before version 3.0.0 of the Sentry SDK for .NET, there was no special treatment for the stack trace. Sentry reported what .NET made available at runtime.
 This behavior now called `StackTraceMode.Original`. With the introduction of 3.0, a new default mode is `Enhanced`.
 
-<Note>
+<Alert>
 
 Changing this value will affect issue grouping. Since the frame significantly changes shape.
 
-</Note>
+</Alert>
 
 </ConfigKey>
 
@@ -141,11 +141,11 @@ Grouping in Sentry is different for events with stack traces and without. As a r
 
 If this flag is enabled, certain personally identifiable information (PII) is added by active integrations. By default, no such data is sent.
 
-<Note>
+<Alert>
 
 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>
+</Alert>
 
 This option is turned off by default.
 
diff --git a/docs/platforms/unity/configuration/releases.mdx b/docs/platforms/unity/configuration/releases.mdx
index d36327936dd7e0..f0399acdceb36d 100644
--- a/docs/platforms/unity/configuration/releases.mdx
+++ b/docs/platforms/unity/configuration/releases.mdx
@@ -4,11 +4,11 @@ sidebar_order: 40
 description: "Learn how to configure your SDK to tell Sentry about your releases."
 ---
 
-<Note>
+<Alert>
 
 The Crash Free Session Rate requires [native support](/platforms/unity/native-support/). On platforms that don't yet have native support, the SDK reports sessions that did not end gracefully as _Abnormal_, which leads to 100% crash free sessions being recorded. If you're building on a platform that doesn't have native support yet, you should monitor your app's _Abnormal_ rate.
 
-</Note>
+</Alert>
 
 A release is a version of your code that is deployed to an <PlatformLink to="/configuration/environments/">environment</PlatformLink>. When you give Sentry information about your releases, you can:
 
@@ -35,11 +35,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -68,11 +68,11 @@ After configuring your SDK, you can install a repository integration or manually
 
 Monitor the [health of releases](/product/releases/health/) by observing user adoption, usage of the application, percentage of [crashes](/product/releases/health/#crash), and [session data](/product/releases/health/#session). Release health will provide insight into the impact of crashes and bugs as it relates to user experience, and reveal trends with each new issue through the [Release Details](/product/releases/release-details/) graphs and filters.
 
-<Note>
+<Alert>
 
 Crash reporting and app hang detection are not available for watchOS.
 
-</Note>
+</Alert>
 
 In order to monitor release health, the SDK sends session data.
 
@@ -82,9 +82,9 @@ A session represents the interaction between the user and the application. Sessi
 
 <PlatformContent includePath="configuration/auto-session-tracking" />
 
-<Note>
+<Alert>
 
 Release health support for .NET is currently limited to single-instance **client** applications only. This means it can be used with WPF, Xamarin, WinForms and similar app models.
 Support for server frameworks such as ASP.NET is planned.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/unity/configuration/sampling.mdx b/docs/platforms/unity/configuration/sampling.mdx
index bc66495c366656..e714c315cfb2b9 100644
--- a/docs/platforms/unity/configuration/sampling.mdx
+++ b/docs/platforms/unity/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
diff --git a/docs/platforms/unity/data-management/debug-files/identifiers/index.mdx b/docs/platforms/unity/data-management/debug-files/identifiers/index.mdx
index aebce9d77c7593..ea0293898bdd60 100644
--- a/docs/platforms/unity/data-management/debug-files/identifiers/index.mdx
+++ b/docs/platforms/unity/data-management/debug-files/identifiers/index.mdx
@@ -24,14 +24,14 @@ compute a _Debug Identifier_ for each uploaded file. This identifier is
 associated with executables and libraries as well as debug companions to ensure
 that they can be uniquely located via one common mechanism.
 
-<Note>
+<Alert>
 
 Debug information does not have to be associated with releases. The unique debug
 identifier ensures that Sentry can choose the right files for every crash
 report. However, it is still recommended to configure releases in the client to
 benefit from other features.
 
-</Note>
+</Alert>
 
 For native events, the issue details page displays a list of _Loaded Images_.
 This list contains the executable and all loaded dynamic libraries including
diff --git a/docs/platforms/unity/data-management/debug-files/index.mdx b/docs/platforms/unity/data-management/debug-files/index.mdx
index b5a401b9febf2e..76457d462212fa 100644
--- a/docs/platforms/unity/data-management/debug-files/index.mdx
+++ b/docs/platforms/unity/data-management/debug-files/index.mdx
@@ -24,12 +24,12 @@ the following formats:
 - [_ProGuard mappings_](./file-formats/#proguard-mappings) for
   Java and Android
 
-<Note>
+<Alert>
 
 Source maps, while also being debug information files, are handled
 differently in Sentry. For more information see [Source Maps in sentry-cli](/cli/releases/#sentry-cli-sourcemaps).
 
-</Note>
+</Alert>
 
 Sentry requires access to debug information files of your application as well as
 system libraries to provide fully symbolicated crash reports. You can either
@@ -46,11 +46,11 @@ for automatic downloads.
 From the [Project Details](/product/projects/project-details/) page, click into settings,
 then click on _Debug Files_ in the page navigation.
 
-<Note>
+<Alert>
 
 ProGuard files are listed separately, in the _ProGuard_ section of the project settings page.
 
-</Note>
+</Alert>
 
 ## Retention Policy
 
diff --git a/docs/platforms/unity/data-management/debug-files/source-context/index.mdx b/docs/platforms/unity/data-management/debug-files/source-context/index.mdx
index 5c4d923b0a1782..48427d9db7ebba 100644
--- a/docs/platforms/unity/data-management/debug-files/source-context/index.mdx
+++ b/docs/platforms/unity/data-management/debug-files/source-context/index.mdx
@@ -20,7 +20,7 @@ needs to be uploaded alongside the debug information files.
 The recommended way to do this is by using `sentry-cli`.
 See [Creating Source Bundles](/cli/dif/#creating-source-bundles) for more information.
 
-<Note>
+<Alert>
 
 Alternatively, you can embedded source code directly into .NET Portable PDB files by using the
 [`EmbedAllSources`](https://github.com/dotnet/sourcelink/blob/main/docs/README.md#embedallsources)
@@ -30,7 +30,7 @@ extracted from them automatically.
 Also note that the similar `EmbedUntrackedSources` option is not yet supported, but may be added
 in the future. Referer to [this issue](https://github.com/getsentry/symbolic/issues/735) for details.
 
-</Note>
+</Alert>
 
 After they've been uploaded you can review and manage source bundles the same as
 any other debug information file. See [Managing Debug Information Files](../#managing-debug-information-files).
diff --git a/docs/platforms/unity/data-management/debug-files/symbol-servers/index.mdx b/docs/platforms/unity/data-management/debug-files/symbol-servers/index.mdx
index 70c5456cbe8c1c..2a17fe0c23bd73 100644
--- a/docs/platforms/unity/data-management/debug-files/symbol-servers/index.mdx
+++ b/docs/platforms/unity/data-management/debug-files/symbol-servers/index.mdx
@@ -42,7 +42,7 @@ Beware that these cause notifications to your team members.
 
 ## Custom Repositories
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 Custom repositories are available for organizations on the _Business_ and
 _Enterprise_ plans.
diff --git a/docs/platforms/unity/data-management/debug-files/upload/index.mdx b/docs/platforms/unity/data-management/debug-files/upload/index.mdx
index 6a4083a6bcc9e2..d49913bf1ba1a9 100644
--- a/docs/platforms/unity/data-management/debug-files/upload/index.mdx
+++ b/docs/platforms/unity/data-management/debug-files/upload/index.mdx
@@ -4,12 +4,12 @@ description: "Learn about uploading debug information files to Sentry."
 sidebar_order: 3
 ---
 
-<Note>
+<Alert>
 
 The Sentry SDK for Unity automatically uploads debug files at build time. That means you don't need to use `sentry-cli` directly.
 You can find more information about this in the [Unity native support documentation](/platforms/unity/native-support/).
 
-</Note>
+</Alert>
 
 The most straightforward way to provide Sentry with debug information file is
 to upload them using `sentry-cli`. Depending on your workflow, you may want to
@@ -18,7 +18,7 @@ application:
 
 <Include name="common-imgs/debug-files-workflow" />
 
-<Note>
+<Alert>
 
 Depending on application type, target platform, and build configuration, the
 Sentry support for .NET may require uploading debug files in order to show a
@@ -33,7 +33,7 @@ Refer to [msbuild configuration](/platforms/dotnet/configuration/msbuild) for de
 
 The remaining information on this page describes invoking the Sentry CLI manually.
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="debug-files">
 
diff --git a/docs/platforms/unity/data-management/sensitive-data/index.mdx b/docs/platforms/unity/data-management/sensitive-data/index.mdx
index dc24987a5b9bd1..4a04734295c717 100644
--- a/docs/platforms/unity/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/unity/data-management/sensitive-data/index.mdx
@@ -23,12 +23,12 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
 
 If you _do not_ wish to use the default PII behavior, you can also choose to identify users in a more controlled manner, using our [user identity context](../../enriching-events/identify-user/).
diff --git a/docs/platforms/unity/data-management/store-minidumps-as-attachments/index.mdx b/docs/platforms/unity/data-management/store-minidumps-as-attachments/index.mdx
index b821cb4a47ffdb..05a0db81eb930a 100644
--- a/docs/platforms/unity/data-management/store-minidumps-as-attachments/index.mdx
+++ b/docs/platforms/unity/data-management/store-minidumps-as-attachments/index.mdx
@@ -6,6 +6,6 @@ sidebar_order: 90
 
 <Include name="store-minidumps-as-attachments-intro" />
 
-<Alert level="note">☝ This feature is supported on Windows, Linux, and Android.</Alert>
+<Alert>☝ This feature is supported on Windows, Linux, and Android.</Alert>
 
 <Include name="store-minidumps-as-attachments-configuration" />
diff --git a/docs/platforms/unity/enriching-events/attachments/index.mdx b/docs/platforms/unity/enriching-events/attachments/index.mdx
index 343bb29c1d3aa8..eb231988e712f5 100644
--- a/docs/platforms/unity/enriching-events/attachments/index.mdx
+++ b/docs/platforms/unity/enriching-events/attachments/index.mdx
@@ -3,11 +3,11 @@ title: Attachments
 description: "Learn more about how Sentry can store additional files in the same request as event attachments."
 ---
 
-<Note>
+<Alert>
 
 This feature is supported in version 3.0 and higher of Sentry's .NET SDK.
 
-</Note>
+</Alert>
 
 Sentry can enrich your events for further investigation by storing additional files, such as config or log files, as attachments.
 
@@ -53,11 +53,11 @@ Unity features a global <PlatformLink to="/enriching-events/scopes/">scope</Plat
 
 <PlatformContent includePath="enriching-events/attachment-upload" />
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
@@ -75,7 +75,7 @@ By default, access is granted to all members when storage is enabled. If a membe
 
 <Include name="store-minidumps-as-attachments-intro" />
 
-<Alert level="note">☝ This feature is supported on Windows, Linux, and Android.</Alert>
+<Alert>☝ This feature is supported on Windows, Linux, and Android.</Alert>
 
 <Include name="store-minidumps-as-attachments-configuration" />
 
diff --git a/docs/platforms/unity/enriching-events/breadcrumbs/index.mdx b/docs/platforms/unity/enriching-events/breadcrumbs/index.mdx
index e65703cd2ddbcf..909b014f6d0e87 100644
--- a/docs/platforms/unity/enriching-events/breadcrumbs/index.mdx
+++ b/docs/platforms/unity/enriching-events/breadcrumbs/index.mdx
@@ -7,7 +7,7 @@ Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an
 
 This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/error-monitoring/breadcrumbs).
 
-<Alert level="" title="Learn about SDK usage">
+<Alert title="Learn about SDK usage">
 
 Developers who want to modify the breadcrumbs interface can learn more in our [developer documentation about the Breadcrumbs Interface](https://develop.sentry.dev/sdk/data-model/event-payloads/breadcrumbs/).
 
diff --git a/docs/platforms/unity/enriching-events/context/index.mdx b/docs/platforms/unity/enriching-events/context/index.mdx
index ea0d70354abac1..50397edad32d75 100644
--- a/docs/platforms/unity/enriching-events/context/index.mdx
+++ b/docs/platforms/unity/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
@@ -21,11 +21,11 @@ Then, use `Contexts` and give the context a unique name:
 
 <PlatformContent includePath="enriching-events/set-context" />
 
-<Note>
+<Alert>
 
 The class must be serializable and only properties are included; fields are not.
 
-</Note>
+</Alert>
 
 There are no restrictions on context name. In the context object, all keys are allowed except for `type`, which is used internally.
 
diff --git a/docs/platforms/unity/enriching-events/scopes/index.mdx b/docs/platforms/unity/enriching-events/scopes/index.mdx
index 751b9de56294df..c70db4f1f633c3 100644
--- a/docs/platforms/unity/enriching-events/scopes/index.mdx
+++ b/docs/platforms/unity/enriching-events/scopes/index.mdx
@@ -72,7 +72,7 @@ made will stay isolated within the callback function. This allows you to
 more easily isolate pieces of context information to specific locations in your code or
 even call `clear` to briefly remove all context information.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 Any exceptions that occur within the callback function for configuring a local scope will not be
 caught, and all errors that occur will be silently ignored and **not** reported.
diff --git a/docs/platforms/unity/enriching-events/tags/index.mdx b/docs/platforms/unity/enriching-events/tags/index.mdx
index 5707e7b98110ca..9657816853afb2 100644
--- a/docs/platforms/unity/enriching-events/tags/index.mdx
+++ b/docs/platforms/unity/enriching-events/tags/index.mdx
@@ -17,11 +17,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/unity/index.mdx b/docs/platforms/unity/index.mdx
index 9cb8fc52db337b..2cbfae484af900 100644
--- a/docs/platforms/unity/index.mdx
+++ b/docs/platforms/unity/index.mdx
@@ -34,10 +34,10 @@ This snippet includes an intentional error, so you can test that everything is w
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
diff --git a/docs/platforms/unity/metrics/index.mdx b/docs/platforms/unity/metrics/index.mdx
index 32ab35a613761c..d1ea81ae8b7e69 100644
--- a/docs/platforms/unity/metrics/index.mdx
+++ b/docs/platforms/unity/metrics/index.mdx
@@ -7,11 +7,11 @@ sidebar_hidden: true
 
 <Include name="metrics-api-change.mdx" />
 
-<Note>
+<Alert>
 
 Metrics for Unity are supported with Sentry Unity SDK version `2.0.0` and above.
 
-</Note>
+</Alert>
 
 Sentry metrics help you pinpoint and solve issues that impact user experience and app performance by measuring the data points that are important to you. You can track things like processing time, event size, user signups, and conversion rates, then correlate them back to tracing data in order to get deeper insights and solve issues faster.
 
diff --git a/docs/platforms/unity/migration/index.mdx b/docs/platforms/unity/migration/index.mdx
index 6f786f71ee014a..e3a48f8fb91c8d 100644
--- a/docs/platforms/unity/migration/index.mdx
+++ b/docs/platforms/unity/migration/index.mdx
@@ -40,14 +40,14 @@ The Sentry SDK deprecated the use of JSON files to store options and now uses sc
 
 ## Migrating From `sentry.unity.lite` to `sentry.unity`
 
-<Note>
+<Alert>
 
 The Sentry Unity Lite SDK is deprecated for mobile, desktop, WebGL, and console players.
 Customers using Unity 5.x can still use the Sentry Unity Lite as it continues to be compatible with sentry.io.
 
 The updated Sentry Unity SDK requires Unity version 2019.4 or higher with .NET Standard 2.0 scripting profile.
 
-</Note>
+</Alert>
 
 
 1. Remove the old `Sentry.cs` and `SentrySdk.cs` files from your project.
diff --git a/docs/platforms/unity/native-support/index.mdx b/docs/platforms/unity/native-support/index.mdx
index 18afc60a5a6102..c6261a7a22eb2f 100644
--- a/docs/platforms/unity/native-support/index.mdx
+++ b/docs/platforms/unity/native-support/index.mdx
@@ -6,17 +6,17 @@ sidebar_order: 100
 
 Currently, the Unity SDK offers native support for Android, iOS, Windows, macOS and Linux. The support is set to `enabled` by default, and you can opt out for each platform individually in the configuration window.
 
-<Note>
+<Alert>
 
 The setup for the iOS and Android native SDKs happens during build time, with the options defined in the Sentry editor configuration window. Changes to the options object done through [ScriptableOptionsConfiguration](/platforms/unity/configuration/options/) will not affect events from the native layer.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 The Unity SDK captures C# exceptions and does not break any builds targeting Nintendo Switch.
 
-</Note>
+</Alert>
 
 ## Mobile
 
@@ -79,6 +79,6 @@ sentry-cli --auth-token ___ORG_AUTH_TOKEN___ debug-files upload --org ___ORG_SLU
 
 <Include name="store-minidumps-as-attachments-intro" />
 
-<Alert level="note">☝ This feature is supported on Windows, Linux, and Android.</Alert>
+<Alert>☝ This feature is supported on Windows, Linux, and Android.</Alert>
 
 <Include name="store-minidumps-as-attachments-configuration" />
diff --git a/docs/platforms/unity/tracing/index.mdx b/docs/platforms/unity/tracing/index.mdx
index c18d9615ce653e..a0bcf61547c081 100644
--- a/docs/platforms/unity/tracing/index.mdx
+++ b/docs/platforms/unity/tracing/index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 4000
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 ## Configure
 
diff --git a/docs/platforms/unity/tracing/instrumentation/custom-instrumentation.mdx b/docs/platforms/unity/tracing/instrumentation/custom-instrumentation.mdx
index a9e53aaa98de73..1ccb9b0eb02be4 100644
--- a/docs/platforms/unity/tracing/instrumentation/custom-instrumentation.mdx
+++ b/docs/platforms/unity/tracing/instrumentation/custom-instrumentation.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
diff --git a/docs/platforms/unity/usage/index.mdx b/docs/platforms/unity/usage/index.mdx
index b16027dca53db6..59f7bda69588c8 100644
--- a/docs/platforms/unity/usage/index.mdx
+++ b/docs/platforms/unity/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/platforms/unity/user-feedback/index.mdx b/docs/platforms/unity/user-feedback/index.mdx
index e9fc782b8c0eb6..171274c1dbacb4 100644
--- a/docs/platforms/unity/user-feedback/index.mdx
+++ b/docs/platforms/unity/user-feedback/index.mdx
@@ -8,11 +8,11 @@ When a user experiences an error, Sentry provides the ability to collect additio
 
 ## Use the .NET SDK
 
-<Note>
+<Alert>
 
 User Feedback for **[ASP.NET](/platforms/dotnet/guides/aspnet/user-feedback/#integration)** or **[ASP.NET Core](/platforms/dotnet/guides/aspnetcore/user-feedback/#integration)** supply integrations specific to supporting those SDKs.
 
-</Note>
+</Alert>
 
 You can create a form to collect the user input in your preferred framework, and use the SDK's API to send the information to Sentry. You can also use the widget, as described below. If you'd prefer an alternative to the widget or do not have a JavaScript frontend, you can use this API:
 
diff --git a/docs/platforms/unreal/configuration/debug-symbols/index.mdx b/docs/platforms/unreal/configuration/debug-symbols/index.mdx
index 4a8ad02367a20c..fe3c3c8ce04afd 100644
--- a/docs/platforms/unreal/configuration/debug-symbols/index.mdx
+++ b/docs/platforms/unreal/configuration/debug-symbols/index.mdx
@@ -5,19 +5,19 @@ description: "Learn how the Unreal Engine SDK handles debug symbols upload."
 
 Sentry requires [debug information files](/platforms/unreal/data-management/debug-files/) to symbolicate crashes. The Unreal Engine SDK provides an automated upload functionality for those symbol files that rely on the [sentry-cli](/cli/). This is done automatically, so running the `sentry-cli` manually isn't required. The symbol upload happens during the execution of `PostBuildSteps`, as specified in the `Sentry.uplugin` file. The `sentry-cli` executables for Windows, macOS, and Linux are included as part of the Unreal Engine SDK package. They can also be downloaded manually via the settings menu if the plugin was installed from the UE Marketplace.
 
-<Note>
+<Alert>
 
 For Android, debug symbols upload is handled by [Sentry Android Gradle Plugin](/platforms/android/configuration/gradle). By default, it bumps Gradle version to 7.5 automatically, however one can fallback to using its legacy version in case compatibility issues with other third-party plugins arise.
 
-</Note>
+</Alert>
 
 The automated debug symbols upload is disabled by default and requires configuration. To configure it, navigate to **Project Settings > Plugins > Sentry**, then enter the [Auth Token](https://sentry.io/orgredirect/organizations/:orgslug/settings/auth-tokens/), Organization Slug, and Project Name. Note, that the Unreal Engine SDK automatically creates a `sentry.properties` file at the root of your project directory to store the configuration. This configuration file should **never** be made publicly available.
 
-<Note>
+<Alert>
 
 You must configure which build configurations, target types, and platforms Sentry will upload debug symbols for in the "Misc" section of the plugin settings.
 
-</Note>
+</Alert>
 
 ![The Unreal Engine debug symbols upload configuration](./img/unreal-debug-symbols.png)
 
diff --git a/docs/platforms/unreal/configuration/options.mdx b/docs/platforms/unreal/configuration/options.mdx
index 99a8a758c1045c..b046076136bc88 100644
--- a/docs/platforms/unreal/configuration/options.mdx
+++ b/docs/platforms/unreal/configuration/options.mdx
@@ -84,7 +84,7 @@ Grouping in Sentry is different for events with stack traces and without. As a r
 Takes a screenshot of the application when an error happens and includes it as an attachment.
 Learn more about enriching events with screenshots in our <PlatformLink to="/enriching-events/screenshots/">Screenshots documentation</PlatformLink>.
 
-<Alert level="info">
+<Alert>
 
 The support for screenshot attachment on crash events is limited to Windows and Linux.
 
@@ -116,7 +116,7 @@ A number between 0 and 1, controlling the percentage chance a given transaction
 
 A function responsible for determining the percentage chance a given transaction will be sent to Sentry. It will automatically be passed information about the transaction and the context in which it's being created, and must return a number between `0` (0% chance of being sent) and `1` (100% chance of being sent). Can also be used for filtering transactions, by returning 0 for those that are unwanted. Either this or <PlatformIdentifier name="traces-sample-rate" /> must be defined to enable tracing.
 
-<Alert level="info">
+<Alert>
 
 Currently, there is no support for sampling functions on Windows or Linux (<PlatformIdentifier name="traces-sampler" />).
 
diff --git a/docs/platforms/unreal/configuration/releases.mdx b/docs/platforms/unreal/configuration/releases.mdx
index 09f36f1ca875ee..d627415afd45be 100644
--- a/docs/platforms/unreal/configuration/releases.mdx
+++ b/docs/platforms/unreal/configuration/releases.mdx
@@ -29,11 +29,11 @@ The value can be arbitrary, but we recommend either of these naming strategies:
   - `build` is the number that identifies an iteration of your app (`CFBundleVersion` on iOS, `versionCode` on Android)
 - **Commit SHA**: If you use a version control system like Git, we recommend using the identifying hash (for example, the commit SHA, `da39a3ee5e6b4b0d3255bfef95601890afd80709`). You can let Sentry CLI automatically determine this hash for supported version control systems. Learn more in our [Sentry CLI](/cli/releases/#creating-releases) documentation.
 
-<Note>
+<Alert>
 
 Releases are global per organization; prefix them with something project-specific for easy differentiation.
 
-</Note>
+</Alert>
 
 The behavior of a few features depends on whether a project is using semantic or time-based versioning.
 
@@ -70,8 +70,8 @@ A session represents the interaction between the user and the application. Sessi
 
 <PlatformContent includePath="configuration/auto-session-tracking" />
 
-<Note>
+<Alert>
 
 On Windows, release health support for Unreal Engine is currently limited to games made with UE 5.2 or later. Note, that "Enable automatic crash capturing (Windows, UE 5.2+)" in the plugin settings has to be checked to track crashed sessions properly.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/unreal/configuration/sampling.mdx b/docs/platforms/unreal/configuration/sampling.mdx
index 2e54aa6003bff0..a16428a3b1b983 100644
--- a/docs/platforms/unreal/configuration/sampling.mdx
+++ b/docs/platforms/unreal/configuration/sampling.mdx
@@ -14,11 +14,11 @@ To send a representative sample of your errors to Sentry, set the <PlatformIdent
 
 The error sample rate defaults to `1`, meaning all errors are sent to Sentry.
 
-<Note>
+<Alert>
 
 Changing the error sample rate requires re-deployment. In addition, setting an SDK sample rate limits visibility into the source of events. Setting a rate limit for your project (which only drops events when volume is high) may better suit your needs.
 
-</Note>
+</Alert>
 
 ## Sampling Transaction Events
 
@@ -96,7 +96,7 @@ When there's the potential for more than one of these to come into play, the fol
 1. If <PlatformIdentifier name="traces-sampler" /> is not defined, but there's a parent sampling decision, the parent sampling decision will be used.
 1. If <PlatformIdentifier name="traces-sampler" /> is not defined and there's no parent sampling decision, <PlatformIdentifier name="traces-sample-rate" /> will be used.
 
-<Alert level="info">
+<Alert>
 
 Currently there is no support for forcing a sampling decision by passing it into <PlatformIdentifier name="start-transaction" />.
 
diff --git a/docs/platforms/unreal/configuration/setup-crashreporter/index.mdx b/docs/platforms/unreal/configuration/setup-crashreporter/index.mdx
index da2479a577d7e6..26656ffbf9f1cd 100644
--- a/docs/platforms/unreal/configuration/setup-crashreporter/index.mdx
+++ b/docs/platforms/unreal/configuration/setup-crashreporter/index.mdx
@@ -58,12 +58,12 @@ CrashReportClientVersion=1.0
 DataRouterUrl="___UNREAL_URL___"
 ```
 
-<Note>
+<Alert>
 
 If a `[CrashReportClient]` section already exists, simply changing the value of `DataRouterUrl`
 is enough.
 
-</Note>
+</Alert>
 
 Alternatively, the endpoint can be added automatically to the _DefaultEngine.ini_ file
 by using the Sentry configuration window.
@@ -118,17 +118,17 @@ void ConfigureCrashReporter()
 You need to call the `ConfigureCrashReporter` some time after your game
 starts. Any [event attribute](https://develop.sentry.dev/sdk/data-model/event-payloads/) can be set.
 
-<Note>
+<Alert>
 
 You should configure Crash Reporter attributes before initializing the Sentry SDK. Otherwise, some information may get overwritten and lost.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 The Sentry SDK provides an API which allows you to set Crash Reporter attributes as well.
 
-</Note>
+</Alert>
 
 Depending on the version of Unreal Engine you are using, you may have to
 add JSON support to the build script (`MyProject.build.cs`):
@@ -144,11 +144,11 @@ symbolicated stack traces, you need to upload _Debug Information Files_
 (sometimes also referred to as _Debug Symbols_ or just _Symbols_). We recommend
 uploading debug information during your build or release process.
 
-<Note>
+<Alert>
 
 The Sentry SDK can handle uploading [debug symbols](/platforms/unreal/configuration/debug-symbols/) automatically at build time.
 
-</Note>
+</Alert>
 
 For all libraries where you'd like to receive symbolication, **you need
 to provide debug information**. This includes dependencies and operating system
@@ -179,6 +179,6 @@ Check out this community-generated [thread in Sentry's forum](https://forum.sent
 
 <Include name="store-minidumps-as-attachments-intro" />
 
-<Alert level="note">☝ This feature is supported on Windows, Linux, and Android.</Alert>
+<Alert>☝ This feature is supported on Windows, Linux, and Android.</Alert>
 
 <Include name="store-minidumps-as-attachments-configuration" />
diff --git a/docs/platforms/unreal/data-management/debug-files/identifiers/index.mdx b/docs/platforms/unreal/data-management/debug-files/identifiers/index.mdx
index aebce9d77c7593..ea0293898bdd60 100644
--- a/docs/platforms/unreal/data-management/debug-files/identifiers/index.mdx
+++ b/docs/platforms/unreal/data-management/debug-files/identifiers/index.mdx
@@ -24,14 +24,14 @@ compute a _Debug Identifier_ for each uploaded file. This identifier is
 associated with executables and libraries as well as debug companions to ensure
 that they can be uniquely located via one common mechanism.
 
-<Note>
+<Alert>
 
 Debug information does not have to be associated with releases. The unique debug
 identifier ensures that Sentry can choose the right files for every crash
 report. However, it is still recommended to configure releases in the client to
 benefit from other features.
 
-</Note>
+</Alert>
 
 For native events, the issue details page displays a list of _Loaded Images_.
 This list contains the executable and all loaded dynamic libraries including
diff --git a/docs/platforms/unreal/data-management/debug-files/index.mdx b/docs/platforms/unreal/data-management/debug-files/index.mdx
index b5a401b9febf2e..76457d462212fa 100644
--- a/docs/platforms/unreal/data-management/debug-files/index.mdx
+++ b/docs/platforms/unreal/data-management/debug-files/index.mdx
@@ -24,12 +24,12 @@ the following formats:
 - [_ProGuard mappings_](./file-formats/#proguard-mappings) for
   Java and Android
 
-<Note>
+<Alert>
 
 Source maps, while also being debug information files, are handled
 differently in Sentry. For more information see [Source Maps in sentry-cli](/cli/releases/#sentry-cli-sourcemaps).
 
-</Note>
+</Alert>
 
 Sentry requires access to debug information files of your application as well as
 system libraries to provide fully symbolicated crash reports. You can either
@@ -46,11 +46,11 @@ for automatic downloads.
 From the [Project Details](/product/projects/project-details/) page, click into settings,
 then click on _Debug Files_ in the page navigation.
 
-<Note>
+<Alert>
 
 ProGuard files are listed separately, in the _ProGuard_ section of the project settings page.
 
-</Note>
+</Alert>
 
 ## Retention Policy
 
diff --git a/docs/platforms/unreal/data-management/debug-files/symbol-servers/index.mdx b/docs/platforms/unreal/data-management/debug-files/symbol-servers/index.mdx
index 70c5456cbe8c1c..2a17fe0c23bd73 100644
--- a/docs/platforms/unreal/data-management/debug-files/symbol-servers/index.mdx
+++ b/docs/platforms/unreal/data-management/debug-files/symbol-servers/index.mdx
@@ -42,7 +42,7 @@ Beware that these cause notifications to your team members.
 
 ## Custom Repositories
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 Custom repositories are available for organizations on the _Business_ and
 _Enterprise_ plans.
diff --git a/docs/platforms/unreal/data-management/sensitive-data/index.mdx b/docs/platforms/unreal/data-management/sensitive-data/index.mdx
index 790cae1b88b608..549e01609d3052 100644
--- a/docs/platforms/unreal/data-management/sensitive-data/index.mdx
+++ b/docs/platforms/unreal/data-management/sensitive-data/index.mdx
@@ -23,10 +23,10 @@ We offer the following options depending on your legal and operational needs:
 - [configuring server-side scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) to ensure Sentry does _not store_ data. Configuration changes are done in the Sentry UI and apply immediately for new events.
 - [running a local Relay](/product/relay/) on your own server between the SDK and Sentry, so that data is _not sent to_ Sentry while configuration can still be applied without deploying.
 
-<Note>
+<Alert>
 
 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.
 
-</Note>
+</Alert>
diff --git a/docs/platforms/unreal/data-management/store-minidumps-as-attachments/index.mdx b/docs/platforms/unreal/data-management/store-minidumps-as-attachments/index.mdx
index 6f1275c4c84141..ed5b9dd274b782 100644
--- a/docs/platforms/unreal/data-management/store-minidumps-as-attachments/index.mdx
+++ b/docs/platforms/unreal/data-management/store-minidumps-as-attachments/index.mdx
@@ -7,6 +7,6 @@ sidebar_order: 90
 
 <Include name="store-minidumps-as-attachments-intro" />
 
-<Alert level="note">☝ This feature is supported on Windows, Linux, and Android.</Alert>
+<Alert>☝ This feature is supported on Windows, Linux, and Android.</Alert>
 
 <Include name="store-minidumps-as-attachments-configuration" />
diff --git a/docs/platforms/unreal/enriching-events/attachments/index.mdx b/docs/platforms/unreal/enriching-events/attachments/index.mdx
index 45e64049a54c64..c99ac9cafd8880 100644
--- a/docs/platforms/unreal/enriching-events/attachments/index.mdx
+++ b/docs/platforms/unreal/enriching-events/attachments/index.mdx
@@ -3,11 +3,11 @@ title: Attachments
 description: "Learn more about how Sentry can store additional files in the same request as event attachments."
 ---
 
-<Note>
+<Alert>
 
 This feature is supported for iOS and Android only.
 
-</Note>
+</Alert>
 
 Sentry can enrich your events for further investigation by storing additional files, such as config or log files, as attachments.
 
@@ -94,11 +94,11 @@ The same result can be achieved by calling the corresponding function in bluepri
 
 ![Upload attachmnet](./img/unreal_attachment_upload.png)
 
-<Note>
+<Alert>
 
 Sentry allows at most 20MB for a compressed request, and at most 100MB of uncompressed attachments per event, including the crash report file (if applicable). Uploads exceeding this size are rejected with HTTP error `413 Payload Too Large` and the data is dropped immediately. To add larger or more files, consider secondary storage options.
 
-</Note>
+</Alert>
 
 Attachments persist for 30 days; if your total storage included in your quota is exceeded, attachments will not be stored. You can delete attachments or their containing events at any time. Deleting an attachment does not affect your quota - Sentry counts an attachment toward your quota as soon as it is stored.
 
@@ -116,7 +116,7 @@ By default, access is granted to all members when storage is enabled. If a membe
 
 <Include name="store-minidumps-as-attachments-intro" />
 
-<Alert level="note">☝ This feature is supported on Windows, Linux, and Android.</Alert>
+<Alert>☝ This feature is supported on Windows, Linux, and Android.</Alert>
 
 <Include name="store-minidumps-as-attachments-configuration" />
 
diff --git a/docs/platforms/unreal/enriching-events/context/index.mdx b/docs/platforms/unreal/enriching-events/context/index.mdx
index 50186db756ffa4..98cb2088f5db63 100644
--- a/docs/platforms/unreal/enriching-events/context/index.mdx
+++ b/docs/platforms/unreal/enriching-events/context/index.mdx
@@ -7,11 +7,11 @@ Custom contexts allow you to attach arbitrary data to an event. Often, this cont
 
 <Include name="common-imgs/additional_data" />
 
-<Note>
+<Alert>
 
 If you need to be able to search on custom data, [use tags](../tags) instead.
 
-</Note>
+</Alert>
 
 ## Structured Context
 
@@ -35,11 +35,11 @@ The same result can be achieved by calling corresponding function in blueprint:
 
 Alternatively, this configuration can be provided to the crash reporter [during initialization](/platforms/unreal/configuration/setup-crashreporter/#configure-attributes).
 
-<Note>
+<Alert>
 
 Sentry's SDK automatically attaches certain context values such as `Engine version`, `Configuration`, and `Target Type`, to name a few, to all events.
 
-</Note>
+</Alert>
 
 There are no restrictions on context name. In the context object, all keys are allowed except for `type`, which is used internally.
 
diff --git a/docs/platforms/unreal/enriching-events/scopes/index.mdx b/docs/platforms/unreal/enriching-events/scopes/index.mdx
index e06c816b282697..89094619a47d3a 100644
--- a/docs/platforms/unreal/enriching-events/scopes/index.mdx
+++ b/docs/platforms/unreal/enriching-events/scopes/index.mdx
@@ -121,7 +121,7 @@ made will stay isolated within the callback function. This allows you to
 more easily isolate pieces of context information to specific locations in your code or
 even call `clear` to briefly remove all context information.
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 Any exceptions that occur within the callback function for configuring a local scope will not be
 caught, and all errors that occur will be silently ignored and **not** reported.
diff --git a/docs/platforms/unreal/enriching-events/tags/index.mdx b/docs/platforms/unreal/enriching-events/tags/index.mdx
index 8035c211bf7cd3..d0595213f5689d 100644
--- a/docs/platforms/unreal/enriching-events/tags/index.mdx
+++ b/docs/platforms/unreal/enriching-events/tags/index.mdx
@@ -15,11 +15,11 @@ Define the tag:
 
 <PlatformContent includePath="enriching-events/set-tag" />
 
-<Note>
+<Alert>
 
 Some tags are automatically set by Sentry. We strongly recommend against overwriting these [tags](/concepts/search/searchable-properties/#search-properties). Instead, name your tags with your organization's nomenclature. If you overwrite an automatically set tag, you must use [explicit tag syntax](/concepts/search/#explicit-tag-syntax) to search for it.
 
-</Note>
+</Alert>
 
 Once you've started sending tagged data, you'll see it when logged in to sentry.io. There, you can view the filters within the sidebar on the Project page, summarized within an event, and on the Tags page for an aggregated event.
 
diff --git a/docs/platforms/unreal/index.mdx b/docs/platforms/unreal/index.mdx
index 0a9546f0c3a073..ce83430ea78eb9 100644
--- a/docs/platforms/unreal/index.mdx
+++ b/docs/platforms/unreal/index.mdx
@@ -69,11 +69,11 @@ We recommend using the `github` version, because it uses `Crashpad`, an out-of-p
 
 To install the SDK, download the most up-to-date sources from the [Releases page](https://github.com/getsentry/sentry-unreal/releases) and add them to your project's `Plugins` directory. On the next project launch, UE will prompt you to build the Sentry and SentryEditor modules.
 
-<Note>
+<Alert>
 
 Currently, this method is available only for C++ UE projects. Blueprint projects can be converted to a C++ one by adding an empty class using the editor.
 
-</Note>
+</Alert>
 
 ### Installing from Fab
 
@@ -88,13 +88,13 @@ To get started, we recommend cloning the [Unreal SDK repository](https://github.
 * `./scripts/init.sh` on macOS/Linux
 * `./scripts/init-win.ps1` on Windows
 
-<Note>
+<Alert>
 Initialization scripts require [GitHub CLI](https://cli.github.com/) to be installed.
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 If the initialization script fails due to errors on Windows, check your PowerShell version by printing the built-in variable `$PSVersionTable`. If the version is `5.x`, upgrading to a newer version of [PowerShell](https://github.com/powershell/powershell) may resolve these errors.
-</Note>
+</Alert>
 
 This script links the checked out version of the plugin (the [plugin-dev](https://github.com/getsentry/sentry-unreal/tree/b67076ad5dc419d46b4be70a0bd6e64c2357a82d/plugin-dev) directory) to the [sample app](https://github.com/getsentry/sentry-unreal/tree/b67076ad5dc419d46b4be70a0bd6e64c2357a82d/sample) and downloads the latest builds of native SDKs from our GitHub CI.
 
@@ -122,11 +122,11 @@ The minimum configuration required is the [DSN](/product/sentry-basics/dsn-expla
 }
 ```
 
-<Note>
+<Alert>
 
 If you are logged in, you can also go to your project settings and copy its DSN directly from there.
 
-</Note>
+</Alert>
 
 Sentry can be configured using the Sentry configuration window.
 The window can be accessed by going to editor's menu: **Project Settings > Plugins > Sentry**.
@@ -156,11 +156,11 @@ The same result can be achieved by calling corresponding function in blueprint:
 
 ![Sentry capture message BP](./img/unreal_bp_message.png)
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
 
@@ -168,6 +168,6 @@ To view and resolve the recorded error, log into [sentry.io](https://sentry.io)
 
 <Include name="store-minidumps-as-attachments-intro" />
 
-<Alert level="note">☝ This feature is supported on Windows, Linux, and Android.</Alert>
+<Alert>☝ This feature is supported on Windows, Linux, and Android.</Alert>
 
 <Include name="store-minidumps-as-attachments-configuration" />
diff --git a/docs/platforms/unreal/tracing/index.mdx b/docs/platforms/unreal/tracing/index.mdx
index c56cf4293ed2e1..636a48dc72ed1d 100644
--- a/docs/platforms/unreal/tracing/index.mdx
+++ b/docs/platforms/unreal/tracing/index.mdx
@@ -6,11 +6,11 @@ sidebar_order: 4000
 
 With [tracing](/product/performance/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems. Sentry captures distributed traces consisting of transactions and spans, which measure individual services and individual operations within those services. Learn more about our model in [Distributed Tracing](/product/sentry-basics/tracing/distributed-tracing/).
 
-<Note>
+<Alert>
 
 If you’re adopting Tracing in a high-throughput environment, we recommend testing prior to deployment to ensure that your service’s performance characteristics maintain expectations.
 
-</Note>
+</Alert>
 
 ## Configure
 
@@ -21,7 +21,7 @@ First, enable tracing and configure the sample rate for transactions. Set the sa
 
 The two options are meant to be mutually exclusive. If you set both, <PlatformIdentifier name="traces-sampler" /> will take precedence.
 
-<Alert level="info">
+<Alert>
 
 Currently there is no support for sampling functions on Windows/Linux (<PlatformIdentifier name="traces-sampler" />).
 
diff --git a/docs/platforms/unreal/tracing/instrumentation/custom-instrumentation.mdx b/docs/platforms/unreal/tracing/instrumentation/custom-instrumentation.mdx
index a07ebf534cff1f..7a5b6d5f6190fb 100644
--- a/docs/platforms/unreal/tracing/instrumentation/custom-instrumentation.mdx
+++ b/docs/platforms/unreal/tracing/instrumentation/custom-instrumentation.mdx
@@ -4,11 +4,11 @@ description: "Learn how to capture performance data on any action in your app."
 sidebar_order: 20
 ---
 
-<Note>
+<Alert>
 
 To capture transactions and spans customized to your organization's needs, you must first <PlatformLink to="/tracing/">set up tracing.</PlatformLink>
 
-</Note>
+</Alert>
 
 <PlatformContent includePath="performance/enable-manual-instrumentation" />
 
diff --git a/docs/platforms/unreal/usage/index.mdx b/docs/platforms/unreal/usage/index.mdx
index 50e620ad6ac60b..b2c5747c9ecb50 100644
--- a/docs/platforms/unreal/usage/index.mdx
+++ b/docs/platforms/unreal/usage/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 10
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.
 
-<Note>
+<Alert>
 
 Key terms:
 
@@ -15,7 +15,7 @@ Key terms:
 - The reporting of an event is called _capturing_.
   When an event is captured, it’s sent to Sentry.
 
-</Note>
+</Alert>
 
 The most common form of capturing is to capture errors. What can be captured as an error varies by platform. In general, if you have something that looks like an exception, it can be captured. For some SDKs, you can also omit the argument to <PlatformIdentifier name="capture-exception" /> and Sentry will attempt to capture the current exception. It is also useful for manual reporting of errors or messages to Sentry.
 
diff --git a/docs/pricing/index.mdx b/docs/pricing/index.mdx
index 506acf38b2b693..14c101d94ca78a 100644
--- a/docs/pricing/index.mdx
+++ b/docs/pricing/index.mdx
@@ -39,11 +39,11 @@ Any data sent after you've run through your reserved volume and pay-as-you-go bu
 
 Sentry offers several products, each of which have their own pricing structure as listed in the tables below. Paid pricing plans include a standard volume of events for each product or data category and you can buy more either by prepaying for reserved volume and/or setting up a pay-as-you-go (PAYG) budget.
 
-<Note>
+<Alert>
 
 Please note that all per-category prices listed below have been rounded to the nearest millionth.
 
-</Note>
+</Alert>
 
 #### Errors Pricing
 
@@ -126,12 +126,12 @@ For more information on how to manage your monthly spending, check out our [Quot
 
 ## Billing Cycles
 
-<Note>
+<Alert>
   You have to have Billing or Owner-level permissions to make changes to
   information on the Subscription page or access invoices. If you need an
   invoice, but don't have the right permissions, reach out to your
   administrator.
-</Note>
+</Alert>
 
 Sentry uses two different billing cycles: one for your paid plan and reserved volume, and another one for your pay-as-you-go usage.
 
diff --git a/docs/pricing/legacy-pricing.mdx b/docs/pricing/legacy-pricing.mdx
index 558750e84829aa..c810e294dcfc29 100644
--- a/docs/pricing/legacy-pricing.mdx
+++ b/docs/pricing/legacy-pricing.mdx
@@ -33,11 +33,11 @@ If you run out of **both** your prepaid and on-demand volume, any new data you s
 
 If you'd like to buy either prepaid or on-demand data on top of what's included in your plan, you can buy as much as you think you'll need per data category. [Errors](#errors-pricing), [Performance](#performance-pricing), [Replays](#replays-pricing), [Cron Monitors](#cron-monitors-pricing), and [Attachments](#attachments-pricing) each have their own unique pricing structures, as listed in the tables below:
 
-<Note>
+<Alert>
 
 Please note that all per-category prices listed below have been rounded to the nearest millionth.
 
-</Note>
+</Alert>
 
 {/*<!-- prettier-ignore-start -->*/}
 
@@ -131,11 +131,11 @@ Buying on-demand volume lets you control the maximum amount you’ll pay for ove
 
 With on-demand volume, you pay for any event or attachment processed, (rounded up to the nearest cent), after your reserved volume has run out.
 
-<Note>
+<Alert>
 
 If you've enabled [Spend Allocation](/pricing/quotas/spend-allocation/), and your project has consumed both its dedicated event allocation and your organization's un-allocated pool, any excess event consumption will come from your on-demand budget **even if you have reserved volume still available**.
 
-</Note>
+</Alert>
 
 On-demand volume is billed at the end of each billing month. To see on-demand pricing per plan type, check out our [per-category-pricing](#per-category-pricing).
 
@@ -161,12 +161,12 @@ In most cases, new budgets will take effect within minutes. Otherwise, we guaran
 
 ## Billing Cycles
 
-<Note>
+<Alert>
   You have to have Billing or Owner-level permissions to make changes to
   information on the Subscription page or access invoices. If you need an
   invoice, but don't have the right permissions, reach out to your
   administrator.
-</Note>
+</Alert>
 
 Sentry uses two different billing cycles: one for your paid plan and reserved volume, and another one for your on-demand volume.
 
diff --git a/docs/pricing/quotas/index.mdx b/docs/pricing/quotas/index.mdx
index 9c3b7757e87518..3c0a28efb5c1ed 100644
--- a/docs/pricing/quotas/index.mdx
+++ b/docs/pricing/quotas/index.mdx
@@ -48,11 +48,11 @@ Sentry completes a thorough evaluation of each event to determine if it counts t
 
 Before completing any of these evaluations, Sentry confirms that each event includes a valid DSN and project as well as whether the event can be parsed. In addition, for error events, Sentry validates that the event contains valid fingerprint information. If any of these items are missing or incorrect, the event is rejected.
 
-<Note>
+<Alert>
 
 This list is ordered from easiest or least time-consuming, to most challenging or potentially time-consuming.
 
-</Note>
+</Alert>
 
 ### Spike Protection
 
diff --git a/docs/pricing/quotas/legacy-manage-transaction-quota.mdx b/docs/pricing/quotas/legacy-manage-transaction-quota.mdx
index 553f41a9a3b866..5a3c68e81bbae5 100644
--- a/docs/pricing/quotas/legacy-manage-transaction-quota.mdx
+++ b/docs/pricing/quotas/legacy-manage-transaction-quota.mdx
@@ -17,7 +17,7 @@ Applying the proper SDK configuration is an iterative and on-going process, but
 
 ## Before You Begin: Check Your Quota Usage
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 The "Usage Stats" tab is only visible if you're on a Team, Business, or Enterprise plan.
 
@@ -39,11 +39,11 @@ The "Project" table in the "Usage Stats" tab of **Stats** breaks down your event
 
 ### Which transactions are consuming my quota?
 
-<Note>
+<Alert>
 
 You can only update the columns of the Results table in **Discover** if your organization is on a Business plan.
 
-</Note>
+</Alert>
 
 You can set up [a query](<https://sentry.io/orgredirect/organizations/:orgslug/discover/results/?field=title&field=project&field=count()&name=All+Events&query=event.type%3Atransaction&sort=-count&statsPeriod=14d&yAxis=count()>) in **Discover** to see which transactions or transactions with profiling you're receiving the most and if you want to adjust that. When you're building the query, search for `event.type:transaction` and then set the columns to `title`, `project`, and `count`, as shown below:
 
@@ -57,11 +57,11 @@ You can look for transactions with profiling using  `has:profile.id`. Adding a `
 
 ## Adjusting Quotas
 
-<Note>
+<Alert>
 
 Quotas can only be updated by a Billing or Owner member of your Sentry organization.
 
-</Note>
+</Alert>
 
 Once your performance units volume is approaching or has exceeded the quota, teammates with the "Owner" organization permission level will receive [notification](/product/alerts/notifications/#quota-notifications) emails. You can then choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
 
@@ -108,11 +108,11 @@ To decrease your quota, go to **Settings > Subscription** and click "Manage Subs
 
 ![The Review & Confirm step of a subscription update.](./img/review-subscription.png)
 
-<Note>
+<Alert>
 
 We strongly recommend that you make subscription changes **before** the last day of your billing period. Depending on your time zone, in some cases, changes made on the last day of the billing period will not go into effect until the next billing period.
 
-</Note>
+</Alert>
 
 ## Inbound Filters
 
@@ -122,11 +122,11 @@ Once applied, you can track the filtered events (numbers and cause) using the gr
 
 ![Built-in Inbound Filters](./img/manage-event-stream-03.png)
 
-<Note>
+<Alert>
 
 The **Inbound Data Filters** page in [sentry.io](https://sentry.io) only refers to errors, but it applies to transactions, transactions with profiling, and attachments as well.
 
-</Note>
+</Alert>
 
 Sentry provides several methods to filter all events and attachments server-side, which are applied before checking for potential rate limits. Inbound filters include:
 
diff --git a/docs/pricing/quotas/manage-attachments-quota.mdx b/docs/pricing/quotas/manage-attachments-quota.mdx
index 2123515707bf90..65befc6540f45b 100644
--- a/docs/pricing/quotas/manage-attachments-quota.mdx
+++ b/docs/pricing/quotas/manage-attachments-quota.mdx
@@ -27,11 +27,11 @@ The "Project" table in the "Usage Stats" tab of **Stats** breaks down your data
 
 ## Adjusting Quotas
 
-<Note>
+<Alert>
 
 Quotas can only be updated by a Billing or Owner member of your Sentry organization.
 
-</Note>
+</Alert>
 
 Once your attachments volume is approaching or has exceeded the quota, teammates with the "Owner" organization permission level will receive [notification](/product/alerts/notifications/#quota-notifications) emails. You can then choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
 
@@ -46,11 +46,11 @@ To increase your quota, go to **Settings > Subscription** and click the "Manage
 
 If you're on a Developer plan and want to increase your quota, you'll need to upgrade to a Team or Business plan. On these plans you can prepay for more attachments volume and purchase pay-as-you-go budget, as needed. Learn about Sentry's plans on our [pricing page](https://sentry.io/pricing/).
 
-<Note>
+<Alert>
 
 If you upgrade from Team to Business mid-billing period, your on-demand pricing changes retroactively.
 
-</Note>
+</Alert>
 
 ### Reserved Volume
 
@@ -76,11 +76,11 @@ Changes to pay-as-you-go budget typically go into effect immediately and are gua
 
 To decrease your quota, go to **Settings > Subscription** and click "Manage Subscriptions". When you reach the "Review & Confirm" step, the date that these changes go into effect will be displayed.
 
-<Note>
+<Alert>
 
 We strongly recommend that you make subscription changes **before** the last day of your billing period. Depending on your time zone, in some cases, changes made on the last day of the billing period will not go into effect until the next billing period.
 
-</Note>
+</Alert>
 
 ## Rate Limiting
 
diff --git a/docs/pricing/quotas/manage-cron-monitors.mdx b/docs/pricing/quotas/manage-cron-monitors.mdx
index 2d8c8cb1ae1ad1..f42999f6ff9238 100644
--- a/docs/pricing/quotas/manage-cron-monitors.mdx
+++ b/docs/pricing/quotas/manage-cron-monitors.mdx
@@ -7,11 +7,11 @@ description: Learn how to manage the number of cron monitors you pay for and adj
 
 All Sentry plans include **one cron monitor**. To activate additional monitors, you need to add a [**pay-as-you-go (PAYG)**](/pricing/#pricing-how-it-works) budget.
 
-<Note>
+<Alert>
 
 The PAYG budget is only available on **paid plans**.
 
-</Note>
+</Alert>
 
 ## Key Terms
 
@@ -69,7 +69,7 @@ You can manually deactivate or delete monitors at any time from the **Crons** pa
 - **Quota Becomes Reusable**: The quota from the deactivated or deleted monitor becomes available for reuse **within the same billing period**.
 - **Billing Impact**: Deactivated or deleted monitors will **count** towards your billing quota if they were previously active in the current billing period. Otherwise, they don't count towards your billing quota.
 
-<Note>
+<Alert>
 
 - **Quota Reuse Limitations**:
 
@@ -77,7 +77,7 @@ You can manually deactivate or delete monitors at any time from the **Crons** pa
   - Applies only to monitors that were previously active and billed.
   - **Reusable quota does not carry over to new billing periods.**
 
-</Note>
+</Alert>
 
 ## Example Scenario
 
@@ -114,4 +114,4 @@ Let's illustrate how this works with an example:
 - **Adjust Budget as Needed**: If you plan to add more monitors, consider increasing your PAYG budget beforehand.
 - **Plan for Renewal**: Remember that quotas reset each billing period. Ensure you have sufficient budget to keep monitors active.
 
-By understanding how monitor activation and billing work, you can effectively manage your cron monitors and avoid interruptions in your monitoring.
\ No newline at end of file
+By understanding how monitor activation and billing work, you can effectively manage your cron monitors and avoid interruptions in your monitoring.
diff --git a/docs/pricing/quotas/manage-event-stream-guide.mdx b/docs/pricing/quotas/manage-event-stream-guide.mdx
index b743c02190d066..5bad779af6a05c 100644
--- a/docs/pricing/quotas/manage-event-stream-guide.mdx
+++ b/docs/pricing/quotas/manage-event-stream-guide.mdx
@@ -31,11 +31,11 @@ The "Project" table in the "Usage Stats" tab of **Stats** breaks down your data
 
 ### Which issues are consuming my quota?
 
-<Note>
+<Alert>
 
 You can only update the columns of the Results table in **Discover** if your organization is on a Business plan.
 
-</Note>
+</Alert>
 
 You can set up [a query](https://sentry.io/orgredirect/organizations/:orgslug/discover/results/?field=title&field=project&field=count%28%29&name=All+Events&query=event.type%3Aerror&sort=-count&statsPeriod=14d&yAxis=count%28%29) in **Discover** to take a more proactive approach to resolving your busiest issues. When you're building the query, search for `event.type:error` and then set the columns `issue`, `title`, `project`, and `count()`, as shown below:
 
@@ -59,11 +59,11 @@ Spike Protection protects users from spiking event volume. Typically, spikes are
 
 ## Adjusting Quotas
 
-<Note>
+<Alert>
 
 Quotas can only be updated by a Billing or Owner member of your Sentry organization.
 
-</Note>
+</Alert>
 
 Once your event volume is approaching or has exceeded the quota, teammates with the "Owner" organization permission level will receive [notification](/product/alerts/notifications/#quota-notifications) emails. You can then choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
 
@@ -79,11 +79,11 @@ To increase your quota, go to **Settings > Subscription** and click the "Manage
 
 If you're on a Developer plan and want to increase your quota, you'll need to upgrade to a Team or Business plan. On these plans you can prepay for more event volume and purchase pay-as-you-go volume, as needed. Learn about Sentry's plans on our [pricing page](https://sentry.io/pricing/).
 
-<Note>
+<Alert>
 
 If you upgrade from Team to Business mid-billing period, your pay-as-you-go pricing changes retroactively.
 
-</Note>
+</Alert>
 
 ### Reserved Volume
 
@@ -109,11 +109,11 @@ Changes to pay-as-you-go volume typically go into effect immediately and are gua
 
 To decrease your quota, go to **Settings > Subscription** and click "Manage Subscriptions". When you reach the "Review & Confirm" step, the date that these changes go into effect will be displayed.
 
-<Note>
+<Alert>
 
 We strongly recommend that you make subscription changes **before** the last day of your billing period. Depending on your time zone, in some cases, changes made on the last day of the billing period will not go into effect until the next billing period.
 
-</Note>
+</Alert>
 
 ## Rate Limiting
 
diff --git a/docs/pricing/quotas/manage-replay-quota.mdx b/docs/pricing/quotas/manage-replay-quota.mdx
index 2c4e57732cd85b..352e967f377dc0 100644
--- a/docs/pricing/quotas/manage-replay-quota.mdx
+++ b/docs/pricing/quotas/manage-replay-quota.mdx
@@ -25,11 +25,11 @@ The "Project" table in the "Usage Stats" tab of the Stats page breaks down you
 
 ## Adjusting Quotas
 
-<Note>
+<Alert>
 
 Quotas can only be updated by a Billing or Owner-level member of your Sentry organization.
 
-</Note>
+</Alert>
 
 Once your replay volume is approaching or has exceeded its quota, teammates with the "Owner" organization permission level will start receiving [notification](/product/alerts/notifications/#quota-notifications) emails. They'll then be able to choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
 
@@ -74,8 +74,8 @@ Changes to pay-as-you-go budget typically go into effect within minutes and are
 
 To decrease your quota, go to **Settings > Subscription** and click "Manage Subscriptions". When you reach the "Review & Confirm" step, the date that these changes go into effect will be displayed.
 
-<Note>
+<Alert>
 
 We strongly recommend that you make subscription changes **before** the last day of your billing period. In some cases, changes made on the last day of the billing period will not go into effect until the next billing period (depending on your time zone).
 
-</Note>
+</Alert>
diff --git a/docs/pricing/quotas/manage-transaction-quota.mdx b/docs/pricing/quotas/manage-transaction-quota.mdx
index 13e2afefcdf2b0..2a2a9aebd762f2 100644
--- a/docs/pricing/quotas/manage-transaction-quota.mdx
+++ b/docs/pricing/quotas/manage-transaction-quota.mdx
@@ -10,7 +10,7 @@ Applying the proper SDK configuration is an iterative and on-going process, but
 
 ## Before You Begin: Check Your Quota Usage
 
-<Alert title="Note" level="info">
+<Alert title="Note">
 
 The "Usage Stats" tab is only visible if you're on a Team, Business, or Enterprise plan.
 
@@ -36,11 +36,11 @@ Sentry SDKs allow you to configure a sample rate ([example](/platforms/javascrip
 
 ## Adjusting Quotas
 
-<Note>
+<Alert>
 
 Quotas can only be updated by a Billing or Owner member of your Sentry organization.
 
-</Note>
+</Alert>
 
 Once your span unit volume is approaching or has exceeded the quota, teammates with the "Owner" organization permission level will receive [notification](/product/alerts/notifications/#quota-notifications) emails. You can then choose to [increase](#increasing-quotas) or [decrease](#decreasing-quotas) your quota.
 
@@ -86,11 +86,11 @@ Changes to pay-as-you-go budget typically go into effect immediately and are gua
 To decrease your quota, go to **Settings > Subscription** and click "Manage Subscriptions". When you reach the "Review & Confirm" step, the date that these changes go into effect will be displayed.
 
 
-<Note>
+<Alert>
 
 We strongly recommend that you make subscription changes **before** the last day of your billing period. Depending on your time zone, in some cases, changes made on the last day of the billing period will not go into effect until the next billing period.
 
-</Note>
+</Alert>
 
 ## Inbound Filters
 
diff --git a/docs/pricing/quotas/spend-allocation.mdx b/docs/pricing/quotas/spend-allocation.mdx
index e759dfea149d5b..530db889320531 100644
--- a/docs/pricing/quotas/spend-allocation.mdx
+++ b/docs/pricing/quotas/spend-allocation.mdx
@@ -5,19 +5,19 @@ sidebar_order: 20
 description: "Learn how to allocate reserved volume to specific projects so that the most important projects are always monitored."
 ---
 
-<Note>
+<Alert>
 
 This feature is only available to organizations with an Enterprise plan.
 
-</Note>
+</Alert>
 
 Spend Allocation gives you the ability to prioritize your most important projects (or make sure that smaller projects don't get ignored). You can do this by setting aside a set amount of reserved volume (errors and attachments) to be used by those projects each month. This ensures that all the projects that are important to you are always monitored, regardless of the volume other projects consume.
 
-<Note>
+<Alert>
 
 The per-project allocation you set is the **minimum** not the **maximum** number of events each project will get.
 
-</Note>
+</Alert>
 
 ## How Spend Allocation Works
 
@@ -25,11 +25,11 @@ To get started with Spend Allocation, look at your total reserved volume and dec
 
 For each project, you'll need to specify how much of your allocation goes to errors and attachments.
 
-<Note>
+<Alert>
 
 With Spend Allocation, excess event consumption may come from your [pay-as-you-go budget](/pricing/), <b>even if you still have reserved volume available.</b>
 
-</Note>
+</Alert>
 
 Once all your monthly volume has been consumed, any additional events will be dropped.
 
diff --git a/docs/pricing/quotas/spike-protection.mdx b/docs/pricing/quotas/spike-protection.mdx
index 65c1b7186792a0..73f6441e806d83 100644
--- a/docs/pricing/quotas/spike-protection.mdx
+++ b/docs/pricing/quotas/spike-protection.mdx
@@ -9,27 +9,27 @@ A spike is a significant, temporary increase in your event volume. Because Sentr
 
 Spike Protection currently applies to errors, transactions or spans, and attachments.
 
-<Note>
+<Alert>
 
 Spike Protection does not apply during trials as category quotas are unlimited for the duration of the trial. For example, new organizations on a trial will not be spike-protected until the trial is over even if projects have Spike Protection enabled.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 Notifications for Spike Protection are turned off by default to avoid excessive noise for users. Read the [notification](/pricing/quotas/spike-protection/#notifications) section below to learn how to turn them on for key projects.
 
-</Note>
+</Alert>
 
 ## How Spike Protection Works
 
 Spike Protection can be enabled on a per-project basis for your organization by any team member with **Manager, Billing or Owner-level permissions**. To select which project to set it up for, go to **Settings > Spike Protection**. You'll be able to toggle it on for individual projects or click “Enable All” to set it up for all your projects at once.
 
-<Note>
+<Alert>
 
 If you're an existing Sentry user with Spike Protection enabled on an org level, you'll be automatically switched to the new per-project level Spike Protection. All your projects will have Spike Protection enabled by default, but you can make adjustments at any time.
 
-</Note>
+</Alert>
 
 ## How Sentry Detects Spikes
 
diff --git a/docs/product/alerts/alert-types.mdx b/docs/product/alerts/alert-types.mdx
index 9cb0440834ff35..dc41e454b84938 100644
--- a/docs/product/alerts/alert-types.mdx
+++ b/docs/product/alerts/alert-types.mdx
@@ -40,11 +40,11 @@ Metric alerts tell you when a [metric](/product/performance/metrics/) crosses a
 
 Metric alerts monitor macro-level metrics for both error and transaction events. A metric takes a set of events and computes an aggregate value using a function, such as `count()` or `avg()`, applied to the event properties over a period of time. When you create a metric alert, you can filter events by attributes and <PlatformLink to="/enriching-events/tags/">tags</PlatformLink>, which is particularly useful for aggregating across events that aren't grouped into single issues. Sentry allows a maximum of 1000 metric alerts for an organization.
 
-<Note>
+<Alert>
 
 Metric alerts may include [archived issues](/product/issues/states-triage/#archive) if events from those issues match the filters of your metric alert rule. Events from archived and resolved issues can be filtered out by using the `is:unresolved` filter in your metric alert rule. This filter is added by default when creating a new metric alert, but you may need to manually add it to older metric alerts if you want them to exclude archived issues.
 
-</Note>
+</Alert>
 
 These alerts use _Critical_ and _Warning_ triggers to measure severity. An alert’s current status is the highest severity trigger that is active, which can be one of three values: Warning, Critical, or Resolved. Sentry notifies you whenever an alert's status changes.
 
@@ -137,6 +137,3 @@ You can enable alerts for the [User Feedback Widget](/product/user-feedback/#use
 ![User Feedback Alert Configuration.](../user-feedback/img/user-feedback-alert-configuration.png)
 
 To get alerts when [crash-report feedback](/product/user-feedback/#crash-report-modal) comes in, make sure to turn on "Enable Crash Report Notifications" in Settings > Projects > [Project Name] > User Feedback.
-
-
-
diff --git a/docs/product/alerts/create-alerts/index.mdx b/docs/product/alerts/create-alerts/index.mdx
index 9b8e7359e779cc..2be75521d9272f 100644
--- a/docs/product/alerts/create-alerts/index.mdx
+++ b/docs/product/alerts/create-alerts/index.mdx
@@ -4,11 +4,11 @@ sidebar_order: 20
 description: "Learn how to create alerts that keep you informed about errors and performance issues in your application."
 ---
 
-<Note>
+<Alert>
 
 The minimum role required to create alerts is member. Sentry users with manager or owner permissions can change the minimum role requirement in **Settings > General Settings > Let Members Create and Edit Alerts**.
 
-</Note>
+</Alert>
 
 To create alerts:
 
diff --git a/docs/product/alerts/create-alerts/metric-alert-config.mdx b/docs/product/alerts/create-alerts/metric-alert-config.mdx
index 06341fc6724d86..a5a20bbcee21b7 100644
--- a/docs/product/alerts/create-alerts/metric-alert-config.mdx
+++ b/docs/product/alerts/create-alerts/metric-alert-config.mdx
@@ -10,9 +10,9 @@ Sentry provides several configuration options to create a metric alert based on
 
 To create a metric alert you first need to choose a metric type. For some alert types the function is built into the alert and for others you can choose functions and parameters to apply to it. For example, if you select “Users Experiencing Errors”, that translates to the function, `count_unique(user.id)`. Since editing this function would change the nature of the alert, it is not editable and thus hidden. On the other hand, if you select “Largest Contentful Paint” the measurement used is `measurement.lcp`, you also need to choose a function, e.g. `p75()`, for a combined metric function of `p75(measurement.lcp)`.
 
-<Note>
+<Alert>
 When creating new metric alerts, the `is:unresolved` filter is added by default. This filter excludes events from archived and resolved issues. If you want your metric alerts to include archived issues, you can manually remove `is:unresolved` from your [filters](#filters).
-</Note>
+</Alert>
 
 ### Metrics Types for Alerting
 
@@ -95,11 +95,11 @@ Add filters in the provided input to narrow down what you'll be alerted about, s
 
 #### Advanced filters for Transactions
 
-<Note>
+<Alert>
 
 This feature is only available to organizations with a Business or Enterprise plan.
 
-</Note>
+</Alert>
 
 A wider variety of fields or tags are available in addition to the basic properties mentioned above, so you can create more advanced filtering conditions. However, Sentry only starts collecting these metrics after the alert is saved. If such a filter is used, Sentry provides an estimate of the metric for the previous period during the alert's creation.
 
@@ -136,7 +136,7 @@ Anomaly alerts automatically detect trends outside expected values. They can be
 
 There are three options for alert responsiveness: low, medium, and high. If you choose low responsiveness, then your alert will fire less frequently but with higher confidence. If you choose high responsiveness, then your alert will fire more frequently with a greater chance of false positives. Our recommendation is to start with medium responsiveness, our default, and adjust the responsiveness based on the results you see.
 
-Another setting is to set the direction of the alert: above and/or below the expected bounds. This setting can help increase the signal of your alert rule. 
+Another setting is to set the direction of the alert: above and/or below the expected bounds. This setting can help increase the signal of your alert rule.
 
 ![When the dynamic threshold is selected.](./img/dynamic-threshold.png)
 
@@ -150,11 +150,11 @@ You can set the status of an alert rule when a threshold is met using the labels
 
 You must set the “Warning” threshold so that it’s triggered before the “Critical” threshold. When Sentry evaluates an alert, the alert’s status is updated to the highest severity trigger that matches. If you don’t set a “Resolved” threshold, the alert automatically resolves when it's no longer breaching the “Critical” or “Warning” conditions. You can also resolve alerts manually.
 
-<Note>
+<Alert>
 
-Note: Anomaly alert thresholds are controlled by Sentry and cannot be manually configured. 
+Note: Anomaly alert thresholds are controlled by Sentry and cannot be manually configured.
 
-</Note>
+</Alert>
 
 ### Auto-Resolve
 
diff --git a/docs/product/alerts/index.mdx b/docs/product/alerts/index.mdx
index 4db2b6e31f7224..94a21317435651 100644
--- a/docs/product/alerts/index.mdx
+++ b/docs/product/alerts/index.mdx
@@ -50,11 +50,11 @@ When you create a new project in [sentry.io](https://sentry.io), you can select
 
 Alerts should notify you when there's an important problem with your application. But they shouldn't be too noisy, because that can lead to alert fatigue. Muting alerts is one way to reduce noise, but we recommend following these [best practices](/product/alerts/best-practices/) to help you create relevant alerts that notify the people equipped to fix the problem.
 
-<Note>
+<Alert>
 
 Any user can mute alerts for their entire organization by default, but users with manager or owner-level permissions can update the minimum role requirement by going to **Settings > General Settings > Let Members Create and Edit Alerts**.
 
-</Note>
+</Alert>
 
 ### Muting Issue Alerts
 
diff --git a/docs/product/alerts/uptime-monitoring/automatic-detection.mdx b/docs/product/alerts/uptime-monitoring/automatic-detection.mdx
index 11d5929baf06b0..60516ece0213f2 100644
--- a/docs/product/alerts/uptime-monitoring/automatic-detection.mdx
+++ b/docs/product/alerts/uptime-monitoring/automatic-detection.mdx
@@ -12,7 +12,7 @@ In order to be able to automatically detect uptime alerts, we analyze all the UR
 
 To avoid creating flaky alerts, the hostname undergoes an "onboarding period" of three days. During this period, we send HTTP requests to the hostname every hour. If the request fails three times or more, the hostname will be dropped and re-evaluated after seven days.
 
-<Alert level="info">
+<Alert>
  Sentry will execute uptime checks against the hostname root path of the most frequently-seen URLs. For example, if the most frequently-seen URL in your events is `GET https://www.example.com/docs/introduction`, the check will be `GET https://www.example.com/`.
 </Alert>
 
diff --git a/docs/product/codecov/set-up.mdx b/docs/product/codecov/set-up.mdx
index dd722b3d04ee13..1813da2c941283 100644
--- a/docs/product/codecov/set-up.mdx
+++ b/docs/product/codecov/set-up.mdx
@@ -12,11 +12,11 @@ There are a few prerequisites that have to be fulfilled in order for Codecov to
 - Owner or manager-level permissions in Sentry.io.
 - The [GitHub Integration](/organization/integrations/source-code-mgmt/github/) installed in Sentry with [Code Mappings](/organization/integrations/source-code-mgmt/github/#stack-trace-linking) enabled.
 
-  <Note>
+  <Alert>
     If you have the GitHub integration set up correctly, your stack traces will
     show an “Open this line in GitHub” prompt that will take you to your app's
     code.
-  </Note>
+  </Alert>
 
 - A [Codecov](https://about.codecov.io/) account with [Source Code Coverage](https://about.codecov.io/product/feature/source-code-coverage/) enabled.
 
@@ -26,8 +26,8 @@ Once the prerequisites have been met, you can enable Codecov by going to the **S
 
 ![Codecov in Org Settings](./img/codecov-setup-in-ui.png)
 
-<Note>
+<Alert>
   Sentry automatically checks to see if you have your GitHub Org in Codecov
   every 24 hours. If Codecov hasn't been enabled and we find that you've met all
   the prerequisites listed above, we'll turn it on for you.
-</Note>
+</Alert>
diff --git a/docs/product/crons/getting-started/http/index.mdx b/docs/product/crons/getting-started/http/index.mdx
index b96ab0b4737c53..640805d141bb48 100644
--- a/docs/product/crons/getting-started/http/index.mdx
+++ b/docs/product/crons/getting-started/http/index.mdx
@@ -54,11 +54,11 @@ GET /api/___PROJECT_ID___/cron/<monitor_slug>/___PUBLIC_KEY___/?status=error HTT
 Host: ___ORG_INGEST_DOMAIN___
 ```
 
-<Note>
+<Alert>
 
 If you expect your scheduled jobs to overlap, read about [Overlapping Jobs](#overlapping-jobs-optional) below.
 
-</Note>
+</Alert>
 
 ### Specifying monitor environments (Optional)
 
@@ -68,7 +68,7 @@ environments.
 
 If you don't specify an environment with your check-ins the default is `production`.
 
-<Alert level="info">
+<Alert>
 
 Monitor environments are still early in development. Currently, after a check-in
 occurs for a specific environment, you must continue sending check-ins on
@@ -144,11 +144,11 @@ This is an object specifying a `schedule_type` of either `crontab` or `interval`
 
 The amount of time (in minutes) Sentry should wait for your check-in before it's considered missed ("grace period"). Optional.
 
-<Note>
+<Alert>
 
 We recommend that your check-in margin be less than or equal to your interval.
 
-</Note>
+</Alert>
 
 `max_runtime`:
 
diff --git a/docs/product/crons/getting-started/index.mdx b/docs/product/crons/getting-started/index.mdx
index 61457dd9a077a6..d44c8c6413cc64 100644
--- a/docs/product/crons/getting-started/index.mdx
+++ b/docs/product/crons/getting-started/index.mdx
@@ -23,7 +23,7 @@ To set up Sentry Crons, use the links below for supported SDKs or the Sentry CLI
 - [Ruby](/platforms/ruby/crons/)
 - [Elixir](/platforms/elixir/crons/)
 
-<Alert level="note" title="Don't see your platform?">
+<Alert title="Don't see your platform?">
 
 We're working on enabling additional platforms for Crons. In the meantime, you can use the Sentry CLI or HTTP to set up monitoring for your jobs.
 
diff --git a/docs/product/crons/legacy-endpoint-migration.mdx b/docs/product/crons/legacy-endpoint-migration.mdx
index b5145c8b1b6c4c..b384f5ae1ea76d 100644
--- a/docs/product/crons/legacy-endpoint-migration.mdx
+++ b/docs/product/crons/legacy-endpoint-migration.mdx
@@ -7,7 +7,7 @@ ingestion-level traffic, so we have since moved Check-In APIs to use
 
 If you're using legacy endpoints for Crons, migrate to the new endpoints to avoid issues.
 
-<Alert level="info">
+<Alert>
 
 The Legacy endpoints **are deprecated** and will be removed in the future,
 however a date has not yet been set for their removal. We will communicate a
diff --git a/docs/product/dev-toolbar/index.mdx b/docs/product/dev-toolbar/index.mdx
index 1f1af9fd4a6c00..6827badf8b001b 100644
--- a/docs/product/dev-toolbar/index.mdx
+++ b/docs/product/dev-toolbar/index.mdx
@@ -4,7 +4,7 @@ sidebar_order: 120
 description: "Bring critical Sentry insights and tools directly into your web app for easier troubleshooting with the Dev Toolbar."
 ---
 
-<Alert level="info">
+<Alert>
   The Dev Toolbar is currently in **beta**. Beta features are still in progress and may have bugs. Please reach out on
   [GitHub](https://github.com/getsentry/sentry-toolbar/issues) if you have any feedback or concerns.
 </Alert>
diff --git a/docs/product/dev-toolbar/setup.mdx b/docs/product/dev-toolbar/setup.mdx
index c98d6ffe0a307d..32c3ac1ac648fb 100644
--- a/docs/product/dev-toolbar/setup.mdx
+++ b/docs/product/dev-toolbar/setup.mdx
@@ -4,7 +4,7 @@ sidebar_order: 10
 description: "Get started with Sentry's Dev Toolbar, bringing critical Sentry insights and tools into your web app to help your team troubleshoot more effectively."
 ---
 
-<Alert level="info">
+<Alert>
   The Dev Toolbar is currently in **beta**. Beta features are still in progress and may have bugs. Please reach out on
   [GitHub](https://github.com/getsentry/sentry-toolbar/issues) if you have any feedback or concerns.
 </Alert>
diff --git a/docs/product/explore/discover-queries/index.mdx b/docs/product/explore/discover-queries/index.mdx
index c90628abfcb545..f5833cc0863090 100644
--- a/docs/product/explore/discover-queries/index.mdx
+++ b/docs/product/explore/discover-queries/index.mdx
@@ -4,11 +4,11 @@ sidebar_order: 90
 description: "Discover is a powerful query engine that allows you to query all your metadata across projects and environments to unlock insights."
 ---
 
-<Note>
+<Alert>
 
 This feature is available only if your organization is on either a Business or Trial Plan, with the exception of the ["All Events" pre-built query](/product/explore/discover-queries/#pre-built-queries), which is available on Team plans or higher.
 
-</Note>
+</Alert>
 
 <SandboxLink scenario="discover" projectSlug="react">Discover</SandboxLink> provides visibility into your data across environments by building
 upon and enriching your error data. You can <SandboxLink scenario="oneDiscoverQuery" projectSlug="react">query</SandboxLink> and unlock insights into the health of your entire system and get
diff --git a/docs/product/explore/discover-queries/query-builder.mdx b/docs/product/explore/discover-queries/query-builder.mdx
index ebf06563cc3e35..65486e3cefe4ed 100644
--- a/docs/product/explore/discover-queries/query-builder.mdx
+++ b/docs/product/explore/discover-queries/query-builder.mdx
@@ -25,7 +25,7 @@ There are five main building blocks that impact the results of your saved query,
 
 ## Dataset Selection
 
-The dataset selector allows you to query for either errors or transactions. You can only query one dataset at a time. The errors dataset returns events related to errors, while the transactions dataset returns transaction events that help you see application performance. 
+The dataset selector allows you to query for either errors or transactions. You can only query one dataset at a time. The errors dataset returns events related to errors, while the transactions dataset returns transaction events that help you see application performance.
 
 ## Filter by Project, Environment, and Date Range
 
@@ -60,13 +60,13 @@ Click on any of these sections to further refine your search. For example, click
 
 ![Facet map for transaction and handled tags. Map looks like a bar with gradient colors.](./img/discover-facet-map.png)
 
-<Note>
+<Alert>
 
 When performing searches on transaction events, based on your search criteria
 and sample rate, the events available may be limited because Discover uses
 sampled data only. Learn more by reading about [our retention priorities](/product/performance/retention-priorities/).
 
-</Note>
+</Alert>
 
 ## Filter by Interactive Graph
 
diff --git a/docs/product/explore/discover-queries/uncover-trends.mdx b/docs/product/explore/discover-queries/uncover-trends.mdx
index 2f2d00eee30001..bcfab6b78d0202 100644
--- a/docs/product/explore/discover-queries/uncover-trends.mdx
+++ b/docs/product/explore/discover-queries/uncover-trends.mdx
@@ -10,11 +10,11 @@ description: "Learn how to work with the data in Discover to gain useful insight
 
 Let's go over some examples of how to work with all this data to gain some useful insights into the health and stability of your applications.
 
-<Note>
+<Alert>
 
 Some table column options may be repeated if you’ve set up a tag with the same name as a Sentry field. For the examples that follow, use the table column option marked “field.”
 
-</Note>
+</Alert>
 
 ## Discover Through Issues
 
diff --git a/docs/product/explore/metrics/index.mdx b/docs/product/explore/metrics/index.mdx
index ba35e4830a6584..37c153497af8bc 100644
--- a/docs/product/explore/metrics/index.mdx
+++ b/docs/product/explore/metrics/index.mdx
@@ -59,11 +59,11 @@ Metrics are useful for analyzing your data in aggregate. If you have more than 1
 
 If you really are interested in individual user actions, consider using [transactions](/product/performance/transaction-summary/#what-is-a-transaction) instead of metrics.
 
-<Note>
+<Alert>
 
 Sentry incorporates protection mechanisms that will drop metrics if their cardinality exceeds an internally defined limit.
 
-</Note>
+</Alert>
 
 ### Supported Characters
 
diff --git a/docs/product/explore/metrics/metrics-explorer-page.mdx b/docs/product/explore/metrics/metrics-explorer-page.mdx
index 548d76d4137af2..fc28aaa3973bdd 100644
--- a/docs/product/explore/metrics/metrics-explorer-page.mdx
+++ b/docs/product/explore/metrics/metrics-explorer-page.mdx
@@ -49,11 +49,11 @@ Within the trace view, custom metrics associated with a span are also displayed
 
 ## Code Locations
 
-<Note>
+<Alert>
 
 This feature is not currently available in all SDKs.
 
-</Note>
+</Alert>
 
 When it comes to custom metrics, you can use the code locations tab to see the line of code in your application where your metric is being emitted. This can come in handy when troubleshooting an issue, especially if you were not the one creating the metric in the first place.
 
diff --git a/docs/product/explore/profiling/differential-flamegraphs.mdx b/docs/product/explore/profiling/differential-flamegraphs.mdx
index 0286f6307c459a..e38a652bfd5f8c 100644
--- a/docs/product/explore/profiling/differential-flamegraphs.mdx
+++ b/docs/product/explore/profiling/differential-flamegraphs.mdx
@@ -12,11 +12,11 @@ Differential flame graphs are graph visualizations that highlight how the call s
 
 In Sentry, differential flame graphs are shown whenever a function regression is detected. When a regression happens, Sentry generates two aggregate flame graphs. One from the period leading up to the regression, and another from the time right after it. A differential flame graph is then used to visualize the difference between the two.
 
-<Note>
+<Alert>
 
 In a differential flame graph, the color red means that a function's execution time has increased or that there's a newly present function. The color blue means that the execution time has decreased.
 
-</Note>
+</Alert>
 
 Be on the lookout for red frames when interpreting differential flame graphs. They're the reason why your application code has been performing worse.
 
diff --git a/docs/product/explore/profiling/flame-charts-graphs.mdx b/docs/product/explore/profiling/flame-charts-graphs.mdx
index e15a74d5b5dea1..0b853c12c9a1ae 100644
--- a/docs/product/explore/profiling/flame-charts-graphs.mdx
+++ b/docs/product/explore/profiling/flame-charts-graphs.mdx
@@ -50,11 +50,11 @@ Aggregating stacks this way helps you find performance optimizations by visualiz
 
 _The same profile data, visualized in a aggregated flame graph on top and a flame graph on the bottom._
 
-<Note>
+<Alert>
 
 The first aggregated flame graph above is shown "flames down", and the second aggregated flame graph is shown "flames up". Whether you choose to look at a aggregated flame graph in a flames up or a flames down view is a matter of personal preference. The information is identical.
 
-</Note>
+</Alert>
 
 In sentry.io, aggregated flame graphs are displayed on your profile summary page. The aggregated flame graphs on this page are created using data from many different profiles so that you can see the most common performance bottlenecks in your program.
 
diff --git a/docs/product/explore/profiling/index.mdx b/docs/product/explore/profiling/index.mdx
index 187aabbe6f05f9..8fa8033b3e7afb 100644
--- a/docs/product/explore/profiling/index.mdx
+++ b/docs/product/explore/profiling/index.mdx
@@ -4,7 +4,7 @@ sidebar_order: 50
 description: "Profiling offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment."
 ---
 
-<Note>
+<Alert>
 
 **The currently supported platforms are:**
 
@@ -19,7 +19,7 @@ description: "Profiling offers a deeper level of visibility on top of traditiona
 - [Flutter [experimental, iOS and macOS only]](/platforms/flutter/profiling/)
 - [.NET [experimental]](/platforms/dotnet/profiling/)
 
-</Note>
+</Alert>
 
 Sentry's profiling feature builds upon our established [Performance Monitoring](/product/performance) capabilities to provide precise code-level visibility into application execution in a production environment. Profiling provides context at a deeper level than traditional tracing, enabling you to visualize the precise details of the call stack without the need for custom instrumentation. With Profiling you can quickly identify hot paths in your code and understand potential performance bottlenecks, enabling you to build in [performance as a feature](https://blog.codinghorror.com/performance-is-a-feature/) from day one.
 
diff --git a/docs/product/explore/profiling/performance-overhead.mdx b/docs/product/explore/profiling/performance-overhead.mdx
index 7eb43313718238..36edd0594b5646 100644
--- a/docs/product/explore/profiling/performance-overhead.mdx
+++ b/docs/product/explore/profiling/performance-overhead.mdx
@@ -6,10 +6,10 @@ description: "Learn more about how enabling Profiling impacts the performance of
 
 Profiling works by taking snapshots (samples) of the call stack of each thread in your application at a regular interval, then transmitting that data to event ingestion servers via the Internet. This method of profiling is known as sampling profiling. Sentry's profilers collect samples approximately 100 times per second (or once every 10ms). Sampling profiling provides a reasonable tradeoff between data fidelity and runtime overhead, as opposed to deterministic profiling, which introduces significantly higher overhead by tracking every function call.
 
-<Note>
+<Alert>
 
 For most applications, the performance overhead of enabling profiling in production is imperceptible to end users.
 
-</Note>
+</Alert>
 
 The quantitative overhead of profiling (measured as a percentage increase in CPU time) is dependent on environmental factors such as the SDK, the platform, the hardware, and whether the workload is CPU or I/O bound. As a rule of thumb, we target approximately **1-5% CPU time overhead** on a typical configuration with mid-end hardware on each platform.
diff --git a/docs/product/explore/session-replay/mobile/index.mdx b/docs/product/explore/session-replay/mobile/index.mdx
index 5a555af25b3d99..4fd2492918a998 100644
--- a/docs/product/explore/session-replay/mobile/index.mdx
+++ b/docs/product/explore/session-replay/mobile/index.mdx
@@ -78,8 +78,10 @@ Session Replay for Mobile is currently available for all plans. Check out our [p
 
 **Are unhandled exceptions (for example, crashes) available as part of Session Replay for mobile?**
 
-Currently, only handled exceptions will include a replay. We’re actively working on covering replays for crashes and ANRs and plan to support them for mobile in the coming weeks. Please refer to the SDK release notes for updates.
+Yes, Session Replay for Mobile covers handled and unhandled exceptions as well as ANRs/App Hangs and native (NDK) crashes. Make sure to use the latest SDK version as mentioned in [SDKs Supported](#sdks-supported).
 
 **How does Session Replay for mobile work if my app is offline?**
 
-Session Replay for Mobile currently doesn’t work in offline mode. We plan on adding support for at least a few segments leading up to errors and crashes. Please subscribe to this [GitHub issue](https://github.com/getsentry/sentry/issues/68287) for updates.
+Session Replay for Mobile currently supports offline mode only when `onErrorSampleRate` is specified. When an error happens, the SDK will capture the segment it recorded until that time (up to 30 seconds) and store it to disk. When the application comes back online, that segment will be sent to Sentry together with the error.
+
+Currently `sessionSampleRate` is not supported in offline mode. Please subscribe to this [GitHub issue](https://github.com/getsentry/sentry/issues/68287) for updates.
diff --git a/docs/product/explore/session-replay/web/index.mdx b/docs/product/explore/session-replay/web/index.mdx
index 586d17e823c85d..93d347e689f168 100644
--- a/docs/product/explore/session-replay/web/index.mdx
+++ b/docs/product/explore/session-replay/web/index.mdx
@@ -31,11 +31,11 @@ The end of a session replay recording can be triggered by:
 - A recording reaching the maximum replay duration limit. (Currently, this is 60 minutes.)
 - Manually calling the [`replay.stop()`](/platforms/javascript/session-replay/understanding-sessions/#manually-stopping-replay) method.
 
-<Note>
+<Alert>
 
 Unlike [sessions](/product/releases/health/#session) on the **Releases** page, user sessions in Session Replay can span multiple page loads.
 
-</Note>
+</Alert>
 
 ## Learn More About Session Replay
 
diff --git a/docs/product/explore/session-replay/web/performance-overhead.mdx b/docs/product/explore/session-replay/web/performance-overhead.mdx
index c187416c94dc2f..e17f0cce06e07f 100644
--- a/docs/product/explore/session-replay/web/performance-overhead.mdx
+++ b/docs/product/explore/session-replay/web/performance-overhead.mdx
@@ -69,7 +69,7 @@ We measured the overhead of the Replay SDK on Sentry's web UI using the methodol
 | Network Upload                   | 21 B           | 3.84 KB         | 272.51 KB           |
 | Network Download                 | 8.06 MB        | 8.09 MB         | 8.07 MB             |
 
-<Note>
+<Alert>
   \* The standard deviation for LCP was 386, 511, and 354 ms, respectively. This
   means that the LCP values are quite spread out and explains why the Sentry
   standalone LCP value is higher than the Sentry with Replay value.
@@ -77,17 +77,17 @@ We measured the overhead of the Replay SDK on Sentry's web UI using the methodol
 {/* prettier-ignore */}
   Benchmarks last updated on Sept 25, 2023
 
-</Note>
+</Alert>
 
 The benchmarks were run on an Apple M1 MacBook Pro against a remote preview server and a remote API backend with 50 iterations. The scenario can be summarized as loading Sentry, navigating to Discover, adding 4 columns, waiting for results, adding another column, and finally waiting for results a second time.
 
 The benchmark test was a strenuous recording scenario (the Discover data table is one of our most complex, in regards to DOM nodes and mutations). A simpler scenario consisting of navigation to four different "Settings" pages was also ran and produced an increase of ~100 ms of total JS blocking time.
 
 {/* prettier-ignore */}
-<Note>
+<Alert>
   There's a known performance issue that happens when replays with many DOM
   mutations are recorded. It generally occurs when rendering large data grids.
   We're working on a fix, but in the meantime we recommend you{" "}
   <PlatformLink to="/session-replay/privacy/#blocking">use the blocking feature</PlatformLink>
   to avoid recording large mutations which can degrade performance for your customers.
-</Note>
+</Alert>
diff --git a/docs/product/explore/traces/index.mdx b/docs/product/explore/traces/index.mdx
index 2f01999485e12a..1aa85e732d5f40 100644
--- a/docs/product/explore/traces/index.mdx
+++ b/docs/product/explore/traces/index.mdx
@@ -4,9 +4,9 @@ sidebar_order: 30
 description: "Learn how to use the Trace Explorer to search span data, find distributed traces, and debug performance issues across your entire application stack."
 ---
 
-<Note>
+<Alert>
 The Traces page is currently in beta. Beta features are still in progress and may have bugs. We recognize the irony.
-</Note>
+</Alert>
 
 The [**Traces**](https://sentry.io/orgredirect/organizations/:orgslug/traces/) page allows you to query individual spans within traces and analyze distributed traces across your entire application stack. When you search by spans, your queries are more targeted and more precise. This helps you pinpoint specific operations that may be causing problems (like slow database queries, API calls, and so on) across multiple traces.
 
@@ -43,11 +43,12 @@ The Query Builder uses [Sentry's standard search syntax](/concepts/search/). Her
 
 For a list of built-in key fields used in Sentry, check out our [Searchable Properties for Spans documentation](/concepts/search/searchable-properties/spans/).
 
-<Note>
+<Alert>
 
 Trace Explorer uses sampled data. Your search results may be limited based on sampling rates and retention policies. Learn more about [retention priorities](/product/performance/retention-priorities/).
 
-</Note>
+
+</Alert>
 
 ## Search Query Results
 
diff --git a/docs/product/insights/ai/llm-monitoring/getting-started/index.mdx b/docs/product/insights/ai/llm-monitoring/getting-started/index.mdx
index 78979941355e86..751af9f38715e3 100644
--- a/docs/product/insights/ai/llm-monitoring/getting-started/index.mdx
+++ b/docs/product/insights/ai/llm-monitoring/getting-started/index.mdx
@@ -4,11 +4,11 @@ sidebar_order: 0
 description: "Learn how to set up Sentry LLM Monitoring"
 ---
 
-<Note>
+<Alert>
 
 This feature is currently only available in the Python SDK.
 
-</Note>
+</Alert>
 
 Sentry LLM Monitoring is easiest to use with the Python SDK and an official integration like OpenAI.
 
@@ -25,7 +25,7 @@ To start sending LLM data to Sentry, make sure you've created a Sentry project f
 - [Huggingface Hub](/platforms/python/integrations/huggingface_hub/)
 - [Cohere](/platforms/python/integrations/cohere/)
 
-<Alert level="note" title="Don't see your platform?">
+<Alert title="Don't see your platform?">
 
 We'll be adding AI integrations continuously. You can also instrument AI manually with the Sentry Python SDK.
 
diff --git a/docs/product/insights/ai/llm-monitoring/getting-started/the-dashboard.mdx b/docs/product/insights/ai/llm-monitoring/getting-started/the-dashboard.mdx
index a37ee5460e3365..292314a8c2680b 100644
--- a/docs/product/insights/ai/llm-monitoring/getting-started/the-dashboard.mdx
+++ b/docs/product/insights/ai/llm-monitoring/getting-started/the-dashboard.mdx
@@ -21,9 +21,9 @@ One has used 58,000 tokens in the past hour, and the other has used 44,900 token
 
 As you can see in the example above, the "Ask Sentry" pipeline has used 59 thousand tokens and taken 3.2 seconds on average.
 
-<Note>
+<Alert>
 Creating an AI pipeline is different than calling an LLM. If you're creating AI pipelines by calling LLMs directly (without using a tool like LangChain), consider using [manual AI instrumentation](/product/insights/llm-monitoring/getting-started/#manually-instrumenting-ai-workloads).
-</Note>
+</Alert>
 
 ## Where AI Data Shows Up In the Trace View
 
diff --git a/docs/product/insights/backend/queries.mdx b/docs/product/insights/backend/queries.mdx
index 5ec0058e341e87..05cd6feb9f9b57 100644
--- a/docs/product/insights/backend/queries.mdx
+++ b/docs/product/insights/backend/queries.mdx
@@ -90,11 +90,11 @@ If you want to investigate a specific endpoint, click on it to open a sidebar sh
 
 ## Query Sources
 
-<Note>
+<Alert>
 
 Query Sources are currently supported in Sentry's [Laravel](/platforms/php/guides/laravel/configuration/laravel-options/#more-configuration) (enabled by default) and [Python](/platforms/python/configuration/options/#enable-db-query-source) (enabled by default) SDKs. Sentry only attaches query sources to queries that are slower than a configurable threshold ([Python](/platforms/python/configuration/options/#db-query-source-threshold-ms), [Laravel](/platforms/php/guides/laravel/configuration/laravel-options/#more-configuration)) to reduce the performance impact.
 
-</Note>
+</Alert>
 
 A query's source is the location in your application's code that triggered the query. Sentry automatically determines the query source by examining the stack trace and attaches the source to the query data.
 
diff --git a/docs/product/insights/frontend/assets.mdx b/docs/product/insights/frontend/assets.mdx
index fbddae92802780..e82220d2855715 100644
--- a/docs/product/insights/frontend/assets.mdx
+++ b/docs/product/insights/frontend/assets.mdx
@@ -116,13 +116,13 @@ The following tokens will be replaced with \* within a asset url
 5. Strings longer then 25 characters
 6. The entire path except for common path segments such as static, chunks, media, etc
 
-<Note>
+<Alert>
 
 Asset parametrization is still a work-in-progress. As these improvements are made, you will will temporarily see instances of the new and old groupings in your Asset Module.
 
 Let us know of any feedback through Github Issues.
 
-</Note>
+</Alert>
 
 To see an example of asset URL from a group, hover over a URL in the asset table.
 
diff --git a/docs/product/insights/frontend/web-vitals/index.mdx b/docs/product/insights/frontend/web-vitals/index.mdx
index 8f45c5d04b6e3e..74f587f3e91272 100644
--- a/docs/product/insights/frontend/web-vitals/index.mdx
+++ b/docs/product/insights/frontend/web-vitals/index.mdx
@@ -24,11 +24,11 @@ Below this, you can see your application's p75 vital values and the individual s
 
 At the bottom of the **Web Vitals** page, a sortable table shows a list of your application's pages, along with their associated p75 values for each Web Vital. Each page also has its own individual Performance Score. The Opportunity column displays a page score's potential improvement to your application's overall Performance Score if maximized to 100. The search bar above this table allows you to filter for specific pages by route name.
 
-<Note>
+<Alert>
 
 The **Web Vitals** page only displays data from your application's initial page load transactions and interactions. Navigations are not included.
 
-</Note>
+</Alert>
 
 ## Page Overview
 
@@ -38,9 +38,9 @@ The **Page Overview** page displays a "Page Loads" chart in the right sidebar of
 
 ### Samples List
 
-<Note>
+<Alert>
 The samples list only shows page loads with web vitals and performance score. If a page load is missing a required web vital, it will not be shown in the samples list. Find out which web vitals are required in the [Browser Support](/product/performance/web-vitals/web-vitals-concepts/#browser-support) table.
-</Note>
+</Alert>
 
 At the center of the **Page Overview**, Web Vital p75 values and scores are displayed. Clicking a Web Vital score will open a slideout panel containing a variety of **Page Load** samples with good to poor scores. Each sample contains an **Event ID** that can be clicked to open the [Trace View](/concepts/key-terms/tracing/trace-view/#product-walkthrough-trace-details-page) page for further investigation. If there is a [Replay](/product/session-replay/) or [Profile](/product/profiling/) associated with the sample page load, links will be included in the associated table columns.
 
@@ -70,11 +70,11 @@ At the center of the **Page Overview**, Web Vital p75 values and scores are disp
 | [Time To First Byte](/product/insights/web-vitals/web-vitals-concepts/#time-to-first-byte-ttfb) (TTFB)           | [800ms](https://www.desmos.com/calculator/xcpjhfvwfo)  | [1800ms](https://www.desmos.com/calculator/xcpjhfvwfo)  | 10%   |
 | [Interaction to Next Paint](/product/insights/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp) (INP)   | [200ms](https://www.desmos.com/calculator/jaqxodpx8d)  | [500ms](https://www.desmos.com/calculator/jaqxodpx8d)  | 30%   |
 
-<Note>
+<Alert>
 These thresholds are meant to match Google Lighthouse as closely as possible, but there may be some differences because Sentry operates on real user data, whereas Google Lighthouse operates on lab data.
 
 Some browsers may not support all **Web Vitals** used in Sentry's **Performance Score** calculation. Look at the [Browser Support](/product/insights/web-vitals/web-vitals-concepts/#browser-support) table to see which Web Vitals are supported by your browser.
-</Note>
+</Alert>
 
 ## Opportunity
 
@@ -96,5 +96,5 @@ You can find out how to set up Sentry on your web application in the [installati
 Although Sentry provides auto instrumentation for many frontend frameworks, there are some environments and scenarios that may not be fully supported. If you are unable to find your pages in the **Web Vitals** page, check to see if your page loads are meeting the following conditions:
 
 - **Performance Scores** only support **Chrome**, **Firefox**, **Safari**, **Opera**, and **Edge** desktop and mobile browsers.
-- Some pageloads may not capture all web vitals supported by Sentry. This may depending on the client browser and/or the unique behavior of your web page. **Performance Score** are calculated based on available web vitals. 
-    - Find out the full list of web vitals in the [Browser Support](/product/insights/web-vitals/web-vitals-concepts/#browser-support) table.
\ No newline at end of file
+- Some pageloads may not capture all web vitals supported by Sentry. This may depending on the client browser and/or the unique behavior of your web page. **Performance Score** are calculated based on available web vitals.
+    - Find out the full list of web vitals in the [Browser Support](/product/insights/web-vitals/web-vitals-concepts/#browser-support) table.
diff --git a/docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx b/docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx
index 034d2f4ef13a57..0527896e6768c7 100644
--- a/docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx
+++ b/docs/product/insights/frontend/web-vitals/web-vitals-concepts.mdx
@@ -23,9 +23,9 @@ Google considers Core Web Vitals to be the most important metrics for measuring
 
 ### Interaction to Next Paint (INP)
 
-<Note>
+<Alert>
 On March 12, 2024, Interaction to Next Paint (INP) replaced First Input Delay (FID) as a Core Web Vital. Prior to this, INP was an experimental metric that Sentry did not collect. To begin collecting INP measurements, make sure your Javascript SDK version is [7.104.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.104.0) or higher and that the option [`enableInp`](/platforms/javascript/tracing/instrumentation/automatic-instrumentation/#enableinp) is on.
-</Note>
+</Alert>
 
 [Interaction to Next Paint (INP)](https://web.dev/articles/inp) measures the time from when a user interacts with a page (through a click, tap, or keyboard input) to when the next paint (rendering of content on the screen) occurs. INP aims to assess how quickly users see a response from the website after taking an action, which is crucial for providing a smooth and responsive user experience.
 
@@ -61,9 +61,9 @@ First Paint (FP) measures the amount of time the first pixel takes to appear in
 
 ### First Input Delay (FID)
 
-<Note>
+<Alert>
 As of March 12, 2024, First Input Delay (FID) was replaced as a Core Web Vital by INP. While Sentry no longer includes FID in our performance score calculations nor on the **Web Vitals** performance page, we continue to collect FID metrics. You can query FID measurements in [Discover](/product/explore/discover-queries/).
-</Note>
+</Alert>
 
 [First Input Delay (FID)](https://web.dev/fid/) measures response time when a user tries to interact with the viewport by clicking a button, link, or any other custom JavaScript controller. FID data is critical for understanding whether interactions on an application page are successful or not.
 
@@ -82,11 +82,11 @@ Google's "Good", "Needs Improvement", and "Poor" thresholds are used to classify
 | [Time To First Byte](#time-to-first-byte-ttfb) (TTFB)           | &lt;= 100ms | &lt;= 200ms | > 600ms |
 | [First Input Delay](#first-input-delay-fid) (FID)               | &lt;= 100ms | &lt;= 300ms | > 300ms |
 
-<Note>
+<Alert>
 
 Some Web Vitals such as FP, FCP, LCP, and TTFB are measured relative to the start of the transaction. Values may differ when compared to values generated with other tools such as [Lighthouse](https://github.com/GoogleChrome/lighthouse).
 
-</Note>
+</Alert>
 
 
 ## Browser Support
diff --git a/docs/product/issues/grouping-and-fingerprints/index.mdx b/docs/product/issues/grouping-and-fingerprints/index.mdx
index 15c921a6a5dcfb..14bb353faba26e 100644
--- a/docs/product/issues/grouping-and-fingerprints/index.mdx
+++ b/docs/product/issues/grouping-and-fingerprints/index.mdx
@@ -27,11 +27,11 @@ Even if a set of issues in the Issues Stream looks similar, if they are separate
 
 ## Changing How Events are Grouped
 
-<Note>
+<Alert>
 
 The solutions described in this section are only applicable to [error issues](/product/issues/issue-details/error-issues/). Other categories of issues (such as [performance issues](/product/issues/issue-details/performance-issues/)) do not support this feature.
 
-</Note>
+</Alert>
 
 There are four different ways to change how events are grouped into issues.
 
diff --git a/docs/product/issues/index.mdx b/docs/product/issues/index.mdx
index e764a95c063e4e..98c614efe01bea 100644
--- a/docs/product/issues/index.mdx
+++ b/docs/product/issues/index.mdx
@@ -12,13 +12,13 @@ A typical application sends a large number of events to Sentry. You can think of
 
 <a name="quota"></a>
 
-<Note>
+<Alert>
 
 **Issues and Event Quotas**
 
 Your quota is consumed by _events_, not _issues_. Issues are generated from your accepted error or transaction events. Generating issues does not cause Sentry to accept more events for you and **does not** directly impact your quota. Sentry does provide tools, however, to control the type and amount of error and transaction events that are accepted. Learn more in [Quota Management](/pricing/quotas/).
 
-</Note>
+</Alert>
 
 For each issue, the page displays:
 
diff --git a/docs/product/explore/feature-flags/index.mdx b/docs/product/issues/issue-details/feature-flags/index.mdx
similarity index 97%
rename from docs/product/explore/feature-flags/index.mdx
rename to docs/product/issues/issue-details/feature-flags/index.mdx
index ddf19e704d1ce7..ba074203b520cf 100644
--- a/docs/product/explore/feature-flags/index.mdx
+++ b/docs/product/issues/issue-details/feature-flags/index.mdx
@@ -4,7 +4,7 @@ sidebar_order: 100
 description: "Learn how to set up and interact with Sentry's feature flag evaluation tracking and feature flag change tracking."
 ---
 
-<Alert level="info" title="Currently in Beta">
+<Alert title="Currently in Beta">
 
 Feature flag change tracking and feature flag evaluation tracking is currently in open beta.
 
diff --git a/docs/product/issues/issue-details/index.mdx b/docs/product/issues/issue-details/index.mdx
index 91a5f50aa03865..4cd2edcaa55642 100644
--- a/docs/product/issues/issue-details/index.mdx
+++ b/docs/product/issues/issue-details/index.mdx
@@ -145,7 +145,7 @@ You can set up your own context items to collect useful debugging information in
 
 ## Feature Flags
 
-<Alert level="info" title="Currently in Beta">
+<Alert title="Currently in Beta">
 
 Feature flag change tracking and feature flag evaluation tracking is currently in open beta.
 
diff --git a/docs/product/issues/issue-details/performance-issues/consecutive-http/index.mdx b/docs/product/issues/issue-details/performance-issues/consecutive-http/index.mdx
index 07555683bac493..58e6c70c5fcd71 100644
--- a/docs/product/issues/issue-details/performance-issues/consecutive-http/index.mdx
+++ b/docs/product/issues/issue-details/performance-issues/consecutive-http/index.mdx
@@ -8,11 +8,11 @@ Consecutive HTTP issues are created when a at least 2000ms of time can be saved
 
 ## Detection Criteria
 
-<Note>
+<Alert>
 
 This issue is currently only available for backend and mobile SDKs.
 
-</Note>
+</Alert>
 
 The detector for this performance issue looks for a set of sequential, non-overlapping HTTP spans. It intentionally ignores non-HTTP spans because the browser commonly performs other asynchronous operations, such as loading resources between HTTP spans.
 
diff --git a/docs/product/issues/issue-details/performance-issues/frame-drop/index.mdx b/docs/product/issues/issue-details/performance-issues/frame-drop/index.mdx
index 648552f0fe2cc0..61ae08868b9f65 100644
--- a/docs/product/issues/issue-details/performance-issues/frame-drop/index.mdx
+++ b/docs/product/issues/issue-details/performance-issues/frame-drop/index.mdx
@@ -12,11 +12,11 @@ We can detect some specific causes for a main thread stall, like decoding [image
 
 [Profiling](/product/explore/profiling/) must be enabled for Sentry to detect Frame Drop issues. Once set up, Sentry will look for profiles that record a frozen UI frame and then search for the most time-consuming application function call delaying the display link's next vsync. In a run of functions calling through without any self-time, the deepest call will be chosen.
 
-<Note>
+<Alert>
 
 The minimum supported version for Cocoa is `8.12.0`.
 
-</Note>
+</Alert>
 
 ## Function Evidence
 
diff --git a/docs/product/issues/issue-details/performance-issues/http-overhead/index.mdx b/docs/product/issues/issue-details/performance-issues/http-overhead/index.mdx
index 535db1634a3513..1e89ccd4e2f358 100644
--- a/docs/product/issues/issue-details/performance-issues/http-overhead/index.mdx
+++ b/docs/product/issues/issue-details/performance-issues/http-overhead/index.mdx
@@ -8,11 +8,11 @@ HTTP/1.1 overhead issues are created when a set of overlapping HTTP spans for th
 
 ## Detection Criteria
 
-<Note>
+<Alert>
 
 This issue is currently only available for browser SDKs.
 
-</Note>
+</Alert>
 
 The detector for this performance issue looks for a set of overlapping HTTP/1.1 spans that are getting slower because the request itself is being delayed. This is a problem for HTTP/1.1 because of browser connection limits.
 
diff --git a/docs/product/issues/issue-details/performance-issues/index.mdx b/docs/product/issues/issue-details/performance-issues/index.mdx
index 452c81cfb57272..aabad22262f9c6 100644
--- a/docs/product/issues/issue-details/performance-issues/index.mdx
+++ b/docs/product/issues/issue-details/performance-issues/index.mdx
@@ -10,11 +10,11 @@ The **Issue Details** page helps you to gain further insight into the source of
 
 ![Performance issue](./img/performance-issue-details.png)
 
-<Note>
+<Alert>
 
 You can find performance issues by searching `issue.category:performance` in **Issues** and **Dashboards**.
 
-</Note>
+</Alert>
 
 While the **Issue Details** page displays information about a specific transaction event that's part of an issue, you can navigate between the events of an issue using the "Older" and "Newer" buttons. On this page, you'll see information about the performance issue as well as the details of the most recent transaction event. The page also displays a summary of when the issue was seen, as well as a breakdown of the tags, span evidence, and breadcrumbs if they are available.
 
diff --git a/docs/product/issues/issue-details/performance-issues/slow-db-queries/index.mdx b/docs/product/issues/issue-details/performance-issues/slow-db-queries/index.mdx
index 8d3cc198bbc563..810275e7452b05 100644
--- a/docs/product/issues/issue-details/performance-issues/slow-db-queries/index.mdx
+++ b/docs/product/issues/issue-details/performance-issues/slow-db-queries/index.mdx
@@ -21,11 +21,11 @@ You can configure detector thresholds for Slow DB Query issues in **Project Sett
 
 ![Slow DB Query detector threshold settings](./img/slow-db-queries-detector-settings.png)
 
-<Note>
+<Alert>
 
 These settings can only be edited by users with owner, manager, or team-level admin roles.
 
-</Note>
+</Alert>
 
 ## Span Evidence
 
diff --git a/docs/product/issues/issue-details/replay-issues/index.mdx b/docs/product/issues/issue-details/replay-issues/index.mdx
index 93df691e88751f..6edd302dd8ef96 100644
--- a/docs/product/issues/issue-details/replay-issues/index.mdx
+++ b/docs/product/issues/issue-details/replay-issues/index.mdx
@@ -8,9 +8,9 @@ If you've enabled [Session Replay](/product/explore/session-replay/), you'll be
 
 ## Quota Consumption
 
-<Note>
+<Alert>
 Replay issues do not consume error quota.
-</Note>
+</Alert>
 
 When a replay is created it consumes [replay quota](/pricing/quotas/manage-replay-quota/) (not to be confused with [error quota](/pricing/quotas/manage-event-stream-guide/)). As the replay is being processed by the server Sentry detects the replay issue types listed below and groups those into issues. These errors are created on the backend after ingest and do not consume error quota. They will not appear on your [stats](https://sentry.io/orgredirect/organizations/:orgslug/stats/) page under the "Total Errors" or "Accepted Errors" graphs. You are not billed for their volume.
 
diff --git a/docs/product/issues/issue-details/replay-issues/rage-clicks.mdx b/docs/product/issues/issue-details/replay-issues/rage-clicks.mdx
index 32b36f39577825..2b397cb6ffc16d 100644
--- a/docs/product/issues/issue-details/replay-issues/rage-clicks.mdx
+++ b/docs/product/issues/issue-details/replay-issues/rage-clicks.mdx
@@ -15,9 +15,9 @@ In order to see rage clicks in your issue stream on the **Issues** page, your or
 - Be sending [Session Replay events](/product/explore/session-replay/getting-started/)
 - Enable the JavaScript SDK (or framework-specific bundle), version 7.60.1 or higher
 
-<Note>
+<Alert>
 While you can enable **Session Replay** with JavaScript SDK version 7.27.0, or higher, you'll need to have version 7.60.1 or higher in order to be able to see **rage click issues**.
-</Note>
+</Alert>
 
 ## Detection Criteria
 
diff --git a/docs/product/issues/issue-details/sentry-ai/index.mdx b/docs/product/issues/issue-details/sentry-ai/index.mdx
index d9ed47f1fd1f9a..b953634f03a9ff 100644
--- a/docs/product/issues/issue-details/sentry-ai/index.mdx
+++ b/docs/product/issues/issue-details/sentry-ai/index.mdx
@@ -19,13 +19,13 @@ The Issue Summary provides a quick overview of an issue by highlighting key insi
 
 ## Autofix
 
-<Note>
+<Alert>
 
  Autofix replaces Suggested Fix (an earlier feature that has been sunset).
- 
- </Note>
 
-**Autofix** uses the issue details, your codebase (integrated through GitHub), and its interactions with you to gain context, reason through the problem, and get a deeper understanding of the root cause. 
+ </Alert>
+
+**Autofix** uses the issue details, your codebase (integrated through GitHub), and its interactions with you to gain context, reason through the problem, and get a deeper understanding of the root cause.
 
 When you start an Autofix run, you'll see the following screen, with an option to share any additional context:
 
@@ -64,4 +64,3 @@ You can learn more about our data privacy practices [here](https://docs.sentry.i
 
 If you don't find the feature useful and want to disable it for all users, you
 can do so in your organization's settings with the "Hide AI Features" toggle. Also remember that the features won't be available until the proper consent is given for your organization.
-
diff --git a/docs/product/issues/issue-priority/index.mdx b/docs/product/issues/issue-priority/index.mdx
index 2369a58fbdb73c..00de14a6ccde2d 100644
--- a/docs/product/issues/issue-priority/index.mdx
+++ b/docs/product/issues/issue-priority/index.mdx
@@ -18,11 +18,11 @@ There are three discrete priority levels for issues in Sentry:
 
 ### Enhanced Issue Priority
 
-<Note>
+<Alert>
 
 This feature is available only if your organization is on either a [Business](https://sentry.io/pricing/) or [Trial](/pricing/#product-trials) Plan.
 
-</Note>
+</Alert>
 
 In addition to the log level or actionability, the enhanced priority calculations will consider factors such as the error message, whether or not the error is handled, and historical actions taken on similar issues, when determining the priority of an issue for Python or JavaScript projects.
 
diff --git a/docs/product/issues/issue-views/index.mdx b/docs/product/issues/issue-views/index.mdx
index c0326bfcafa5e1..ff42c79998cc58 100644
--- a/docs/product/issues/issue-views/index.mdx
+++ b/docs/product/issues/issue-views/index.mdx
@@ -6,9 +6,9 @@ description: "Learn how to customize your issue stream in Sentry and quickly see
 
 Issue views let you customize what shows up in your issue stream so you can quickly see what's most important to you. You have full control over which search query your issue stream renders by default, and which other queries are within a click's reach.
 
-<Note>
+<Alert>
   This feature is only available if your organization has enabled [early adopter features](/organization/early-adopter-features/). Early adopter features are still in-progress and may have bugs. We recognize the irony. If you’re interested in participating, enable early adopter features in [organization settings](https://sentry.io/orgredirect/organizations/:orgslug/settings/organization).
-</Note>
+</Alert>
 
 ## Creating Your First View
 
@@ -24,9 +24,9 @@ Here, you'll be able to select a view from one of the recommended options or cre
 3. **Set your view's sort**: Select how you want the issues to be sorted in this view (for example, by date, events, and so on).
 4. **Save your view**: Click on the ellipsis menu within the tab and select **Save Changes**.
 
-<Note>
+<Alert>
 If you had a default custom saved search, it'll be converted to an issue view and will appear as your default view automatically, just like before. Any other saved searches you created will be available in the **Add View** menu until the end of the year. Please save them as views if you'd like to keep them.
-</Note>
+</Alert>
 
 ## Customizing Your Views
 
diff --git a/docs/product/issues/ownership-rules/index.mdx b/docs/product/issues/ownership-rules/index.mdx
index 750bf2ab478336..117766ed9835cb 100644
--- a/docs/product/issues/ownership-rules/index.mdx
+++ b/docs/product/issues/ownership-rules/index.mdx
@@ -80,7 +80,7 @@ This feature supports GitHub and GitLab CODEOWNERS file syntax with the followin
 - [GitLab Premium syntax](https://docs.gitlab.com/ee/user/project/code_owners.html#code-owners-sections)
 - [GitHub CODEOWNERS syntax exceptions](https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-repository-on-github/about-code-owners#syntax-exceptions)
 
-<Alert level="info">
+<Alert>
 
 Ownership rules take precedence over the information provided by your CODEOWNERS file when Sentry assigns issues.
 
diff --git a/docs/product/issues/states-triage/escalating-issues/index.mdx b/docs/product/issues/states-triage/escalating-issues/index.mdx
index c14d2c1a67209f..a7a277c4003604 100644
--- a/docs/product/issues/states-triage/escalating-issues/index.mdx
+++ b/docs/product/issues/states-triage/escalating-issues/index.mdx
@@ -6,7 +6,7 @@ description: "Learn how the escalating issues algorithm works."
 
 <Include name="merge-escalating-note.mdx" />
 
-By default, issues are archived until escalating. Sentry defines an issue as `Escalating` when the number of events is significantly higher than the previous week.
+By default, archived issues will transition to unresolved when the event count escalates. Sentry defines an issue as `Escalating` when the number of events is significantly higher than the previous week.
 
 The escalating issues algorithm uses historical data from the previous week to calculate thresholds for the next week on a per-issue basis. If an archived issue exceeds its predetermined threshold, it gets tagged as `Escalating`, unless it was "[Archived Forever](/product/issues/states-triage/#archive)". An escalating issue is automatically surfaced in the "Unresolved" and "Escalating" tabs.
 
diff --git a/docs/product/issues/states-triage/index.mdx b/docs/product/issues/states-triage/index.mdx
index 358117ab5ac3db..3c241a805bd0f6 100644
--- a/docs/product/issues/states-triage/index.mdx
+++ b/docs/product/issues/states-triage/index.mdx
@@ -60,8 +60,8 @@ You can remove an issue from the issue list by deleting it, but it will reappear
 
 There's also an option to `Delete and Discard Forever`, which will make it so that the issue is never seen again, even if it recurs. Any future events tied to the permanently deleted issue will be discarded automatically and won't count towards [your quota](/pricing/quotas/).
 
-<Note>
+<Alert>
 
 You can only delete [Error Issues](/product/issues/issue-details/error-issues/?original_referrer=https%3A%2F%2Fdocs.sentry.io%2Fproduct%2Fissues%2Fstates-triage%2F). Other issue categories, such as [Performance Issues](/product/issues/issue-details/performance-issues/?original_referrer=https%3A%2F%2Fdocs.sentry.io%2Fproduct%2Fissues%2Fstates-triage%2F), don't support this feature.
 
-</Note>
+</Alert>
diff --git a/docs/product/issues/suspect-commits/index.mdx b/docs/product/issues/suspect-commits/index.mdx
index a023ca6d826099..dbd0fb746ab5aa 100644
--- a/docs/product/issues/suspect-commits/index.mdx
+++ b/docs/product/issues/suspect-commits/index.mdx
@@ -38,11 +38,11 @@ In [sentry.io](https://sentry.io):
 
 ### Set Up Code Mappings
 
-<Note>
+<Alert>
 
 Sentry will automatically try to set up code mappings on C#, Go, JavaScript, Node.js, PHP, Python, and Ruby projects for organizations with the GitHub integration installed. However, you can still manually add code mappings if you choose to do so. Support for other languages and other source code integrations are planned.
 
-</Note>
+</Alert>
 
 1. Go to **Settings > Integrations > [Integration] > Configurations**.
 1. Click the "Configure" button.
@@ -59,11 +59,11 @@ Sentry will automatically try to set up code mappings on C#, Go, JavaScript, Nod
 
 #### Stack Trace Root and Source Code Root
 
-<Note>
+<Alert>
 
 The following information is only valid for platforms which use traditional file paths. Platforms with package names require additional steps. For **Java**, read more in the [page on source context](/platforms/java/source-context#setting-up-code-mappings).
 
-</Note>
+</Alert>
 
 First, navigate to a stack trace that you wish to map. Find an **In App** frame, which is denoted by a bubble on the right side of the frame. The filename will be shown as the first piece of text at the left hand side of the frame header. In this example, it is `src/main.py`.
 
diff --git a/docs/product/performance/filters-display/widgets.mdx b/docs/product/performance/filters-display/widgets.mdx
index c8d8991233df79..bc5dfbe261ff40 100644
--- a/docs/product/performance/filters-display/widgets.mdx
+++ b/docs/product/performance/filters-display/widgets.mdx
@@ -7,11 +7,11 @@ description: "Learn more about Sentry's Performance widgets such as Most Related
 Performance widgets offer visualizations that you can change to best match your workflow. They provide performance-specific views that allow you to see and act on transaction data across your organization.
 Depending on which [Performance Tab](/product/performance/filters-display/#tabs) you've selected, different curated performance widgets will be available.
 
-<Note>
+<Alert>
 
 The value displayed in the top right of some widgets is the **overall value for the selected time period**, not the average of the data displayed in the chart. For datasets with low event volume, the overall value may be higher or lower than expected because metrics like [Apdex](/product/performance/metrics/#apdex) and [User Misery](/product/performance/metrics/#user-misery) are non-linear.
 
-</Note>
+</Alert>
 
 ## Average TTIDs
 
diff --git a/docs/product/performance/index.mdx b/docs/product/performance/index.mdx
index 9f016b49a8f862..eec381abc50bfd 100644
--- a/docs/product/performance/index.mdx
+++ b/docs/product/performance/index.mdx
@@ -8,11 +8,11 @@ description: "With performance monitoring, you can track, analyze, and debug you
 
 With performance monitoring, Sentry tracks application performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple services. Sentry captures [distributed traces](/product/sentry-basics/tracing/distributed-tracing/) consisting of [transactions](/product/performance/transaction-summary/#what-is-a-transaction) and spans to measure individual services and operations within those services.
 
-<Note>
+<Alert>
 
 Learn more about traces in the [full Tracing documentation](/product/sentry-basics/tracing/).
 
-</Note>
+</Alert>
 
 The **Performance** page is the main view in [sentry.io](https://sentry.io) where you can search or browse for transaction data. A transaction represents a single instance of an activity you want to measure or track, such as a page load, page navigation, or an asynchronous task. The page displays graphs that visualize transactions or [trends](/product/performance/trends/), as well as a table where you can view relevant transactions and drill down to get more information about them.
 
@@ -40,13 +40,13 @@ There are several types of [metrics](/product/performance/metrics/) that you can
 
 ## Triage Performance Issues
 
-<Note>
+<Alert>
 
 **Issue and Event Quotas**
 
 Your quota is consumed by events or traces, not issues. Performance issues are generated from your accepted transactions, which **doesn't** directly impact your quota. Performance transaction events use transactions, which **does** directly impact your quota. Sentry provides tools to control the type and number of error and transaction events that are accepted. Learn more in [Quota Management](/pricing/quotas/manage-transaction-quota).
 
-</Note>
+</Alert>
 
 If your application is configured for Performance Monitoring, Sentry will detect common performance problems, and group them into issues just like it does with errors. Performance issues help to surface performance problems in your application and provide a workflow for resolving them. Learn more about [performance issues](/product/issues/issue-details/performance-issues/).
 
diff --git a/docs/product/performance/metrics.mdx b/docs/product/performance/metrics.mdx
index 2490c0ecf859ad..a127ff81bab8c3 100644
--- a/docs/product/performance/metrics.mdx
+++ b/docs/product/performance/metrics.mdx
@@ -81,11 +81,11 @@ The calculation accounts for the volume and proportion of users that experienced
 
 You can set satisfactory thresholds for each project with [custom thresholds](#custom-thresholds).
 
-<Note>
+<Alert>
 
 User Misery is calculated using a probability distribution. This prevents false positives and ensures reasonable values for datasets with low event volume. You can view the underlying data by querying for the [`count_miserable()` function](/product/explore/discover-queries/query-builder/#stacking-functions).
 
-</Note>
+</Alert>
 
 ## Custom Thresholds
 
diff --git a/docs/product/performance/performance-overhead.mdx b/docs/product/performance/performance-overhead.mdx
index af33d635e90416..f0d9b4c6a50deb 100644
--- a/docs/product/performance/performance-overhead.mdx
+++ b/docs/product/performance/performance-overhead.mdx
@@ -19,11 +19,11 @@ To perform this instrumentation, Sentry SDKs wrap or monkeypatch specific functi
 
 The SDKs also make sure to propagate some headers on outgoing requests so that [Distributed Tracing](/product/sentry-basics/tracing/) can work effectively.
 
-<Note>
+<Alert>
 
 For most applications, the performance overhead of enabling performance in production is imperceptible to end users.
 
-</Note>
+</Alert>
 
 ## Will Performance break my application?
 
diff --git a/docs/product/performance/retention-priorities/index.mdx b/docs/product/performance/retention-priorities/index.mdx
index 59deb0898a39b0..fa788d8f92d1f5 100644
--- a/docs/product/performance/retention-priorities/index.mdx
+++ b/docs/product/performance/retention-priorities/index.mdx
@@ -4,11 +4,11 @@ sidebar_order: 130
 description: "Learn how Sentry determines retention priorities and how to update them."
 ---
 
-<Note>
+<Alert>
 
 Retention priorities are only available on the latest version of our plans, starting from 1M reserved transactions. Anyone in your org with owner or billing-level permissions can update your plan by going to Settings > Subscription, and clicking the "Manage Subscription" button.
 
-</Note>
+</Alert>
 
 While storing all your data makes sense at relatively low volumes, as your application scales, storing a raw copy of all your data has diminishing returns. When data reaches high volumes, Sentry begins to automatically prioritize retaining certain transactions over others with server-side data retention strategies called retention priorities.
 
@@ -57,11 +57,11 @@ Since dev environments usually generate a small number of transactions as compar
 
 #### Low Volume Projects
 
-<Note>
+<Alert>
 
 You won't be able to disable the Low Volume Projects retention priority because it's set on an organization-wide level, not on a per-project basis.
 
-</Note>
+</Alert>
 
 Some projects within your organization are very high volume compared to others. This means that low-volume projects might get drowned out if we treat all projects equally. To ensure that you have enough samples regardless of project scale, we prioritize low-volume projects.
 
@@ -84,11 +84,11 @@ When you perform a query on transactions either in [Discover](/product/explore/d
 
 ![Investigation Mode in Discover](./img/investigation-bias-discover.png)
 
-<Note>
+<Alert>
 
 Please note that this feature only applies to transactions. Therefore, in Discover, you have to specify `event.type:transaction` in the query to access the feature, whereas in Performance the event type is implicit.
 
-</Note>
+</Alert>
 
 Clicking this button triggers the creation of an investigation rule for the respective query. After the successful creation of the rule, a notification will appear and the button for creating the investigation rule will be replaced by a message specifying that the investigation is in progress and the amount of time since it has been active.
 
@@ -130,9 +130,9 @@ To make changes to a project's retention priorities in Sentry, go to **Settings
 
 To give Sentry the fullest, most accurate picture of your application’s health, we recommend that you send us 100% of your transactions. You can do this by setting your [tracesSampleRate](/platform-redirect/?next=/performance/) to 1.0. If this isn't feasible for your organization, set a lower value, or switch to sampling selectively by using the [tracesSampler](/platform-redirect/?next=/performance/) to filter your transactions based on contextual data. Note that when calculating throughput, transaction metering is based on received transactions not stored transactions.
 
-<Note>
+<Alert>
   Please note that changes to your SDK sampling configuration may affect your
   quota. If you increase your SDK sampling rate, you'll also be increasing the
   volume of transactions you send to Sentry. This may require that you adjust
   your transaction quota.
-</Note>
+</Alert>
diff --git a/docs/product/performance/transaction-summary.mdx b/docs/product/performance/transaction-summary.mdx
index 49a815a96021a7..c3b272bf7765e1 100644
--- a/docs/product/performance/transaction-summary.mdx
+++ b/docs/product/performance/transaction-summary.mdx
@@ -14,11 +14,11 @@ A transaction represents a single instance of an activity you want to measure or
 
 Transactions on the **Performance** page are grouped by the transaction names, such as endpoint paths for backend request transactions (like `/store/checkout/` or `api/v2/users/<user_id>/`) or URLs/routes for page load transactions (like `https://docs.sentry.io/performance-monitoring/`). When you click a transaction on the **Performance** page, it takes you to the **Transaction Summary**, where you can see a list of transaction events: that is, the individual instances of that specific transaction.
 
-<Note>
+<Alert>
 
 Learn more about setting transaction names in our [SDK documentation](/platform-redirect/?next=/enriching-events/transaction-name/).
 
-</Note>
+</Alert>
 
 Learn about how to control the type and amount of transactions you send to Sentry, in [Manage Your Transaction Quota](/pricing/quotas/manage-transaction-quota/). For a more in-depth explanation of what’s in a transaction as it relates to traces, check out our [full tracing documentation](/product/sentry-basics/tracing/).
 
@@ -55,11 +55,11 @@ The table also updates dynamically if you change any of the project, environment
 
 When viewing transactions, you may want to create more curated views. Click "Open in Discover" above the table to create a custom query to investigate further. For more details, see the full documentation for the Discover [Query Builder](/product/explore/discover-queries/query-builder/).
 
-<Note>
+<Alert>
 
 Currently, only transaction data — the transaction name and any attributes the transaction inherits from its root span — is searchable. Data contained in spans other than the root span is not indexed and therefore cannot be searched.
 
-</Note>
+</Alert>
 
 ### Suspect Spans
 
@@ -123,11 +123,11 @@ Choose from one of several [metrics](#metrics) to sort spans and identify differ
 
 Clicking on a span will take you to its summary page which will give you more details about this specific span [group](#grouping). On the page, you can see the performance of the span over time and see a list of transaction events that contain the span.
 
-<Note>
+<Alert>
 
 This span distribution feature is available only if you're in the Early Adopter program. Features available to Early Adopters are still in-progress and may have bugs. We recognize the irony. If you’re interested in being an Early Adopter, you can turn your organization’s Early Adopter status on/off in General Settings. This will affect all users in your organization and can be turned back off just as easily.
 
-</Note>
+</Alert>
 
 If you're in the Early Adopter program, you can also see the distribution of the span self time using the (added) "Display" dropdown. This histogram can help you identify systemic performance issues across the entire dataset by showing how self time for every span instance is distributed.
 
diff --git a/docs/product/relay/getting-started.mdx b/docs/product/relay/getting-started.mdx
index e9dd3656d3b9cf..04c8e2263e5b76 100644
--- a/docs/product/relay/getting-started.mdx
+++ b/docs/product/relay/getting-started.mdx
@@ -6,12 +6,12 @@ sidebar_order: 1
 
 Getting started with [Relay](/product/relay/) is as simple as using the default settings. You can also configure Relay to suit your organization's needs. Check the [Configuration Options](../options/) page for a detailed discussion of operating scenarios.
 
-<Note>
+<Alert>
 
 The Relay server is called `relay`. Download binaries from [GitHub
 Releases](https://github.com/getsentry/relay/releases). A Docker image is provided on [DockerHub](https://hub.docker.com/r/getsentry/relay/).
 
-</Note>
+</Alert>
 
 ## Initializing Configuration
 
@@ -19,14 +19,14 @@ To create the initial configuration, use Relay's `relay config init` command,
 which puts configuration files in the `.relay` folder under the current working
 directory.
 
-<Note>
+<Alert>
 
 In Docker, provide the configuration directory using the standard
 mechanisms offered by Docker, either by mounting [Docker
 volumes](https://docs.docker.com/storage/volumes/) or by building a new
 container and copying in the files.
 
-</Note>
+</Alert>
 
 ```shell {tabTitle:Run in Docker}
 # Adjust permissions for the configuration directory
@@ -94,7 +94,7 @@ Configurations are fully documented in [Configuration Options](../options/).
 
 ## Creating Credentials
 
-<Alert level="info">
+<Alert>
 
 Not applicable in `proxy` or `static` mode.
 
@@ -118,7 +118,7 @@ Use the `public_key` to register your Relay with the upstream server when runnin
 
 ## Registering Relay with Sentry
 
-<Alert level="info">
+<Alert>
 
 Not applicable in `proxy` or `static` mode.
 
diff --git a/docs/product/relay/index.mdx b/docs/product/relay/index.mdx
index dcd84276461f14..d843004d192c8b 100644
--- a/docs/product/relay/index.mdx
+++ b/docs/product/relay/index.mdx
@@ -12,11 +12,11 @@ Relay is specifically designed to:
 - Improve event response time in regions with low bandwidth or limited connectivity
 - Act as an opaque proxy for organizations that restrict all HTTP communication to a custom domain name
 
-<Note>
+<Alert>
 
 Relay in `managed` mode is available only on the [Business and Enterprise plans](https://sentry.io/pricing/).
 
-</Note>
+</Alert>
 
 ## Use Cases for Relay
 
diff --git a/docs/product/relay/modes/index.mdx b/docs/product/relay/modes/index.mdx
index bc37aa4df988c1..e8ce65dab5e59e 100644
--- a/docs/product/relay/modes/index.mdx
+++ b/docs/product/relay/modes/index.mdx
@@ -8,11 +8,11 @@ Relay can operate in one of several major modes, and it is critical to understan
 
 The mode is stored in the configuration file, which contains the `relay.mode` field. This field specifies the mode in which Relay will run: `managed`, `static`, or `proxy`. The Relay mode controls the way Relay obtains project settings for events.
 
-<Note>
+<Alert>
 
 Relay in `managed` mode is available only on the [Business and Enterprise plans](https://sentry.io/pricing/).
 
-</Note>
+</Alert>
 
 In Sentry, event processing is configured according to both project and organization settings. Some settings, such as privacy controls, are set at the organization level, then inherited by all projects in that organization; other settings are specified per project. For Relay, events are processed according to the inherited project settings to which the event is sent.
 
@@ -40,7 +40,7 @@ In static mode, projects must be configured manually. In this mode, Relay will p
 
 This mode is useful when you know the projects sending events and you need to explicitly control the projects allowed to send events through this Relay.
 
-<Alert level="info" title="Note">
+<Alert title="Note">
 
 In `static` mode, Relay does not register with upstream since it does not query
 information from it. After processing events for configured projects, it
@@ -67,7 +67,7 @@ identically to `static` mode. Events for unknown projects -- projects for which
 there are no statically configured settings -- are forwarded (proxied) with
 minimal processing.
 
-<Alert level="info" title="Rate Limiting">
+<Alert title="Rate Limiting">
 
 Rate limiting is still applied in `proxy` mode for all projects,
 regardless of whether they are statically configured or proxied.
diff --git a/docs/product/relay/modes/pii-and-data-scrubbing.mdx b/docs/product/relay/modes/pii-and-data-scrubbing.mdx
index a0de09be040481..13cb8009fb9cd4 100644
--- a/docs/product/relay/modes/pii-and-data-scrubbing.mdx
+++ b/docs/product/relay/modes/pii-and-data-scrubbing.mdx
@@ -6,12 +6,12 @@ sidebar_order: 7
 
 The following document explores the syntax and semantics of the configuration for [Advanced Data Scrubbing], as consumed and executed by [Relay]. Sometimes, this is also referred to as PII scrubbing.
 
-<Note>
+<Alert>
 
 This guide applies when you are running Relay in [Static Mode](/product/relay/modes/), and you do not want sensitive data to leave your premises.
 If you are running Managed Mode, _or_ you are OK with sensitive data being scrubbed by Sentry's own servers, refer to [Server-Side Data Scrubbing](/security-legal-pii/scrubbing/server-side-scrubbing/) instead.
 
-</Note>
+</Alert>
 
 ## A Basic Example
 
diff --git a/docs/product/relay/operating-guidelines.mdx b/docs/product/relay/operating-guidelines.mdx
index b7d71d0012b40b..02e6fbf793d049 100644
--- a/docs/product/relay/operating-guidelines.mdx
+++ b/docs/product/relay/operating-guidelines.mdx
@@ -105,7 +105,7 @@ Depending on the SDK or client, requests to these endpoints are performed with c
 - `X-Forwarded-For`: to the client IP address
 - `X-Sentry-Auth`: to the value provided by the client
 
-<Alert level="info">
+<Alert>
 
 Proxies often set a default maximum body size for requests. Especially native crash reports and attachments can exceed these limits. We recommend to configure a maximum client body size of _100MB_.
 
diff --git a/docs/product/relay/projects.mdx b/docs/product/relay/projects.mdx
index 869616220902b7..6a2379215f859b 100644
--- a/docs/product/relay/projects.mdx
+++ b/docs/product/relay/projects.mdx
@@ -6,11 +6,11 @@ sidebar_order: 4
 
 When running Relay in either `static` or `proxy` mode, you can configure project settings on the file system. Static project configurations are found under the `projects` subdirectory of the Relay configuration directory, By default, this is located at `.relay/projects`.
 
-<Note>
+<Alert>
 
 Relay in `managed` mode is available only on the [Business and Enterprise plans](https://sentry.io/pricing/).
 
-</Note>
+</Alert>
 
 To configure projects, add files named `<PROJECT_ID>.json` in that location:
 
diff --git a/docs/product/releases/associate-commits/index.mdx b/docs/product/releases/associate-commits/index.mdx
index 26367832fccd9a..b36a8cad245c0c 100644
--- a/docs/product/releases/associate-commits/index.mdx
+++ b/docs/product/releases/associate-commits/index.mdx
@@ -61,10 +61,10 @@ The following example associates commits (or refs) between `from` and `to` with
 sentry-cli releases set-commits --commit "my-repo@from..to" $VERSION
 ```
 
-<Note>
+<Alert>
   The repository name `my-repo` should match the name you entered when linking
   the repo, and should be in the form `owner-name/repo-name`.
-</Note>
+</Alert>
 
 ### Using the API
 
@@ -133,11 +133,11 @@ The commit ID.
 
 Here is an example of a request using patch data:
 
-<Note>
+<Alert>
 
 Confirm you’re using [Auth Tokens](/api/auth/#auth-tokens), **not** [API Keys](/api/auth/#api-keys), which are deprecated.
 
-</Note>
+</Alert>
 
 ```bash
 curl https://sentry.io/api/0/organizations/your-organization-name/releases/ \
@@ -203,11 +203,11 @@ res = requests.post(
 
 For more information, see the [API reference](/api/releases/create-a-new-release-for-an-organization/).
 
-<Note>
+<Alert>
 
 If you receive an "Unable to Fetch Commits" email, take a look at our [help center article](https://sentry.zendesk.com/hc/en-us/articles/23968845267739-Why-am-I-receiving-the-email-Unable-to-Fetch-Commits).
 
-</Note>
+</Alert>
 
 ## Resolve Issues by Commit
 
@@ -223,8 +223,8 @@ Fixes SENTRY-317
 
 When Sentry sees this commit, we’ll reference the commit in the issue, and when you create a release in Sentry, we’ll mark the issue as resolved in that release. You can also resolve issues with pull requests by including `fixes <SENTRY-SHORT-ID>` in the title or description.
 
-<Note>
+<Alert>
 
 If you’re using GitHub, you may have a privacy setting enabled that prevents Sentry from identifying the user’s actual email address. To use the suggested owners feature, uncheck “Keep my email address private” in GitHub’s [account settings](https://github.com/settings/emails).
 
-</Note>
+</Alert>
diff --git a/docs/product/releases/health/index.mdx b/docs/product/releases/health/index.mdx
index 5c2ba29ecc0fcf..1dac33b09d7beb 100644
--- a/docs/product/releases/health/index.mdx
+++ b/docs/product/releases/health/index.mdx
@@ -4,11 +4,11 @@ sidebar_order: 50
 description: "Monitor the health of releases by observing user adoption, usage of the application, percentage of crashes, and session data."
 ---
 
-<Note>
+<Alert>
 
 Note, that Sessions (as described below) are not the same as a [Session Replay](/product/explore/session-replay/), (a video-like reproduction of the user's session). We don't bill for release health sessions.
 
-</Note>
+</Alert>
 
 You can monitor the health of releases by observing user adoption, usage of your application, percentage of [crashes](#crashes), and [session data](#sessions). Release health data provides insight into the impact of crashes and bugs related to user experience and reveals trends with each new issue through the release details, graphs, and filters. This data is primarily displayed on the [Releases](/product/releases/) and [Release Details](/product/releases/release-details) pages, but is also reflected in other parts of [sentry.io](https://sentry.io).
 
@@ -89,11 +89,11 @@ Depending on your "Display" selection, the sort options for the **Releases** pag
 
 A _crash_ is when the application had an explicit unhandled error or hard crash. You'll typically be able to view the corresponding issue that captures this event in [sentry.io](https://sentry.io), and errors that did not cause the end of the application should not be included. To search for crash events in **Discover** or on the **Issues** page, filter by `error.unhandled:true`.
 
-<Note>
+<Alert>
 
 Crash detection is not available for watchOS.
 
-</Note>
+</Alert>
 
 ### Crash Free Sessions/Users
 
@@ -109,7 +109,7 @@ Depending on your "Display" selection, the sort options for the **Releases** pag
 
 ![Sort By: Crash Free Users dropdown](./img/release_crash_free_users.png)
 
-<Alert level="info">
+<Alert>
 
 Please note that the number of crashes is not expected to match the number of crashed sessions because sessions are not subject to [inbound filters](/concepts/data-management/filtering/) or [sampling](/platform-redirect/?next=/configuration/sampling/).
 
@@ -132,11 +132,11 @@ The adoption progress bar is calculated as a percentage of sessions/users in thi
 
 ### Adoption Chart
 
-<Note>
+<Alert>
 
 This feature is applicable only if the project selected is available for mobile or desktop devices.
 
-</Note>
+</Alert>
 
 If you select a project that has release health configured, and there are releases and user/session data in the selected time period, an adoption chart is displayed. The chart provides you with adoption percentages for each release in the project, over time.
 
@@ -152,11 +152,11 @@ _Adoption stage_ is a high-level overview of the usage your release is seeing re
 
 ![Adoption stage label on the Releases page.](./img/adoption-stage-label.png)
 
-<Note>
+<Alert>
 
 Adoption stage labels are only displayed for mobile projects and only when you filter down to a single environment.
 
-</Note>
+</Alert>
 
 For each release, the release's percentage of sessions is calculated against all sessions in the same environment and project. It's then marked as being in one of three stages, based on a threshold of 10%. These stages are:
 
diff --git a/docs/product/releases/index.mdx b/docs/product/releases/index.mdx
index c8d09d71aa786d..a450d273995170 100644
--- a/docs/product/releases/index.mdx
+++ b/docs/product/releases/index.mdx
@@ -4,11 +4,11 @@ sidebar_order: 110
 description: "Learn how to provide information to Sentry about your releases to determine regressions and resolve issues quickly."
 ---
 
-<Note>
+<Alert>
 
 If you're looking for the latest Sentry SDK release details, head on over to <a href="https://github.com/getsentry" className="plausible-event-name=release+cta">Sentry's GitHub profile</a>, find your specific SDK repo, and browse the tags for releases.
 
-</Note>
+</Alert>
 
 A _release_ is a version of your code deployed to an environment. When you notify Sentry about a <SandboxLink scenario="oneRelease" projectSlug="react">release</SandboxLink>, you can easily identify new issues and regressions, determine whether an issue was resolved, and monitor the health of your newly deployed app. The **Releases** page provides a visualization of your releases. It presents adoption of releases from the past 24 hours and provides a high-level view of:
 
@@ -19,11 +19,11 @@ A _release_ is a version of your code deployed to an environment. When you notif
 - The percentage of crash-free users
 - The percentage of crash-free sessions
 
-<Note>
+<Alert>
 
 Crash and app hang detection are not available for watchOS.
 
-</Note>
+</Alert>
 
 ![View of the release index page showing each version of projects related to the release and the project details.](./img/release_index.png)
 
@@ -38,11 +38,11 @@ Releases offer significant additional features when [fully configured](/product/
 - Resolve issues by including the issue number in your commit message
 - [Receive email notifications when your code gets deployed](/product/alerts/notifications/#deploy-notifications)
 
-<Note>
+<Alert>
 
 We recommend notifying Sentry about a new release before deploying it. But if you don't, Sentry will automatically create a release entity in the system the first time it sees an event with that release identifier.
 
-</Note>
+</Alert>
 
 You don't need a repository integration for any of these features, though we recommend [installing one as part of an automated release option](/product/releases/setup/release-automation/) for efficiency.
 
diff --git a/docs/product/releases/setup/index.mdx b/docs/product/releases/setup/index.mdx
index 081de2b5a01f96..80048c84de70eb 100644
--- a/docs/product/releases/setup/index.mdx
+++ b/docs/product/releases/setup/index.mdx
@@ -12,11 +12,11 @@ If you're using one of our [release automation](/product/releases/setup/release-
 
 With your SDK configured to provide a release identifier and enable session tracking, you can monitor both [releases](/product/releases/) and [release health](/product/releases/health/). Check out the documentation for your specific platform to [configure the SDK](/platform-redirect/?next=/configuration/releases/).
 
-<Note>
+<Alert>
 
 You must have the environment [configured in your SDK](/platform-redirect/?next=/configuration/environments/) to use this feature.
 
-</Note>
+</Alert>
 
 ### Release Health
 
@@ -63,11 +63,11 @@ If you're not using one of our [release automation](/product/releases/setup/rele
 sentry-cli releases --org ORGANIZATION_SLUG deploys VERSION new -e ENVIRONMENT
 ```
 
-<Note>
+<Alert>
 
 Make sure you have a [token](/cli/configuration/) properly configured.
 
-</Note>
+</Alert>
 
 Typically, a release = a deployment, but if you have several environments in which you want to deploy a release, this step also allows you to create those deployments individually.
 
diff --git a/docs/product/releases/setup/release-automation/index.mdx b/docs/product/releases/setup/release-automation/index.mdx
index 82c9eb96c5b374..e2d8b53830c139 100644
--- a/docs/product/releases/setup/release-automation/index.mdx
+++ b/docs/product/releases/setup/release-automation/index.mdx
@@ -28,17 +28,17 @@ If you’re linking a GitHub repository, you must have Admin or Owner permission
 
 ![](./img/releases-repo-add.png)
 
-  <Note>
+  <Alert>
 
 If you’re having trouble adding the integration, [disconnect](https://sentry.io/account/settings/identities/) then [reconnect](https://sentry.io/account/settings/social/associate/github/) your GitHub identity.
 
-  </Note>
+  </Alert>
 
 <PageGrid />
 
 
-  <Note>
+  <Alert>
 
 The list above includes all platforms currently supported to automate the release management. If your platform is not included, you must use the [manual process](/product/releases/associate-commits/) to integrate release data.
 
-  </Note>
+  </Alert>
diff --git a/docs/product/releases/setup/release-automation/netlify/index.mdx b/docs/product/releases/setup/release-automation/netlify/index.mdx
index 0edadb156813a4..f64b01984847f3 100644
--- a/docs/product/releases/setup/release-automation/netlify/index.mdx
+++ b/docs/product/releases/setup/release-automation/netlify/index.mdx
@@ -15,7 +15,7 @@ Full docs are available in the [plugin's README](https://github.com/getsentry/se
 
 For more details about Sentry release management concepts, see our docs on [releases](/product/releases/).
 
-<Alert level="note">
+<Alert>
 
 Note: This build plugin is separate from `@netlify/sentry`, which is a monitoring plugin built by Netlify. Docs for that plugin can be found [here](https://docs.netlify.com/netlify-labs/experimental-features/sentry-integration/). For more information, see [`@sentry/netlify-build-plugin` vs. `@netlify/sentry`](https://github.com/getsentry/sentry-netlify-build-plugin#sentrynetlify-build-plugin-vs-netlifysentry).
 
diff --git a/docs/product/sentry-basics/integrate-backend/capturing-errors.mdx b/docs/product/sentry-basics/integrate-backend/capturing-errors.mdx
index 0537f3e1c06198..29b2ab7f09a3e2 100644
--- a/docs/product/sentry-basics/integrate-backend/capturing-errors.mdx
+++ b/docs/product/sentry-basics/integrate-backend/capturing-errors.mdx
@@ -6,11 +6,11 @@ description: "Learn more about how Sentry captures unhandled and handled errors
 
 Once initialized in your code, the Sentry SDK will capture various types of events and notify you about them in real-time, depending on the alert rules you've configured. With the Django app already running on your [localhost](http://localhost:8000/), let's try them out.
 
-<Note>
+<Alert>
 
 If you're using your own source code, follow the instructions in [Getting Started](/platforms/python/integrations/django/) to introduce an error into your app.
 
-</Note>
+</Alert>
 
 ## Unhandled Errors
 
diff --git a/docs/product/sentry-basics/integrate-backend/getting-started.mdx b/docs/product/sentry-basics/integrate-backend/getting-started.mdx
index 7ae1b468bdcd9f..41a24c68abde5a 100644
--- a/docs/product/sentry-basics/integrate-backend/getting-started.mdx
+++ b/docs/product/sentry-basics/integrate-backend/getting-started.mdx
@@ -6,14 +6,14 @@ description: "Learn how to add and initialize the Sentry SDK for a sample backen
 
 In this tutorial, you'll import the backend app source code into your local development environment, add the Sentry SDK, and initialize it.
 
-<Note>
+<Alert>
 
 If you're using your own source code, you can skip this tutorial and either:
 
 - Follow the instructions in the [Getting Started](/platforms/python/) docs.
 - Go directly to [the next step](/guides/integrate-backend/configuration-options/).
 
-</Note>
+</Alert>
 
 ## Prerequisites
 
@@ -131,9 +131,9 @@ To build and run the demo application on your localhost:
 
 Commands mentioned within the `Makefile` will be explained in detail in the next part of the tutorial, [Configuration Options](/product/sentry-basics/integrate-backend/configuration-options/).
 
- <Note>
-In addition to installing Python requirements and running the server, we also use the `sentry-cli` to create a new Sentry release and associate commits to that release. Sentry will look through these commits when flagging a suspect commit. 
-</Note>
+ <Alert>
+In addition to installing Python requirements and running the server, we also use the `sentry-cli` to create a new Sentry release and associate commits to that release. Sentry will look through these commits when flagging a suspect commit.
+</Alert>
 
 8. To execute the `sentry-cli` commands, follow these [instructions](/product/sentry-basics/integrate-frontend/upload-source-maps/#step-1-prepare-the-build-environment) to obtain the values for your `SENTRY_AUTH_TOKEN`, `SENTRY_ORG`, and `SENTRY_PROJECT` environment variables.
 
diff --git a/docs/product/stats/index.mdx b/docs/product/stats/index.mdx
index 1f2613d38c2c6a..2a0de3ac08e5d9 100644
--- a/docs/product/stats/index.mdx
+++ b/docs/product/stats/index.mdx
@@ -9,10 +9,10 @@ The [**Stats**](https://sentry.io/orgredirect/organizations/:orgslug/stats/) pag
 
 With the dropdowns at the top of the page, you can set whether the page displays stats for errors, transactions, or attachments, as well as the date range. With the date selector, the time period can be set from an hour to a maximum of 90 days, and all of the page elements change dynamically when you update this setting.
 
-<Note>
+<Alert>
   This page does not include data about sessions because they are not a billable
   event type.
-</Note>
+</Alert>
 
 
 There are three tabs available on the page: [Usage](#usage-stats), [Issues](#issue-stats), and [Health](#health-stats).
@@ -30,9 +30,10 @@ Events and attachments that were successfully processed and stored.
 
 ### Filtered
 
-Filtered events and attachments intentionally excluded based on defined settings. The following reasons are currently defined:
+Filtered events and attachments intentionally excluded based on defined settings. Common reasons include:
 
 - **Browser Extensions**: Filtered by browser extension.
+- **Chunk Load Errors**: Filtered when code chunks can’t be found on the server.
 - **Error Message**: Filtered based on specific error messages.
 - **Filtered Transaction**: Filtered because it was a call to a filtered transaction.
 - **Invalid CSP**: Filtered due to an invalid Content Security Policy (CSP) policy.
@@ -40,8 +41,8 @@ Filtered events and attachments intentionally excluded based on defined settings
 - **Legacy Browsers**: Filtered by certain legacy versions of browsers that are known to cause problems.
 - **Localhost**: Filtered due to localhost restriction.
 - **Release Version**: Filtered by release name (version).
+- **React Hydration Errors**: Filtered due to a mismatch between the server-rendered and initial client User Interface.
 - **Web Crawlers**: Identified as a known web crawler.
-- **Other**: Filtered due to other generic filtering rules not specified above.
 
 For more details, please consult the [Inbound Filters](/concepts/data-management/filtering/) documentation.
 
diff --git a/docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx b/docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx
index c0578e46b14327..675f5e7b6fb6b6 100644
--- a/docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx
+++ b/docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx
@@ -11,7 +11,7 @@ In addition to <PlatformLink to="/data-management/sensitive-data/">using hooks i
 - Detailed tuning on which parts of an event to scrub
 - Partial removal or hashing of sensitive data instead of deletion
 
-<Alert level="info" title="Rule Precedence">
+<Alert title="Rule Precedence">
 
 Advanced Data Scrubbing rules take precedence over other Server-Side Data Scrubbing settings. Specifically, any advanced rule will apply regardless of whether the matched field is in Safe Fields or not.
 
diff --git a/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx b/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx
index 03e52381f54372..070d089cee6675 100644
--- a/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx
+++ b/docs/security-legal-pii/scrubbing/server-side-scrubbing/index.mdx
@@ -46,11 +46,11 @@ credentials = {
 Using the default options will cause the _object_ `credentials` to be set to `null`, and the object itself will not be entered. To prevent this from happening add the keyname to Safe Fields (`credentials` in this case). This will leave the `credentials` object intact, while making all of its entries subject to scrubbing.
 So `password` will be redacted by default, and adding `cats`, `username`, and/or `lastLogin` to the list of additional fields will cause those values to be redacted as well.
 
-<Note>
+<Alert>
 
 You can choose to expand the keys that are scrubbed by the server, as well as prevent IP addresses from being stored. The latter is particularly important if you’re concerned about PII and using our Browser JavaScript SDK.
 
-</Note>
+</Alert>
 
 Only a select number of fields are scrubbed. You can find a list of the fields that will be scrubbed in [Event PII Fields](/data-management-settings/event-pii-fields/).
 
diff --git a/docs/security-legal-pii/security/ai-ml-policy.mdx b/docs/security-legal-pii/security/ai-ml-policy.mdx
index d81bb16c975472..ac02917179e267 100644
--- a/docs/security-legal-pii/security/ai-ml-policy.mdx
+++ b/docs/security-legal-pii/security/ai-ml-policy.mdx
@@ -4,9 +4,9 @@ sidebar_order: 10
 description: "Learn about Sentry's approach to AI/ML"
 ---
 
-<Note>
+<Alert>
 These settings will be rolling out to users over the next few weeks.
-</Note>
+</Alert>
 
 Throughout Sentry’s history, we’ve operated under a policy of [privacy by default](https://sentry.io/lp/privacy-by-default/). This same principle applies to our work in the Artificial Intelligence (AI) and Machine Learning (ML) space, where we want to be just as [transparent](https://blog.sentry.io/terms-of-service-update/) about what data we’re using and why.
 
diff --git a/docs/security-legal-pii/security/security-policy-reporting.mdx b/docs/security-legal-pii/security/security-policy-reporting.mdx
index b9a2e63d396394..3a040edd1d51e8 100644
--- a/docs/security-legal-pii/security/security-policy-reporting.mdx
+++ b/docs/security-legal-pii/security/security-policy-reporting.mdx
@@ -23,7 +23,7 @@ Content-Security-Policy: ...;
 Report-To: {"group":"csp-endpoint","max_age":10886400,"endpoints":[{"url":"https://___ORG_INGEST_DOMAIN___/api/___PROJECT_ID___/security/?sentry_key=___PUBLIC_KEY___"}],"include_subdomains":true}
 ```
 
-<Alert level="note" title="Compatibility Recommendation">
+<Alert title="Compatibility Recommendation">
 
 Though the `report-to` directive is intended to replace the deprecated `report-uri` directive, `report-to` isn't supported in most browsers yet. So for compatibility with current browsers while also adding forward compatibility when browsers get `report-to` support, you can specify both `report-uri` and `report-to` in your Content-Security-Policy (CSP).
 
diff --git a/includes/custom-measurements-units-disclaimer.mdx b/includes/custom-measurements-units-disclaimer.mdx
index 2e08f75340dc69..dd80a835576286 100644
--- a/includes/custom-measurements-units-disclaimer.mdx
+++ b/includes/custom-measurements-units-disclaimer.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 Currently, unit conversion is only supported once the data has already been stored. This means that, for example, `('myMeasurement', 60, 'second')` and `('myMeasurement', 3, 'minute')` would not be aggregated, but rather stored as two separate measurements. To avoid this, make sure to use a consistent unit when recording a custom measurement.
 
-</Note>
+</Alert>
diff --git a/includes/debug-id-requirement.mdx b/includes/debug-id-requirement.mdx
index 64eb5a994293d9..d86bb6a6049a63 100644
--- a/includes/debug-id-requirement.mdx
+++ b/includes/debug-id-requirement.mdx
@@ -1,8 +1,8 @@
-<Note>
+<Alert>
 
 This guide assumes the following:
 
 - `sentry-cli` version >= `2.17.0`
 - Sentry Javascript SDK version >= `7.47.0`
 
-</Note>
+</Alert>
diff --git a/includes/feature-available-for-plan-business-no-trial.mdx b/includes/feature-available-for-plan-business-no-trial.mdx
index a0114bae642be5..25a7d23fe46eaa 100644
--- a/includes/feature-available-for-plan-business-no-trial.mdx
+++ b/includes/feature-available-for-plan-business-no-trial.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is available only if your organization is on a <a href="https://sentry.io/pricing/" target="_blank">Business or Enterprise plan</a>. This feature is not available on Trial plans.
 
-</Note>
+</Alert>
diff --git a/includes/feature-available-for-plan-business.mdx b/includes/feature-available-for-plan-business.mdx
index d4eefc2735cfb6..eccf1bb865172d 100644
--- a/includes/feature-available-for-plan-business.mdx
+++ b/includes/feature-available-for-plan-business.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is available only if your organization is on a <a href="https://sentry.io/pricing/" target="_blank">Business or Enterprise plan</a>.
 
-</Note>
+</Alert>
diff --git a/includes/feature-available-for-plan-enterprise.mdx b/includes/feature-available-for-plan-enterprise.mdx
index e44670df127650..f480c5b5e514ff 100644
--- a/includes/feature-available-for-plan-enterprise.mdx
+++ b/includes/feature-available-for-plan-enterprise.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is available only if your organization is on <a href="https://sentry.io/pricing/" target="_blank">an Enterprise plan</a>.
 
-</Note>
+</Alert>
diff --git a/includes/feature-available-for-plan-team.mdx b/includes/feature-available-for-plan-team.mdx
index 91c709a1df230a..2f61d5559ab600 100644
--- a/includes/feature-available-for-plan-team.mdx
+++ b/includes/feature-available-for-plan-team.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is available only if your organization is on <a href="https://sentry.io/pricing/" target="_blank">a Team plan or higher</a>.
 
-</Note>
+</Alert>
diff --git a/includes/feature-available-for-plan-trial-business.mdx b/includes/feature-available-for-plan-trial-business.mdx
index 69f6620553ba62..8b46f6e122e601 100644
--- a/includes/feature-available-for-plan-trial-business.mdx
+++ b/includes/feature-available-for-plan-trial-business.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is available only if your organization is on <a href="https://sentry.io/pricing/" target="_blank">a Trial, Business, or Enterprise plan</a>.
 
-</Note>
+</Alert>
diff --git a/includes/feature-available-for-plan-trial-enterprise.mdx b/includes/feature-available-for-plan-trial-enterprise.mdx
index 5192d88c8236c7..d652f615fc8c26 100644
--- a/includes/feature-available-for-plan-trial-enterprise.mdx
+++ b/includes/feature-available-for-plan-trial-enterprise.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is available only if your organization is on <a href="https://sentry.io/pricing/" target="_blank">a Trial or Enterprise plan</a>.
 
-</Note>
+</Alert>
diff --git a/includes/feature-available-for-plan-trial-team.mdx b/includes/feature-available-for-plan-trial-team.mdx
index 6a02a3691bed6d..c078637f94111d 100644
--- a/includes/feature-available-for-plan-trial-team.mdx
+++ b/includes/feature-available-for-plan-trial-team.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is available only if your organization is on <a href="https://sentry.io/pricing/" target="_blank">a Trial, Team, or higher plan</a>.
 
-</Note>
+</Alert>
diff --git a/includes/feature-available-for-user-group-early-adopter.mdx b/includes/feature-available-for-user-group-early-adopter.mdx
index c19fc0101ed330..779fb83b58d979 100644
--- a/includes/feature-available-for-user-group-early-adopter.mdx
+++ b/includes/feature-available-for-user-group-early-adopter.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is available only if you're in the <a href="/organization/early-adopter-features/" target="_blank">Early Adopter program</a>. Features available to Early Adopters are still in-progress and may have bugs. We recognize the irony.
 
-</Note>
+</Alert>
diff --git a/includes/feature-available-for-user-group-limited-avail.mdx b/includes/feature-available-for-user-group-limited-avail.mdx
index 9f0cce32e9eae3..7954cbc7a073b0 100644
--- a/includes/feature-available-for-user-group-limited-avail.mdx
+++ b/includes/feature-available-for-user-group-limited-avail.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is in beta and is only available if your organization is participating in its limited release. Features in beta are still in-progress and may have bugs. We recognize the irony.
 
-</Note>
+</Alert>
diff --git a/includes/feature-limited-on-team-retention.mdx b/includes/feature-limited-on-team-retention.mdx
index ece8f89d7447a3..94389a328ba6dc 100644
--- a/includes/feature-limited-on-team-retention.mdx
+++ b/includes/feature-limited-on-team-retention.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This view is only available on Team and Business plans. Team plans can access the last 7 days of data, while Business plans can access the last 90 days. To enable extended data access, upgrade to the <a href="https://sentry.io/pricing/" target="_blank">Business or Enterprise plan</a>.
 
-</Note>
+</Alert>
diff --git a/includes/feature-stage-alpha-metrics.mdx b/includes/feature-stage-alpha-metrics.mdx
index 139079f670dba1..67bebf0fd09ffa 100644
--- a/includes/feature-stage-alpha-metrics.mdx
+++ b/includes/feature-stage-alpha-metrics.mdx
@@ -1,6 +1,6 @@
-<Note title="Now in alpha!">
+<Alert title="Now in alpha!">
 
 Sentry Metrics is currently in Alpha, so be gentle - features are still in-progress and may have bugs. We recognize the irony.
 If you would like to join the Alpha program, you can register [here](https://sentry.io/lp/metrics/).
 
-</Note>
+</Alert>
diff --git a/includes/feature-stage-alpha.mdx b/includes/feature-stage-alpha.mdx
index 84988d44f09247..3922f77f44af56 100644
--- a/includes/feature-stage-alpha.mdx
+++ b/includes/feature-stage-alpha.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is currently in Alpha. Alpha features are still in-progress and may have bugs. We recognize the irony.
 
-</Note>
+</Alert>
diff --git a/includes/feature-stage-beta-metrics.mdx b/includes/feature-stage-beta-metrics.mdx
index 8b642efc9703d7..6e7b759e11cde0 100644
--- a/includes/feature-stage-beta-metrics.mdx
+++ b/includes/feature-stage-beta-metrics.mdx
@@ -1,6 +1,6 @@
-<Note title="Now in beta!">
+<Alert title="Now in beta!">
 
 Sentry Metrics is currently in open beta, so be gentle - features are still in-progress and may have bugs. We recognize the irony.
 For any questions or feedback, you can reach us on [Discord](https://discord.gg/sentry) or [GitHub](https://github.com/getsentry/sentry/discussions/64195).
 
-</Note>
+</Alert>
diff --git a/includes/feature-stage-beta-uptime.mdx b/includes/feature-stage-beta-uptime.mdx
index 42706f9808b6ce..e1a6a3aaece431 100644
--- a/includes/feature-stage-beta-uptime.mdx
+++ b/includes/feature-stage-beta-uptime.mdx
@@ -1,6 +1,6 @@
-<Note>
+<Alert>
 
 Sentry Uptime Monitoring is currently in open beta, so be gentle - features are still in-progress and may have bugs. We recognize the irony.
 For any questions or feedback, you can reach us on [Github Discussions](https://github.com/getsentry/sentry/discussions/78100).
 
-</Note>
+</Alert>
diff --git a/includes/feature-stage-beta.mdx b/includes/feature-stage-beta.mdx
index 6a66b4fe66e5eb..b4ecab92a82aa9 100644
--- a/includes/feature-stage-beta.mdx
+++ b/includes/feature-stage-beta.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is currently in Beta. Beta features are still in progress and may have bugs. We recognize the irony.
 
-</Note>
+</Alert>
diff --git a/includes/feature-stage-preview.mdx b/includes/feature-stage-preview.mdx
index f89d8ac5c3a033..8215b63add277a 100644
--- a/includes/feature-stage-preview.mdx
+++ b/includes/feature-stage-preview.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is currently in Preview. Preview features are still in-progress and may have bugs. We recognize the irony.
 
-</Note>
+</Alert>
diff --git a/includes/insights-requests-body.mdx b/includes/insights-requests-body.mdx
index 6cb797e5c7d5b0..8ce4445ca4a851 100644
--- a/includes/insights-requests-body.mdx
+++ b/includes/insights-requests-body.mdx
@@ -10,9 +10,9 @@ On the [**Requests** page](#requests-page), you get an overview of the domains t
 
 ## Prerequisites and Limitations
 
-<Note>
+<Alert>
 Network requests using non-HTTP protocols (FTP, WebSocket, etc.) are not supported at this time.
-</Note>
+</Alert>
 
 Availability of HTTP request monitoring depends on the SDK your application uses. In most cases, Sentry's SDKs automatically enable HTTP request tracking. You can check your SDK's <PlatformLink to="/tracing/instrumentation/automatic-instrumentation">automatic instrumentation documentation</PlatformLink> to see if it includes tracking HTTP requests.
 
@@ -37,9 +37,9 @@ By default, the table is sorted by most time spent, which serves as a proxy for
 
 To view more details, click on a domain name to open its **Domain Summary** page.
 
-<Note>
+<Alert>
 If Sentry cannot extract the domain of the outgoing HTTP request, it will group the requests in a special table row named "Unknown Domain". This can happen because of malformed URLs, or old JavaScript SDKs that don't support relative URLs. To fix this problem in JavaScript projects, please upgrade to version [7.111.0](https://github.com/getsentry/sentry-javascript/releases/tag/7.111.0) or above.
-</Note>
+</Alert>
 
 ## Domain Summary Page
 
diff --git a/includes/javascript-crons-upsert.mdx b/includes/javascript-crons-upsert.mdx
index 8e940d9f38fc8f..fc03f7c684e9b4 100644
--- a/includes/javascript-crons-upsert.mdx
+++ b/includes/javascript-crons-upsert.mdx
@@ -77,11 +77,11 @@ The schedule representation for your monitor, either `crontab` or `interval`. Th
 
 The amount of time (in minutes) Sentry should wait for your check-in before it's considered missed ("grace period"). Optional.
 
-<Note>
+<Alert>
 
 We recommend that your check-in margin be less than or equal to your interval.
 
-</Note>
+</Alert>
 
 `maxRuntime`:
 
@@ -91,11 +91,11 @@ The amount of time (in minutes) your job is allowed to run before it's considere
 
 The `tz` where your job is running. This is usually your server's timezone, (such as `America/Los_Angeles`). See [list of tz database time zones](https://en.wikipedia.org/wiki/List_of_tz_database_time_zones). Optional.
 
-<Note>
+<Alert>
 
 `node-cron` allows you to pass luxon timezones, but you have to convert them to an IANA timezone when using Sentry (for example, using `DateTime.local().zoneName`).
 
-</Note>
+</Alert>
 
 `failureIssueThreshold`:
 
diff --git a/includes/merge-escalating-note.mdx b/includes/merge-escalating-note.mdx
index c1a3429f62504f..228a091cfbaae4 100644
--- a/includes/merge-escalating-note.mdx
+++ b/includes/merge-escalating-note.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 Escalating issues currently does not work for merged/unmerged issues, but we're working on fixing this.
 
-</Note>
+</Alert>
diff --git a/includes/metrics-api-change.mdx b/includes/metrics-api-change.mdx
index 7ef8367c07071b..08b9e81790e54e 100644
--- a/includes/metrics-api-change.mdx
+++ b/includes/metrics-api-change.mdx
@@ -1,3 +1,3 @@
-<Alert level="danger" title="The Metrics beta has ended on October 7th">
+<Alert level="warning" title="The Metrics beta has ended on October 7th">
 Thank you for participating in our Metrics beta program. After careful consideration, we have ended the beta program and retired the current Metrics solution. We're actively developing a new solution that will make tracking and debugging any issues in your application easier. [Learn more](https://sentry.zendesk.com/hc/en-us/articles/26369339769883-Upcoming-API-Changes-to-Metrics).
 </Alert>
diff --git a/includes/only-error-issues-note.mdx b/includes/only-error-issues-note.mdx
index 98c1d37406ed17..5e58df9c20dad1 100644
--- a/includes/only-error-issues-note.mdx
+++ b/includes/only-error-issues-note.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 This feature is only applicable for [error issues](/product/issues/issue-details/error-issues/) with debug information files, excluding source maps. Other categories of issues (such as [performance issues](/product/issues/issue-details/performance-issues/) or [replay issues](/product/issues/issue-details/replay-issues/)) do not support this feature.
 
-</Note>
+</Alert>
diff --git a/includes/opentelemetry-available.mdx b/includes/opentelemetry-available.mdx
index ad2342a19478d4..997e2d820dd6de 100644
--- a/includes/opentelemetry-available.mdx
+++ b/includes/opentelemetry-available.mdx
@@ -1,4 +1,4 @@
-<Alert level="note">
+<Alert>
   Sentry can integrate with <strong>OpenTelemetry</strong>. You can find more
   information about it
   <PlatformLink to="/tracing/instrumentation/opentelemetry/">here</PlatformLink>.
diff --git a/includes/performance-moving.mdx b/includes/performance-moving.mdx
index ee97dbe06b1fcf..f4959da7d6b5da 100644
--- a/includes/performance-moving.mdx
+++ b/includes/performance-moving.mdx
@@ -1,6 +1,6 @@
-<Note>
+<Alert>
 
 To make it easier to see what's relevant for you, Sentry's Performance landing page is now being split into separate <a href="/product/insights/frontend/" target="_blank">Frontend</a>,  <a href="/product/insights/backend/" target="_blank">Backend</a>, <a href="/product/insights/mobile/" target="_blank">Mobile</a>, and
  <a href="/product/insights/ai/" target="_blank">AI</a> performance pages. They can all be found in the **Insights** tab.
 
-</Note>
+</Alert>
diff --git a/includes/platforms/configuration/integrations/redux.mdx b/includes/platforms/configuration/integrations/redux.mdx
index 7dc8b82f8a31b5..37fdacd4bc2341 100644
--- a/includes/platforms/configuration/integrations/redux.mdx
+++ b/includes/platforms/configuration/integrations/redux.mdx
@@ -9,7 +9,7 @@ const store = createStore(
 );
 ```
 
-<Alert level="info" title="Note">
+<Alert title="Note">
 
 Because Sentry uses a redux **enhancer**, you should pass it as indicated above rather than passing it to `applyMiddleware`. Don't call the method when you pass it to `createStore`.
 
diff --git a/includes/profiling-node-runtime-flags.mdx b/includes/profiling-node-runtime-flags.mdx
index d6c553a6720221..067868768b15bf 100644
--- a/includes/profiling-node-runtime-flags.mdx
+++ b/includes/profiling-node-runtime-flags.mdx
@@ -2,9 +2,9 @@
 
 There are three runtime flags you can set that control the behavior of the profiler. Two of the flags relate to how the SDK resolves the profiler binaries. The third alters how the underlying profiler is initialized by [v8](https://v8docs.nodesource.com/).
 
-<Note>
+<Alert>
 These flags are intended for advanced use cases only. Setting them isn't required for most use cases.
-</Note>
+</Alert>
 
 - SENTRY_PROFILER_BINARY_PATH
 
diff --git a/includes/python-use-older-sdk-for-legacy-support.mdx b/includes/python-use-older-sdk-for-legacy-support.mdx
index 7cac629ab7bbe6..39d019990863a4 100644
--- a/includes/python-use-older-sdk-for-legacy-support.mdx
+++ b/includes/python-use-older-sdk-for-legacy-support.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 The versions above apply for Sentry Python SDK version `2.0+`, which drops support for some legacy Python and framework versions. If you're looking to use Sentry with older Python or framework versions, consider using an SDK version from the `1.x` major line of releases.
 
-</Note>
+</Alert>
diff --git a/includes/sentry-cli-sourcemaps.mdx b/includes/sentry-cli-sourcemaps.mdx
index 8f2f090f7b5761..ca74e2e2032ec8 100644
--- a/includes/sentry-cli-sourcemaps.mdx
+++ b/includes/sentry-cli-sourcemaps.mdx
@@ -1,12 +1,12 @@
 ### 2. Configure Sentry CLI
 
-<Note>
+<Alert>
 
 You can find installation instructions for Sentry CLI here: https://docs.sentry.io/cli/installation/
 
 For more info on `sentry-cli` configuration visit the [Sentry CLI configuration docs](/cli/configuration/).
 
-</Note>
+</Alert>
 
 Make sure `sentry-cli` is configured for your project. For that you can use environment variables:
 
@@ -97,12 +97,12 @@ Afterwards, run the `sourcemaps upload` command with the additional `--release`
 sentry-cli sourcemaps upload --release=<release_name> /path/to/directory
 ```
 
-<Note>
+<Alert>
 
 Running `upload` with `--release` **doesn't automatically create a release in Sentry**.
 Either wait until the first event with the new release set in `Sentry.init` is sent to Sentry, or create a release with the same name in a separate step [with the CLI](/cli/releases).
 
-</Note>
+</Alert>
 
 #### Associating `dist` with Artifact Bundle
 
diff --git a/includes/session-replay-web-report-bug.mdx b/includes/session-replay-web-report-bug.mdx
index 3f55e2c1af0049..6510556960d611 100644
--- a/includes/session-replay-web-report-bug.mdx
+++ b/includes/session-replay-web-report-bug.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 If you have any questions, feedback or would like to report a bug, please open a [GitHub issue](https://github.com/getsentry/sentry/issues/new?assignees=&labels=&template=bug.yml) with a link to a relevant replay or, if possible, a publicly accessible URL to the page you're attempting to record a replay of.
 
-</Note>
+</Alert>
diff --git a/includes/store-minidumps-as-attachments-intro.mdx b/includes/store-minidumps-as-attachments-intro.mdx
index bb192b35f59b0c..08c645f74e612f 100644
--- a/includes/store-minidumps-as-attachments-intro.mdx
+++ b/includes/store-minidumps-as-attachments-intro.mdx
@@ -1,3 +1,3 @@
-Minidumps may contain sensitive information about the target system, such as environment variables, local pathnames, or in-memory representations of input fields, including passwords. By default, Sentry only uses minidump files to create events and immediately drops them. All sensitive information is stripped from the resulting events.
+[Minidumps](/platforms/native/guides/minidumps/#what-is-a-minidump) may contain sensitive information about the target system, such as environment variables, local pathnames, or in-memory representations of input fields, including passwords. By default, Sentry only uses minidump files to create events and immediately drops them. All sensitive information is stripped from the resulting events.
 
 All other types of attachments, such as log files or screenshots, are stored for 30 days when sent to Sentry. Note that Sentry does not apply data scrubbing to attachments.
diff --git a/package.json b/package.json
index 8d47e334b1eb4a..b7d98d47d56393 100644
--- a/package.json
+++ b/package.json
@@ -53,7 +53,7 @@
     "@radix-ui/react-tooltip": "^1.1.4",
     "@radix-ui/themes": "^3.1.3",
     "@sentry-internal/global-search": "^1.1.0",
-    "@sentry/nextjs": "8.36.0",
+    "@sentry/nextjs": "9.0.0-alpha.0",
     "@types/mdx": "^2.0.9",
     "algoliasearch": "^4.23.3",
     "dompurify": "3.1.7",
@@ -103,7 +103,7 @@
   },
   "devDependencies": {
     "@babel/preset-typescript": "^7.15.0",
-    "@codecov/nextjs-webpack-plugin": "^1.0.0",
+    "@codecov/nextjs-webpack-plugin": "^1.8.0",
     "@spotlightjs/spotlight": "^2.5.0",
     "@tailwindcss/forms": "^0.5.7",
     "@tailwindcss/typography": "^0.5.10",
diff --git a/platform-includes/alert-using-a-framework/_default.mdx b/platform-includes/alert-using-a-framework/_default.mdx
index 13c17c570a1da2..2d46c550e45d8e 100644
--- a/platform-includes/alert-using-a-framework/_default.mdx
+++ b/platform-includes/alert-using-a-framework/_default.mdx
@@ -1,4 +1,4 @@
-<Alert level="info" title="Using a framework?">
+<Alert title="Using a framework?">
 
 Check out the other SDKs we support in the left-hand dropdown.
 
diff --git a/platform-includes/capture-error/_default.mdx b/platform-includes/capture-error/_default.mdx
index b54e76fb4f76d4..bd525c829d9156 100644
--- a/platform-includes/capture-error/_default.mdx
+++ b/platform-includes/capture-error/_default.mdx
@@ -1,8 +1,8 @@
-<Note>
+<Alert>
 
 The platform or SDK you've selected either does not support this functionality, or it is missing from our documentation. Please use this code sample from JavaScript as a basis:
 
-</Note>
+</Alert>
 
 ```javascript
 try {
diff --git a/platform-includes/capture-error/apple.mdx b/platform-includes/capture-error/apple.mdx
index 0689a564473f8f..b2efbb6035c01e 100644
--- a/platform-includes/capture-error/apple.mdx
+++ b/platform-includes/capture-error/apple.mdx
@@ -97,11 +97,11 @@ do {
 
 ## Capturing Uncaught Exceptions
 
-<Note>
+<Alert>
 
 The SDK can't install the uncaught exception handler if a debugger is attached. To test these locally, ensure you've unchecked the "Debug executable" option in your app's Xcode scheme's Run action.
 
-</Note>
+</Alert>
 
 By default, macOS applications don't crash whenever an uncaught exception occurs. As the Cocoa Frameworks are generally not [exception-safe on macOS](https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/Exceptions/Articles/ExceptionsAndCocoaFrameworks.html), the application could end up in a corrupted state when an uncaught exception occurs. Therefore, we recommend changing your application configuration so it crashes on uncaught NSExceptions. To achieve this, you can use the `SentryCrashExceptionApplication`, or enable the option `enableUncaughtNSExceptionReporting`, available as of version [8.40.0](https://github.com/getsentry/sentry-cocoa/blob/main/CHANGELOG.md#8400). Both options set the `NSApplicationCrashOnExceptions` on the `NSUserDefaults` so your application crashes on uncaught NSExceptions and send the crash report to Sentry.
 
diff --git a/platform-includes/capture-message/unreal.mdx b/platform-includes/capture-message/unreal.mdx
index e45126e4a1728b..9a053882da85e3 100644
--- a/platform-includes/capture-message/unreal.mdx
+++ b/platform-includes/capture-message/unreal.mdx
@@ -28,11 +28,11 @@ The same result can be achieved by calling corresponding functions in blueprint:
 
 ![Capture message](./img/unreal_capture_message.png)
 
-<Note>
+<Alert>
 
 Scoped message capturing is supported only on macOS, iOS and Android.
 
-</Note>
+</Alert>
 
 ## Manual Events
 
@@ -80,10 +80,10 @@ The same result can be achieved by calling corresponding functions in blueprint:
 
 ![Capture event](./img/unreal_capture_event.png)
 
-<Note>
+<Alert>
 
 Scoped events capturing is supported only on macOS, iOS and Android platforms.
 
-</Note>
+</Alert>
 
 For the full list of supported values, check out [_Event Payloads_](https://develop.sentry.dev/sdk/data-model/event-payloads/) and linked documents.
diff --git a/platform-includes/configuration/before-send-check-in/php.laravel.mdx b/platform-includes/configuration/before-send-check-in/php.laravel.mdx
index 198decbeb0af0b..43a1d30bf43e76 100644
--- a/platform-includes/configuration/before-send-check-in/php.laravel.mdx
+++ b/platform-includes/configuration/before-send-check-in/php.laravel.mdx
@@ -13,8 +13,8 @@ In the Laravel config, a closure can be used to modify the event or return a com
 },
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Closures and Config Caching](/platforms/php/guides/laravel/configuration/laravel-options/#closures-and-config-caching).
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/before-send-check-in/php.symfony.mdx b/platform-includes/configuration/before-send-check-in/php.symfony.mdx
index ab8d4647fae178..815e675a05edb8 100644
--- a/platform-includes/configuration/before-send-check-in/php.symfony.mdx
+++ b/platform-includes/configuration/before-send-check-in/php.symfony.mdx
@@ -37,8 +37,8 @@ class Sentry
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Callables in Symfony Options](/platforms/php/guides/symfony/configuration/symfony-options/#callables).
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/before-send-fingerprint/php.laravel.mdx b/platform-includes/configuration/before-send-fingerprint/php.laravel.mdx
index c20217b7d64e5c..2d11066de09eec 100644
--- a/platform-includes/configuration/before-send-fingerprint/php.laravel.mdx
+++ b/platform-includes/configuration/before-send-fingerprint/php.laravel.mdx
@@ -8,8 +8,8 @@
 },
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Closures and Config Caching](/platforms/php/guides/laravel/configuration/laravel-options/#closures-and-config-caching).
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/before-send-fingerprint/php.symfony.mdx b/platform-includes/configuration/before-send-fingerprint/php.symfony.mdx
index acf6f004cec199..1c2527c7ff1466 100644
--- a/platform-includes/configuration/before-send-fingerprint/php.symfony.mdx
+++ b/platform-includes/configuration/before-send-fingerprint/php.symfony.mdx
@@ -32,8 +32,8 @@ class Sentry
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Callables in Symfony Options](/platforms/php/guides/symfony/configuration/symfony-options/#callables).
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/before-send-hint/native.mdx b/platform-includes/configuration/before-send-hint/native.mdx
index 00cbc9576f2248..ac1089d1c53a47 100644
--- a/platform-includes/configuration/before-send-hint/native.mdx
+++ b/platform-includes/configuration/before-send-hint/native.mdx
@@ -1,4 +1,4 @@
-<Alert level="info">
+<Alert>
 
 The Native SDK does not pass exception information into the hint, but instead allows to set a custom hint in SDK options. To detect the exception type, inspect the event instead.
 
diff --git a/platform-includes/configuration/before-send-hint/php.laravel.mdx b/platform-includes/configuration/before-send-hint/php.laravel.mdx
index 589723f3858e05..23a54cd9825040 100644
--- a/platform-includes/configuration/before-send-hint/php.laravel.mdx
+++ b/platform-includes/configuration/before-send-hint/php.laravel.mdx
@@ -9,8 +9,8 @@
 },
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Closures and Config Caching](/platforms/php/guides/laravel/configuration/laravel-options/#closures-and-config-caching).
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/before-send-hint/php.symfony.mdx b/platform-includes/configuration/before-send-hint/php.symfony.mdx
index 45cc30c365f0ac..56a011308d2bf7 100644
--- a/platform-includes/configuration/before-send-hint/php.symfony.mdx
+++ b/platform-includes/configuration/before-send-hint/php.symfony.mdx
@@ -33,8 +33,8 @@ class Sentry
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Callables in Symfony Options](/platforms/php/guides/symfony/configuration/symfony-options/#callables).
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/before-send-transaction/php.laravel.mdx b/platform-includes/configuration/before-send-transaction/php.laravel.mdx
index a9d9acd668e0ac..de3f1969a1840f 100644
--- a/platform-includes/configuration/before-send-transaction/php.laravel.mdx
+++ b/platform-includes/configuration/before-send-transaction/php.laravel.mdx
@@ -6,8 +6,8 @@ In the Laravel config, a closure can be used to modify the event or return a com
 },
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Closures and Config Caching](/platforms/php/guides/laravel/configuration/laravel-options/#closures-and-config-caching).
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/before-send-transaction/php.symfony.mdx b/platform-includes/configuration/before-send-transaction/php.symfony.mdx
index 460756e313a3a9..12a4949bfb62ef 100644
--- a/platform-includes/configuration/before-send-transaction/php.symfony.mdx
+++ b/platform-includes/configuration/before-send-transaction/php.symfony.mdx
@@ -30,8 +30,8 @@ class Sentry
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Callables in Symfony Options](/platforms/php/guides/symfony/configuration/symfony-options/#callables).
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/before-send/php.laravel.mdx b/platform-includes/configuration/before-send/php.laravel.mdx
index a3f076d058a6c1..a27193a54b11ae 100644
--- a/platform-includes/configuration/before-send/php.laravel.mdx
+++ b/platform-includes/configuration/before-send/php.laravel.mdx
@@ -6,8 +6,8 @@ In the Laravel config, a closure can be used to modify the event or return a com
 },
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Closures and Config Caching](/platforms/php/guides/laravel/configuration/laravel-options/#closures-and-config-caching).
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/before-send/php.symfony.mdx b/platform-includes/configuration/before-send/php.symfony.mdx
index a2ba2513ad5fe6..1c2720e5c970a2 100644
--- a/platform-includes/configuration/before-send/php.symfony.mdx
+++ b/platform-includes/configuration/before-send/php.symfony.mdx
@@ -30,8 +30,8 @@ class Sentry
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Callables in Symfony Options](/platforms/php/guides/symfony/configuration/symfony-options/#callables).
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/config-intro/dotnet.aspnetcore.mdx b/platform-includes/configuration/config-intro/dotnet.aspnetcore.mdx
index 0a9c63fdebfded..597c658b4c8efc 100644
--- a/platform-includes/configuration/config-intro/dotnet.aspnetcore.mdx
+++ b/platform-includes/configuration/config-intro/dotnet.aspnetcore.mdx
@@ -45,7 +45,7 @@ Additionally, you can set your options on `appsettings.json` when using `UseSent
   }
 ```
 
-<Alert level="info" title="Note">
+<Alert title="Note">
 
 You can configure the Sentry options inside of the `UseSentry` callback or through `appsettings.json`. The settings from `appsettings.json` will be applied before the callback is invoked.
 
diff --git a/platform-includes/configuration/config-intro/dotnet.mdx b/platform-includes/configuration/config-intro/dotnet.mdx
index a54bb8b9badeee..8145eb19009f0d 100644
--- a/platform-includes/configuration/config-intro/dotnet.mdx
+++ b/platform-includes/configuration/config-intro/dotnet.mdx
@@ -26,10 +26,10 @@ SentrySdk.Init(options =>
 });
 ```
 
-<Note>
+<Alert>
 
 After you have configured Sentry in your code, you can also configure the
 [MSBuild setup](/platforms/dotnet/configuration/msbuild/) for your project. While this step is optional,
 it can greatly improve your Sentry experience.
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/config-intro/dotnet.nlog.mdx b/platform-includes/configuration/config-intro/dotnet.nlog.mdx
index 7f406b6e56b6b4..fcde9145aad182 100644
--- a/platform-includes/configuration/config-intro/dotnet.nlog.mdx
+++ b/platform-includes/configuration/config-intro/dotnet.nlog.mdx
@@ -1,4 +1,4 @@
-<Alert level="" title="NLog Layouts">
+<Alert title="NLog Layouts">
 
 For more information on how to dynamically set event data via `NLog.config`, see NLog's [layout renderer documentation](https://nlog-project.org/config/?tab=layout-renderers).
 
diff --git a/platform-includes/configuration/config-intro/unity.mdx b/platform-includes/configuration/config-intro/unity.mdx
index 738b3f40cba5bd..a3a6866a6006db 100644
--- a/platform-includes/configuration/config-intro/unity.mdx
+++ b/platform-includes/configuration/config-intro/unity.mdx
@@ -19,13 +19,13 @@ There are two situations when a scriptable configuration object comes into play:
 - `Buildtime Options Script` - is executed by the Unity Editor during app build.
   Changes you make here affect the current build and also allow you to alter native platform build-time settings (Android, iOS, macOS).
 
-<Note>
+<Alert>
   Not all options can be used on all platforms, also some may need to be changed
   at build-time, others at runtime. In most cases it's safe for both functions
   to run the same code.
-</Note>
+</Alert>
 
-<Note>
+<Alert>
   You can click the button _New_ to create a scriptable object from template to
   get started.
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/config-intro/unreal.mdx b/platform-includes/configuration/config-intro/unreal.mdx
index d7b105cf7cefe8..8e4a63e44ff058 100644
--- a/platform-includes/configuration/config-intro/unreal.mdx
+++ b/platform-includes/configuration/config-intro/unreal.mdx
@@ -2,8 +2,8 @@ In order to provide native crash support, the Sentry SDK for Unreal Engine inclu
 
 The UE layer self-initializes through the use of the custom [UEngineSubsystem](https://docs.unrealengine.com/5.3/en-US/API/Runtime/Engine/Subsystems/UEngineSubsystem/).
 
-<Note>
+<Alert>
 
 Different options won't always be compatible with all platforms. Be sure to read the UE editor notices specifying which platforms the specific option works with.
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/diagnostic-logger/dotnet.mdx b/platform-includes/configuration/diagnostic-logger/dotnet.mdx
index 9596719dd6de01..d6b02cd52511c3 100644
--- a/platform-includes/configuration/diagnostic-logger/dotnet.mdx
+++ b/platform-includes/configuration/diagnostic-logger/dotnet.mdx
@@ -71,8 +71,8 @@ The `FileDiagnosticLogger` implementation will overwrite any existing file, and
 
 </ConfigKey>
 
-<Note>
+<Alert>
 
 You can also create your own diagnostic logger class, either by implementing the `IDiagnosticLogger` interface, or inherting from the `DiagnosticLogger` abstract class and overriding the `LogMessage` method.
 
-</Note>
+</Alert>
diff --git a/platform-includes/configuration/integrations/javascript.mdx b/platform-includes/configuration/integrations/javascript.mdx
index f30badab3f0ace..8dbde52fe5f85c 100644
--- a/platform-includes/configuration/integrations/javascript.mdx
+++ b/platform-includes/configuration/integrations/javascript.mdx
@@ -27,3 +27,4 @@
 | [`replayCanvasIntegration`](./replaycanvas)           |                  |            |             |     ✓      |                        |
 | [`reportingObserverIntegration`](./reportingobserver) |                  |     ✓      |             |            |                        |
 | [`sessionTimingIntegration`](./sessiontiming)         |                  |            |             |            |           ✓            |
+| [`unleashIntegration`](./unleash)                     |                  |            |             |            |           ✓            |
diff --git a/platform-includes/configuration/unleash/javascript.ember.mdx b/platform-includes/configuration/unleash/javascript.ember.mdx
new file mode 100644
index 00000000000000..e053ce33712aaa
--- /dev/null
+++ b/platform-includes/configuration/unleash/javascript.ember.mdx
@@ -0,0 +1,24 @@
+Before using this integration, you need to install and instrument Unleash in your app. Learn more by reading [Unleash's SDK reference](https://docs.getunleash.io/reference/sdks/javascript-browser) and [quickstart](https://docs.getunleash.io/quickstart).
+
+```javascript
+import * as Sentry from '@sentry/ember';
+import { UnleashClient } from 'unleash-proxy-client';
+
+Sentry.init({
+  dsn: '___PUBLIC_DSN___',
+  integrations: [Sentry.unleashIntegration({unleashClientClass: UnleashClient})],
+});
+
+const unleash = new UnleashClient({
+  url: 'https://<your-unleash-instance>/api/frontend',
+  clientKey: '<your-client-side-token>',
+  appName: 'my-webapp',
+});
+
+unleash.start();
+
+// Evaluate a flag with a default value. You may have to wait for your client to synchronize first.
+unleash.isEnabled('test-flag');
+
+Sentry.captureException(new Error('Something went wrong!'));
+```
diff --git a/platform-includes/configuration/unleash/javascript.gatsby.mdx b/platform-includes/configuration/unleash/javascript.gatsby.mdx
new file mode 100644
index 00000000000000..e04bcf48bba6bc
--- /dev/null
+++ b/platform-includes/configuration/unleash/javascript.gatsby.mdx
@@ -0,0 +1,24 @@
+Before using this integration, you need to install and instrument Unleash in your app. Learn more by reading [Unleash's SDK reference](https://docs.getunleash.io/reference/sdks/javascript-browser) and [quickstart](https://docs.getunleash.io/quickstart).
+
+```javascript
+import * as Sentry from '@sentry/gatsby';
+import { UnleashClient } from 'unleash-proxy-client';
+
+Sentry.init({
+  dsn: '___PUBLIC_DSN___',
+  integrations: [Sentry.unleashIntegration({unleashClientClass: UnleashClient})],
+});
+
+const unleash = new UnleashClient({
+  url: 'https://<your-unleash-instance>/api/frontend',
+  clientKey: '<your-client-side-token>',
+  appName: 'my-webapp',
+});
+
+unleash.start();
+
+// Evaluate a flag with a default value. You may have to wait for your client to synchronize first.
+unleash.isEnabled('test-flag');
+
+Sentry.captureException(new Error('Something went wrong!'));
+```
diff --git a/platform-includes/configuration/unleash/javascript.mdx b/platform-includes/configuration/unleash/javascript.mdx
new file mode 100644
index 00000000000000..c818cedfdd040e
--- /dev/null
+++ b/platform-includes/configuration/unleash/javascript.mdx
@@ -0,0 +1,24 @@
+Before using this integration, you need to install and instrument Unleash in your app. Learn more by reading [Unleash's SDK reference](https://docs.getunleash.io/reference/sdks/javascript-browser) and [quickstart](https://docs.getunleash.io/quickstart).
+
+```javascript
+import * as Sentry from '@sentry/browser';
+import { UnleashClient } from 'unleash-proxy-client';
+
+Sentry.init({
+  dsn: '___PUBLIC_DSN___',
+  integrations: [Sentry.unleashIntegration({unleashClientClass: UnleashClient})],
+});
+
+const unleash = new UnleashClient({
+  url: 'https://<your-unleash-instance>/api/frontend',
+  clientKey: '<your-client-side-token>',
+  appName: 'my-webapp',
+});
+
+unleash.start();
+
+// Evaluate a flag with a default value. You may have to wait for your client to synchronize first.
+unleash.isEnabled('test-flag');
+
+Sentry.captureException(new Error('Something went wrong!'));
+```
diff --git a/platform-includes/configuration/unleash/javascript.nextjs.mdx b/platform-includes/configuration/unleash/javascript.nextjs.mdx
new file mode 100644
index 00000000000000..6a3afd7ef2992a
--- /dev/null
+++ b/platform-includes/configuration/unleash/javascript.nextjs.mdx
@@ -0,0 +1,24 @@
+Before using this integration, you need to install and instrument Unleash in your app. Learn more by reading [Unleash's SDK reference](https://docs.getunleash.io/reference/sdks/javascript-browser) and [quickstart](https://docs.getunleash.io/quickstart).
+
+```javascript
+import * as Sentry from '@sentry/nextjs';
+import { UnleashClient } from 'unleash-proxy-client';
+
+Sentry.init({
+  dsn: '___PUBLIC_DSN___',
+  integrations: [Sentry.unleashIntegration({unleashClientClass: UnleashClient})],
+});
+
+const unleash = new UnleashClient({
+  url: 'https://<your-unleash-instance>/api/frontend',
+  clientKey: '<your-client-side-token>',
+  appName: 'my-webapp',
+});
+
+unleash.start();
+
+// Evaluate a flag with a default value. You may have to wait for your client to synchronize first.
+unleash.isEnabled('test-flag');
+
+Sentry.captureException(new Error('Something went wrong!'));
+```
diff --git a/platform-includes/configuration/unleash/javascript.nuxt.mdx b/platform-includes/configuration/unleash/javascript.nuxt.mdx
new file mode 100644
index 00000000000000..a3bcd9dfb3696b
--- /dev/null
+++ b/platform-includes/configuration/unleash/javascript.nuxt.mdx
@@ -0,0 +1,24 @@
+Before using this integration, you need to install and instrument Unleash in your app. Learn more by reading [Unleash's SDK reference](https://docs.getunleash.io/reference/sdks/javascript-browser) and [quickstart](https://docs.getunleash.io/quickstart).
+
+```javascript
+import * as Sentry from '@sentry/nuxt';
+import { UnleashClient } from 'unleash-proxy-client';
+
+Sentry.init({
+  dsn: '___PUBLIC_DSN___',
+  integrations: [Sentry.unleashIntegration({unleashClientClass: UnleashClient})],
+});
+
+const unleash = new UnleashClient({
+  url: 'https://<your-unleash-instance>/api/frontend',
+  clientKey: '<your-client-side-token>',
+  appName: 'my-webapp',
+});
+
+unleash.start();
+
+// Evaluate a flag with a default value. You may have to wait for your client to synchronize first.
+unleash.isEnabled('test-flag');
+
+Sentry.captureException(new Error('Something went wrong!'));
+```
diff --git a/platform-includes/configuration/unleash/javascript.react.mdx b/platform-includes/configuration/unleash/javascript.react.mdx
new file mode 100644
index 00000000000000..d1f31117c7e1a9
--- /dev/null
+++ b/platform-includes/configuration/unleash/javascript.react.mdx
@@ -0,0 +1,24 @@
+Before using this integration, you need to install and instrument Unleash in your app. Learn more by reading [Unleash's SDK reference](https://docs.getunleash.io/reference/sdks/javascript-browser) and [quickstart](https://docs.getunleash.io/quickstart).
+
+```javascript
+import * as Sentry from '@sentry/react';
+import { UnleashClient } from 'unleash-proxy-client';
+
+Sentry.init({
+  dsn: '___PUBLIC_DSN___',
+  integrations: [Sentry.unleashIntegration({unleashClientClass: UnleashClient})],
+});
+
+const unleash = new UnleashClient({
+  url: 'https://<your-unleash-instance>/api/frontend',
+  clientKey: '<your-client-side-token>',
+  appName: 'my-webapp',
+});
+
+unleash.start();
+
+// Evaluate a flag with a default value. You may have to wait for your client to synchronize first.
+unleash.isEnabled('test-flag');
+
+Sentry.captureException(new Error('Something went wrong!'));
+```
diff --git a/platform-includes/configuration/unleash/javascript.remix.mdx b/platform-includes/configuration/unleash/javascript.remix.mdx
new file mode 100644
index 00000000000000..192a3bfaa1db68
--- /dev/null
+++ b/platform-includes/configuration/unleash/javascript.remix.mdx
@@ -0,0 +1,24 @@
+Before using this integration, you need to install and instrument Unleash in your app. Learn more by reading [Unleash's SDK reference](https://docs.getunleash.io/reference/sdks/javascript-browser) and [quickstart](https://docs.getunleash.io/quickstart).
+
+```javascript
+import * as Sentry from '@sentry/remix';
+import { UnleashClient } from 'unleash-proxy-client';
+
+Sentry.init({
+  dsn: '___PUBLIC_DSN___',
+  integrations: [Sentry.unleashIntegration({unleashClientClass: UnleashClient})],
+});
+
+const unleash = new UnleashClient({
+  url: 'https://<your-unleash-instance>/api/frontend',
+  clientKey: '<your-client-side-token>',
+  appName: 'my-webapp',
+});
+
+unleash.start();
+
+// Evaluate a flag with a default value. You may have to wait for your client to synchronize first.
+unleash.isEnabled('test-flag');
+
+Sentry.captureException(new Error('Something went wrong!'));
+```
diff --git a/platform-includes/configuration/unleash/javascript.solid.mdx b/platform-includes/configuration/unleash/javascript.solid.mdx
new file mode 100644
index 00000000000000..ff8e03545c9eac
--- /dev/null
+++ b/platform-includes/configuration/unleash/javascript.solid.mdx
@@ -0,0 +1,24 @@
+Before using this integration, you need to install and instrument Unleash in your app. Learn more by reading [Unleash's SDK reference](https://docs.getunleash.io/reference/sdks/javascript-browser) and [quickstart](https://docs.getunleash.io/quickstart).
+
+```javascript
+import * as Sentry from '@sentry/solid';
+import { UnleashClient } from 'unleash-proxy-client';
+
+Sentry.init({
+  dsn: '___PUBLIC_DSN___',
+  integrations: [Sentry.unleashIntegration({unleashClientClass: UnleashClient})],
+});
+
+const unleash = new UnleashClient({
+  url: 'https://<your-unleash-instance>/api/frontend',
+  clientKey: '<your-client-side-token>',
+  appName: 'my-webapp',
+});
+
+unleash.start();
+
+// Evaluate a flag with a default value. You may have to wait for your client to synchronize first.
+unleash.isEnabled('test-flag');
+
+Sentry.captureException(new Error('Something went wrong!'));
+```
diff --git a/platform-includes/configuration/unleash/javascript.solidstart.mdx b/platform-includes/configuration/unleash/javascript.solidstart.mdx
new file mode 100644
index 00000000000000..369cf7803e0d91
--- /dev/null
+++ b/platform-includes/configuration/unleash/javascript.solidstart.mdx
@@ -0,0 +1,24 @@
+Before using this integration, you need to install and instrument Unleash in your app. Learn more by reading [Unleash's SDK reference](https://docs.getunleash.io/reference/sdks/javascript-browser) and [quickstart](https://docs.getunleash.io/quickstart).
+
+```javascript
+import * as Sentry from '@sentry/solidstart';
+import { UnleashClient } from 'unleash-proxy-client';
+
+Sentry.init({
+  dsn: '___PUBLIC_DSN___',
+  integrations: [Sentry.unleashIntegration({unleashClientClass: UnleashClient})],
+});
+
+const unleash = new UnleashClient({
+  url: 'https://<your-unleash-instance>/api/frontend',
+  clientKey: '<your-client-side-token>',
+  appName: 'my-webapp',
+});
+
+unleash.start();
+
+// Evaluate a flag with a default value. You may have to wait for your client to synchronize first.
+unleash.isEnabled('test-flag');
+
+Sentry.captureException(new Error('Something went wrong!'));
+```
diff --git a/platform-includes/configuration/unleash/javascript.svelte.mdx b/platform-includes/configuration/unleash/javascript.svelte.mdx
new file mode 100644
index 00000000000000..eea7c36e709347
--- /dev/null
+++ b/platform-includes/configuration/unleash/javascript.svelte.mdx
@@ -0,0 +1,24 @@
+Before using this integration, you need to install and instrument Unleash in your app. Learn more by reading [Unleash's SDK reference](https://docs.getunleash.io/reference/sdks/javascript-browser) and [quickstart](https://docs.getunleash.io/quickstart).
+
+```javascript
+import * as Sentry from '@sentry/svelte';
+import { UnleashClient } from 'unleash-proxy-client';
+
+Sentry.init({
+  dsn: '___PUBLIC_DSN___',
+  integrations: [Sentry.unleashIntegration({unleashClientClass: UnleashClient})],
+});
+
+const unleash = new UnleashClient({
+  url: 'https://<your-unleash-instance>/api/frontend',
+  clientKey: '<your-client-side-token>',
+  appName: 'my-webapp',
+});
+
+unleash.start();
+
+// Evaluate a flag with a default value. You may have to wait for your client to synchronize first.
+unleash.isEnabled('test-flag');
+
+Sentry.captureException(new Error('Something went wrong!'));
+```
diff --git a/platform-includes/configuration/unleash/javascript.sveltekit.mdx b/platform-includes/configuration/unleash/javascript.sveltekit.mdx
new file mode 100644
index 00000000000000..2443707b188773
--- /dev/null
+++ b/platform-includes/configuration/unleash/javascript.sveltekit.mdx
@@ -0,0 +1,24 @@
+Before using this integration, you need to install and instrument Unleash in your app. Learn more by reading [Unleash's SDK reference](https://docs.getunleash.io/reference/sdks/javascript-browser) and [quickstart](https://docs.getunleash.io/quickstart).
+
+```javascript
+import * as Sentry from '@sentry/sveltekit';
+import { UnleashClient } from 'unleash-proxy-client';
+
+Sentry.init({
+  dsn: '___PUBLIC_DSN___',
+  integrations: [Sentry.unleashIntegration({unleashClientClass: UnleashClient})],
+});
+
+const unleash = new UnleashClient({
+  url: 'https://<your-unleash-instance>/api/frontend',
+  clientKey: '<your-client-side-token>',
+  appName: 'my-webapp',
+});
+
+unleash.start();
+
+// Evaluate a flag with a default value. You may have to wait for your client to synchronize first.
+unleash.isEnabled('test-flag');
+
+Sentry.captureException(new Error('Something went wrong!'));
+```
diff --git a/platform-includes/configuration/unleash/javascript.vue.mdx b/platform-includes/configuration/unleash/javascript.vue.mdx
new file mode 100644
index 00000000000000..e284125f818c5e
--- /dev/null
+++ b/platform-includes/configuration/unleash/javascript.vue.mdx
@@ -0,0 +1,24 @@
+Before using this integration, you need to install and instrument Unleash in your app. Learn more by reading [Unleash's SDK reference](https://docs.getunleash.io/reference/sdks/javascript-browser) and [quickstart](https://docs.getunleash.io/quickstart).
+
+```javascript
+import * as Sentry from '@sentry/vue';
+import { UnleashClient } from 'unleash-proxy-client';
+
+Sentry.init({
+  dsn: '___PUBLIC_DSN___',
+  integrations: [Sentry.unleashIntegration({unleashClientClass: UnleashClient})],
+});
+
+const unleash = new UnleashClient({
+  url: 'https://<your-unleash-instance>/api/frontend',
+  clientKey: '<your-client-side-token>',
+  appName: 'my-webapp',
+});
+
+unleash.start();
+
+// Evaluate a flag with a default value. You may have to wait for your client to synchronize first.
+unleash.isEnabled('test-flag');
+
+Sentry.captureException(new Error('Something went wrong!'));
+```
diff --git a/platform-includes/crons/setup/php.laravel.mdx b/platform-includes/crons/setup/php.laravel.mdx
index b3e6108cf85a82..caceb707cbf3b9 100644
--- a/platform-includes/crons/setup/php.laravel.mdx
+++ b/platform-includes/crons/setup/php.laravel.mdx
@@ -27,12 +27,16 @@ protected function schedule(Schedule $schedule)
     $schedule->command('emails:send')
         ->everyHour()
         ->sentryMonitor(
-            // Specify the slug of the job monitor in case of duplicate commands or if the monitor was created in the UI
+            // Specify the slug of the job monitor in case of duplicate commands or if the monitor was created in the UI.
             monitorSlug: null,
-            // Check-in margin in minutes
+            // Number of minutes before a check-in is considered missed.
             checkInMargin: 5,
-            // Max runtime in minutes
+            // Number of minutes before an in-progress check-in is marked timed out.
             maxRuntime: 15,
+            // Create a new issue when this many consecutive missed or error check-ins are processed.
+            failureIssueThreshold: 1,
+            // Resolve the issue when this many consecutive healthy check-ins are processed.
+            recoveryThreshold: 1,
             // In case you want to configure the job monitor exclusively in the UI, you can turn off sending the monitor config with the check-in.
             // Passing a monitor-slug is required in this case.
             updateMonitorConfig: false,
diff --git a/platform-includes/crons/setup/python.mdx b/platform-includes/crons/setup/python.mdx
index bda83f46a2e18f..66d23ff50f212b 100644
--- a/platform-includes/crons/setup/python.mdx
+++ b/platform-includes/crons/setup/python.mdx
@@ -29,9 +29,9 @@ def tell_the_world():
         print('My scheduled task...')
 ```
 
-<Note>
+<Alert>
 
 Since version `1.44.1` of the SDK you can use `monitor` to annotate asynchronous
 functions as well.
 
-</Note>
+</Alert>
diff --git a/platform-includes/debug-symbols-apple/_default.mdx b/platform-includes/debug-symbols-apple/_default.mdx
index 96e691d59dac4b..0cf7a319aa965c 100644
--- a/platform-includes/debug-symbols-apple/_default.mdx
+++ b/platform-includes/debug-symbols-apple/_default.mdx
@@ -8,12 +8,12 @@ To view uploaded dSYMs in your project, select an existing project from the "Pro
 - [Sentry Fastlane Plugin](#fastlane)
 - [Xcode Build Phase](#xcode-build-phase)
 
-<Note>
+<Alert>
 
 Starting with Xcode 13, newly generated projects don't automatically create a required `Info.plist` configuration file.
 If this is your situation, please read [Info.plist Is Missing in Xcode 13 — Here's How To Get It Back](https://betterprogramming.pub/info-plist-is-missing-in-xcode-13-heres-how-to-get-it-back-1a7abf3e2514).
 
-</Note>
+</Alert>
 
 ## Sentry-cli
 
@@ -29,7 +29,7 @@ You can also upload your code for source context. This feature allows Sentry to
 
 <OnboardingOptionButtons
   options={[{ id:"source-context", checked: false }]}
-/> 
+/>
 
 ```bash {"onboardingOptions": {"source-context": "2"}}
 sentry-cli debug-files upload --auth-token ___ORG_AUTH_TOKEN___ \
@@ -39,13 +39,13 @@ sentry-cli debug-files upload --auth-token ___ORG_AUTH_TOKEN___ \
   PATH_TO_DSYMS
 ```
 
-<Note>
+<Alert>
 
 You can find installation instructions for Sentry CLI https://docs.sentry.io/cli/installation/.
 
 For more info on `sentry-cli` configuration visit the [Sentry CLI configuration docs](/cli/configuration/).
 
-</Note>
+</Alert>
 
 ## Sentry Fastlane Plugin
 
@@ -74,7 +74,7 @@ sentry_upload_dif(
 )
 ```
 
-<Alert level="" title="On Prem">
+<Alert title="On Prem">
 
 By default fastlane will connect to sentry.io. For on-prem you need to provide the _url_ parameter to instruct the tool to connect to your server:
 
@@ -96,7 +96,7 @@ Sentry can display snippets of your code next to the event stack traces. This fe
 
 For this to work, your project settings for `DEBUG_INFORMATION_FORMAT` must be set to `DWARF with dSYM File`, which is the default for release builds but not for debug builds. If you don't want Sentry to upload your source code, remove the `--include-sources` argument from the copied script.
 
-<Alert level="" title="Warnings vs. Errors">
+<Alert title="Warnings vs. Errors">
 
 Depending on your needs, you may want to emit warnings to the Xcode build log to let the build pass, or emit errors to fail it. For example, in a CI deployment where debug symbols may be harder to recover, and you might not realize symbols couldn't be symbolicated until after release, it might be better to fail the build.
 
@@ -115,7 +115,7 @@ if which sentry-cli >/dev/null; then
 export SENTRY_ORG=___ORG_SLUG___
 export SENTRY_PROJECT=___PROJECT_SLUG___
 export SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___
-ERROR=$(sentry-cli debug-files upload \ 
+ERROR=$(sentry-cli debug-files upload \
 --include-sources \
 "$DWARF_DSYM_FOLDER_PATH" 2>&1 >/dev/null)
 if [ ! $? -eq 0 ]; then
@@ -136,7 +136,7 @@ export SENTRY_ORG=___ORG_SLUG___
 export SENTRY_PROJECT=___PROJECT_SLUG___
 export SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___
 ERROR=$(sentry-cli debug-files upload \
---include-sources \ 
+--include-sources \
 "$DWARF_DSYM_FOLDER_PATH" --force-foreground 2>&1 >/dev/null)
 if [ ! $? -eq 0 ]; then
 echo "error: sentry-cli - $ERROR"
@@ -145,9 +145,9 @@ else
 echo "error: sentry-cli not installed, download from https://github.com/getsentry/sentry-cli/releases"
 fi
 ```
-<Note>
+<Alert>
 You can add `--force-foreground` argument to sentry-cli to help you debug any error that could happen during the upload process.
-</Note>
+</Alert>
 
 3.  You also need to add the following line to the _Input Files_ section in the _Run Script_ from step 2:
 
@@ -162,7 +162,7 @@ ${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_FILE_NAME}/Contents/Resources/DWARF/${TAR
 
 ![enable-user-script-sandboxing](./img/enable_user_script_sandboxing.png)
 
-<Alert level="" title="Self Hosted">
+<Alert title="Self Hosted">
 
 By default sentry-cli will connect to sentry.io. For on-prem you need to export the _SENTRY_URL_ environment variable to instruct the tool to connect to your server:
 
diff --git a/platform-includes/distributed-tracing/custom-instrumentation/browser/javascript.mdx b/platform-includes/distributed-tracing/custom-instrumentation/browser/javascript.mdx
new file mode 100644
index 00000000000000..42fe4a7f7e38b0
--- /dev/null
+++ b/platform-includes/distributed-tracing/custom-instrumentation/browser/javascript.mdx
@@ -0,0 +1,91 @@
+Distributed tracing will be set up automatically if you've <PlatformLink to="/tracing/">set up tracing</PlatformLink>.
+
+<Expandable title="What is Distributed Tracing?">
+  <PlatformContent includePath="distributed-tracing/explanation" />
+</Expandable>
+
+When tracing is enabled, the Sentry SDK will not only create spans for pageloads and transactions but also propagate trace information to other systems. This allows you to connect multiple systems and see how they interact with each other.
+
+By default, outgoing HTTP requests will automatically be instrumented for you. For other cases where you may want to continue traces (for example when working with websockets), you can manually extract and inject tracing information.
+
+## Enabling Automatic Distributed Tracing
+
+To enable distributed tracing for your frontend, add `browserTracingIntegration` to your `Sentry.init()` options as described in the <PlatformLink to="/tracing/instrumentation/automatic-instrumentation/">Automatic Instrumentation</PlatformLink> docs.
+
+### Continuing a Trace Manually
+
+By default, the `browserTracingIntegration` will automatically continue a trace found in a `<meta>` tag - see <PlatformLink to="/tracing/trace-propagation/#automatic-trace-propagation">Automatic Trace Propagation</PlatformLink> for details.
+If you want to continue a different trace, for example because you cannot propagate the trace through meta tags but through some different mechanism, you can do this:
+
+```javascript
+const client = Sentry.init({
+  dsn: "___PUBLIC_DSN___",
+  integrations: [
+    Sentry.browserTracingIntegration({
+      // Disable default pageload instrumentation
+      instrumentPageLoad: false,
+    }),
+  ],
+});
+
+// Start the pageload span manually
+const sentryTrace = getSentryTraceStringFromSomewhere();
+const baggage = getBaggageStringFromSomewhere();
+
+Sentry.startBrowserTracingPageLoadSpan(
+  client,
+  {
+    name: window.location.pathname,
+  },
+  { sentryTrace, baggage }
+);
+```
+
+## Configuring Distributed Tracing Without `browserTracingIntegration`
+
+If you don't want to use the `browserTracingIntegration` integration, or you want to propagate traces in other places than HTTP requests (for example, with websockets), you can manually extract and inject tracing data in your application to connect multiple systems. For this, you must:
+
+- Extract and store incoming tracing information from HTML `<meta>` tags when loading the page.
+- Inject tracing information to any outgoing requests.
+
+To learn more about distributed tracing, see our <PlatformLink to="/tracing/trace-propagation/">Distributed Tracing</PlatformLink> docs.
+
+### Extract Tracing Information From HTML `meta` Tags
+
+If you have a server that renders your application's HTML (server-side rendering) and is also running a Sentry SDK, you can connect your backend to your backend via tracing.
+
+To do this, have your server render HTML `<meta>` tags with the Sentry trace information. In your frontend, extract that tracing information when the page is loading and use it to create new transactions connected to that incoming backend trace.
+
+Some Sentry backend SDKs provide a built-in way to inject these `<meta>` tags into rendered HTML. For example:
+
+- [Node](/platforms/javascript/guides/node/tracing/trace-propagation/custom-instrumentation/#injecting-tracing-information-into-html)
+- [Python](/platforms/python/distributed-tracing/custom-instrumentation/#inject-tracing-information-into-rendered-html)
+- [Ruby](/platforms/ruby/distributed-tracing/custom-instrumentation/#inject-tracing-information-into-rendered-html)
+- [PHP](/platforms/php/distributed-tracing/custom-instrumentation/#inject-tracing-information-into-rendered-html)
+
+Then, on `pageload` you can do the following:
+
+```javascript
+import { propagationContextFromHeaders } from "@sentry/core"; // Before version 8.40.0, import from "@sentry/utils"
+import * as Sentry from "@sentry/browser";
+
+// Read meta tag values
+const sentryTrace = document.querySelector("meta[name=sentry-trace]")?.content;
+const baggage = document.querySelector("meta[name=baggage]")?.content;
+
+// Generate a propagation context from the meta tags
+const propagationContext = propagationContextFromHeaders(sentryTrace, baggage);
+Sentry.getCurrentScope().setPropagationContext(propagationContext);
+
+Sentry.startSpan(
+  {
+    name: `Pageload: ${window.location.pathname}`,
+    op: "pageload",
+  },
+  () => {
+    // do something
+  }
+);
+```
+
+In this example, we create a new root span that is attached to the trace specified in the `sentry-trace` and `baggage` HTML `<meta>` tags.
diff --git a/platform-includes/distributed-tracing/custom-instrumentation/dart.mdx b/platform-includes/distributed-tracing/custom-instrumentation/dart.mdx
index 76ee7a23d0bbaf..6a2446e7803310 100644
--- a/platform-includes/distributed-tracing/custom-instrumentation/dart.mdx
+++ b/platform-includes/distributed-tracing/custom-instrumentation/dart.mdx
@@ -16,8 +16,8 @@ try {
 }
 ```
 
-<Note>
+<Alert>
 
 The `SentryHttpClient` instrumentation handles trace continuations automatically when enabling the [performance](/platforms/dart/performance/) feature.
 
-</Note>
+</Alert>
diff --git a/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx b/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
index c0321cdb4b5e7c..93d39f7c72f349 100644
--- a/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
+++ b/platform-includes/distributed-tracing/custom-instrumentation/javascript.mdx
@@ -1,174 +1,14 @@
 On this page you will learn how to manually propagate trace information into and out of your JavaScript application.
 
-Distributed tracing will be set up automatically if:
-
-- You've <PlatformLink to="/tracing/">Set Up Tracing</PlatformLink>, or
-- You're using one of the SDKs that include tracing propagation out of the box:
-  - `@sentry/astro`
-  - `@sentry/nextjs`
-  - `@sentry/nuxt`
-  - `@sentry/remix`
-  - `@sentry/solidstart`
-  - `@sentry/sveltekit`
-
-If you are using a different package, and have not enabled tracing, you can manually set up your application for distributed tracing to work.
-
-## Enabling Distributed Tracing
-
-<PlatformCategorySection supported={['browser']}>
-
-To enable distributed tracing for your frontend, add `browserTracingIntegration` to your `Sentry.init()` options as described in the <PlatformLink to="/tracing/instrumentation/automatic-instrumentation/">Automatic Instrumentation</PlatformLink> docs.
-
-If you want to use distributed tracing but not tracing, set the `tracesSampleRate` option to `0`.
-
-```javascript
-Sentry.init({
-  dsn: "___PUBLIC_DSN___",
-  integrations: [Sentry.browserTracingIntegration()],
-
-  // If this is 0, tracing is disabled
-  // but distributed tracing is not
-  tracesSampleRate: 0,
-});
-```
-
-### Continuing a Trace Manually
-
-By default, the `browserTracingIntegration` will automatically continue a trace found in a `<meta>` tags - see <PlatformLink to="/tracing/trace-propagation/#automatic-trace-propagation">Automatic Trace Propagation</PlatformLink> for details.
-If you want to continue a different trace, for example because you cannot propagate the trace through meta tags but through some different mechanism, you can do this as follows:
-
-```javascript
-const client = Sentry.init({
-  dsn: "___PUBLIC_DSN___",
-  integrations: [
-    Sentry.browserTracingIntegration({
-      // Disable default pageload instrumentation
-      instrumentPageLoad: false,
-    }),
-  ],
-});
-
-// Start the pageload span manually
-const sentryTrace = getSentryTraceStringFromSomewhere();
-const baggage = getBaggageStringFromSomewhere();
-
-Sentry.startBrowserTracingPageLoadSpan(
-  client,
-  {
-    name: window.location.pathname,
-  },
-  { sentryTrace, baggage }
-);
-```
-
-## Enabling Distributed Tracing without `browserTracingIntegration`
-
-If you don't want to use the `browserTracingIntegration` integration, you can manually extract and inject tracing data in your application to connect multiple systems. For this, you must:
-
-- Extract and store incoming tracing information from HTML `<meta>` tags when loading the page.
-- Inject tracing information to any outgoing requests.
-
-To learn more about distributed tracing, see our <PlatformLink to="/tracing/trace-propagation/">Distributed Tracing</PlatformLink> docs.
-
-### Extract Tracing Information From HTML `meta` Tags
-
-If you have a server that renders your application's HTML (SSR) and is also running a Sentry SDK, you can connect your backend to your backend via tracing.
-
-To do this, have your server render HTML `<meta>` tags with the Sentry trace information. In your frontend, extract that tracing information when the page is loading and use it to create new transactions connected to that incoming backend trace.
-
-Some Sentry backend SDKs provide a built-in way to inject these `<meta>` tags into rendered HTML. For example:
-
-- [Python](/platforms/python/distributed-tracing/custom-instrumentation/#inject-tracing-information-into-rendered-html)
-- [Ruby](/platforms/ruby/distributed-tracing/custom-instrumentation/#inject-tracing-information-into-rendered-html)
-- [PHP](/platforms/php/distributed-tracing/custom-instrumentation/#inject-tracing-information-into-rendered-html)
-
-Then, on `pageload` you can do the following:
-
-```javascript
-import { propagationContextFromHeaders } from "@sentry/core"; // Before version 8.40.0, import from "@sentry/utils"
-import * as Sentry from "@sentry/browser";
-
-// Read meta tag values
-const sentryTrace = document.querySelector("meta[name=sentry-trace]")?.content;
-const baggage = document.querySelector("meta[name=baggage]")?.content;
-
-// Generate a propagation context from the meta tags
-const propagationContext = propagationContextFromHeaders(sentryTrace, baggage);
-Sentry.getCurrentScope().setPropagationContext(propagationContext);
-
-Sentry.startSpan(
-  {
-    name: `Pageload: ${window.location.pathname}`,
-    op: "pageload",
-  },
-  () => {
-    // do something
-  }
-);
-```
-
-In this example, we create a new root span that is attached to the trace specified in the `sentry-trace` and `baggage` HTML `<meta>` tags.
-
+<PlatformCategorySection
+  supported={["browser"]}
+  notSupported={["server", "serverless"]}
+>
+  <PlatformContent includePath="distributed-tracing/custom-instrumentation/browser" />
 </PlatformCategorySection>
 
-<PlatformCategorySection supported={['server', 'serverless']}>
-If you want to use distributed tracing but not tracing, set the `tracesSampleRate` option to `0`.
-
-```javascript
-Sentry.init({
-  dsn: "___PUBLIC_DSN___",
-
-  // If this is 0, tracing is disabled
-  // but distributed tracing is not
-  tracesSampleRate: 0,
-});
-```
-
-## Manually Extracting and Injecting Distributed Tracing Information
-
-You can also manually extract and inject tracing data into your application. For this, you must:
-
-- Extract and store incoming tracing information from incoming request headers or similar.
-- Inject tracing information to any outgoing requests.
-
-To learn more about distributed tracing, see our <PlatformLink to="/tracing/trace-propagation/">Distributed Tracing</PlatformLink> docs.
-
-### Extracting Incoming Tracing Information
-
-You must extract and store incoming tracing information in memory for later use. Sentry provides the `continueTrace()` function to help you with this. Incoming tracing information can come from different places:
-
-- In a web environment, it's sent with HTTP headers, for example, by another Sentry SDK used in your frontend project.
-- In a job queue, it can be retrieved from meta or header variables.
-- You also can pick up tracing information from environment variables.
-
-Here's an example of how to extract and store incoming tracing information using `continueTrace()`:
-
-```javascript
-const http = require("http");
-
-http.createServer((request, response) => {
-  const sentryTraceHeaders = request.headers["sentry-trace"];
-  const sentryTrace = Array.isArray(sentryTraceHeaders)
-    ? sentryTraceHeaders.join(",")
-    : sentryTraceHeaders;
-  const baggage = request.headers["baggage"];
-
-  Sentry.continueTrace({ sentryTrace, baggage }, () => {
-    Sentry.startSpan(
-      {,
-        name: "my request",
-        op: "http.server",
-      },
-      () => {
-        // Your API code...
-      }
-    );
-  });
-});
-```
-
-In this example, we create a new transaction that is attached to the trace specified in the `sentry-trace` and `baggage` headers.
-
+<PlatformCategorySection supported={["server", "serverless"]}>
+  <PlatformContent includePath="distributed-tracing/custom-instrumentation/server" />
 </PlatformCategorySection>
 
 ### Inject Tracing Information into Outgoing Requests
@@ -178,18 +18,9 @@ For distributed tracing to work, the two headers that you extracted and stored i
 Here's an example of how to collect and inject this tracing information to outgoing requests:
 
 ```javascript
-const activeSpan = Sentry.getActiveSpan();
-const rootSpan = activeSpan ? Sentry.getRootSpan(activeSpan) : undefined;
-
-// Create `sentry-trace` header
-const sentryTraceHeader = rootSpan
-  ? Sentry.spanToTraceHeader(rootSpan)
-  : undefined;
-
-// Create `baggage` header
-const sentryBaggageHeader = rootSpan
-  ? Sentry.spanToBaggageHeader(rootSpan)
-  : undefined;
+const traceData = Sentry.getTraceData();
+const sentryTraceHeader = traceData["sentry-trace"];
+const sentryBaggageHeader = traceData["baggage"];
 
 // Make outgoing request
 fetch("https://example.com", {
@@ -207,51 +38,6 @@ In this example, tracing information is propagated to the project running at `ht
 
 The two services are now connected with your custom distributed tracing implementation.
 
-<PlatformCategorySection notSupported={['browser']}>
-
-### Injecting Tracing Information into HTML
-
-If you're server-side rendering HTML and you use a Sentry SDK in your browser application, you can connect the backend and frontend traces by injecting your server's tracing information as `<meta>` tags into the HTML that's initially served to the browser. When the frontend SDK is initialized, it will automatically pick up the tracing information from the `<meta>` tags and continue the trace. Note, that your browser SDK needs to register `browserTracingIntegration` for this to work.
-
-The easiest and recommended way to do this is to use the `Sentry.getTraceMetaTags()`:
-
-```javascript {5} {filename:index.js}
-function renderHtml() {
-  return `
-    <html>
-      <head>
-        ${Sentry.getTraceMetaTags()}
-      </head>
-      <body>
-        <!-- Your HTML content -->
-      </body>
-    </html>
-  `;
-}
-```
-
-Alternatively, if you need more control over how meta tags are generated, you can use `Sentry.getTraceData()` to get only the meta tag values and generate the meta tags yourself:
-
-```javascript {2, 7-8} {filename:index.js}
-function renderHtml() {
-  const metaTagValues = Sentry.getTraceData();
-
-  return `
-    <html>
-      <head>
-        <meta name="sentry-trace" content="${metaTagValues["sentry-trace"]}">
-        <meta name="baggage" content="${metaTagValues.baggage}">
-      </head>
-      <body>
-        <!-- Your HTML content -->
-      </body>
-    </html>
-  `;
-}
-```
-
-</PlatformCategorySection>
-
 ### Starting a New Trace
 
 Available since SDK version `8.5.0`.
diff --git a/platform-includes/distributed-tracing/custom-instrumentation/rust.mdx b/platform-includes/distributed-tracing/custom-instrumentation/rust.mdx
index 972b3c31197c48..8ca062859b3d5d 100644
--- a/platform-includes/distributed-tracing/custom-instrumentation/rust.mdx
+++ b/platform-includes/distributed-tracing/custom-instrumentation/rust.mdx
@@ -30,8 +30,8 @@ let tx_ctx = sentry::TransactionContext::continue_from_headers(
 let transaction = sentry::start_transaction(tx_ctx);
 ```
 
-<Note>
+<Alert>
 
 For usage with the `tower` crate, the `SentryHttpLayer` handles trace continuations automatically when constructed via `SentryHttpLayer::with_transaction()`.
 
-</Note>
+</Alert>
diff --git a/platform-includes/distributed-tracing/custom-instrumentation/server/javascript.mdx b/platform-includes/distributed-tracing/custom-instrumentation/server/javascript.mdx
new file mode 100644
index 00000000000000..060c24539cd498
--- /dev/null
+++ b/platform-includes/distributed-tracing/custom-instrumentation/server/javascript.mdx
@@ -0,0 +1,89 @@
+Trace propagation is set up automatically in this SDK. By default, outgoing HTTP requests will automatically be instrumented for you.
+For other cases where you may want to continue traces (for example, in a job queue or when working with websockets), you can manually extract and inject tracing information.
+
+<Expandable title="What is Distributed Tracing?">
+  <PlatformContent includePath="distributed-tracing/explanation" />
+</Expandable>
+
+## Manually Extracting and Injecting Distributed Tracing Information
+
+You can also manually extract and inject tracing data into your application. For this, you must:
+
+- Extract and store incoming tracing information from incoming request headers or similar.
+- Inject tracing information to any outgoing requests.
+
+To learn more about distributed tracing, see our <PlatformLink to="/tracing/trace-propagation/">Distributed Tracing</PlatformLink> docs.
+
+### Extracting Incoming Tracing Information
+
+You must extract and store incoming tracing information in memory for later use. Sentry provides the `continueTrace()` function to help you with this. Incoming tracing information can come from different places:
+
+- In a web environment, it's sent with HTTP headers, for example, by another Sentry SDK used in your frontend project.
+- In a job queue, it can be retrieved from meta or header variables.
+- You also can pick up tracing information from environment variables.
+
+Here's an example of how to extract and store incoming tracing information using `continueTrace()`:
+
+```javascript
+const http = require("http");
+
+http.createServer((request, response) => {
+  const sentryTrace = request.headers["sentry-trace"];
+  const baggage = request.headers["baggage"];
+
+  Sentry.continueTrace({ sentryTrace, baggage }, () => {
+    Sentry.startSpan(
+      {,
+        name: "my request",
+        op: "http.server",
+      },
+      () => {
+        // Your API code...
+      }
+    );
+  });
+});
+```
+
+In this example, we create a new transaction that is attached to the trace specified in the `sentry-trace` and `baggage` headers.
+
+### Injecting Tracing Information Into HTML
+
+If you're server-side rendering HTML and you use a Sentry SDK in your browser application, you can connect the backend and frontend traces by injecting your server's tracing information as `<meta>` tags into the HTML that's initially served to the browser. When the frontend SDK is initialized, it will automatically pick up the tracing information from the `<meta>` tags and continue the trace. Note, that your browser SDK needs to register `browserTracingIntegration` for this to work.
+
+The easiest and recommended way to do this is to use the `Sentry.getTraceMetaTags()`:
+
+```javascript {5} {filename:index.js}
+function renderHtml() {
+  return `
+    <html>
+      <head>
+        ${Sentry.getTraceMetaTags()}
+      </head>
+      <body>
+        <!-- Your HTML content -->
+      </body>
+    </html>
+  `;
+}
+```
+
+Alternatively, if you need more control over how meta tags are generated, you can use `Sentry.getTraceData()` to get only the meta tag values and generate the meta tags yourself:
+
+```javascript {2, 7-8} {filename:index.js}
+function renderHtml() {
+  const metaTagValues = Sentry.getTraceData();
+
+  return `
+    <html>
+      <head>
+        <meta name="sentry-trace" content="${metaTagValues["sentry-trace"]}">
+        <meta name="baggage" content="${metaTagValues.baggage}">
+      </head>
+      <body>
+        <!-- Your HTML content -->
+      </body>
+    </html>
+  `;
+}
+```
diff --git a/platform-includes/distributed-tracing/explanation/javascript.mdx b/platform-includes/distributed-tracing/explanation/javascript.mdx
new file mode 100644
index 00000000000000..dddfe68569b47c
--- /dev/null
+++ b/platform-includes/distributed-tracing/explanation/javascript.mdx
@@ -0,0 +1,3 @@
+In the context of tracing events across a distributed system, distributed tracing acts as a powerful debugging tool. Imagine your application as a vast network of interconnected parts. For example, your system might be spread across different servers or your application might split into different backend and frontend services, each potentially having their own technology stack.
+
+When an error or performance issue occurs, it can be challenging to pinpoint the root cause due to the complexity of such a system. Distributed tracing helps you follow the path of an event as it travels through this intricate web, recording every step it takes. By examining these traces, you can reconstruct the sequence of events leading up to the event of interest, identify the specific components involved, and understand their interactions. This detailed visibility enables you to diagnose and resolve issues more effectively, ultimately improving the reliability and performance of your distributed system.
diff --git a/platform-includes/enriching-events/add-attachment/java.mdx b/platform-includes/enriching-events/add-attachment/java.mdx
index 50339926f480df..e9857da5c49a2c 100644
--- a/platform-includes/enriching-events/add-attachment/java.mdx
+++ b/platform-includes/enriching-events/add-attachment/java.mdx
@@ -70,11 +70,11 @@ class AttachmentManipulationEventProcessor: EventProcessor {
 Sentry.captureMessage("Hello, world!")
 ```
 
-<Note>
+<Alert>
 
 Instead of adding attachments, you can also remove them, by setting a different (or empty) list of attachments using `Hint#setAttachments()`.
 
-</Note>
+</Alert>
 
 ### Adding Attachments in `beforeSend`
 
@@ -103,10 +103,10 @@ options.beforeSend = BeforeSendCallback { event, hint ->
 }
 ```
 
-<Note>
+<Alert>
 
 Instead of adding attachments, you can also remove them, by setting a different (or empty) list of attachments using `Hint#setAttachments()`.
 
-</Note>
+</Alert>
 
 ### Adding Attachments to the Scope
diff --git a/platform-includes/enriching-events/attach-screenshots/android.mdx b/platform-includes/enriching-events/attach-screenshots/android.mdx
index 9b4036c1480456..93a5272c8601d7 100644
--- a/platform-includes/enriching-events/attach-screenshots/android.mdx
+++ b/platform-includes/enriching-events/attach-screenshots/android.mdx
@@ -6,11 +6,11 @@
 
 ### Customize Screenshot Capturing
 
-<Note>
+<Alert>
 
 Requires SDK version `6.24.0` or higher.
 
-</Note>
+</Alert>
 
 Because capturing screenshots can be a resource-intensive operation on Android, it's limited to one screenshot every 2 seconds using a debouncing mechanism. This behavior can be overruled if you supply a `BeforeCaptureCallback` for screenshots in the `SentryAndroidOptions`.
 
diff --git a/platform-includes/enriching-events/attach-screenshots/apple.mdx b/platform-includes/enriching-events/attach-screenshots/apple.mdx
index 864bf876b7ecc9..b748359cf9c159 100644
--- a/platform-includes/enriching-events/attach-screenshots/apple.mdx
+++ b/platform-includes/enriching-events/attach-screenshots/apple.mdx
@@ -16,11 +16,11 @@ SentrySDK.start { options in
 
 ### Customize Screenshot Capturing
 
-<Note>
+<Alert>
 
 Requires Cocoa SDK version `8.27.0` or higher.
 
-</Note>
+</Alert>
 
 
 The `beforeCaptureScreenshot` also allows you to customize the behavior based on event data, so you can decide when to capture a screenshot and when not to. The callback doesn't work for crash events.
diff --git a/platform-includes/enriching-events/attach-screenshots/flutter.mdx b/platform-includes/enriching-events/attach-screenshots/flutter.mdx
index 70bb59631aba6e..a19cedf2382e81 100644
--- a/platform-includes/enriching-events/attach-screenshots/flutter.mdx
+++ b/platform-includes/enriching-events/attach-screenshots/flutter.mdx
@@ -15,11 +15,11 @@ await SentryFlutter.init(
 
 ### Customize Screenshot Capturing
 
-<Note>
+<Alert>
 
 Requires SDK version `8.11.0` or higher.
 
-</Note>
+</Alert>
 
 Capturing screenshots on Flutter is limited to once every 2 seconds by default to minimize performance impact. While this debounce interval is fixed, you can override individual capture decisions by implementing the `beforeCaptureScreenshot` option in your `SentryFlutterOptions`.
 
diff --git a/platform-includes/enriching-events/attach-screenshots/unity.mdx b/platform-includes/enriching-events/attach-screenshots/unity.mdx
index 64fb0d72dd24ed..6c6e880509a43d 100644
--- a/platform-includes/enriching-events/attach-screenshots/unity.mdx
+++ b/platform-includes/enriching-events/attach-screenshots/unity.mdx
@@ -15,8 +15,8 @@ Since the Unity SDK internally consists of multiple SDKs, the mechanism with whi
 - C# errors from within your game will be captured through Unity's built-in [ScreenCapture](https://docs.unity3d.com/ScriptReference/ScreenCapture.html). This means that screenshots only contain things visible within your game. Overlays on top of your game will not be visible.
 - Native errors get captured by their respective SDK. If you're using a native plugin to display an overlay and an error occurs then that SDK will try to capture a screenshot that contains the overlay.
 
-<Note>
+<Alert>
 
 Screenshots might contain PII of your app. For example, if your game has a registration form and an error happens while the form is being displayed.
 
-</Note>
+</Alert>
diff --git a/platform-includes/enriching-events/attach-screenshots/unreal.mdx b/platform-includes/enriching-events/attach-screenshots/unreal.mdx
index 708c1200fd0500..f6b93b54a4b050 100644
--- a/platform-includes/enriching-events/attach-screenshots/unreal.mdx
+++ b/platform-includes/enriching-events/attach-screenshots/unreal.mdx
@@ -9,11 +9,11 @@ USentrySettings* Settings = FSentryModule::Get().GetSettings();
 Settings->AttachScreenshot = true;
 ```
 
-<Note>
+<Alert>
 
 Currently, this feature is supported for Windows and Linux only.
 
-</Note>
+</Alert>
 
 ## Screenshot Capture Mechanism
 
@@ -22,8 +22,8 @@ Since the Unreal Engine SDK consists of multiple SDKs, the specific mechanism wi
 - On Windows/Linux, errors from within your game will be captured using the Unreal Engine API. This means that screenshots will only contain what's visible within your game. Any overlays on top of your game won't be visible.
 - On Apple/Android, screenshots will be captured using platform APIs. If you're using a native plugin to display an overlay and an error occurs, the SDK will try to capture a screenshot that contains the overlay.
 
-<Note>
+<Alert>
 
 **Screenshots may contain PII.** For example, if your game has a registration form and an error occurs while the form is being displayed.
 
-</Note>
+</Alert>
diff --git a/platform-includes/enriching-events/attach-viewhierarchy/apple.mdx b/platform-includes/enriching-events/attach-viewhierarchy/apple.mdx
index 308c004975de2c..831d0fd83ea95c 100644
--- a/platform-includes/enriching-events/attach-viewhierarchy/apple.mdx
+++ b/platform-includes/enriching-events/attach-viewhierarchy/apple.mdx
@@ -16,11 +16,11 @@ SentrySDK.start { options in
 
 ### Customize View Hierarchy Capturing
 
-<Note>
+<Alert>
 
 Requires Cocoa SDK version `8.33.0` or higher.
 
-</Note>
+</Alert>
 
 
 The `beforeCaptureViewHierarchy` also allows you to customize the behavior based on event data, so you can decide when to capture a view hierarchy and when not to. The callback doesn't work for crash events.
diff --git a/platform-includes/enriching-events/attach-viewhierarchy/kotlin.kotlin-multiplatform.mdx b/platform-includes/enriching-events/attach-viewhierarchy/kotlin.kotlin-multiplatform.mdx
index 0b33a1c91cf710..a28834e90ad4a7 100644
--- a/platform-includes/enriching-events/attach-viewhierarchy/kotlin.kotlin-multiplatform.mdx
+++ b/platform-includes/enriching-events/attach-viewhierarchy/kotlin.kotlin-multiplatform.mdx
@@ -1,8 +1,8 @@
-<Note>
+<Alert>
 
 Currently only available on iOS and Android.
 
-</Note>
+</Alert>
 
 
 ```kotlin
diff --git a/platform-includes/enriching-events/attachment-init-with-path/dart.mdx b/platform-includes/enriching-events/attachment-init-with-path/dart.mdx
index 3892b1adfd44c4..9952de61f114a5 100644
--- a/platform-includes/enriching-events/attachment-init-with-path/dart.mdx
+++ b/platform-includes/enriching-events/attachment-init-with-path/dart.mdx
@@ -1,8 +1,8 @@
-<Note>
+<Alert>
 
 Adding an attachment by way of path is not available on web platforms.
 
-</Note>
+</Alert>
 
 ```dart
 import 'package:sentry/sentry_io.dart';
diff --git a/platform-includes/enriching-events/breadcrumbs/before-breadcrumb/php.laravel.mdx b/platform-includes/enriching-events/breadcrumbs/before-breadcrumb/php.laravel.mdx
index 5552f2ec65d73a..999c42170ff869 100644
--- a/platform-includes/enriching-events/breadcrumbs/before-breadcrumb/php.laravel.mdx
+++ b/platform-includes/enriching-events/breadcrumbs/before-breadcrumb/php.laravel.mdx
@@ -4,8 +4,8 @@
 },
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Closures and Config Caching](/platforms/php/guides/laravel/configuration/laravel-options/#closures-and-config-caching).
 
-</Note>
+</Alert>
diff --git a/platform-includes/enriching-events/breadcrumbs/before-breadcrumb/php.symfony.mdx b/platform-includes/enriching-events/breadcrumbs/before-breadcrumb/php.symfony.mdx
index 967e15541d4273..366741d52807c1 100644
--- a/platform-includes/enriching-events/breadcrumbs/before-breadcrumb/php.symfony.mdx
+++ b/platform-includes/enriching-events/breadcrumbs/before-breadcrumb/php.symfony.mdx
@@ -28,8 +28,8 @@ class Sentry
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Callables in Symfony Options](/platforms/php/guides/symfony/configuration/symfony-options/#callables).
 
-</Note>
+</Alert>
diff --git a/platform-includes/enriching-events/scopes/configure-scope/android__v7.x.mdx b/platform-includes/enriching-events/scopes/configure-scope/android__v7.x.mdx
new file mode 100644
index 00000000000000..3a9fcd2f272d85
--- /dev/null
+++ b/platform-includes/enriching-events/scopes/configure-scope/android__v7.x.mdx
@@ -0,0 +1,25 @@
+```java {tabTitle: Java}
+import io.sentry.Sentry;
+import io.sentry.protocol.User;
+
+Sentry.configureScope(scope -> {
+  scope.setTag("my-tag", "my value");
+  User user = new User();
+  user.setId("42");
+  user.setEmail("john.doe@example.com");
+  scope.setUser(user);
+});
+```
+
+```kotlin {tabTitle: Kotlin}
+import io.sentry.Sentry
+import io.sentry.protocol.User
+
+Sentry.configureScope { scope ->
+  scope.setTag("my-tag", "my value")
+  scope.user = User().apply {
+    id = "42"
+    email = "john.doe@example.com"
+  }
+}
+```
diff --git a/platform-includes/enriching-events/scopes/configure-scope/java__v7.x.mdx b/platform-includes/enriching-events/scopes/configure-scope/java__v7.x.mdx
new file mode 100644
index 00000000000000..3a9fcd2f272d85
--- /dev/null
+++ b/platform-includes/enriching-events/scopes/configure-scope/java__v7.x.mdx
@@ -0,0 +1,25 @@
+```java {tabTitle: Java}
+import io.sentry.Sentry;
+import io.sentry.protocol.User;
+
+Sentry.configureScope(scope -> {
+  scope.setTag("my-tag", "my value");
+  User user = new User();
+  user.setId("42");
+  user.setEmail("john.doe@example.com");
+  scope.setUser(user);
+});
+```
+
+```kotlin {tabTitle: Kotlin}
+import io.sentry.Sentry
+import io.sentry.protocol.User
+
+Sentry.configureScope { scope ->
+  scope.setTag("my-tag", "my value")
+  scope.user = User().apply {
+    id = "42"
+    email = "john.doe@example.com"
+  }
+}
+```
diff --git a/platform-includes/enriching-events/scopes/scope-callback-param/java__v7.x.mdx b/platform-includes/enriching-events/scopes/scope-callback-param/java__v7.x.mdx
new file mode 100644
index 00000000000000..e7dbe6e8eafd4b
--- /dev/null
+++ b/platform-includes/enriching-events/scopes/scope-callback-param/java__v7.x.mdx
@@ -0,0 +1,27 @@
+```java {tabTitle: Java}
+import io.sentry.Sentry;
+import io.sentry.SentryLevel;
+
+// will be tagged with my-tag="my value"
+Sentry.captureException(new Exception("my error"), scope -> {
+  scope.setTag("my-tag", "my value");
+  scope.setLevel(SentryLevel.WARNING);
+});
+
+// will not be tagged with my-tag
+Sentry.captureException(new Exception("my error"));
+```
+
+```kotlin {tabTitle: Kotlin}
+import io.sentry.Sentry
+import io.sentry.SentryLevel
+
+// will be tagged with my-tag="my value"
+Sentry.captureException(Exception("my error")) { scope ->
+  scope.setTag("my-tag", "my value")
+  scope.level = SentryLevel.WARNING
+}
+
+// will not be tagged with my-tag
+Sentry.captureException(Exception("my error"))
+```
diff --git a/platform-includes/enriching-events/scopes/with-isolation-scope/java.mdx b/platform-includes/enriching-events/scopes/with-isolation-scope/java.mdx
index 679972585945c5..440c0679dc360c 100644
--- a/platform-includes/enriching-events/scopes/with-isolation-scope/java.mdx
+++ b/platform-includes/enriching-events/scopes/with-isolation-scope/java.mdx
@@ -32,7 +32,7 @@ Sentry.withIsolationScope { scope ->
 Sentry.captureException(Exception("my other error"))
 ```
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 In the Java SDK `withIsolationScope` does **not** work reliably in `globalHubMode`, as the SDK always uses the global root scopes unless you call the `captureXXX` methods directly on `Scopes`.
 
diff --git a/platform-includes/enriching-events/scopes/with-scope/java.mdx b/platform-includes/enriching-events/scopes/with-scope/java.mdx
index 7853931058dc0c..48579041dc5511 100644
--- a/platform-includes/enriching-events/scopes/with-scope/java.mdx
+++ b/platform-includes/enriching-events/scopes/with-scope/java.mdx
@@ -32,7 +32,7 @@ Sentry.withScope { scope ->
 Sentry.captureException(Exception("my error"))
 ```
 
-<Alert level="info" title="Important">
+<Alert title="Important">
 
 In the Java SDK `withScope` does **not** work reliably in `globalHubMode` as the SDK always uses the global root scopes unless you call the `captureXXX` methods directly on `Scopes`.
 
diff --git a/platform-includes/enriching-events/scopes/with-scope/java__v7.x.mdx b/platform-includes/enriching-events/scopes/with-scope/java__v7.x.mdx
new file mode 100644
index 00000000000000..b343e1d61e24be
--- /dev/null
+++ b/platform-includes/enriching-events/scopes/with-scope/java__v7.x.mdx
@@ -0,0 +1,41 @@
+<PlatformSection notSupported={["android"]}>
+
+```java {tabTitle: Java}
+import io.sentry.Sentry;
+import io.sentry.SentryLevel;
+
+Sentry.withScope(scope -> {
+  scope.setTag("my-tag", "my value");
+  scope.setLevel(SentryLevel.WARNING);
+
+  // will be tagged with my-tag="my value"
+  Sentry.captureException(new Exception("my error"));
+});
+
+// will not be tagged with my-tag
+Sentry.captureException(new Exception("my error"));
+```
+
+```kotlin {tabTitle: Kotlin}
+import io.sentry.Sentry
+import io.sentry.SentryLevel
+
+Sentry.withScope { scope ->
+  scope.setTag("my-tag", "my value")
+  scope.level = SentryLevel.WARNING
+
+  // will be tagged with my-tag="my value"
+  Sentry.captureException(Exception("my error"))
+}
+
+// will not be tagged with my-tag
+Sentry.captureException(Exception("my error"))
+```
+
+<Alert title="Important">
+
+In the Java SDK `withScope` does **not** work reliably in `globalHubMode` as the `scope` gets pushed on the stack global to the hub. In `globalHubMode` use the callback parameter of the capture methods detailed below.
+
+</Alert>
+
+</PlatformSection>
diff --git a/platform-includes/enriching-events/scopes/with-scope/unreal.mdx b/platform-includes/enriching-events/scopes/with-scope/unreal.mdx
index 7f12f9f8b79a35..7367ca978da54f 100644
--- a/platform-includes/enriching-events/scopes/with-scope/unreal.mdx
+++ b/platform-includes/enriching-events/scopes/with-scope/unreal.mdx
@@ -1,8 +1,8 @@
-<Note>
+<Alert>
 
 Local scopes are supported for iOS and Android only.
 
-</Note>
+</Alert>
 
 ```cpp
 FConfigureScopeDelegate ScopeDelegate;
diff --git a/platform-includes/enriching-events/set-tag/dotnet.nlog.mdx b/platform-includes/enriching-events/set-tag/dotnet.nlog.mdx
index afcbda6bbf2160..d5917315c7a4b8 100644
--- a/platform-includes/enriching-events/set-tag/dotnet.nlog.mdx
+++ b/platform-includes/enriching-events/set-tag/dotnet.nlog.mdx
@@ -1,4 +1,4 @@
-<Alert level="" title="NLog Layouts">
+<Alert title="NLog Layouts">
 
 For more information on how to dynamically set event tags via `NLog.config`, see NLog's [layout renderer documentation](https://nlog-project.org/config/?tab=layout-renderers).
 
diff --git a/platform-includes/enriching-events/set-user/dotnet.nlog.mdx b/platform-includes/enriching-events/set-user/dotnet.nlog.mdx
index 76e2198ef9f9cc..28ec6343db210c 100644
--- a/platform-includes/enriching-events/set-user/dotnet.nlog.mdx
+++ b/platform-includes/enriching-events/set-user/dotnet.nlog.mdx
@@ -1,4 +1,4 @@
-<Alert level="" title="NLog Configuration">
+<Alert title="NLog Configuration">
 
 - If setting it via `NLog.config`, the camelCase key `ipAddress` should be used instead of `ip_address`.
 - For more information on how to dynamically set event data via `NLog.config`, see NLog's [layout renderer documentation](https://nlog-project.org/config/?tab=layout-renderers).
diff --git a/platform-includes/enriching-events/set-user/native.mdx b/platform-includes/enriching-events/set-user/native.mdx
index f77b4a2a3584fc..a4549957ae4315 100644
--- a/platform-includes/enriching-events/set-user/native.mdx
+++ b/platform-includes/enriching-events/set-user/native.mdx
@@ -7,8 +7,8 @@ sentry_value_set_by_key(user, "email", sentry_value_new_string("jane.doe@example
 sentry_set_user(user);
 ```
 
-<Note>
+<Alert>
 
 To see user statistics in [Release Health](/platforms/native/configuration/releases/#release-health), set at least one of the following: `id`, `username`, or `email`.
 
-</Note>
+</Alert>
diff --git a/platform-includes/enriching-events/unset-user/java__v7.x.mdx b/platform-includes/enriching-events/unset-user/java__v7.x.mdx
new file mode 100644
index 00000000000000..6f76599534358d
--- /dev/null
+++ b/platform-includes/enriching-events/unset-user/java__v7.x.mdx
@@ -0,0 +1,15 @@
+```java {tabTitle: Java}
+import io.sentry.Sentry;
+
+Sentry.configureScope(scope -> {
+  scope.setUser(null);
+});
+```
+
+```kotlin {tabTitle: Kotlin}
+import io.sentry.Sentry
+
+Sentry.configureScope { scope ->
+  scope.user = null
+}
+```
diff --git a/platform-includes/feature-flags/prerelease-alert/_default.mdx b/platform-includes/feature-flags/prerelease-alert/_default.mdx
index 30f9be37162271..3c6d9940aa5ad6 100644
--- a/platform-includes/feature-flags/prerelease-alert/_default.mdx
+++ b/platform-includes/feature-flags/prerelease-alert/_default.mdx
@@ -1,4 +1,4 @@
-<Alert level="info" title="Currently in Beta">
+<Alert title="Currently in Beta">
 
 Feature flag change tracking and feature flag evaluation tracking is currently in open beta.
 
diff --git a/platform-includes/getting-started-config/dotnet.mdx b/platform-includes/getting-started-config/dotnet.mdx
index a54bb8b9badeee..8145eb19009f0d 100644
--- a/platform-includes/getting-started-config/dotnet.mdx
+++ b/platform-includes/getting-started-config/dotnet.mdx
@@ -26,10 +26,10 @@ SentrySdk.Init(options =>
 });
 ```
 
-<Note>
+<Alert>
 
 After you have configured Sentry in your code, you can also configure the
 [MSBuild setup](/platforms/dotnet/configuration/msbuild/) for your project. While this step is optional,
 it can greatly improve your Sentry experience.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-config/java.jul.mdx b/platform-includes/getting-started-config/java.jul.mdx
index 70c236ef177f32..c53cc62e6a1581 100644
--- a/platform-includes/getting-started-config/java.jul.mdx
+++ b/platform-includes/getting-started-config/java.jul.mdx
@@ -2,11 +2,11 @@ Configuration should happen as early as possible in your application's lifecycle
 
 The following example configures a `ConsoleHandler` that logs to standard out at the `INFO` level and a `SentryHandler` that logs to the Sentry server at the `WARN` level. The `ConsoleHandler` is only provided as an example of a non-Sentry appender that is set to a different logging threshold, like one you may already have in your project.
 
-<Note>
+<Alert>
 
 The `ConsoleHandler` is provided only as an example of a non-Sentry appender set to a different logging threshold, similar to what you may already have in your project.
 
-</Note>
+</Alert>
 
 Example configuration using the `logging.properties` format:
 
@@ -45,11 +45,11 @@ Two log levels are used to configure this integration:
 1. Configure the lowest level required for a log message to become an event (`minimumEventLevel`) sent to Sentry.
 2. Configure the lowest level a message has to be to become a breadcrumb (`minimumBreadcrumbLevel`).
 
-<Note>
+<Alert>
 
 Setting `minimumEventLevel` or `minimumBreadcrumbLevel` in `logging.properties` only affects events logged by way of JUL. The settings will have no effect when calling `Sentry.captureMessage` or similar directly.
 
-</Note>
+</Alert>
 
 Breadcrumbs are kept in memory (by default the last 100 records) and are sent with events. For example, by default, if you log 100 entries with `logger.config` or `logger.warn`, no event is sent to Sentry. If you then log with `logger.error`, an event is sent to Sentry which includes those 100 `config` or `warning` messages. For this to work, `SentryHandler` needs to receive **all** log entries to decide what to keep as breadcrumb or send as event. Set the `SentryHandler` log level configuration to a value lower than what is set for the `minimumBreadcrumbLevel` and `minimumEventLevel` so that `SentryHandler` receives these log messages.
 
diff --git a/platform-includes/getting-started-config/java.log4j2.mdx b/platform-includes/getting-started-config/java.log4j2.mdx
index 7cd216ff422881..6e20b2077b0aca 100644
--- a/platform-includes/getting-started-config/java.log4j2.mdx
+++ b/platform-includes/getting-started-config/java.log4j2.mdx
@@ -2,11 +2,11 @@ Configuration should happen as early as possible in your application's lifecycle
 
 The following example using the `log4j2.xml` format to configure a `ConsoleAppender` that logs to standard out at the `INFO` level, and a `SentryAppender` that logs to the Sentry server at the `ERROR` level.
 
-<Note>
+<Alert>
 
 The `ConsoleAppender` is provided only as an example of a non-Sentry appender set to a different logging threshold, similar to what you may already have in your project.
 
-</Note>
+</Alert>
 
 <OnboardingOption optionId="opentelemetry" hideForThisOption>
 ```xml
@@ -75,11 +75,11 @@ Two log levels are used to configure this integration, as illustrated below in t
 1. Configure the lowest level required for a log message to become an event (`minimumEventLevel`) sent to Sentry.
 2. Configure the lowest level a message has to be to become a breadcrumb (`minimumBreadcrumbLevel`)
 
-<Note>
+<Alert>
 
 Setting `minimumEventLevel` or `minimumBreadcrumbLevel` in `log4j2.xml` only affects events logged by way of Log4j2. The settings will have no effect when calling `Sentry.captureMessage` or similar directly.
 
-</Note>
+</Alert>
 
 Breadcrumbs are kept in memory (by default the last 100 records) and are sent with events. For example, by default, if you log 100 entries with `logger.info` or `logger.warn`, no event is sent to Sentry. If you then log with `logger.error`, an event is sent to Sentry that includes those 100 `info` or `warn` messages. For this to work, `SentryAppender` needs to receive **all** log entries to decide what to keep as breadcrumb or send as event. Set the `SentryAppender` log level configuration to a value lower than what is set for the `minimumBreadcrumbLevel` and `minimumEventLevel` so that `SentryAppender` receives these log messages.
 
diff --git a/platform-includes/getting-started-config/java.logback.mdx b/platform-includes/getting-started-config/java.logback.mdx
index c47a2f0ac18b24..bc0a377d9bb263 100644
--- a/platform-includes/getting-started-config/java.logback.mdx
+++ b/platform-includes/getting-started-config/java.logback.mdx
@@ -2,11 +2,11 @@ Configuration should happen as early as possible in your application's lifecycle
 
 The following example configures a `ConsoleAppender` that logs to standard out at the `INFO` level, and a `SentryAppender` that logs to the Sentry server at the `ERROR` level.
 
-<Note>
+<Alert>
 
 The `ConsoleAppender` is provided only as an example of a non-Sentry appender set to a different logging threshold, similar to what you may already have in your project.
 
-</Note>
+</Alert>
 
 <OnboardingOption optionId="opentelemetry" hideForThisOption>
 ```xml
@@ -84,11 +84,11 @@ Two log levels are used to configure this integration:
 1. Configure the lowest level required for a log message to become an event (`minimumEventLevel`) sent to Sentry.
 2. Configure the lowest level a message has to be to become a breadcrumb (`minimumBreadcrumbLevel`).
 
-<Note>
+<Alert>
 
 Setting `minimumEventLevel` or `minimumBreadcrumbLevel` in `logback.xml` only affects events logged by way of Logback. The settings will have no effect when calling `Sentry.captureMessage` or similar directly.
 
-</Note>
+</Alert>
 
 Breadcrumbs are kept in memory (by default the last 100 records) and are sent with events. For example, by default, if you log 100 entries with `logger.info` or `logger.warn`, no event is sent to Sentry. If you then log with `logger.error`, an event is sent to Sentry which includes those 100 `info` or `warn` messages. For this to work, `SentryAppender` needs to receive **all** log entries to decide what to keep as breadcrumb or sent as event. Set the `SentryAppender` log level configuration to a value lower than what is set for the `minimumBreadcrumbLevel` and `minimumEventLevel` so that `SentryAppender` receives these log messages.
 
diff --git a/platform-includes/getting-started-config/javascript.cloudflare.mdx b/platform-includes/getting-started-config/javascript.cloudflare.mdx
index 815755c2e0c0de..e9de333b3cb502 100644
--- a/platform-includes/getting-started-config/javascript.cloudflare.mdx
+++ b/platform-includes/getting-started-config/javascript.cloudflare.mdx
@@ -1,11 +1,21 @@
-To use the SDK, you'll need to set either the `nodejs_compat` or `nodejs_als` compatibility flags in your `wrangler.toml`. This is because the SDK
+To use the SDK, you'll need to set either the `nodejs_compat` or `nodejs_als` compatibility flags in your `wrangler.toml`/`wrangler.json`. This is because the SDK
 needs access to the `AsyncLocalStorage` API to work correctly.
 
-```toml {filename:wrangler.toml}
+
+```toml {tabTitle:Toml} {filename:wrangler.toml}
 compatibility_flags = ["nodejs_compat"]
 # compatibility_flags = ["nodejs_als"]
 ```
 
+```json {tabTitle:JSON} {filename:wrangler.json}
+{
+  "compatibility_flags": [
+    "nodejs_compat",
+    // "nodejs_als"
+  ]
+}
+```
+
 Then you can install the SDK and add it to your project:
 
 You can either setup up the SDK for [Cloudflare Pages](#setup-cloudflare-pages) or
@@ -40,10 +50,10 @@ export const onRequest = [
 To use this SDK, wrap your handler with the `withSentry` function. This will initialize the SDK and hook into the
 environment. Note that you can turn off almost all side effects using the respective options.
 
-```javascript
-import * as Sentry from '@sentry/cloudflare';
+```typescript {filename:index.ts}
+import * as Sentry from "@sentry/cloudflare";
 
-export default withSentry(
+export default Sentry.withSentry(
   env => ({
     dsn: "___PUBLIC_DSN___",
     // Set tracesSampleRate to 1.0 to capture 100% of spans for tracing.
@@ -53,7 +63,7 @@ export default withSentry(
   }),
   {
     async fetch(request, env, ctx) {
-      return new Response('Hello World!');
+      return new Response("Hello World!");
     },
   } satisfies ExportedHandler<Env>,
 );
diff --git a/platform-includes/getting-started-config/javascript.ember.mdx b/platform-includes/getting-started-config/javascript.ember.mdx
index 318b47d4b0c648..299f6c20e46993 100644
--- a/platform-includes/getting-started-config/javascript.ember.mdx
+++ b/platform-includes/getting-started-config/javascript.ember.mdx
@@ -35,8 +35,8 @@ export default class App extends Application {
 }
 ```
 
-<Note>
+<Alert>
 
 This SDK uses Ember configuration conventions to manage its automatic instrumentation and other Sentry options. This additional configuration can be found under <PlatformLink to="/configuration/ember-options/">Ember options</PlatformLink>.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-config/javascript.solid.mdx b/platform-includes/getting-started-config/javascript.solid.mdx
index 996f89baa2cab5..0f25675adbf56e 100644
--- a/platform-includes/getting-started-config/javascript.solid.mdx
+++ b/platform-includes/getting-started-config/javascript.solid.mdx
@@ -1,8 +1,8 @@
 To use the SDK, initialize it in your Solid entry point before bootstrapping your app. In a typical Solid project, that is your `index.jsx` file.
 
-<Note>
+<Alert>
   We currently support Solid 1.8.4 and up.
-</Note>
+</Alert>
 
 
 ```javascript {filename: index.jsx} {"onboardingOptions": {"performance": "2, 12, 15-22", "session-replay": "13, 23-27"}}
diff --git a/platform-includes/getting-started-config/javascript.solidstart.mdx b/platform-includes/getting-started-config/javascript.solidstart.mdx
index 44ea4be0dc10e8..97bf45757f4476 100644
--- a/platform-includes/getting-started-config/javascript.solidstart.mdx
+++ b/platform-includes/getting-started-config/javascript.solidstart.mdx
@@ -17,24 +17,24 @@ Sentry.init({
 mount(() => <StartClient />, document.getElementById('app'));
 ```
 
-<Note>
+<Alert>
 
   Depending on the configuration of your SolidStart project, the file structure may differ from the code listed on this page.
   For example, for JavaScript projects files end in `.js` and `.jsx` while we use TypeScript snippets here ending in `.ts` and `.tsx`.
 
-</Note>
+</Alert>
 
 ### Server-side Setup
 
 Create an instrument file `instrument.server.mjs`, initialize the Sentry SDK and deploy it alongside your application.
 For example by placing it in the `public` folder.
 
-<Note>
+<Alert>
 
   Placing `instrument.server.mjs` inside the `public` folder makes it accessible to the outside world.
   Consider blocking requests to this file or finding a more appropriate location which your backend can access.
 
-</Note>
+</Alert>
 
 
 ```javascript {filename:public/instrument.server.mjs}
diff --git a/platform-includes/getting-started-config/unreal.mdx b/platform-includes/getting-started-config/unreal.mdx
index c28fe39381f10d..74b35f21c63a19 100644
--- a/platform-includes/getting-started-config/unreal.mdx
+++ b/platform-includes/getting-started-config/unreal.mdx
@@ -7,11 +7,11 @@ The minimum configuration required is the [DSN](/product/sentry-basics/dsn-expla
 }
 ```
 
-<Note>
+<Alert>
 
 If you are logged in, you can also go to your project settings and copy its DSN directly from there.
 
-</Note>
+</Alert>
 
 Sentry can be configured using the Sentry configuration window.
 The window can be accessed by going to editor's menu: **Project Settings > Plugins > Sentry**.
diff --git a/platform-includes/getting-started-install/java.jul.mdx b/platform-includes/getting-started-install/java.jul.mdx
index d850fd7c907f29..03194c8bcfbf95 100644
--- a/platform-includes/getting-started-install/java.jul.mdx
+++ b/platform-includes/getting-started-install/java.jul.mdx
@@ -20,8 +20,8 @@ libraryDependencies += "io.sentry" % "sentry-jul" % "{{@inject packages.version(
 
 For other dependency managers, see the [central Maven repository](https://search.maven.org/artifact/io.sentry/sentry-jul).
 
-<Note>
+<Alert>
 
 If you are using multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-install/java.log4j2.mdx b/platform-includes/getting-started-install/java.log4j2.mdx
index 6b8c10478faac0..fe53fa47cdb28b 100644
--- a/platform-includes/getting-started-install/java.log4j2.mdx
+++ b/platform-includes/getting-started-install/java.log4j2.mdx
@@ -26,10 +26,10 @@ libraryDependencies += "io.sentry" % "sentry-log4j2" % "{{@inject packages.versi
 
 For other dependency managers see the [central Maven repository](https://search.maven.org/artifact/io.sentry/sentry-log4j2).
 
-<Note>
+<Alert>
 
 We recommend using our Gradle plugin as it can add integrations and provide source context for events.
 
 If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-install/java.logback.mdx b/platform-includes/getting-started-install/java.logback.mdx
index 64d1cd3d779e37..e267a1c74af0ba 100644
--- a/platform-includes/getting-started-install/java.logback.mdx
+++ b/platform-includes/getting-started-install/java.logback.mdx
@@ -26,10 +26,10 @@ libraryDependencies += "io.sentry" % "sentry-logback" % "{{@inject packages.vers
 
 For other dependency managers, see the [central Maven repository](https://search.maven.org/artifact/io.sentry/sentry-logback).
 
-<Note>
+<Alert>
 
 We recommend using our Gradle plugin as it can add integrations and provide source context for events.
 
 If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-install/java.mdx b/platform-includes/getting-started-install/java.mdx
index f5e51bb43616ba..b5725503b1a2df 100644
--- a/platform-includes/getting-started-install/java.mdx
+++ b/platform-includes/getting-started-install/java.mdx
@@ -20,10 +20,10 @@ plugins {
 libraryDependencies += "io.sentry" % "sentry" % "{{@inject packages.version('sentry.java', '4.2.0') }}"
 ```
 
-<Note>
+<Alert>
 
 We recommend using our Gradle plugin as it can add integrations and provide source context for events.
 
 If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-install/java.servlet.mdx b/platform-includes/getting-started-install/java.servlet.mdx
index 7e317e40b7211f..a461b7d5bf14ae 100644
--- a/platform-includes/getting-started-install/java.servlet.mdx
+++ b/platform-includes/getting-started-install/java.servlet.mdx
@@ -22,11 +22,11 @@ For other dependency managers, see the [central Maven repository](https://search
 
 `sentry-servlet` module comes with a `ServletContainerInitializer` that registers a `ServletRequestListener` which enhances each Sentry event triggered within the scope of HTTP request with a request information like HTTP method, query string, url and HTTP headers.
 
-<Note>
+<Alert>
 
 If you are using multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency.
 
-</Note>
+</Alert>
 
 ### Jakarta support
 
diff --git a/platform-includes/getting-started-install/java.spring-boot.mdx b/platform-includes/getting-started-install/java.spring-boot.mdx
index 80b0108e57c96b..0c7db852f4e862 100644
--- a/platform-includes/getting-started-install/java.spring-boot.mdx
+++ b/platform-includes/getting-started-install/java.spring-boot.mdx
@@ -32,10 +32,10 @@ implementation 'io.sentry:sentry-spring-boot-starter:{{@inject packages.version(
 implementation 'io.sentry:sentry-spring-boot-starter-jakarta:{{@inject packages.version('sentry.java.spring-boot.jakarta', '6.7.0') }}'
 ```
 
-<Note>
+<Alert>
 
 We recommend using our Gradle plugin as it can add integrations and provide source context for events.
 
 If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-install/java.spring.mdx b/platform-includes/getting-started-install/java.spring.mdx
index 8929fc9cb223b9..d1a2b3a07ea632 100644
--- a/platform-includes/getting-started-install/java.spring.mdx
+++ b/platform-includes/getting-started-install/java.spring.mdx
@@ -42,10 +42,10 @@ libraryDependencies += "io.sentry" % "sentry-spring-jakarta" % "{{@inject packag
 
 For other dependency managers see the [central Maven repository (Spring 5)](https://search.maven.org/artifact/io.sentry/sentry-spring) and [central Maven repository (Spring 6)](https://search.maven.org/artifact/io.sentry/sentry-spring-jakarta).
 
-<Note>
+<Alert>
 
 We recommend using our Gradle plugin as it can add integrations and provide source context for events.
 
 If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-install/javascript.mdx b/platform-includes/getting-started-install/javascript.mdx
index 3334157abccef8..28f8993139551c 100644
--- a/platform-includes/getting-started-install/javascript.mdx
+++ b/platform-includes/getting-started-install/javascript.mdx
@@ -24,11 +24,11 @@ yarn add @sentry/browser
 pnpm add @sentry/browser
 ```
 
-<Note>
+<Alert>
 
 We also support installation via [CDN bundles](/platforms/javascript/install/loader/#cdn).
 
-</Note>
+</Alert>
 
 If you're updating your Sentry SDK to the latest version, check out our [migration guide](https://github.com/getsentry/sentry-javascript/blob/master/MIGRATION.md) to learn more about breaking changes.
 
diff --git a/platform-includes/getting-started-install/javascript.nextjs.mdx b/platform-includes/getting-started-install/javascript.nextjs.mdx
index 6f31f16534b08e..2be74b8fe81c0f 100644
--- a/platform-includes/getting-started-install/javascript.nextjs.mdx
+++ b/platform-includes/getting-started-install/javascript.nextjs.mdx
@@ -17,8 +17,8 @@ You can also <PlatformLink to="/usage/">manually capture errors</PlatformLink>.
 
 To learn how to connect your app to Sentry and deploy it on Vercel, see the [Vercel integration](/organization/integrations/deployment/vercel/).
 
-<Note>
+<Alert>
 
 If the setup through the wizard doesn't work for you, you can also <PlatformLink to="/manual-setup/">set up the SDK manually</PlatformLink>.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-install/javascript.nuxt.mdx b/platform-includes/getting-started-install/javascript.nuxt.mdx
index 4225ac74c5cdf0..08cf6b3740c764 100644
--- a/platform-includes/getting-started-install/javascript.nuxt.mdx
+++ b/platform-includes/getting-started-install/javascript.nuxt.mdx
@@ -16,6 +16,6 @@ After the wizard setup is completed, the SDK will automatically capture unhandle
 
 You can also <PlatformLink to="/usage/">manually capture errors</PlatformLink>.
 
-<Note>
+<Alert>
   If the setup through the wizard doesn't work for you, you can also <PlatformLink to="/manual-setup/">set up the SDK manually</PlatformLink>.
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-install/javascript.remix.mdx b/platform-includes/getting-started-install/javascript.remix.mdx
index f077b6a874aaba..9174e7f78015d3 100644
--- a/platform-includes/getting-started-install/javascript.remix.mdx
+++ b/platform-includes/getting-started-install/javascript.remix.mdx
@@ -17,8 +17,8 @@ If you use [Remix future flags](https://remix.run/docs/en/main/pages/api-develop
 After the wizard setup is completed, the SDK will automatically capture unhandled errors, and monitor performance.
 You can also <PlatformLink to="/usage/">manually capture errors</PlatformLink>.
 
-<Note>
+<Alert>
 
 If the wizard setup isn't working for you, you can <PlatformLink to="/manual-setup/">set up the SDK manually</PlatformLink>.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-install/javascript.sveltekit.mdx b/platform-includes/getting-started-install/javascript.sveltekit.mdx
index 07ffb583e14c6f..2828ed8a363ad7 100644
--- a/platform-includes/getting-started-install/javascript.sveltekit.mdx
+++ b/platform-includes/getting-started-install/javascript.sveltekit.mdx
@@ -15,8 +15,8 @@ The wizard will prompt you to log in to Sentry. It will then automatically do th
 After the wizard setup is completed, the SDK will automatically capture unhandled errors, and monitor performance.
 You can also <PlatformLink to="/usage/">manually capture errors</PlatformLink>.
 
-<Note>
+<Alert>
 
 If the setup through the wizard doesn't work for you, you can also <PlatformLink to="/manual-setup/">set up the SDK manually</PlatformLink>.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-install/native.qt.mdx b/platform-includes/getting-started-install/native.qt.mdx
index 36c840e3abbea4..e5d8718dc4babf 100644
--- a/platform-includes/getting-started-install/native.qt.mdx
+++ b/platform-includes/getting-started-install/native.qt.mdx
@@ -5,11 +5,11 @@ To build the SDK, download the latest sources from the [Releases page](https://g
 
 To enable the Qt integration set the `SENTRY_INTEGRATION_QT` option to `YES`.
 
-<Note>
+<Alert>
 
 If the Qt libraries are not installed in one of the predefined `CMake` [system prefix paths](https://cmake.org/cmake/help/latest/variable/CMAKE_SYSTEM_PREFIX_PATH.html), where they can be found by `CMake`, you will need to set [`CMAKE_PREFIX_PATH`](https://cmake.org/cmake/help/latest/variable/CMAKE_PREFIX_PATH.html) explicitly.
 
-</Note>
+</Alert>
 
 For example (on macOS):
 
diff --git a/platform-includes/getting-started-install/unity.mdx b/platform-includes/getting-started-install/unity.mdx
index 98633f3a0c758b..13cea3dd63585b 100644
--- a/platform-includes/getting-started-install/unity.mdx
+++ b/platform-includes/getting-started-install/unity.mdx
@@ -4,8 +4,8 @@ Install the package via the [Unity Package Manager using a Git URL](https://docs
 https://github.com/getsentry/unity.git#{{@inject packages.version('sentry.dotnet.unity', '0.0.5') }}
 ```
 
-<Note>
+<Alert>
 
 Confirm the URL doesn't have a trailing whitespace at the end. The Unity Package Manager will fail to find the package if a trailing whitespace is appended.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-install/unreal.mdx b/platform-includes/getting-started-install/unreal.mdx
index 1d5d74da5cfc0c..01ccbbe9695255 100644
--- a/platform-includes/getting-started-install/unreal.mdx
+++ b/platform-includes/getting-started-install/unreal.mdx
@@ -2,27 +2,27 @@ The Unreal Engine (UE) SDK is officially supported for the three latest UE versi
 
 To install the SDK, download the most up-to-date sources from the [Releases page](https://github.com/getsentry/sentry-unreal/releases) and add them to your project's `Plugins` directory. On the next project launch, UE will prompt you to build the Sentry and SentryEditor modules.
 
-<Note>
+<Alert>
 
 Currently, this method is available only for C++ UE projects. Blueprint projects can be converted to a C++ one by adding an empty class using the editor.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 The [Releases page](https://github.com/getsentry/sentry-unreal/releases) provides two plugin packages: `github` and `marketplace`. The key difference between the two is the crash capturing backend, which is used under the hood on Windows.
 
 We recommend using the `github` version which uses `Crashpad`, an out-of-proc handler that sends the crash report right away. The `marketplace` version relies on `Breakpad`, an in-proc handler which requires the UE application or game to be relaunched in order to send the crash reports to Sentry.
 
-</Note>
+</Alert>
 
 Alternatively, the Sentry SDK can be downloaded via the [standard installation process](https://docs.unrealengine.com/5.2/en-US/working-with-plugins-in-unreal-engine/#installingpluginsfromtheunrealenginemarketplace) from its [UE Marketplace](https://www.unrealengine.com/marketplace/en-US/product/sentry-01) page within the Epic Games Launcher.
 
-<Note>
+<Alert>
 
 This method is recommended only for Blueprint UE projects. If you already have a C++ UE project or don't mind converting an existing Blueprint UE project to a C++ one, consider downloading the plugin from GitHub instead.
 
-</Note>
+</Alert>
 
 To make sure the Sentry plugin has been enabled after installation has been completed, go to the editor and navigate to the **Settings > Plugins > Code Plugins** menu and check for the installation.
 
diff --git a/platform-includes/getting-started-node/javascript.mdx b/platform-includes/getting-started-node/javascript.mdx
index e57b37a6a738e0..fe1d810d822269 100644
--- a/platform-includes/getting-started-node/javascript.mdx
+++ b/platform-includes/getting-started-node/javascript.mdx
@@ -53,10 +53,10 @@ This snippet includes an intentional error, so you can test to make sure that ev
 
 <PlatformContent includePath="getting-started-verify" />
 
-<Note>
+<Alert>
 
 Learn more about manually capturing an error or message in our <PlatformLink to="/usage/">Usage documentation</PlatformLink>.
 
-</Note>
+</Alert>
 
 To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
diff --git a/platform-includes/getting-started-primer/java.jul.mdx b/platform-includes/getting-started-primer/java.jul.mdx
index 049b3b419485b8..6d4c29d67e15fc 100644
--- a/platform-includes/getting-started-primer/java.jul.mdx
+++ b/platform-includes/getting-started-primer/java.jul.mdx
@@ -1,7 +1,7 @@
-<Note>
+<Alert>
 
 The `sentry-jul` library provides a [java.util.logging Handler](http://docs.oracle.com/javase/8/docs/api/java/util/logging/Handler.html) that sends logged exceptions to Sentry.
 
-</Note>
+</Alert>
 
 Once this integration is configured you can _also_ use Sentry’s static API, <PlatformLink to="/usage/">as shown on the usage page</PlatformLink>, 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-jul).
diff --git a/platform-includes/getting-started-primer/java.log4j2.mdx b/platform-includes/getting-started-primer/java.log4j2.mdx
index 35c05f29899ad9..8d6dd2f15f689f 100644
--- a/platform-includes/getting-started-primer/java.log4j2.mdx
+++ b/platform-includes/getting-started-primer/java.log4j2.mdx
@@ -1,7 +1,7 @@
-<Note>
+<Alert>
 
 The `sentry-log4j2` library provides [Log4j 2.x](https://logging.apache.org/log4j/2.x/) support for Sentry via an [Appender](https://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/Appender.html) that sends logged exceptions to Sentry.
 
-</Note>
+</Alert>
 
 Once the integration is configured you can _also_ use Sentry’s static API, [as shown on the usage page](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-log4j2).
diff --git a/platform-includes/getting-started-primer/java.logback.mdx b/platform-includes/getting-started-primer/java.logback.mdx
index 48ba20bf3884ee..1b6508c1b726cc 100644
--- a/platform-includes/getting-started-primer/java.logback.mdx
+++ b/platform-includes/getting-started-primer/java.logback.mdx
@@ -1,7 +1,7 @@
-<Note>
+<Alert>
 
 The `sentry-logback` library provides [Logback](https://logback.qos.ch/) support for Sentry using an [Appender](https://logback.qos.ch/apidocs/ch/qos/logback/core/Appender.html) that sends logged exceptions to Sentry.
 
-</Note>
+</Alert>
 
 Once this integration is configured you can _also_ use Sentry’s static API, [as shown on the usage page](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).
diff --git a/platform-includes/getting-started-primer/java.mdx b/platform-includes/getting-started-primer/java.mdx
index 2588453f2b81ad..71d9f4d17370b3 100644
--- a/platform-includes/getting-started-primer/java.mdx
+++ b/platform-includes/getting-started-primer/java.mdx
@@ -1,9 +1,9 @@
-<Note>
+<Alert>
 
 Sentry's Java SDK enables capturing sessions for Release health as well as reporting messages and errors.
 
 Sentry for Java is a collection of modules provided by Sentry; it supports Java 1.8 and above. At its core, Sentry for Java provides a raw client for sending events to Sentry. To begin, we **highly recommend** you use one of the logging libraries or framework integrations.
 
-</Note>
+</Alert>
 
 The Sentry Java SDK can be used with Kotlin, Scala, and other JVM languages. Code examples are typically provided in both Java and Kotlin.
diff --git a/platform-includes/getting-started-primer/java.spring-boot.mdx b/platform-includes/getting-started-primer/java.spring-boot.mdx
index 21c0f0a884e244..a7285e9e1a08da 100644
--- a/platform-includes/getting-started-primer/java.spring-boot.mdx
+++ b/platform-includes/getting-started-primer/java.spring-boot.mdx
@@ -1,4 +1,4 @@
-<Note>
+<Alert>
 
 There are two variants of Sentry available for Spring Boot. If you're using our Gradle plugin it will pick the right dependency for you. If you're manually adding the dependency and using Spring Boot 2, use `sentry-spring-boot-starter` ([GitHub](https://github.com/getsentry/sentry-java/tree/master/sentry-spring-boot-starter)). If you're using Spring Boot 3, use `sentry-spring-boot-starter-jakarta` instead ([GitHub](https://github.com/getsentry/sentry-java/tree/master/sentry-spring-boot-starter-jakarta)).
 
@@ -10,4 +10,4 @@ The `sentry-spring-boot-starter` and `sentry-spring-boot-starter-jakarta` librar
 - automatically include the release when [Spring Boot Git integration is configured](https://docs.spring.io/spring-boot/how-to/build.html#howto.build.generate-git-info)
 - automatically register `BeforeSendCallback`, `BeforeBreadcrumbCallback`, `EventProcessor`, `Integration` beans
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-primer/java.spring.mdx b/platform-includes/getting-started-primer/java.spring.mdx
index 2e9c70b324aed2..0f7c69904187d4 100644
--- a/platform-includes/getting-started-primer/java.spring.mdx
+++ b/platform-includes/getting-started-primer/java.spring.mdx
@@ -1,4 +1,4 @@
-<Note>
+<Alert>
 
 There are two variants of Sentry available for Spring. If you're using Spring 5, use `sentry-spring` ([GitHub](https://github.com/getsentry/sentry-java/tree/master/sentry-spring)). If you're using Spring 6, use `sentry-spring-jakarta` instead ([GitHub](https://github.com/getsentry/sentry-java/tree/master/sentry-spring-jakarta)).
 
@@ -10,4 +10,4 @@ Sentry's integration with [Spring](https://spring.io/projects/spring-framework)
 
 To use Sentry with <strong>Spring Boot</strong>, we recommend using Sentry [Spring Boot integration](/platforms/java/guides/spring-boot) as it provides richer configuration capabilities.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-primer/javascript.cordova.mdx b/platform-includes/getting-started-primer/javascript.cordova.mdx
index 39d60276a950be..3af561969eb8a3 100644
--- a/platform-includes/getting-started-primer/javascript.cordova.mdx
+++ b/platform-includes/getting-started-primer/javascript.cordova.mdx
@@ -1,10 +1,10 @@
-<Note>
+<Alert>
 
 Sentry's Cordova SDK enables automatic reporting of errors, messages, and exceptions, and identifies performance issues in your application. The SDK is available on GitHub [`sentry-cordova`](https://github.com/getsentry/sentry-cordova).
 
 The Cordova SDK uses a native extension for iOS and Android, but will fall back to a pure JavaScript version (`@sentry/browser`) if needed. When you install `sentry-cordova`, the [Sentry Wizard](https://github.com/getsentry/sentry-wizard) will help configure your project. We also add a build step to your Xcode project to upload debug symbols we need to symbolicate iOS crashes.
 
-</Note>
+</Alert>
 
 Features:
 
diff --git a/platform-includes/getting-started-primer/javascript.deno.mdx b/platform-includes/getting-started-primer/javascript.deno.mdx
index 8e9f59b1e1c19c..81cadd65538c9a 100644
--- a/platform-includes/getting-started-primer/javascript.deno.mdx
+++ b/platform-includes/getting-started-primer/javascript.deno.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 The Deno SDK is currently in Beta.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-primer/javascript.ember.mdx b/platform-includes/getting-started-primer/javascript.ember.mdx
index 73c36ff978f1c9..fd370d254c4cac 100644
--- a/platform-includes/getting-started-primer/javascript.ember.mdx
+++ b/platform-includes/getting-started-primer/javascript.ember.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 Sentry's Ember addon enables automatic reporting of errors, exceptions, and transactions.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-primer/javascript.nextjs.mdx b/platform-includes/getting-started-primer/javascript.nextjs.mdx
index b17d52df894729..6cbd7f3cb1f611 100644
--- a/platform-includes/getting-started-primer/javascript.nextjs.mdx
+++ b/platform-includes/getting-started-primer/javascript.nextjs.mdx
@@ -7,7 +7,7 @@ Features:
 - [Breadcrumbs](/platforms/javascript/enriching-events/breadcrumbs/) created for outgoing HTTP request with XHR and Fetch, and console logs
 - [Release health](/product/releases/health/) for tracking crash-free users and sessions
 
-<Note>
+<Alert>
 
 The Sentry SDK does not fully support `next dev --turbo` while Turbopack does not ship all the features required to run Sentry.
 
@@ -21,4 +21,4 @@ To support the SDK in the browser with Turbopack, [follow the feature request fo
 
 You can track Sentry's Turbopack support in the [GitHub Issue in the Sentry SDK repository](https://github.com/getsentry/sentry-javascript/issues/8105).
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-primer/javascript.react-router.mdx b/platform-includes/getting-started-primer/javascript.react-router.mdx
index 116fe5cc3cade2..a65cb1180a57ac 100644
--- a/platform-includes/getting-started-primer/javascript.react-router.mdx
+++ b/platform-includes/getting-started-primer/javascript.react-router.mdx
@@ -1,10 +1,10 @@
-<Alert title='Library Mode' level='info'>
+<Alert title='Looking for library mode?' level='warning'>
 
-If you are using React Router in library mode, you can follow the instructions in the [React Router library mode guide](/platforms/javascript/guides/react/features/react-router/).
+If you are using React Router in library mode, you can follow the instructions in the [React guide here](/platforms/javascript/guides/react/features/react-router/v7).
 
 </Alert>
 
-<Alert title='Limited Support' level='warning'>
+<Alert title='SDK Limitations' level='warning'>
 
 We do not yet have a dedicated SDK for React Router in framework mode.
 This guide demonstrates how to setup error monitoring and basic performance tracing using the `@sentry/react` and `@sentry/node` packages instead.
diff --git a/platform-includes/getting-started-primer/javascript.react.mdx b/platform-includes/getting-started-primer/javascript.react.mdx
index 75b872ae8c043d..14c6bb447ba4bf 100644
--- a/platform-includes/getting-started-primer/javascript.react.mdx
+++ b/platform-includes/getting-started-primer/javascript.react.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 Sentry's React SDK enables automatic reporting of errors and exceptions. The SDK is a wrapper around @sentry/browser, with added functionality related to React. All methods available in @sentry/browser can be imported from @sentry/react.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-primer/javascript.remix.mdx b/platform-includes/getting-started-primer/javascript.remix.mdx
index 5c609da1871e2d..a15d726cb12e58 100644
--- a/platform-includes/getting-started-primer/javascript.remix.mdx
+++ b/platform-includes/getting-started-primer/javascript.remix.mdx
@@ -1,8 +1,8 @@
-<Note>
+<Alert>
 
 Sentry's Remix SDK enables automatic reporting of errors and exceptions, as well as the performance metrics for both client and server side operations.
 
-</Note>
+</Alert>
 
 Sentry's Remix SDK relies on our [React SDK](/platforms/javascript/guides/react/) for the frontend and [Node SDK](/platforms/node) for the backend. That means all features available in those SDKs are also available in this SDK.
 
diff --git a/platform-includes/getting-started-primer/javascript.svelte.mdx b/platform-includes/getting-started-primer/javascript.svelte.mdx
index d465731b6fe925..13ed16c08444f7 100644
--- a/platform-includes/getting-started-primer/javascript.svelte.mdx
+++ b/platform-includes/getting-started-primer/javascript.svelte.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 Sentry's Svelte SDK enables automatic reporting of errors and exceptions, as well as tracing for your client-side Svelte apps.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-primer/javascript.sveltekit.mdx b/platform-includes/getting-started-primer/javascript.sveltekit.mdx
index cecf2b8192ccb5..b0c214f4469ca8 100644
--- a/platform-includes/getting-started-primer/javascript.sveltekit.mdx
+++ b/platform-includes/getting-started-primer/javascript.sveltekit.mdx
@@ -5,7 +5,7 @@ Sentry's SvelteKit SDK enables automatic reporting of errors and performance dat
 The minimum supported SvelteKit version is `1.0.0` but we recommend using **SvelteKit version `1.24.0` or newer** for best performance.
 This SDK works best with **Vite 4.2** and newer. Older Vite versions might not generate source maps correctly.
 
-<Note>
+<Alert>
 
 The SvelteKit SDK is designed to work out of the box with the following SvelteKit adapters:
 
@@ -18,4 +18,4 @@ We're looking into extending first-class support to [more adapters](https://kit.
 
 The SvelteKit SDK does not yet work with non-node server runtimes, such as Vercel's edge runtime or Cloudflare Workers.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-primer/kotlin.kotlin-multiplatform.mdx b/platform-includes/getting-started-primer/kotlin.kotlin-multiplatform.mdx
index 975677de27eda0..1838bfa20dc806 100644
--- a/platform-includes/getting-started-primer/kotlin.kotlin-multiplatform.mdx
+++ b/platform-includes/getting-started-primer/kotlin.kotlin-multiplatform.mdx
@@ -8,11 +8,11 @@ Installing this SDK will enable native crash reporting and automatic breadcrumbs
 
 Don't already have an account and Sentry project established? Head over to [sentry.io](https://sentry.io/signup/), then return to this page.
 
-<Note>
+<Alert>
 Xcode 16 support starts with Sentry Cocoa SDK version `8.36.0` or higher.
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use. Use Sentry Cocoa SDK version `8.25.0` or higher to ensure compliance with these requirements.
 Follow our [Apple Privacy Manifest](/platforms/kotlin/guides/kotlin-multiplatform/data-management/apple-privacy-manifest) guide to learn more.
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-primer/native.mdx b/platform-includes/getting-started-primer/native.mdx
index c63e0aca270832..a4dc3e80f01e8f 100644
--- a/platform-includes/getting-started-primer/native.mdx
+++ b/platform-includes/getting-started-primer/native.mdx
@@ -1,10 +1,10 @@
 The Sentry Native SDK is intended for C and C++. However, since it builds as a dynamic library and exposes C-bindings, it can be used by any language that supports interoperability with C, such as the Foreign Function Interface (FFI).
 
-<Note>
+<Alert>
 
 Using the `sentry-native` SDK in a standalone use case is currently an experimental feature. The SDK’s primary function is to fuel our other SDKs, like [`sentry-java`](https://github.com/getsentry/sentry-java) or [`sentry-unreal`](https://github.com/getsentry/sentry-unreal). Support from our side is best effort and we do what we can to respond to issues in a timely fashion, but please understand if we won’t be able to address your issues or feature suggestions.
 
-</Note>
+</Alert>
 
 Sentry also offers higher-level SDKs for platforms with built-in support for native crashes:
 
diff --git a/platform-includes/getting-started-primer/native.qt.mdx b/platform-includes/getting-started-primer/native.qt.mdx
index d1ab3569926f16..5442404a2a8a0d 100644
--- a/platform-includes/getting-started-primer/native.qt.mdx
+++ b/platform-includes/getting-started-primer/native.qt.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 Sentry's Qt integration enables automatic reporting of errors, exceptions, and log messages.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-verify/javascript.angular.mdx b/platform-includes/getting-started-verify/javascript.angular.mdx
index 178d733deb6562..d9364aaa5a70c8 100644
--- a/platform-includes/getting-started-verify/javascript.angular.mdx
+++ b/platform-includes/getting-started-verify/javascript.angular.mdx
@@ -12,8 +12,8 @@ public throwTestError(): void {
 }
 ```
 
-<Note>
+<Alert>
 
 Errors triggered from within Browser DevTools are sandboxed and won't trigger an error handler. Place the snippet directly in your code instead.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-verify/javascript.astro.mdx b/platform-includes/getting-started-verify/javascript.astro.mdx
index 16fa0d31c3f5a0..692502f454c440 100644
--- a/platform-includes/getting-started-verify/javascript.astro.mdx
+++ b/platform-includes/getting-started-verify/javascript.astro.mdx
@@ -6,8 +6,8 @@ Trigger a test error somewhere in your Astro app, for example in one of your pag
 </button>
 ```
 
-<Note>
+<Alert>
 
 Errors triggered from within Browser DevTools are sandboxed and won't trigger an error handler. Place the snippet directly in your code instead.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-verify/javascript.mdx b/platform-includes/getting-started-verify/javascript.mdx
index 5c46f93e33ff3e..68894584469230 100644
--- a/platform-includes/getting-started-verify/javascript.mdx
+++ b/platform-includes/getting-started-verify/javascript.mdx
@@ -4,8 +4,8 @@ setTimeout(() => {
 });
 ```
 
-<Note>
+<Alert>
 
 Errors triggered from within Browser DevTools are sandboxed and won't trigger an error handler. Place the snippet directly in your code instead.
 
-</Note>
+</Alert>
diff --git a/platform-includes/getting-started-verify/javascript.nextjs.mdx b/platform-includes/getting-started-verify/javascript.nextjs.mdx
index d969d897985e75..789594e95cefc0 100644
--- a/platform-includes/getting-started-verify/javascript.nextjs.mdx
+++ b/platform-includes/getting-started-verify/javascript.nextjs.mdx
@@ -29,11 +29,11 @@ export default (req: NextApiRequest, res: NextApiResponse) => {
 };
 ```
 
-<Note>
+<Alert>
 
 Errors triggered from within Browser DevTools are sandboxed, so they will not trigger error monitoring. Keep this in mind when verifying your Sentry SDK installation.
 
-</Note>
+</Alert>
 
 <Alert title="Nested React Server Components" level="warning">
 
diff --git a/platform-includes/getting-started-verify/javascript.remix.mdx b/platform-includes/getting-started-verify/javascript.remix.mdx
index ed9280270e595e..6a636e7ff864ed 100644
--- a/platform-includes/getting-started-verify/javascript.remix.mdx
+++ b/platform-includes/getting-started-verify/javascript.remix.mdx
@@ -11,11 +11,11 @@
 
 This snippet adds a button that throws an error in a component or page.
 
-<Note>
+<Alert>
 
 Errors triggered from within Browser DevTools are sandboxed, so will not trigger an error handler. Place the snippet directly in your code instead.
 
-</Note>
+</Alert>
 
 Then, throw an error in a `loader` or `action`.
 
diff --git a/platform-includes/getting-started-verify/javascript.sveltekit.mdx b/platform-includes/getting-started-verify/javascript.sveltekit.mdx
index 262e3ea596cfb4..b79df3030a8cca 100644
--- a/platform-includes/getting-started-verify/javascript.sveltekit.mdx
+++ b/platform-includes/getting-started-verify/javascript.sveltekit.mdx
@@ -28,8 +28,8 @@ export const GET = () => {
 
 The possibilities are endless!
 
-<Note>
+<Alert>
 
 Errors triggered from within Browser DevTools are sandboxed and will not trigger error monitoring. Keep this in mind when verifying your Sentry SDK installation.
 
-</Note>
+</Alert>
diff --git a/platform-includes/metrics/version-support-note/javascript.electron.mdx b/platform-includes/metrics/version-support-note/javascript.electron.mdx
index c7a7d0e4a19657..8927a70b474305 100644
--- a/platform-includes/metrics/version-support-note/javascript.electron.mdx
+++ b/platform-includes/metrics/version-support-note/javascript.electron.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 Metrics for JavaScript are supported with Sentry Electron SDK version `4.17.0` and above.
 
-</Note>
+</Alert>
diff --git a/platform-includes/metrics/version-support-note/javascript.mdx b/platform-includes/metrics/version-support-note/javascript.mdx
index c194d4b0825055..7e393c28a51822 100644
--- a/platform-includes/metrics/version-support-note/javascript.mdx
+++ b/platform-includes/metrics/version-support-note/javascript.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 Metrics for JavaScript are supported with Sentry JavaScript SDK version `7.103.0` and above.
 
-</Note>
+</Alert>
diff --git a/platform-includes/metrics/version-support-note/react-native.mdx b/platform-includes/metrics/version-support-note/react-native.mdx
index b5e6e77682a02c..38e074d2fdfd13 100644
--- a/platform-includes/metrics/version-support-note/react-native.mdx
+++ b/platform-includes/metrics/version-support-note/react-native.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 Metrics for React Native are supported in Sentry React Native SDK version `5.19.0` and above.
 
-</Note>
+</Alert>
diff --git a/platform-includes/migration/javascript-v8/important-changes/javascript.remix.mdx b/platform-includes/migration/javascript-v8/important-changes/javascript.remix.mdx
index 1ab7a499b98ee3..75606774e36f21 100644
--- a/platform-includes/migration/javascript-v8/important-changes/javascript.remix.mdx
+++ b/platform-includes/migration/javascript-v8/important-changes/javascript.remix.mdx
@@ -27,13 +27,13 @@ export const handleError = Sentry.wrapRemixHandleError;
 // rest of your code and imports
 ```
 
-<Note>
+<Alert>
   Since
   [8.10.0](https://github.com/getsentry/sentry-javascript/releases/tag/8.10.0),
   you can also setup `@sentry/remix` with a new `autoInstrumentRemix: true`
   option. See <PlatformLink to="/manual-setup">Manual Setup</PlatformLink> for
   details on how to use this option.
-</Note>
+</Alert>
 
 2. Remove any performance related integrations from your server-side init in `entry.server.tsx`.
 
diff --git a/platform-includes/migration/javascript-v8/integrations-package-removal/javascript.mdx b/platform-includes/migration/javascript-v8/integrations-package-removal/javascript.mdx
index 028d3431d51fa5..59badf504e566e 100644
--- a/platform-includes/migration/javascript-v8/integrations-package-removal/javascript.mdx
+++ b/platform-includes/migration/javascript-v8/integrations-package-removal/javascript.mdx
@@ -2,11 +2,11 @@
 
 `@sentry/integrations` has been removed and will no longer be published. We moved pluggable integrations from their own package (`@sentry/integrations`) to `@sentry/browser`. In addition they are now functions instead of classes.
 
-<Note>
+<Alert>
 
 Integrations will still be available via the CDN, but they will exposed as functions not classes as is shown below.
 
-</Note>
+</Alert>
 
 Integrations that are now exported from `@sentry/browser` for client-side init:
 
diff --git a/platform-includes/migration/javascript-v8/v7-deprecation/javascript.mdx b/platform-includes/migration/javascript-v8/v7-deprecation/javascript.mdx
index de7096d5660507..cf48d2c92ec005 100644
--- a/platform-includes/migration/javascript-v8/v7-deprecation/javascript.mdx
+++ b/platform-includes/migration/javascript-v8/v7-deprecation/javascript.mdx
@@ -58,10 +58,10 @@ Client-side Integrations:
  });
 ```
 
-<Note>
+<Alert>
 
 You only need to add the `integrations` configuration for the loader if you were previously explicitly using the `BrowserTracing` integration.
 
-</Note>
+</Alert>
 
 <Include name="migration/javascript-v8/v7-deprecation/general" />
diff --git a/platform-includes/performance/always-inherit-sampling-decision/php.laravel.mdx b/platform-includes/performance/always-inherit-sampling-decision/php.laravel.mdx
index a41b1407d76085..30474994d651b7 100644
--- a/platform-includes/performance/always-inherit-sampling-decision/php.laravel.mdx
+++ b/platform-includes/performance/always-inherit-sampling-decision/php.laravel.mdx
@@ -9,8 +9,8 @@
 },
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Closures and Config Caching](/platforms/php/guides/laravel/configuration/laravel-options/#closures-and-config-caching).
 
-</Note>
+</Alert>
diff --git a/platform-includes/performance/always-inherit-sampling-decision/php.symfony.mdx b/platform-includes/performance/always-inherit-sampling-decision/php.symfony.mdx
index d5d8d6a8a1b37a..d7e29f5709ce03 100644
--- a/platform-includes/performance/always-inherit-sampling-decision/php.symfony.mdx
+++ b/platform-includes/performance/always-inherit-sampling-decision/php.symfony.mdx
@@ -33,8 +33,8 @@ class Sentry
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Callables in Symfony Options](/platforms/php/guides/symfony/configuration/symfony-options/#callables).
 
-</Note>
+</Alert>
diff --git a/platform-includes/performance/configure-sample-rate/java.mdx b/platform-includes/performance/configure-sample-rate/java.mdx
index ad1cf7af6b1155..5cb0d63ecbde6c 100644
--- a/platform-includes/performance/configure-sample-rate/java.mdx
+++ b/platform-includes/performance/configure-sample-rate/java.mdx
@@ -1,8 +1,8 @@
-<Note>
+<Alert>
 
 If you are using either our [Spring](/platforms/java/guides/spring/performance/) or [Spring Boot](/platforms/java/guides/spring-boot/performance/) integrations, errors are linked with spans automatically.
 
-</Note>
+</Alert>
 
 
 ```java {diff, tabTitle:Java}
diff --git a/platform-includes/performance/configure-sample-rate/javascript.cloudflare.mdx b/platform-includes/performance/configure-sample-rate/javascript.cloudflare.mdx
index 081fe43b3766bd..c2e5a4b13bfff4 100644
--- a/platform-includes/performance/configure-sample-rate/javascript.cloudflare.mdx
+++ b/platform-includes/performance/configure-sample-rate/javascript.cloudflare.mdx
@@ -17,10 +17,10 @@ export const onRequest = [
 
 ## Cloudflare Workers
 
-```javascript {filename:functions/_middleware.js}
-import * as Sentry from '@sentry/cloudflare';
+```typescript {filename:index.ts}
+import * as Sentry from "@sentry/cloudflare";
 
-export default withSentry(
+export default Sentry.withSentry(
   env => ({
     dsn: "___PUBLIC_DSN___",
     // To set a uniform sample rate
@@ -31,7 +31,7 @@ export default withSentry(
   }),
   {
     async fetch(request, env, ctx) {
-      return new Response('Hello World!');
+      return new Response("Hello World!");
     },
   } satisfies ExportedHandler<Env>,
 );
diff --git a/platform-includes/performance/configure-sample-rate/php.laravel.mdx b/platform-includes/performance/configure-sample-rate/php.laravel.mdx
index e6813f0651f090..1e439f40db5eff 100644
--- a/platform-includes/performance/configure-sample-rate/php.laravel.mdx
+++ b/platform-includes/performance/configure-sample-rate/php.laravel.mdx
@@ -7,8 +7,8 @@
 },
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Closures and Config Caching](/platforms/php/guides/laravel/configuration/laravel-options/#closures-and-config-caching).
 
-</Note>
+</Alert>
diff --git a/platform-includes/performance/configure-sample-rate/php.symfony.mdx b/platform-includes/performance/configure-sample-rate/php.symfony.mdx
index eb634ab43a1f3c..bfc22ca369f329 100644
--- a/platform-includes/performance/configure-sample-rate/php.symfony.mdx
+++ b/platform-includes/performance/configure-sample-rate/php.symfony.mdx
@@ -32,8 +32,8 @@ class Sentry
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Callables in Symfony Options](/platforms/php/guides/symfony/configuration/symfony-options/#callables).
 
-</Note>
+</Alert>
diff --git a/platform-includes/performance/connect-errors-spans/java.mdx b/platform-includes/performance/connect-errors-spans/java.mdx
index 0660a0e4f3a0e8..17a18a383eea71 100644
--- a/platform-includes/performance/connect-errors-spans/java.mdx
+++ b/platform-includes/performance/connect-errors-spans/java.mdx
@@ -4,11 +4,11 @@ Sentry errors can be linked with transactions and spans.
 
 <PlatformSection supported={["java"]} notSupported={["android", "java.spring", "java.spring-boot"]}>
 
-<Note>
+<Alert>
 
 We have dedicated performance features for our [Spring](/platforms/java/guides/spring/) and [Spring Boot](/platforms/java/guides/spring-boot/) integrations. In addition, errors are linked with spans automatically using either of these integrations.
 
-</Note>
+</Alert>
 
 </PlatformSection>
 
diff --git a/platform-includes/performance/connect-services/javascript.mdx b/platform-includes/performance/connect-services/javascript.mdx
index efbaf28480a701..8402565f2f0f7a 100644
--- a/platform-includes/performance/connect-services/javascript.mdx
+++ b/platform-includes/performance/connect-services/javascript.mdx
@@ -2,11 +2,11 @@
 
 For traces that begin in the front end, any requests made (and any requests your backend makes as a result) are linked through the request headers `sentry-trace` and `baggage`. The `sentry-trace` header holds information for identifying the trace, while the [W3C compliant](https://www.w3.org/TR/baggage/) `baggage` header contains additional trace-related data that is used for trace-based sampling.
 
-<Note>
+<Alert>
 
 The `baggage` header was added with version 7 of the Sentry Javascript SDK and is not yet standardized across other Sentry SDKs. It is part of an ongoing effort to create a more frictionless and targeted sampling approach, and its content is subject to change.
 
-</Note>
+</Alert>
 
 All Sentry JavaScript SDKs support distributed tracing once you add the <PlatformLink to="/tracing/instrumentation/automatic-instrumentation/">BrowserTracing</PlatformLink> integration to your `Sentry.init` option. The [Next.js](/platforms/javascript/guides/nextjs/) and [SvelteKit](/platforms/javascript/guides/sveltekit/) SDKs already include this integration by default.
 
@@ -56,11 +56,11 @@ This feature is available on Sentry Remix SDK version 7.9.0 and above.
 
 The `name` attributes must be the strings `"sentry-trace"` and `"baggage"` and the `content` attributes must be generated by your backend Sentry SDK. For `sentry-trace`, use `span.toSentryTrace()` (or equivalent, depending on the backend platform). This guarantees that a new and unique value will be generated for each request. For `baggage`, use `serializeBaggage(span.getBaggage())`.
 
-<Note>
+<Alert>
 
 The `span.toSentryTrace()` was previously called `span.toTraceparent()`, so that's what you may find depending on the SDK and version.
 
-</Note>
+</Alert>
 
 The `span` reference is either the transaction that serves the HTML or any of its child spans. It defines the parent of the `pageload` transaction.
 
diff --git a/platform-includes/performance/improving-data/native.mdx b/platform-includes/performance/improving-data/native.mdx
new file mode 100644
index 00000000000000..cb1b96e225dde1
--- /dev/null
+++ b/platform-includes/performance/improving-data/native.mdx
@@ -0,0 +1,81 @@
+## Improving Data on Transactions and Spans
+You can add Data Attributes to both Spans and Transactions. This data is visible in the trace explorer in Sentry.
+The data must be of type `sentry_value_t`, which can store:
+* 32-bit signed integers,
+* double-precision floating-points,
+* null-terminated strings, as well as
+* lists and string-keyed maps containing `sentry_value_t` entries
+
+### Adding Data Attributes to Transactions
+
+You can add data attributes to your transactions using the following API:
+
+```c
+sentry_transaction_context_t *tx_ctx =
+    sentry_transaction_context_new("processOrderBatch()", "task");
+sentry_transaction_t *tx =
+    sentry_transaction_start(tx_ctx, sentry_value_new_null());
+
+sentry_transaction_set_data(tx, "my-data-attribute-1",
+    sentry_value_new_string("value1"));
+sentry_transaction_set_data(tx, "my-data-attribute-2",
+    sentry_value_new_int32(42));
+sentry_transaction_set_data(tx, "my-data-attribute-3",
+    sentry_value_new_double(3.14));
+sentry_transaction_set_data(tx, "my-data-attribute-4",
+    sentry_value_new_bool(true));
+
+sentry_value_t value_list = sentry_value_new_list();
+sentry_value_append(value_list, sentry_value_new_string("value1"));
+sentry_value_append(value_list, sentry_value_new_int32(42));
+sentry_value_append(value_list, sentry_value_new_double(3.14));
+sentry_value_append(value_list, sentry_value_new_bool(true));
+
+sentry_transaction_set_data(tx, "my-data-attribute-5", value_list);
+
+sentry_value_t value_object = sentry_value_new_object();
+sentry_value_set_by_key(value_object, "key_1", sentry_value_new_string("value1"));
+sentry_value_set_by_key(value_object, "key_2", sentry_value_new_int32(42));
+sentry_value_set_by_key(value_object, "key_3", sentry_value_new_double(3.14));
+sentry_value_set_by_key(value_object, "key_4", sentry_value_new_bool(true));
+
+sentry_transaction_set_data(tx, "my-data-attribute-6", value_object);
+```
+
+### Adding Data Attributes to Spans
+
+You can add data attributes to your spans using the following API:
+
+```c
+sentry_transaction_context_t *tx_ctx =
+    sentry_transaction_context_new("processOrderBatch()", "task");
+sentry_transaction_t *tx =
+    sentry_transaction_start(tx_ctx, sentry_value_new_null());
+sentry_span_t *span =
+    sentry_transaction_start_child(tx, "task", "operation");
+
+sentry_span_set_data(span, "my-data-attribute-1",
+    sentry_value_new_string("value1"));
+sentry_span_set_data(span, "my-data-attribute-2",
+    sentry_value_new_int32(42));
+sentry_span_set_data(span, "my-data-attribute-3",
+    sentry_value_new_double(3.14));
+sentry_span_set_data(span, "my-data-attribute-4",
+    sentry_value_new_bool(true));
+
+sentry_value_t value_list = sentry_value_new_list();
+sentry_value_append(value_list, sentry_value_new_string("value1"));
+sentry_value_append(value_list, sentry_value_new_int32(42));
+sentry_value_append(value_list, sentry_value_new_double(3.14));
+sentry_value_append(value_list, sentry_value_new_bool(true));
+
+sentry_span_set_data(span, "my-data-attribute-5", value_list);
+
+sentry_value_t value_object = sentry_value_new_object();
+sentry_value_set_by_key(value_object, "key_1", sentry_value_new_string("value1"));
+sentry_value_set_by_key(value_object, "key_2", sentry_value_new_int32(42));
+sentry_value_set_by_key(value_object, "key_3", sentry_value_new_double(3.14));
+sentry_value_set_by_key(value_object, "key_4", sentry_value_new_bool(true));
+
+sentry_span_set_data(span, "my-data-attribute-6", value_object);
+```
diff --git a/platform-includes/performance/opentelemetry-install/dotnet.mdx b/platform-includes/performance/opentelemetry-install/dotnet.mdx
index 3a7242c764dbf5..b7d1367248c3ac 100644
--- a/platform-includes/performance/opentelemetry-install/dotnet.mdx
+++ b/platform-includes/performance/opentelemetry-install/dotnet.mdx
@@ -1,8 +1,8 @@
-<Note>
+<Alert>
 
 The `Sentry.OpenTelemetry` package requires `OpenTelemetry` package `1.5.0` or higher.
 
-</Note>
+</Alert>
 
 To install, add the `Sentry` and `Sentry.OpenTelemetry` **NuGet** packages to your project:
 
diff --git a/platform-includes/performance/opentelemetry-install/go.mdx b/platform-includes/performance/opentelemetry-install/go.mdx
index 9caa0b6fee7e65..f87df010f9ce6a 100644
--- a/platform-includes/performance/opentelemetry-install/go.mdx
+++ b/platform-includes/performance/opentelemetry-install/go.mdx
@@ -1,14 +1,14 @@
-<Note>
+<Alert>
 
 OpenTelemetry integration was added in `sentry-go` version 0.18.0, and works only for Go >= 1.18.
 
-</Note>
+</Alert>
 
-<Note>
+<Alert>
 
 The Sentry Go OpenTelemetry integration requires `go.opentelemetry.io/otel` (and its submodules), version `1.11.0` or higher.
 
-</Note>
+</Alert>
 
 Install the `otel` module in addition to the main SDK:
 
diff --git a/platform-includes/performance/opentelemetry-install/javascript.nextjs.mdx b/platform-includes/performance/opentelemetry-install/javascript.nextjs.mdx
index e4ef7908dfa2e9..d8f4645f3ac530 100644
--- a/platform-includes/performance/opentelemetry-install/javascript.nextjs.mdx
+++ b/platform-includes/performance/opentelemetry-install/javascript.nextjs.mdx
@@ -1,4 +1,4 @@
-<Alert level="info" title="Note">
+<Alert title="Note">
 
 OpenTelemetry support is only available for server-side instrumentation on Node runtimes.
 
@@ -18,11 +18,11 @@ pnpm add @sentry/nextjs @sentry/opentelemetry-node
 
 The minimum required version of the `@sentry/node` and the `@sentry/opentelemetry-node` package is `7.20.0` and their versions should always be aligned.
 
-<Note>
+<Alert>
 
 Note that @sentry/opentelemetry-node depends on the following peer dependencies:
 
 - @opentelemetry/api, version 1.0.0 or greater
 - @opentelemetry/sdk-trace-base, version 1.0.0 or greater, or a package that implements it, like @opentelemetry/sdk-node
 
-</Note>
+</Alert>
diff --git a/platform-includes/performance/opentelemetry-install/javascript.node.mdx b/platform-includes/performance/opentelemetry-install/javascript.node.mdx
index 1076f47e866c77..6d271045bdb86f 100644
--- a/platform-includes/performance/opentelemetry-install/javascript.node.mdx
+++ b/platform-includes/performance/opentelemetry-install/javascript.node.mdx
@@ -12,11 +12,11 @@ pnpm add @sentry/node @sentry/opentelemetry
 
 The minimum required version of the `@sentry/node` and the `@sentry/opentelemetry` package is `7.75.0` and their versions should always be aligned.
 
-<Note>
+<Alert>
 
 Note that `@sentry/opentelemetry` depends on the following peer dependencies:
 
 - `@opentelemetry/api`, version 1.0.0 or greater
 - `@opentelemetry/sdk-trace-base`, version 1.0.0 or greater, or a package that implements it, like `@opentelemetry/sdk-node`
 
-</Note>
+</Alert>
diff --git a/platform-includes/performance/opentelemetry-install/python.mdx b/platform-includes/performance/opentelemetry-install/python.mdx
index 4e317ed9a6d8de..c275f200303f18 100644
--- a/platform-includes/performance/opentelemetry-install/python.mdx
+++ b/platform-includes/performance/opentelemetry-install/python.mdx
@@ -1,8 +1,8 @@
-<Note>
+<Alert>
 
 Sentry requires `opentelemetry-distro` version `0.350b0` or higher.
 
-</Note>
+</Alert>
 
 ```bash
 pip install --upgrade 'sentry-sdk[opentelemetry]'
diff --git a/platform-includes/performance/opentelemetry-install/ruby.mdx b/platform-includes/performance/opentelemetry-install/ruby.mdx
index 03459132fbacc8..1772412d86c181 100644
--- a/platform-includes/performance/opentelemetry-install/ruby.mdx
+++ b/platform-includes/performance/opentelemetry-install/ruby.mdx
@@ -1,8 +1,8 @@
-<Note>
+<Alert>
 
 The `sentry-opentelemetry` gem requires `opentelemetry-sdk` `1.0.0` or higher.
 
-</Note>
+</Alert>
 
 ```ruby
 gem "sentry-ruby"
diff --git a/platform-includes/performance/opentelemetry-setup/javascript.node.mdx b/platform-includes/performance/opentelemetry-setup/javascript.node.mdx
index da9be266fa6176..fab130b89c5a41 100644
--- a/platform-includes/performance/opentelemetry-setup/javascript.node.mdx
+++ b/platform-includes/performance/opentelemetry-setup/javascript.node.mdx
@@ -87,11 +87,11 @@ const span = startInactiveSpan({ name: "my span" });
 span.end();
 ```
 
-<Note>
+<Alert>
 
 If you are using the [@sentry/opentelemetry-node](https://www.npmjs.com/package/@sentry/opentelemetry-node) package, you can continue to do so. Usage instructions are in the
 package's README. This package has a slightly easier setup process but
 provides a more limited connection between Sentry and OpenTelemetry than the
 instructions outlined above.
 
-</Note>
+</Alert>
diff --git a/platform-includes/performance/sampling-function-intro/unreal.mdx b/platform-includes/performance/sampling-function-intro/unreal.mdx
index 80f82dcc3c56ec..08e4560640eca0 100644
--- a/platform-includes/performance/sampling-function-intro/unreal.mdx
+++ b/platform-includes/performance/sampling-function-intro/unreal.mdx
@@ -2,7 +2,7 @@ To use the sampling function, set the <PlatformIdentifier name="traces-sampler"
 
 <PlatformContent includePath="performance/traces-sampler-as-sampler" />
 
-<Alert level="info">
+<Alert>
 
 Currently there's no support for sampling functions on Windows/Linux (<PlatformIdentifier name="traces-sampler" />).
 
diff --git a/platform-includes/performance/span-api-version/javascript.mdx b/platform-includes/performance/span-api-version/javascript.mdx
index e0850dec5503a4..95c6478068c799 100644
--- a/platform-includes/performance/span-api-version/javascript.mdx
+++ b/platform-includes/performance/span-api-version/javascript.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 The below span APIs (`startSpan`, `startInactiveSpan`, and `startSpanManual`) require SDK version `7.69.0` or higher. If you are using an older version of the SDK, you can use the [explicit transaction APIs](#start-transaction) for custom instrumentation.
 
-</Note>
+</Alert>
diff --git a/platform-includes/performance/traces-sampler-as-filter/php.laravel.mdx b/platform-includes/performance/traces-sampler-as-filter/php.laravel.mdx
index 5983d9c2a373f2..f097bbc9665aa2 100644
--- a/platform-includes/performance/traces-sampler-as-filter/php.laravel.mdx
+++ b/platform-includes/performance/traces-sampler-as-filter/php.laravel.mdx
@@ -16,8 +16,8 @@
 },
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Closures and Config Caching](/platforms/php/guides/laravel/configuration/laravel-options/#closures-and-config-caching).
 
-</Note>
+</Alert>
diff --git a/platform-includes/performance/traces-sampler-as-filter/php.symfony.mdx b/platform-includes/performance/traces-sampler-as-filter/php.symfony.mdx
index a292c7c8d7d686..74bf4bd403a009 100644
--- a/platform-includes/performance/traces-sampler-as-filter/php.symfony.mdx
+++ b/platform-includes/performance/traces-sampler-as-filter/php.symfony.mdx
@@ -40,8 +40,8 @@ class Sentry
 }
 ```
 
-<Note>
+<Alert>
 
 Learn more in [Callables in Symfony Options](/platforms/php/guides/symfony/configuration/symfony-options/#callables).
 
-</Note>
+</Alert>
diff --git a/platform-includes/performance/traces-sampler-as-sampler/ruby.mdx b/platform-includes/performance/traces-sampler-as-sampler/ruby.mdx
index 45686f39e00f3c..45ff41648d32f0 100644
--- a/platform-includes/performance/traces-sampler-as-sampler/ruby.mdx
+++ b/platform-includes/performance/traces-sampler-as-sampler/ruby.mdx
@@ -34,7 +34,7 @@ Sentry.init do |config|
       else
         0.1
       end
-    when /sidekiq/
+    when /queue/
       0.01 # you may want to set a lower rate for background jobs if the number is large
     else
       0.0 # ignore all other transactions
diff --git a/platform-includes/performance/what-instrumentation-provides/javascript.react.mdx b/platform-includes/performance/what-instrumentation-provides/javascript.react.mdx
index d333d1bf2e2186..6e144e681af14c 100644
--- a/platform-includes/performance/what-instrumentation-provides/javascript.react.mdx
+++ b/platform-includes/performance/what-instrumentation-provides/javascript.react.mdx
@@ -1,7 +1,7 @@
 The `BrowserTracing` integration creates a new transaction for each page load and navigation event, and creates a child span for every `XMLHttpRequest` or `fetch` request that occurs while those transactions are open.
 
-<Note>
+<Alert>
 
 If you are using `react-router` in your application, you need to use our [`react-router` instrumentation](/platforms/javascript/guides/react/configuration/integrations/react-router/) to be able to trace `navigation` events.
 
-</Note>
+</Alert>
diff --git a/platform-includes/profiling/index/preface/go.mdx b/platform-includes/profiling/index/preface/go.mdx
index 381395b8be8245..6615a3712580c1 100644
--- a/platform-includes/profiling/index/preface/go.mdx
+++ b/platform-includes/profiling/index/preface/go.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 Go Profiling is currently in alpha and is available since SDK version `0.22.0`. Alpha features are still in progress and may have bugs. We recognize the irony.
 
-</Note>
+</Alert>
diff --git a/platform-includes/profiling/index/preface/ruby.mdx b/platform-includes/profiling/index/preface/ruby.mdx
index 911b110ab5a880..2ee46006eeb6af 100644
--- a/platform-includes/profiling/index/preface/ruby.mdx
+++ b/platform-includes/profiling/index/preface/ruby.mdx
@@ -1,5 +1,5 @@
-<Note>
+<Alert>
 
 Ruby Profiling is currently in beta. Beta features are still in progress and may have bugs. We recognize the irony.
 
-</Note>
+</Alert>
diff --git a/platform-includes/replay/privacy-configuration/flutter.mdx b/platform-includes/replay/privacy-configuration/flutter.mdx
index 472a97f2ca8257..101e0d17e4dfaa 100644
--- a/platform-includes/replay/privacy-configuration/flutter.mdx
+++ b/platform-includes/replay/privacy-configuration/flutter.mdx
@@ -44,11 +44,11 @@ Mask given widget type `T` (or subclasses of `T`) in the screenshot. Note: maski
 
 You can find more details in the documentation for each method.
 
-<Note>
+<Alert>
 
 If you find that data isn't being masked with the default settings, please let us know by creating a [GitHub issue](https://github.com/getsentry/sentry-dart/issues/new?template=BUG_REPORT.yml).
 
-</Note>
+</Alert>
 
 To disable masking for <PlatformLink to="/enriching-events/screenshots/">`Screenshots`</PlatformLink> and <PlatformLink to="/session-replay/">`Session Replay`</PlatformLink> (not to be used on applications with sensitive data):
 
diff --git a/platform-includes/sensitive-data/set-tag/_default.mdx b/platform-includes/sensitive-data/set-tag/_default.mdx
index f145756676341b..a4e2033d367788 100644
--- a/platform-includes/sensitive-data/set-tag/_default.mdx
+++ b/platform-includes/sensitive-data/set-tag/_default.mdx
@@ -1,8 +1,8 @@
-<Note>
+<Alert>
 
 The platform or SDK you've selected either does not support this functionality, or it is missing from our documentation. Please use this code sample from JavaScript as a basis:
 
-</Note>
+</Alert>
 
 ```javascript
 Sentry.setTag("birthday", checksumOrHash("08/12/1990"));
diff --git a/platform-includes/sensitive-data/set-user/_default.mdx b/platform-includes/sensitive-data/set-user/_default.mdx
index aa6c70a81e3b85..87e331471dd82e 100644
--- a/platform-includes/sensitive-data/set-user/_default.mdx
+++ b/platform-includes/sensitive-data/set-user/_default.mdx
@@ -1,8 +1,8 @@
-<Note>
+<Alert>
 
 The platform or SDK you've selected either does not support this functionality, or the code sample is missing from our documentation. Please use this code sample from JavaScript as a basis:
 
-</Note>
+</Alert>
 
 ```javascript
 Sentry.setUser({ id: user.id });
diff --git a/platform-includes/session-replay/install/javascript.astro.mdx b/platform-includes/session-replay/install/javascript.astro.mdx
index 7bebb971e20476..88d983675735c2 100644
--- a/platform-includes/session-replay/install/javascript.astro.mdx
+++ b/platform-includes/session-replay/install/javascript.astro.mdx
@@ -4,8 +4,8 @@ The Replay integration is already included with the Sentry Astro SDK.
 npx astro add @sentry/astro
 ```
 
-<Note>
+<Alert>
 
 If the Astro CLI setup doesn't work for you, you can also <PlatformLink to="/manual-setup/">set up the SDK manually</PlatformLink>.
 
-</Note>
+</Alert>
diff --git a/platform-includes/session-replay/install/javascript.remix.mdx b/platform-includes/session-replay/install/javascript.remix.mdx
index c7688fa8cc531f..94a2e1c75e7195 100644
--- a/platform-includes/session-replay/install/javascript.remix.mdx
+++ b/platform-includes/session-replay/install/javascript.remix.mdx
@@ -17,8 +17,8 @@ If you use [Remix future flags](https://remix.run/docs/en/main/pages/api-develop
 After the wizard setup is completed, the SDK will automatically capture unhandled errors, and monitor performance.
 You can also <PlatformLink to="/usage/">manually capture errors</PlatformLink>.
 
-<Note>
+<Alert>
 
 If the wizard setup isn't working for you, you can <PlatformLink to="/manual-setup/">set up the SDK manually</PlatformLink>.
 
-</Note>
+</Alert>
diff --git a/platform-includes/session-replay/install/javascript.sveltekit.mdx b/platform-includes/session-replay/install/javascript.sveltekit.mdx
index 1c22fa4d2d73e6..7e6101598d3f7a 100644
--- a/platform-includes/session-replay/install/javascript.sveltekit.mdx
+++ b/platform-includes/session-replay/install/javascript.sveltekit.mdx
@@ -15,8 +15,8 @@ The wizard will prompt you to log in to Sentry. It will then automatically do th
 After the wizard setup is completed, the SDK will automatically capture unhandled errors, and monitor performance.
 You can also <PlatformLink to="/usage/">manually capture errors</PlatformLink>.
 
-<Note>
+<Alert>
 
 If the setup through the wizard doesn't work for you, you can also <PlatformLink to="/manual-setup/">set up the SDK manually</PlatformLink>.
 
-</Note>
+</Alert>
diff --git a/platform-includes/session-replay/setup/javascript.capacitor.mdx b/platform-includes/session-replay/setup/javascript.capacitor.mdx
index 06ce14a2371e0f..b6db292ebf1e74 100644
--- a/platform-includes/session-replay/setup/javascript.capacitor.mdx
+++ b/platform-includes/session-replay/setup/javascript.capacitor.mdx
@@ -1,8 +1,8 @@
 Several options are supported and passable using the integration constructor. See the [configuration documentation](/platforms/javascript/guides/capacitor/session-replay/configuration/) for more details. To set up the integration, add the following to your Sentry initialization:
 
-<Note>
+<Alert>
   The minimal supported version of Sentry's SDK for Capacitor is 0.11.0.
-</Note>
+</Alert>
 
 
 ```javascript {9,13,15-21}
diff --git a/platform-includes/set-environment/dotnet.nlog.mdx b/platform-includes/set-environment/dotnet.nlog.mdx
index a6feb04ad4aa46..9b31a70582387f 100644
--- a/platform-includes/set-environment/dotnet.nlog.mdx
+++ b/platform-includes/set-environment/dotnet.nlog.mdx
@@ -1,4 +1,4 @@
-<Alert level="" title="NLog Layouts">
+<Alert title="NLog Layouts">
 
 For more information on how to dynamically set event data via `NLog.config`, see NLog's [layout renderer documentation](https://nlog-project.org/config/?tab=layout-renderers).
 
diff --git a/platform-includes/set-release/dotnet.mdx b/platform-includes/set-release/dotnet.mdx
index 015bb348920273..75cae89bc97cab 100644
--- a/platform-includes/set-release/dotnet.mdx
+++ b/platform-includes/set-release/dotnet.mdx
@@ -14,6 +14,6 @@ The SDK will first check if there's a version set on the environment via `SENTRY
 
 If no version is found, the SDK will look at the [entry assembly's](<https://msdn.microsoft.com/en-us/library/system.reflection.assembly.getentryassembly(v=vs.110).aspx>) `AssemblyInformationalVersionAttribute`, which accepts a string value and is often used to set a GIT commit hash. If that returns null, then the SDK will look at the default `AssemblyVersionAttribute`, which accepts the numeric version number. The resulting release will be in the format `<assembly-name>@<version-number>`.
 
-<Note>
+<Alert>
 An `AssemblyInformationalVersionAttribute` is included automatically in SDK-style projects with a default value of `"1.0.0.0"`. You can set the `Version` property in your project file to override this value or [disable it entirely](https://learn.microsoft.com/en-us/dotnet/standard/assembly/set-attributes-project-file#use-package-properties-as-assembly-attributes) by setting the `GenerateAssemblyInformationalVersionAttribute` property to `false`.
-</Note>
+</Alert>
diff --git a/platform-includes/set-release/dotnet.nlog.mdx b/platform-includes/set-release/dotnet.nlog.mdx
index 49bc1af722a2e1..7972d4f355bd39 100644
--- a/platform-includes/set-release/dotnet.nlog.mdx
+++ b/platform-includes/set-release/dotnet.nlog.mdx
@@ -1,4 +1,4 @@
-<Alert level="" title="NLog Layouts">
+<Alert title="NLog Layouts">
 
 For more information on how to dynamically set event data via `NLog.config`, see NLog's [layout renderer documentation](https://nlog-project.org/config/?tab=layout-renderers).
 
diff --git a/platform-includes/set-release/ruby.mdx b/platform-includes/set-release/ruby.mdx
index 2e65a2991a3287..644dca7ab907d9 100644
--- a/platform-includes/set-release/ruby.mdx
+++ b/platform-includes/set-release/ruby.mdx
@@ -5,8 +5,8 @@ Sentry.init do |config|
 end
 ```
 
-<Note>
+<Alert>
 
 We'll automatically attempt to detect the release in certain environments, such as Heroku and Capistrano.
 
-</Note>
+</Alert>
diff --git a/platform-includes/sourcemaps/artifact-bundles/javascript.mdx b/platform-includes/sourcemaps/artifact-bundles/javascript.mdx
index 1fe64e28cb27df..1d17bc2ae258a2 100644
--- a/platform-includes/sourcemaps/artifact-bundles/javascript.mdx
+++ b/platform-includes/sourcemaps/artifact-bundles/javascript.mdx
@@ -14,11 +14,11 @@ Artifact Bundles solve the challenge of matching paths by using a new identifica
 
 When using sentry-cli or the Webpack, Vite, or Rollup bundler plugins, Debug IDs are generated deterministically based on the source file contents. Deterministic Debug IDs for esbuild are currently not supported.
 
-<Note>
+<Alert>
 
 If you want to learn more about the rationale behind Debug IDs, we suggest taking a look at our [engineering blog](https://sentry.engineering/blog/the-case-for-debug-ids).
 
-</Note>
+</Alert>
 
 ### Associating a Release with Artifact Bundles
 
diff --git a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx
index 6ebf402308d800..035e82649ce700 100644
--- a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx
+++ b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx
@@ -134,11 +134,11 @@ You can upload using the URL of `~/js/app.js`. This will tell Sentry to ignore t
 
 Additionally you can also upload the same file under multiple names. Under the hood Sentry will deduplicate these.
 
-<Note>
+<Alert>
 
 The ~ prefix tells Sentry that for a given URL, **any** combination of protocol and hostname whose path is `/js/app.js` should use this artifact. Use this method **only** if your source/source map files are identical at all possible protocol/hostname combinations. **Sentry will prioritize full URLs over tilde prefixed paths**, if found.
 
-</Note>
+</Alert>
 
 ## Verify artifact names match `sourceMappingURL` value
 
diff --git a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx
index f5cad68edcc3fa..7a0907b873da7f 100644
--- a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx
+++ b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx
@@ -408,11 +408,11 @@ You can upload using the URL of `~/js/app.js`. This will tell Sentry to ignore t
 
 Additionally you can also upload the same file under multiple names. Under the hood Sentry will deduplicate these.
 
-<Note>
+<Alert>
 
 The ~ prefix tells Sentry that for a given URL, **any** combination of protocol and hostname whose path is `/js/app.js` should use this artifact. Use this method **only** if your source/source map files are identical at all possible protocol/hostname combinations. **Sentry will prioritize full URLs over tilde prefixed paths**, if found.
 
-</Note>
+</Alert>
 
 ### Verify artifact names match `sourceMappingURL` value
 
diff --git a/platform-includes/sourcemaps/overview/javascript.mdx b/platform-includes/sourcemaps/overview/javascript.mdx
index 4cf709b3b67d02..22605cf7619870 100644
--- a/platform-includes/sourcemaps/overview/javascript.mdx
+++ b/platform-includes/sourcemaps/overview/javascript.mdx
@@ -4,11 +4,11 @@ The easiest way to configure uploading source maps is by using the Sentry Wizard
 
 <Include name="sourcemaps-wizard-instructions.mdx" />
 
-<Note>
+<Alert>
 
 This guide assumes you are using a Browser JavaScript SDK. For instructions on how to set up source maps for React Native, follow the [source maps guide for React Native](/platforms/react-native/sourcemaps/).
 
-</Note>
+</Alert>
 
 If you want to configure source maps upload manually, follow the guide for your bundler or build tool below.
 
@@ -30,10 +30,10 @@ If you used Create React App to set up your React application see our <PlatformL
 ### Guides
 
 - <PlatformLink to="/sourcemaps/uploading/typescript/"> TypeScript (tsc) </PlatformLink>
-  <Note>
+  <Alert>
     If you're using one of webpack, Vite, Rollup or Esbuild, use the
     corresponding Sentry plugin instead (see section "Sentry Bundler Support").
-  </Note>
+  </Alert>
 - <PlatformLink to="/sourcemaps/uploading/uglifyjs/">UglifyJS</PlatformLink>
 - <PlatformLink to="/sourcemaps/uploading/systemjs/">SystemJS</PlatformLink>
 - [GitHub Actions](/product/releases/setup/release-automation/github-actions/)
@@ -44,10 +44,10 @@ If you're not using one of these tools, we assume you already know how to genera
 
 <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']}>
 
-<Note>
+<Alert>
 
 Though we strongly recommend uploading source maps as part of your build process, for browser applications it's also possible to <PlatformLink to="/sourcemaps/uploading/hosting-publicly/">host your source maps publicly</PlatformLink>.
 
-</Note>
+</Alert>
 
 </PlatformSection>
diff --git a/platform-includes/sourcemaps/overview/javascript.remix.mdx b/platform-includes/sourcemaps/overview/javascript.remix.mdx
index fb91692dcdfd6d..8b5884bfb893a7 100644
--- a/platform-includes/sourcemaps/overview/javascript.remix.mdx
+++ b/platform-includes/sourcemaps/overview/javascript.remix.mdx
@@ -132,8 +132,8 @@ rm ./build/**/*.map
 
 Please note that these commands might vary for the operating system or shell you use.
 
-<Note>
+<Alert>
 
 By default, if Sentry can't find the uploaded files it needs, it will attempt to download them from the URLs in the stack trace. To disable this, turn off "Enable JavaScript source fetching" in either your organization's "Security & Privacy" settings or your project's general settings.
 
-</Note>
+</Alert>
diff --git a/platform-includes/sourcemaps/overview/javascript.svelte.mdx b/platform-includes/sourcemaps/overview/javascript.svelte.mdx
index e58d386792c205..ce7ba244f05c29 100644
--- a/platform-includes/sourcemaps/overview/javascript.svelte.mdx
+++ b/platform-includes/sourcemaps/overview/javascript.svelte.mdx
@@ -1,12 +1,12 @@
 ## Upload Source Maps for a Svelte Project
 
-<Note>
+<Alert>
 
 This guide assumes you are using the `@sentry/svelte` SDK on version `7.47.0` or higher.
 
 If you are on an older version and you want to upload source maps we recommend upgrading your SDK to the newest version.
 
-</Note>
+</Alert>
 
 ### Using the Sentry Wizard
 
@@ -95,19 +95,19 @@ export default defineConfig({
   option to delete source maps after they've been uploaded to Sentry.
 </Alert>
 
-<Note>
+<Alert>
 
 The Sentry Vite plugin doesn't upload source maps in watch-mode/development-mode.
 We recommend running a production build to test your implementation.
 
-</Note>
+</Alert>
 
 ### Other Bundlers
 
 If you're using a bundler other than Vite, check out our general guide on how to <PlatformLink to="/sourcemaps/uploading/">upload source maps</PlatformLink>, or refer to your bundler's documentation.
 
-<Note>
+<Alert>
 
 By default, if Sentry can't find the uploaded files it needs, it will attempt to download them from the URLs in the stack trace. To disable this, turn off "Enable JavaScript source fetching" in either your organization's "Security & Privacy" settings or your project's general settings.
 
-</Note>
+</Alert>
diff --git a/platform-includes/sourcemaps/overview/javascript.vue.mdx b/platform-includes/sourcemaps/overview/javascript.vue.mdx
index 6a566ccd843fc1..f7586c50f599e8 100644
--- a/platform-includes/sourcemaps/overview/javascript.vue.mdx
+++ b/platform-includes/sourcemaps/overview/javascript.vue.mdx
@@ -1,12 +1,12 @@
 ## Uploading Source Maps in a Vue Project
 
-<Note>
+<Alert>
 
 This guide assumes you are using the `@sentry/vue` SDK on version `7.47.0` or higher.
 
 If you are on an older version and you want to upload source maps we recommend upgrading your SDK to the newest version.
 
-</Note>
+</Alert>
 
 ### Using the Sentry Wizard
 
@@ -86,12 +86,12 @@ export default defineConfig({
   option to delete source maps after they've been uploaded to Sentry.
 </Alert>
 
-<Note>
+<Alert>
 
 The Sentry Vite plugin doesn't upload source maps in watch-mode/development-mode.
 We recommend running a production build to test your implementation.
 
-</Note>
+</Alert>
 
 ### Other Bundlers
 
@@ -108,8 +108,8 @@ In case you are using a bundler other than Vite to build your Vue project, we've
 
 If you're not using any of tools above, we assume you already know how to generate source maps with your toolchain and we recommend you upload them using <PlatformLink to="/sourcemaps/uploading/cli/">Sentry CLI</PlatformLink>.
 
-<Note>
+<Alert>
 
 Though we strongly recommend uploading source maps as part of your build process, for browser applications it's also possible to <PlatformLink to="/sourcemaps/uploading/hosting-publicly/">host your source maps publicly</PlatformLink>.
 
-</Note>
+</Alert>
diff --git a/platform-includes/sourcemaps/troubleshooting/javascript.mdx b/platform-includes/sourcemaps/troubleshooting/javascript.mdx
index c26ea7ba1c149c..337c86bdd96bc8 100644
--- a/platform-includes/sourcemaps/troubleshooting/javascript.mdx
+++ b/platform-includes/sourcemaps/troubleshooting/javascript.mdx
@@ -1,4 +1,4 @@
-<Note>
+<Alert>
 
 If you previously set up source maps, we suggest updating your tools (SDK, bundler plugins, Sentry CLI).
 It is generally easier to upgrade to the latest versions and follow the current process rather than troubleshooting with older versions.
@@ -28,7 +28,7 @@ Dependency versions that require the legacy method of uploading source maps incl
   </li>
 </ul>
 
-</Note>
+</Alert>
 
 Setting up source maps can be tricky, but it's worth it to get it right. To troubleshoot your source maps set up, you can either:
 
diff --git a/platform-includes/sourcemaps/upload/primer/javascript.mdx b/platform-includes/sourcemaps/upload/primer/javascript.mdx
index e201aa9d9c20d7..f19448a94e44bb 100644
--- a/platform-includes/sourcemaps/upload/primer/javascript.mdx
+++ b/platform-includes/sourcemaps/upload/primer/javascript.mdx
@@ -3,21 +3,21 @@ Pick one from the list below to learn more.
 
 <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']}>
 
-<Note>
+<Alert>
 
 If you can't find the tool of your choice in the list below, we recommend you choose either the "Sentry CLI" or "Hosting Publicly" guide.
 
-</Note>
+</Alert>
 
 </PlatformSection>
 
 <PlatformSection supported={['javascript.node', 'javascript.aws-lambda', 'javascript.azure-functions', 'javascript.connect', 'javascript.express', 'javascript.fastify', 'javascript.gcp-functions', 'javascript.hapi', 'javascript.koa', 'javascript.nestjs']}>
 
-<Note>
+<Alert>
 
 If you can't find the tool of your choice in the list below, we recommend you choose the "Sentry CLI" guide.
 
-</Note>
+</Alert>
 
 </PlatformSection>
 
diff --git a/platform-includes/user-feedback/install/javascript.astro.mdx b/platform-includes/user-feedback/install/javascript.astro.mdx
index 111136c51f2b6e..7fa0fafb77fcf8 100644
--- a/platform-includes/user-feedback/install/javascript.astro.mdx
+++ b/platform-includes/user-feedback/install/javascript.astro.mdx
@@ -4,8 +4,8 @@ The User Feedback integration is already included with the Sentry Astro SDK.
 npx astro add @sentry/astro
 ```
 
-<Note>
+<Alert>
 
 If the Astro CLI setup doesn't work for you, you can also <PlatformLink to="/manual-setup/">set up the SDK manually</PlatformLink>.
 
-</Note>
+</Alert>
diff --git a/platform-includes/user-feedback/install/javascript.remix.mdx b/platform-includes/user-feedback/install/javascript.remix.mdx
index 3c5c9043de59ab..1b284009fa2253 100644
--- a/platform-includes/user-feedback/install/javascript.remix.mdx
+++ b/platform-includes/user-feedback/install/javascript.remix.mdx
@@ -17,8 +17,8 @@ If you use [Remix future flags](https://remix.run/docs/en/main/pages/api-develop
 After the wizard setup is completed, the SDK will automatically capture unhandled errors, and monitor performance.
 You can also <PlatformLink to="/usage/">manually capture errors</PlatformLink>.
 
-<Note>
+<Alert>
 
 If the wizard setup isn't working for you, you can <PlatformLink to="/manual-setup/">set up the SDK manually</PlatformLink>.
 
-</Note>
+</Alert>
diff --git a/platform-includes/user-feedback/install/javascript.sveltekit.mdx b/platform-includes/user-feedback/install/javascript.sveltekit.mdx
index a301858cffd48f..130e82190dc704 100644
--- a/platform-includes/user-feedback/install/javascript.sveltekit.mdx
+++ b/platform-includes/user-feedback/install/javascript.sveltekit.mdx
@@ -15,8 +15,8 @@ The wizard will prompt you to log in to Sentry. It will then automatically do th
 After the wizard setup is completed, the SDK will automatically capture unhandled errors, and monitor performance.
 You can also <PlatformLink to="/usage/">manually capture errors</PlatformLink>.
 
-<Note>
+<Alert>
 
 If the setup through the wizard doesn't work for you, you can also <PlatformLink to="/manual-setup/">set up the SDK manually</PlatformLink>.
 
-</Note>
+</Alert>
diff --git a/platform-includes/user-feedback/sdk-api-example/javascript.mdx b/platform-includes/user-feedback/sdk-api-example/javascript.mdx
index 7fe8ab66c98efc..a7717c6de83ffb 100644
--- a/platform-includes/user-feedback/sdk-api-example/javascript.mdx
+++ b/platform-includes/user-feedback/sdk-api-example/javascript.mdx
@@ -1,9 +1,22 @@
-```javascript
+```javascript {tabTitle: JavaScript}
+import * as Sentry from "@sentry/browser";
+
+// All feedback fields are optional, except `message`.
+const userFeedback = {
+  name: "John Doe",
+  email: "john@doe.com",
+  message: "I really like your App, thanks!",
+};
+Sentry.captureFeedback(userFeedback);
+```
+
+```javascript {tabTitle: JavaScript with eventId}
 import * as Sentry from "@sentry/browser";
 
-const eventId = Sentry.captureMessage("User Feedback");
+const eventId = Sentry.captureException(new Error("Something went wrong!"));
 // OR: const eventId = Sentry.lastEventId();
 
+// All feedback fields are optional, except `message`.
 const userFeedback = {
   name: "John Doe",
   email: "john@doe.com",
diff --git a/platform-includes/user-feedback/sdk-api-example/unreal.mdx b/platform-includes/user-feedback/sdk-api-example/unreal.mdx
index 497a336c4b51c0..cabc6f1d4f0eea 100644
--- a/platform-includes/user-feedback/sdk-api-example/unreal.mdx
+++ b/platform-includes/user-feedback/sdk-api-example/unreal.mdx
@@ -20,8 +20,8 @@ The same result can be achieved by calling corresponding functions in blueprint:
 
 ![Capture user feedback](./img/unreal_user_feedback.png)
 
-<Note>
+<Alert>
 
 The ability to capture user feedback is only supported on macOS, iOS, and Android.
 
-</Note>
+</Alert>
diff --git a/redirects.js b/redirects.js
index 67a96ffa5adbf7..44348baca137ff 100644
--- a/redirects.js
+++ b/redirects.js
@@ -944,6 +944,10 @@ const userDocsRedirects = [
     source: '/platforms/kotlin-multiplatform/:path*',
     destination: '/platforms/kotlin/guides/kotlin-multiplatform/:path*',
   },
+  {
+    source: '/product/explore/feature-flags/:path*',
+    destination: '/product/issues/issue-details/feature-flags/:path*',
+  },
 ];
 
 /**
diff --git a/src/build/resolveOpenAPI.ts b/src/build/resolveOpenAPI.ts
index 1e8d7420a8db38..848960528e954d 100644
--- a/src/build/resolveOpenAPI.ts
+++ b/src/build/resolveOpenAPI.ts
@@ -8,7 +8,7 @@ import {DeRefedOpenAPI} from './open-api/types';
 
 // SENTRY_API_SCHEMA_SHA is used in the sentry-docs GHA workflow in getsentry/sentry-api-schema.
 // DO NOT change variable name unless you change it in the sentry-docs GHA workflow in getsentry/sentry-api-schema.
-const SENTRY_API_SCHEMA_SHA = '216615cb68bc61c73c5acc421c92e7dc5adae687';
+const SENTRY_API_SCHEMA_SHA = '421589ca453b898372204963465c7d856feec7c7';
 
 const activeEnv = process.env.GATSBY_ENV || process.env.NODE_ENV || 'development';
 
diff --git a/src/components/alert.tsx b/src/components/alert.tsx
new file mode 100644
index 00000000000000..091fb7d3a1c95c
--- /dev/null
+++ b/src/components/alert.tsx
@@ -0,0 +1,34 @@
+import {ReactNode} from 'react';
+import {
+  CheckCircledIcon,
+  ExclamationTriangleIcon,
+  InfoCircledIcon,
+} from '@radix-ui/react-icons';
+
+import {Callout} from './callout';
+
+type AlertProps = {
+  children?: ReactNode;
+  level?: 'info' | 'warning' | 'success';
+  title?: string;
+};
+
+const ICON_MAP = {
+  info: InfoCircledIcon,
+  warning: ExclamationTriangleIcon,
+  success: CheckCircledIcon,
+} as const;
+
+export function Alert({title, children, level = 'info'}: AlertProps) {
+  const Icon = ICON_MAP[level];
+
+  if (!Icon) {
+    throw new Error(`Invalid alert level: "${level}" passed to Alert component`);
+  }
+
+  return (
+    <Callout role="alert" level={level} Icon={Icon} title={title}>
+      {children}
+    </Callout>
+  );
+}
diff --git a/src/components/alert/index.tsx b/src/components/alert/index.tsx
deleted file mode 100644
index 550cbaba70b137..00000000000000
--- a/src/components/alert/index.tsx
+++ /dev/null
@@ -1,32 +0,0 @@
-import {ReactNode} from 'react';
-
-// explicitly not usig CSS modules here
-// because there's some prerendered content that depends on these exact class names
-import './styles.scss';
-
-type AlertProps = {
-  children?: ReactNode;
-  level?: 'info' | 'warning' | 'danger' | 'success' | '';
-  title?: string;
-};
-
-export function Alert({title, children, level = 'info'}: AlertProps) {
-  return (
-    <div className={`alert ${'alert-' + level}`} role="alert">
-      {title && <h5 className="alert-header">{title}</h5>}
-      <div className="alert-body content-flush-bottom">{children}</div>
-    </div>
-  );
-}
-
-type NoteProps = {
-  children: ReactNode;
-};
-
-export function Note({children}: NoteProps) {
-  return (
-    <div role="note" className="alert">
-      <div className="alert-body">{children}</div>
-    </div>
-  );
-}
diff --git a/src/components/alert/styles.scss b/src/components/alert/styles.scss
deleted file mode 100644
index 02dd702abf4067..00000000000000
--- a/src/components/alert/styles.scss
+++ /dev/null
@@ -1,66 +0,0 @@
-.alert,
-.note {
-  background: var(--accent-2);
-  border-color: var(--accent-12);
-  border-left: 3px solid var(--accent-12);
-  margin-bottom: 1rem;
-  padding: 0.5rem 1rem;
-
-  > .alert-header {
-    font-weight: 500;
-    position: relative;
-    font-size: 1em;
-    margin-bottom: 0.5rem;
-    margin-top: 0.25rem;
-  }
-
-  p {
-    margin-bottom: 0.5rem;
-  }
-
-  strong {
-    font-weight: 500;
-  }
-
-  ul {
-    padding-inline-start: 2rem;
-  }
-
-  p:last-of-type,
-  ul:last-of-type {
-    margin-bottom: 0;
-  }
-
-  p:first-of-type,
-  ul:first-of-type {
-    margin-top: 0;
-  }
-
-  .alert-body {
-    font-size: 0.9rem;
-  }
-}
-
-.alert-info {
-  background: var(--blue-2);
-  border-color: var(--blue-11);
-  color: var(--blue-12);
-}
-
-.alert-warning {
-  background: var(--amber-2);
-  border-color: var(--amber-10);
-  color: var(--amber-12);
-}
-
-.alert-danger {
-  background: var(--red-2);
-  border-color: var(--red-10);
-  color: var(--red-12);
-}
-
-.alert-success {
-  background: var(--green-2);
-  border-color: var(--green-10);
-  color: var(--green-12);
-}
diff --git a/src/components/callout/index.tsx b/src/components/callout/index.tsx
new file mode 100644
index 00000000000000..903d382e8e2654
--- /dev/null
+++ b/src/components/callout/index.tsx
@@ -0,0 +1,88 @@
+import {
+  ForwardRefExoticComponent,
+  MouseEventHandler,
+  ReactNode,
+  useCallback,
+} from 'react';
+
+// explicitly not usig CSS modules here
+// because there's some prerendered content that depends on these exact class names
+import './styles.scss';
+
+type CalloutProps = {
+  Icon: ForwardRefExoticComponent<any>;
+  children?: ReactNode;
+  /** If defined, the title of the callout will receive this ID and render a link to this ID. */
+  id?: string;
+  level?: 'info' | 'warning' | 'success';
+  role?: string;
+  title?: string;
+  titleOnClick?: MouseEventHandler;
+};
+
+function Header({
+  title,
+  id,
+  onClick,
+}: {
+  title: string;
+  id?: string;
+  onClick?: MouseEventHandler;
+}) {
+  // We want to avoid actually triggering the link
+  const preventDefaultOnClick = useCallback(
+    (event: React.MouseEvent) => {
+      if (!onClick) {
+        return;
+      }
+
+      event.preventDefault();
+      onClick(event);
+    },
+    [onClick]
+  );
+
+  if (!id) {
+    return (
+      <h5
+        className="callout-header"
+        onClick={onClick}
+        role={onClick ? 'button' : undefined}
+      >
+        {title}
+      </h5>
+    );
+  }
+
+  return (
+    <h5 className="callout-header" id={id}>
+      <a href={'#' + id} onClick={preventDefaultOnClick}>
+        {title}
+      </a>
+    </h5>
+  );
+}
+
+export function Callout({
+  title,
+  children,
+  level = 'info',
+  Icon,
+  role,
+  id,
+  titleOnClick,
+}: CalloutProps) {
+  return (
+    <div className={`callout ${'callout-' + level}`} role={role}>
+      <Icon
+        className="callout-icon"
+        onClick={titleOnClick}
+        role={titleOnClick ? 'button' : undefined}
+      />
+      <div className="callout-content">
+        {title && <Header title={title} id={id} onClick={titleOnClick} />}
+        <div className="callout-body content-flush-bottom">{children}</div>
+      </div>
+    </div>
+  );
+}
diff --git a/src/components/callout/styles.scss b/src/components/callout/styles.scss
new file mode 100644
index 00000000000000..312e6aa69cff2a
--- /dev/null
+++ b/src/components/callout/styles.scss
@@ -0,0 +1,74 @@
+.callout {
+  margin-bottom: 1rem;
+  padding: 0.5rem 1rem;
+  border-radius: 6px;
+  display: flex;
+  flex-direction: row;
+  gap: 0.7rem;
+  line-height: 1.75rem;
+  border: 1px solid var(--callout-highlight-color);
+
+  p {
+    margin-bottom: 1rem;
+    margin-top: 0;
+  }
+
+  strong {
+    font-weight: 500;
+  }
+
+  ul,
+  ol {
+    padding-inline-start: 2rem;
+    margin-top: 0;
+    margin-bottom: 1rem;
+  }
+
+  li {
+    padding-inline-start: 0;
+    margin: 0;
+  }
+
+  .callout-header {
+    font-weight: 500;
+    color: inherit;
+
+    & a {
+      color: inherit;
+    }
+
+    &[role="button"] {
+      cursor: pointer;
+    }
+  }
+}
+
+.callout-icon {
+  flex: 1em 0 0;
+  height: 1.75rem;
+  color: var(--callout-highlight-color);
+
+  &[role="button"] {
+    cursor: pointer;
+  }
+}
+
+.callout-content {
+  min-width: 0;
+}
+
+.callout-info {
+  --callout-highlight-color: var(--accent-11);
+  background: var(--accent-2);
+}
+
+.callout-success {
+  --callout-highlight-color: var(--successGreen);
+  background: var(--successGreen);
+  background: color-mix(in srgb, var(--successGreen), transparent 85%);
+}
+
+.callout-warning {
+  --callout-highlight-color: var(--amber-10);
+  background: var(--amber-2);
+}
diff --git a/src/components/docFeedback/index.tsx b/src/components/docFeedback/index.tsx
new file mode 100644
index 00000000000000..b0dd8704f29af6
--- /dev/null
+++ b/src/components/docFeedback/index.tsx
@@ -0,0 +1,122 @@
+'use client';
+import {Fragment, useEffect, useState} from 'react';
+import {CheckIcon as Check} from '@radix-ui/react-icons';
+import {Button} from '@radix-ui/themes';
+import * as Sentry from '@sentry/browser';
+
+import {usePlausibleEvent} from 'sentry-docs/hooks/usePlausibleEvent';
+
+type Props = {
+  pathname: string;
+};
+
+export function DocFeedback({pathname}: Props) {
+  const {emit} = usePlausibleEvent();
+  const [showFeedback, setShowFeedback] = useState(false);
+  const [feedbackSubmitted, setFeedbackSubmitted] = useState(false);
+  const [feedbackType, setFeedbackType] = useState<'helpful' | 'not_helpful' | null>(
+    null
+  );
+
+  // Initialize feedback state from sessionStorage
+  useEffect(() => {
+    const storedFeedback = sessionStorage.getItem(`feedback_${pathname}`);
+    if (storedFeedback === 'submitted') {
+      setFeedbackSubmitted(true);
+    }
+  }, [pathname]);
+
+  const handleFeedback = (helpful: boolean) => {
+    emit('Doc Feedback', {props: {page: pathname, helpful}});
+    setFeedbackType(helpful ? 'helpful' : 'not_helpful');
+    setShowFeedback(true);
+  };
+
+  const handleSubmitFeedback = (e: React.FormEvent<HTMLFormElement>) => {
+    e.preventDefault();
+    const formData = new FormData(e.currentTarget);
+    const comments = formData.get('comments') as string;
+
+    try {
+      Sentry.captureFeedback(
+        {
+          message: comments,
+        },
+        {captureContext: {tags: {page: pathname, type: feedbackType}}}
+      );
+      setFeedbackSubmitted(true);
+      sessionStorage.setItem(`feedback_${pathname}`, 'submitted');
+    } catch (error) {
+      if (process.env.NODE_ENV === 'development') {
+        // eslint-disable-next-line no-console
+        console.error('Failed to submit feedback:', error);
+      }
+      Sentry.captureException(error);
+    }
+  };
+
+  return (
+    <Fragment>
+      <div className="space-y-4 py-4 border-[var(--gray-6)]">
+        {feedbackSubmitted ? (
+          <div className="flex items-center gap-2 text-sm text-[var(--gray-11)]">
+            <Check className="w-4 h-4" /> Thanks for your feedback
+          </div>
+        ) : (
+          <Fragment>
+            <div className="flex items-center gap-4 text-sm mt-8">
+              <span className="font-medium">Was this helpful?</span>
+              <div className="flex">
+                <button
+                  onClick={() => handleFeedback(true)}
+                  className="py-1 px-2 gap-4 hover:bg-[var(--gray-3)] rounded flex items-center justify-center"
+                  aria-label="Yes, this was helpful"
+                >
+                  Yes 👍
+                </button>
+                <button
+                  onClick={() => handleFeedback(false)}
+                  className="py-1 px-2 gap-4 hover:bg-[var(--gray-3)] rounded flex items-center justify-center"
+                  aria-label="No, this wasn't helpful"
+                >
+                  No 👎
+                </button>
+              </div>
+            </div>
+
+            <div
+              className={`overflow-hidden transition-all duration-300 ease-in-out ${
+                showFeedback ? 'max-h-[300px] opacity-100' : 'max-h-0 opacity-0'
+              }`}
+            >
+              <form onSubmit={handleSubmitFeedback} className="space-y-4">
+                <div>
+                  <label htmlFor="comments" className="block text-sm font-medium mb-4">
+                    {feedbackType === 'helpful'
+                      ? 'What did you like about this page?'
+                      : 'How can we improve this page?'}
+                  </label>
+                  <textarea
+                    id="comments"
+                    name="comments"
+                    required
+                    rows={2}
+                    className="w-[calc(100%-4px)] ml-[2px] px-3 py-2 border border-[var(--gray-6)] rounded-lg focus:outline-none focus:ring-2 focus:ring-[var(--accent)] bg-transparent text-sm"
+                    placeholder="Please share your thoughts..."
+                  />
+                </div>
+                <Button
+                  type="submit"
+                  className="px-4 py-2 text-sm rounded-lg bg-[var(--accent-purple)]"
+                  size={'3'}
+                >
+                  Submit feedback
+                </Button>
+              </form>
+            </div>
+          </Fragment>
+        )}
+      </div>
+    </Fragment>
+  );
+}
diff --git a/src/components/docPage/index.tsx b/src/components/docPage/index.tsx
index 10da08e5c9ec1b..5e7f93a7f1d8a0 100644
--- a/src/components/docPage/index.tsx
+++ b/src/components/docPage/index.tsx
@@ -12,6 +12,7 @@ import './type.scss';
 import {Banner} from '../banner';
 import {Breadcrumbs} from '../breadcrumbs';
 import {CodeContextProvider} from '../codeContext';
+import {DocFeedback} from '../docFeedback';
 import {GitHubCTA} from '../githubCTA';
 import {Header} from '../header';
 import Mermaid from '../mermaid';
@@ -100,6 +101,8 @@ export function DocPage({
                 </div>
               </div>
 
+              <DocFeedback pathname={pathname} />
+
               {hasGithub && <GitHubCTA />}
             </div>
           </div>
diff --git a/src/components/expandable.tsx b/src/components/expandable.tsx
index 28368464d68c48..e57e91de0c84e6 100644
--- a/src/components/expandable.tsx
+++ b/src/components/expandable.tsx
@@ -1,38 +1,17 @@
 'use client';
 
 import {ReactNode, useEffect, useState} from 'react';
-import {ArrowDown} from 'react-feather';
-import styled from '@emotion/styled';
+import {ChevronDownIcon, ChevronRightIcon} from '@radix-ui/react-icons';
+
+import {Callout} from './callout';
 
 type Props = {
   children: ReactNode;
   title: string;
+  level?: 'info' | 'warning' | 'success';
   permalink?: boolean;
 };
 
-const Arrow = styled(({...props}) => <ArrowDown {...props} />)<{className: string}>`
-  user-select: none;
-  transition: transform 200ms ease-in-out;
-  stroke-width: 3px;
-  position: absolute;
-  right: 0;
-  top: 4px;
-`;
-
-const Details = styled.details`
-  background: var(--accent-2);
-  border-color: var(--accent-12);
-  border-left: 3px solid var(--accent-12);
-  margin-bottom: 1rem;
-  padding: 0.5rem 1rem;
-  h2 {
-    margin-top: 0;
-  }
-  &[open] .expandable-arrow {
-    transform: rotate(180deg);
-  }
-`;
-
 function slugify(str: string) {
   return str
     .toLowerCase()
@@ -40,31 +19,28 @@ function slugify(str: string) {
     .replace(/[^a-z0-9-]/g, '');
 }
 
-const header = (title: string, permalink?: boolean) =>
-  permalink ? (
-    <h2 id={slugify(title)} className="!mb-0">
-      <a
-        href={'#' + slugify(title)}
-        className="w-full !text-[1rem] !font-medium hover:!no-underline !text-[var(--foreground)]"
-      >
-        {title}
-      </a>
-    </h2>
-  ) : (
-    title
-  );
+export function Expandable({title, level, children, permalink}: Props) {
+  const id = permalink ? slugify(title) : undefined;
 
-export function Expandable({title, children, permalink}: Props) {
   const [isExpanded, setIsExpanded] = useState(false);
 
+  // Ensure we scroll to the element if the URL hash matches
   useEffect(() => {
-    // if the url hash matches the title, expand the section
-    if (permalink && window.location.hash === `#${slugify(title)}`) {
+    if (!id) {
+      return () => {};
+    }
+
+    if (window.location.hash === `#${id}`) {
+      document.querySelector(`#${id}`)?.scrollIntoView();
       setIsExpanded(true);
     }
+
+    // When the hash changes (e.g. when the back/forward browser buttons are used),
+    // we want to ensure to jump to the correct section
     const onHashChange = () => {
-      if (window.location.hash === `#${slugify(title)}`) {
+      if (window.location.hash === `#${id}`) {
         setIsExpanded(true);
+        document.querySelector(`#${id}`)?.scrollIntoView();
       }
     };
     // listen for hash changes and expand the section if the hash matches the title
@@ -72,15 +48,31 @@ export function Expandable({title, children, permalink}: Props) {
     return () => {
       window.removeEventListener('hashchange', onHashChange);
     };
-  }, [title, permalink]);
+  }, [id]);
+
+  function toggleIsExpanded() {
+    const newVal = !isExpanded;
+
+    if (id) {
+      if (newVal) {
+        window.history.pushState({}, '', `#${id}`);
+      } else {
+        window.history.pushState({}, '', '#');
+      }
+    }
+
+    setIsExpanded(newVal);
+  }
 
   return (
-    <Details open={isExpanded}>
-      <summary className="m-0 font-medium cursor-pointer relative pr-8 select-none appearance-none list-none">
-        {header(title, permalink)}
-        <Arrow className="expandable-arrow" />
-      </summary>
-      {children}
-    </Details>
+    <Callout
+      level={level}
+      title={title}
+      Icon={isExpanded ? ChevronDownIcon : ChevronRightIcon}
+      id={id}
+      titleOnClick={toggleIsExpanded}
+    >
+      {isExpanded ? children : undefined}
+    </Callout>
   );
 }
diff --git a/src/components/orgAuthTokenNote.tsx b/src/components/orgAuthTokenNote.tsx
index 752052942624f2..8d679d0adde539 100644
--- a/src/components/orgAuthTokenNote.tsx
+++ b/src/components/orgAuthTokenNote.tsx
@@ -3,7 +3,7 @@
 import {Fragment, useContext} from 'react';
 import {usePathname} from 'next/navigation';
 
-import {Alert, Note} from './alert';
+import {Alert} from './alert';
 import {CodeContext} from './codeContext';
 import {ExternalLink} from './externalLink';
 import {SignedInCheck} from './signedInCheck';
@@ -17,7 +17,7 @@ export function OrgAuthTokenNote() {
   return (
     <Fragment>
       <SignedInCheck isUserAuthenticated={false}>
-        <Note>
+        <Alert>
           You can{' '}
           <ExternalLink href={orgAuthTokenUrl} target="_blank">
             manually create an Auth Token
@@ -27,7 +27,7 @@ export function OrgAuthTokenNote() {
             sign in
           </ExternalLink>{' '}
           to create a token directly from this page.
-        </Note>
+        </Alert>
       </SignedInCheck>
 
       <SignedInCheck isUserAuthenticated>
diff --git a/src/components/relayMetrics/index.tsx b/src/components/relayMetrics/index.tsx
index e36653cbcdb73d..290fdeceffc915 100644
--- a/src/components/relayMetrics/index.tsx
+++ b/src/components/relayMetrics/index.tsx
@@ -24,7 +24,7 @@ export function RelayMetrics() {
 function RelayFeatures({features}) {
   if (Array.isArray(features) && features.includes('processing')) {
     return (
-      <Alert level="info" title="Note">
+      <Alert title="Note">
         This metric is emitted only when Relay runs as internal Sentry service for event
         ingestion (<code>processing</code> feature).
       </Alert>
diff --git a/src/components/search/index.tsx b/src/components/search/index.tsx
index 5b75b757852e83..a5fc3c2f0068ee 100644
--- a/src/components/search/index.tsx
+++ b/src/components/search/index.tsx
@@ -9,19 +9,19 @@ import {
   SentryGlobalSearch,
   standardSDKSlug,
 } from '@sentry-internal/global-search';
-import DOMPurify from 'dompurify';
-import Link from 'next/link';
-import {usePathname, useRouter} from 'next/navigation';
+import {usePathname} from 'next/navigation';
 import algoliaInsights from 'search-insights';
 
 import {useOnClickOutside} from 'sentry-docs/clientUtils';
-import {useKeyboardNavigate} from 'sentry-docs/hooks/useKeyboardNavigate';
 import {isDeveloperDocs} from 'sentry-docs/isDeveloperDocs';
 
 import styles from './search.module.scss';
 
 import {Logo} from '../logo';
 
+import {SearchResultItems} from './searchResultItems';
+import {relativizeUrl} from './util';
+
 // Initialize Algolia Insights
 algoliaInsights('init', {
   appId: process.env.NEXT_PUBLIC_ALGOLIA_APP_ID,
@@ -33,8 +33,6 @@ algoliaInsights('init', {
 // treat it as a random user.
 const randomUserToken = crypto.randomUUID();
 
-const MAX_HITS = 10;
-
 // this type is not exported from the global-search package
 type SentryGlobalSearchConfig = ConstructorParameters<typeof SentryGlobalSearch>[0];
 
@@ -59,12 +57,6 @@ const userDocsSites: SentryGlobalSearchConfig = [
 const config = isDeveloperDocs ? developerDocsSites : userDocsSites;
 const search = new SentryGlobalSearch(config);
 
-function relativizeUrl(url: string) {
-  return isDeveloperDocs
-    ? url
-    : url.replace(/^(https?:\/\/docs\.sentry\.io)(?=\/|$)/, '');
-}
-
 type Props = {
   autoFocus?: boolean;
   path?: string;
@@ -79,7 +71,7 @@ export function Search({path, autoFocus, searchPlatforms = [], showChatBot}: Pro
   const [inputFocus, setInputFocus] = useState(false);
   const [showOffsiteResults, setShowOffsiteResults] = useState(false);
   const [loading, setLoading] = useState(true);
-  const router = useRouter();
+
   const pathname = usePathname();
 
   const handleClickOutside = useCallback((ev: MouseEvent) => {
@@ -176,16 +168,6 @@ export function Search({path, autoFocus, searchPlatforms = [], showChatBot}: Pro
 
   const totalHits = results.reduce((a, x) => a + x.hits.length, 0);
 
-  const flatHits = results.reduce<Hit[]>(
-    (items, item) => [...items, ...item.hits.slice(0, MAX_HITS)],
-    []
-  );
-
-  const {focused} = useKeyboardNavigate({
-    list: flatHits,
-    onSelect: hit => router.push(relativizeUrl(hit.url)),
-  });
-
   const trackSearchResultClick = useCallback((hit: Hit, position: number): void => {
     try {
       algoliaInsights('clickedObjectIDsAfterSearch', {
@@ -305,77 +287,13 @@ export function Search({path, autoFocus, searchPlatforms = [], showChatBot}: Pro
           {loading && <Logo loading />}
 
           {!loading && totalHits > 0 && (
-            <div className={styles['sgs-search-results-scroll-container']}>
-              {results
-                .filter(x => x.hits.length > 0)
-                .map((result, i) => (
-                  <Fragment key={result.site}>
-                    {showOffsiteResults && (
-                      <h4 className={styles['sgs-site-result-heading']}>
-                        From {result.name}
-                      </h4>
-                    )}
-                    <ul
-                      className={`${styles['sgs-hit-list']} ${i === 0 ? '' : styles['sgs-offsite']}`}
-                    >
-                      {result.hits.slice(0, MAX_HITS).map((hit, index) => (
-                        <li
-                          key={hit.id}
-                          className={`${styles['sgs-hit-item']} ${
-                            focused?.id === hit.id ? styles['sgs-hit-focused'] : ''
-                          }`}
-                          ref={
-                            // Scroll to element on focus
-                            hit.id === focused?.id
-                              ? el => el?.scrollIntoView({block: 'nearest'})
-                              : undefined
-                          }
-                        >
-                          <Link
-                            href={relativizeUrl(hit.url)}
-                            onClick={e => handleSearchResultClick(e, hit, index)}
-                          >
-                            {hit.title && (
-                              <h6>
-                                <span
-                                  dangerouslySetInnerHTML={{
-                                    __html: DOMPurify.sanitize(hit.title, {
-                                      ALLOWED_TAGS: ['mark'],
-                                    }),
-                                  }}
-                                />
-                              </h6>
-                            )}
-                            {hit.text && (
-                              <span
-                                dangerouslySetInnerHTML={{
-                                  __html: DOMPurify.sanitize(hit.text, {
-                                    ALLOWED_TAGS: ['mark'],
-                                  }),
-                                }}
-                              />
-                            )}
-                            {hit.context && (
-                              <div className={styles['sgs-hit-context']}>
-                                {hit.context.context1 && (
-                                  <div className={styles['sgs-hit-context-left']}>
-                                    {hit.context.context1}
-                                  </div>
-                                )}
-                                {hit.context.context2 && (
-                                  <div className={styles['sgs-hit-context-right']}>
-                                    {hit.context.context2}
-                                  </div>
-                                )}
-                              </div>
-                            )}
-                          </Link>
-                        </li>
-                      ))}
-                    </ul>
-                  </Fragment>
-                ))}
-            </div>
+            <SearchResultItems
+              results={results}
+              onSearchResultClick={({event, hit, position}) =>
+                handleSearchResultClick(event, hit, position)
+              }
+              showOffsiteResults={showOffsiteResults}
+            />
           )}
 
           {!loading && totalHits === 0 && (
diff --git a/src/components/search/searchResultItems.tsx b/src/components/search/searchResultItems.tsx
new file mode 100644
index 00000000000000..06585d682751ca
--- /dev/null
+++ b/src/components/search/searchResultItems.tsx
@@ -0,0 +1,111 @@
+import {Fragment} from 'react';
+import {Hit, Result} from '@sentry-internal/global-search';
+import DOMPurify from 'dompurify';
+import Link from 'next/link';
+import {useRouter} from 'next/navigation';
+
+import {useListKeyboardNavigate} from 'sentry-docs/hooks/useListKeyboardNavigate';
+
+import styles from './search.module.scss';
+
+import {relativizeUrl} from './util';
+
+const MAX_HITS = 10;
+
+interface SearchResultClickHandler {
+  event: React.MouseEvent<HTMLAnchorElement>;
+  hit: Hit;
+  position: number;
+}
+
+export function SearchResultItems({
+  results,
+  showOffsiteResults,
+  onSearchResultClick,
+}: {
+  onSearchResultClick: (params: SearchResultClickHandler) => void;
+  results: Result[];
+  showOffsiteResults: boolean;
+}) {
+  const router = useRouter();
+  const flatHits = results.reduce<Hit[]>(
+    (items, item) => [...items, ...item.hits.slice(0, MAX_HITS)],
+    []
+  );
+  const {focused} = useListKeyboardNavigate({
+    list: flatHits,
+    onSelect: hit => router.push(relativizeUrl(hit.url)),
+  });
+
+  return (
+    <div className={styles['sgs-search-results-scroll-container']}>
+      {results
+        .filter(x => x.hits.length > 0)
+        .map((result, i) => (
+          <Fragment key={result.site}>
+            {showOffsiteResults && (
+              <h4 className={styles['sgs-site-result-heading']}>From {result.name}</h4>
+            )}
+            <ul
+              className={`${styles['sgs-hit-list']} ${i === 0 ? '' : styles['sgs-offsite']}`}
+            >
+              {result.hits.slice(0, MAX_HITS).map((hit, index) => (
+                <li
+                  key={hit.id}
+                  className={`${styles['sgs-hit-item']} ${
+                    focused?.id === hit.id ? styles['sgs-hit-focused'] : ''
+                  }`}
+                  ref={
+                    // Scroll to element on focus
+                    hit.id === focused?.id
+                      ? el => el?.scrollIntoView({block: 'nearest'})
+                      : undefined
+                  }
+                >
+                  <Link
+                    href={relativizeUrl(hit.url)}
+                    onClick={event => onSearchResultClick({event, hit, position: index})}
+                  >
+                    {hit.title && (
+                      <h6>
+                        <span
+                          dangerouslySetInnerHTML={{
+                            __html: DOMPurify.sanitize(hit.title, {
+                              ALLOWED_TAGS: ['mark'],
+                            }),
+                          }}
+                        />
+                      </h6>
+                    )}
+                    {hit.text && (
+                      <span
+                        dangerouslySetInnerHTML={{
+                          __html: DOMPurify.sanitize(hit.text, {
+                            ALLOWED_TAGS: ['mark'],
+                          }),
+                        }}
+                      />
+                    )}
+                    {hit.context && (
+                      <div className={styles['sgs-hit-context']}>
+                        {hit.context.context1 && (
+                          <div className={styles['sgs-hit-context-left']}>
+                            {hit.context.context1}
+                          </div>
+                        )}
+                        {hit.context.context2 && (
+                          <div className={styles['sgs-hit-context-right']}>
+                            {hit.context.context2}
+                          </div>
+                        )}
+                      </div>
+                    )}
+                  </Link>
+                </li>
+              ))}
+            </ul>
+          </Fragment>
+        ))}
+    </div>
+  );
+}
diff --git a/src/components/search/util.ts b/src/components/search/util.ts
new file mode 100644
index 00000000000000..f5191b930da18f
--- /dev/null
+++ b/src/components/search/util.ts
@@ -0,0 +1,7 @@
+import {isDeveloperDocs} from 'sentry-docs/isDeveloperDocs';
+
+export function relativizeUrl(url: string) {
+  return isDeveloperDocs
+    ? url
+    : url.replace(/^(https?:\/\/docs\.sentry\.io)(?=\/|$)/, '');
+}
diff --git a/src/components/signInNote.tsx b/src/components/signInNote.tsx
index f43644fde438bc..16d6dab2eee382 100644
--- a/src/components/signInNote.tsx
+++ b/src/components/signInNote.tsx
@@ -3,7 +3,7 @@
 import Link from 'next/link';
 import {usePathname} from 'next/navigation';
 
-import {Note} from './alert';
+import {Alert} from './alert';
 import {SignedInCheck} from './signedInCheck';
 
 export function SignInNote() {
@@ -13,11 +13,11 @@ export function SignInNote() {
 
   return (
     <SignedInCheck isUserAuthenticated={false}>
-      <Note>
+      <Alert>
         The following code sample will let you choose your personal config from the
         dropdown, once you're{' '}
         <Link href={`https://sentry.io/auth/login/?next=${url}`}>logged in</Link>.
-      </Note>
+      </Alert>
     </SignedInCheck>
   );
 }
diff --git a/src/data/relay_metrics.json b/src/data/relay_metrics.json
index a5eb6bf2957726..0beffd21d4f5c4 100644
--- a/src/data/relay_metrics.json
+++ b/src/data/relay_metrics.json
@@ -835,6 +835,12 @@
     "description": "Time spent on minidump scrubbing.\n\nThis is the total time spent on parsing and scrubbing the minidump.  Even if no PII\nscrubbing rules applied the minidump will still be parsed and the rules evaluated on\nthe parsed minidump, this duration is reported here with status of \"n/a\".\n\nThis metric is tagged with:\n\n- `status`: Scrubbing status: \"ok\" means successful scrubbed, \"error\" means there\nwas an error during scrubbing and finally \"n/a\" means scrubbing was successful\nbut no scurbbing rules applied.",
     "features": []
   },
+  {
+    "type": "Timer",
+    "name": "scrubbing.view_hierarchy_scrubbing.duration",
+    "description": "Time spent on view hierarchy scrubbing.\n\nThis is the total time spent on parsing and scrubbing the view hierarchy json file.\n\nThis metric is tagged with:\n\n- `status`: \"ok\" means successful scrubbed, \"error\" means there was an error during\nscrubbing",
+    "features": []
+  },
   {
     "type": "Counter",
     "name": "server.http.accepted",
diff --git a/src/hooks/useKeyboardNavigate.tsx b/src/hooks/useListKeyboardNavigate.tsx
similarity index 95%
rename from src/hooks/useKeyboardNavigate.tsx
rename to src/hooks/useListKeyboardNavigate.tsx
index ffe6bf0b41bde8..9a841146c4d11d 100644
--- a/src/hooks/useKeyboardNavigate.tsx
+++ b/src/hooks/useListKeyboardNavigate.tsx
@@ -5,6 +5,7 @@ type Props<T> = {
    * The list of values to navigate through
    */
   list: T[];
+
   /**
    * Callback triggered when the item is selected
    */
@@ -14,7 +15,7 @@ type Props<T> = {
 /**
  * Navigate a list of items using the up/down arrow and ^j/^k keys
  */
-function useKeyboardNavigate<T>({list, onSelect}: Props<T>) {
+function useListKeyboardNavigate<T>({list, onSelect}: Props<T>) {
   const [focused, setFocus] = useState<T | null>(null);
 
   const setFocusIndex = useCallback(
@@ -92,4 +93,4 @@ function useKeyboardNavigate<T>({list, onSelect}: Props<T>) {
   return {focused, setFocus};
 }
 
-export {useKeyboardNavigate};
+export {useListKeyboardNavigate};
diff --git a/src/hooks/usePlausibleEvent.tsx b/src/hooks/usePlausibleEvent.tsx
index 071eeb5fdf6ca2..8124e464908541 100644
--- a/src/hooks/usePlausibleEvent.tsx
+++ b/src/hooks/usePlausibleEvent.tsx
@@ -4,6 +4,10 @@ import {ReadProgressMilestone} from 'sentry-docs/types/plausible';
 
 // Adding custom events here will make them available via the hook
 type PlausibleEventProps = {
+  ['Doc Feedback']: {
+    helpful: boolean;
+    page: string;
+  };
   ['Read Progress']: {
     page: string;
     readProgress: ReadProgressMilestone;
diff --git a/src/instrumentation.ts b/src/instrumentation.ts
index be7ccace1b861d..7d1940f413051e 100644
--- a/src/instrumentation.ts
+++ b/src/instrumentation.ts
@@ -21,3 +21,5 @@ export function register() {
     });
   }
 }
+
+export const onRequestError = Sentry.captureRequestError;
diff --git a/src/mdxComponents.ts b/src/mdxComponents.ts
index 459d16a9648a05..f22c2e0214382c 100644
--- a/src/mdxComponents.ts
+++ b/src/mdxComponents.ts
@@ -1,4 +1,4 @@
-import {Alert, Note} from './components/alert';
+import {Alert} from './components/alert';
 import {Arcade} from './components/arcade';
 import {Break} from './components/break';
 import {CliChecksumTable} from './components/cliChecksumTable';
@@ -58,7 +58,6 @@ export function mdxComponents(
     LambdaLayerDetail,
     Link: SmartLink,
     LinkWithPlatformIcon,
-    Note,
     OrgAuthTokenNote,
     PageGrid,
     ParamTable,
diff --git a/vercel.json b/vercel.json
index c2ea1d0de44db9..877b7b53d8ae11 100644
--- a/vercel.json
+++ b/vercel.json
@@ -17,7 +17,7 @@
         },
         {
           "key": "Content-Security-Policy",
-          "value": "upgrade-insecure-requests; default-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval' *.sentry-cdn.com www.googletagmanager.com plausible.io widget.kapa.ai www.gstatic.com www.google.com vercel.live; connect-src 'self' *.sentry.io sentry.io *.algolia.net *.algolianet.com *.algolia.io kapa-widget-proxy-la7dkmplpq-uc.a.run.app plausible.io reload.getsentry.net storage.googleapis.com; img-src * 'self' data: www.google.com www.googletagmanager.com; style-src 'self' 'unsafe-inline'; font-src 'self' fonts.gstatic.com; frame-src www.google.com recaptcha.google.com demo.arcade.software player.vimeo.com; worker-src blob:; report-uri https://o1.ingest.sentry.io/api/1267915/security/?sentry_key=ad63ba38287245f2803dc220be959636; report-to csp"
+          "value": "upgrade-insecure-requests; default-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval' *.sentry-cdn.com www.googletagmanager.com plausible.io widget.kapa.ai www.gstatic.com www.google.com vercel.live; connect-src 'self' *.sentry.io sentry.io *.algolia.net *.algolianet.com *.algolia.io kapa-widget-proxy-la7dkmplpq-uc.a.run.app plausible.io reload.getsentry.net storage.googleapis.com; img-src * 'self' data: www.google.com www.googletagmanager.com; style-src 'self' 'unsafe-inline'; font-src 'self' fonts.gstatic.com; frame-src www.google.com recaptcha.google.com demo.arcade.software player.vimeo.com; worker-src blob:; report-uri https://o1.ingest.sentry.io/api/1297620/security/?sentry_key=b3cfba5788cb4c138f855c8120f70eab; report-to csp"
         },
         {
           "key": "NEL",
@@ -25,7 +25,7 @@
         },
         {
           "key": "Report-To",
-          "value": "{\"group\":\"nel\",\"max_age\":3600,\"endpoints\":[{\"url\":\"https://o1.ingest.sentry.io/api/1267915/nel/?sentry_key=ad63ba38287245f2803dc220be959636\"}]},{\"group\":\"csp\",\"max_age\":3600,\"endpoints\":[{\"url\":\"https://o1.ingest.sentry.io/api/1267915/security/?sentry_key=ad63ba38287245f2803dc220be959636\"}]}"
+          "value": "{\"group\":\"nel\",\"max_age\":3600,\"endpoints\":[{\"url\":\"https://o1.ingest.sentry.io/api/4507503193292800/nel/?sentry_key=ade2f3d18e4f49c513b0a8644927d27b\"}]},{\"group\":\"csp\",\"max_age\":3600,\"endpoints\":[{\"url\":\"https://o1.ingest.sentry.io/api/1297620/security/?sentry_key=b3cfba5788cb4c138f855c8120f70eab\"}]}"
         }
       ]
     }
diff --git a/yarn.lock b/yarn.lock
index 51cf93f6fd0e94..c74d2435ea0d96 100644
--- a/yarn.lock
+++ b/yarn.lock
@@ -624,33 +624,34 @@
   resolved "https://registry.yarnpkg.com/@chevrotain/utils/-/utils-11.0.3.tgz#e39999307b102cff3645ec4f5b3665f5297a2224"
   integrity sha512-YslZMgtJUyuMbZ+aKvfF3x1f5liK4mWNxghFRv7jqRR9C3R3fAOGTTKvxXDa2Y1s9zSbcpuO0cAxDYsc9SrXoQ==
 
-"@codecov/bundler-plugin-core@^1.4.0":
-  version "1.4.0"
-  resolved "https://registry.yarnpkg.com/@codecov/bundler-plugin-core/-/bundler-plugin-core-1.4.0.tgz#6035d8fe2a321b125c883ab77b9e6c36c9c08abd"
-  integrity sha512-/Rglx52KLdyqoZBW3DH2E/31c9/zWWZ4efTf+qxV0FSLb7oJ9/JZT3IBKL7f6fbVujR8PDMLIoG4Q0pmVY7LzA==
+"@codecov/bundler-plugin-core@^1.8.0":
+  version "1.8.0"
+  resolved "https://registry.yarnpkg.com/@codecov/bundler-plugin-core/-/bundler-plugin-core-1.8.0.tgz#662369cc13efecc860759dcbdf90636cb665b21e"
+  integrity sha512-D1aeA8u3RHOkQVLImLHxW6zFdUrw5wgoeDzYrKZeDExGp5ePs4RpJxKwklg1N0e1JxRcAgKj+zZo/y3Q4nV+sA==
   dependencies:
     "@actions/core" "^1.10.1"
     "@actions/github" "^6.0.0"
+    "@sentry/core" "^8.42.0"
     chalk "4.1.2"
     semver "^7.5.4"
     unplugin "^1.10.1"
     zod "^3.22.4"
 
-"@codecov/nextjs-webpack-plugin@^1.0.0":
-  version "1.4.0"
-  resolved "https://registry.yarnpkg.com/@codecov/nextjs-webpack-plugin/-/nextjs-webpack-plugin-1.4.0.tgz#fa266ae311668d7d9afbb22b0c25b757e15c6af1"
-  integrity sha512-zRvXgpQTwaRqUX/28Z9QHzXAoheCQELe3C7J85ZzmTLoiCPNMmj1IS3YqMzQ6y3mv4myAqbWqOBssjFzuQ2LuA==
+"@codecov/nextjs-webpack-plugin@^1.8.0":
+  version "1.8.0"
+  resolved "https://registry.yarnpkg.com/@codecov/nextjs-webpack-plugin/-/nextjs-webpack-plugin-1.8.0.tgz#22fe73ea887d7fb3696e13bce610fdf5dded40d1"
+  integrity sha512-EjsY8AyBKzpMeKbd74/S8zi3dav/7QhPWCWrJBgnyV1tFYRlq3sE2dyKghgASJe7SVAbvK2suiX72SwvFIieUQ==
   dependencies:
-    "@codecov/bundler-plugin-core" "^1.4.0"
-    "@codecov/webpack-plugin" "^1.4.0"
+    "@codecov/bundler-plugin-core" "^1.8.0"
+    "@codecov/webpack-plugin" "^1.8.0"
     unplugin "^1.10.1"
 
-"@codecov/webpack-plugin@^1.4.0":
-  version "1.4.0"
-  resolved "https://registry.yarnpkg.com/@codecov/webpack-plugin/-/webpack-plugin-1.4.0.tgz#2e60d9c13ba2e8c08784265f93f8eb509ed0bc14"
-  integrity sha512-2mkaa7W5zyn1vcJIe2JIRIJ+VMjJH5r8HgdhdY274WhsT5sJdgnCtStFvFZBH/ysRFbU0OybMdDpF/75POQXFg==
+"@codecov/webpack-plugin@^1.8.0":
+  version "1.8.0"
+  resolved "https://registry.yarnpkg.com/@codecov/webpack-plugin/-/webpack-plugin-1.8.0.tgz#21430775530cde139c22a55318dccbfda3c0eb32"
+  integrity sha512-G62kbpAFuutQIrbuw97MAf5vkgIKXf64Nj0pRe6OPbC5Aps0nWrEL9v0Sr0WPdHcbQnr3i6noIXyUDdV1lUZ5g==
   dependencies:
-    "@codecov/bundler-plugin-core" "^1.4.0"
+    "@codecov/bundler-plugin-core" "^1.8.0"
     unplugin "^1.10.1"
 
 "@cspotcode/source-map-support@^0.8.0":
@@ -1820,13 +1821,6 @@
   dependencies:
     "@octokit/openapi-types" "^22.2.0"
 
-"@opentelemetry/api-logs@0.52.1":
-  version "0.52.1"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/api-logs/-/api-logs-0.52.1.tgz#52906375da4d64c206b0c4cb8ffa209214654ecc"
-  integrity sha512-qnSqB2DQ9TPP96dl8cDubDvrUyWc0/sK81xHTK8eSUspzDM3bsewX903qclQFvVhgStjRWdC5bLb3kQqMkfV5A==
-  dependencies:
-    "@opentelemetry/api" "^1.0.0"
-
 "@opentelemetry/api-logs@0.53.0":
   version "0.53.0"
   resolved "https://registry.yarnpkg.com/@opentelemetry/api-logs/-/api-logs-0.53.0.tgz#c478cbd8120ec2547b64edfa03a552cfe42170be"
@@ -1834,10 +1828,17 @@
   dependencies:
     "@opentelemetry/api" "^1.0.0"
 
-"@opentelemetry/api-logs@0.54.2":
-  version "0.54.2"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/api-logs/-/api-logs-0.54.2.tgz#bb8aa11cdc69b327b58d7e10cc2bc26bf540421f"
-  integrity sha512-4MTVwwmLgUh5QrJnZpYo6YRO5IBLAggf2h8gWDblwRagDStY13aEvt7gGk3jewrMaPlHiF83fENhIx0HO97/cQ==
+"@opentelemetry/api-logs@0.56.0":
+  version "0.56.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/api-logs/-/api-logs-0.56.0.tgz#68f8c51ca905c260b610c8a3c67d3f9fa3d59a45"
+  integrity sha512-Wr39+94UNNG3Ei9nv3pHd4AJ63gq5nSemMRpCd8fPwDL9rN3vK26lzxfH27mw16XzOSO+TpyQwBAMaLxaPWG0g==
+  dependencies:
+    "@opentelemetry/api" "^1.3.0"
+
+"@opentelemetry/api-logs@0.57.1":
+  version "0.57.1"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/api-logs/-/api-logs-0.57.1.tgz#97ebd714f0b1fcdf896e85c465ae5c5b22747425"
+  integrity sha512-I4PHczeujhQAQv6ZBzqHYEUiggZL4IdSMixtVD3EYqbdrjujE7kRfI5QohjlPoJm8BvenoW5YaTMWRrbpot6tg==
   dependencies:
     "@opentelemetry/api" "^1.3.0"
 
@@ -1846,245 +1847,255 @@
   resolved "https://registry.yarnpkg.com/@opentelemetry/api/-/api-1.9.0.tgz#d03eba68273dc0f7509e2a3d5cba21eae10379fe"
   integrity sha512-3giAOQvZiH5F9bMlMiv8+GSPMeqg0dbaeo58/0SlA9sxSqZhnUtxzX9/2FzyhS9sWQf5S0GJE0AKBrFqjpeYcg==
 
-"@opentelemetry/context-async-hooks@^1.25.1":
-  version "1.28.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/context-async-hooks/-/context-async-hooks-1.28.0.tgz#287afda2b75cb226f70d433244c3ef6f6dd8abdd"
-  integrity sha512-igcl4Ve+F1N2063PJUkesk/GkYyuGIWinYkSyAFTnIj3gzrOgvOA4k747XNdL47HRRL1w/qh7UW8NDuxOLvKFA==
+"@opentelemetry/context-async-hooks@^1.30.1":
+  version "1.30.1"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/context-async-hooks/-/context-async-hooks-1.30.1.tgz#4f76280691a742597fd0bf682982126857622948"
+  integrity sha512-s5vvxXPVdjqS3kTLKMeBMvop9hbWkwzBpu+mUO2M7sZtlkyDJGwFe33wRKnbaYDo8ExRVBIIdwIGrqpxHuKttA==
 
-"@opentelemetry/core@1.26.0":
-  version "1.26.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/core/-/core-1.26.0.tgz#7d84265aaa850ed0ca5813f97d831155be42b328"
-  integrity sha512-1iKxXXE8415Cdv0yjG3G6hQnB5eVEsJce3QaawX8SjDn0mAS0ZM8fAbZZJD4ajvhC15cePvosSCut404KrIIvQ==
+"@opentelemetry/core@1.30.1", "@opentelemetry/core@^1.26.0", "@opentelemetry/core@^1.30.1":
+  version "1.30.1"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/core/-/core-1.30.1.tgz#a0b468bb396358df801881709ea38299fc30ab27"
+  integrity sha512-OOCM2C/QIURhJMuKaekP3TRBxBKxG/TWWA0TL2J6nXUtDnuCtccy49LUJF8xPFXMX+0LMcxFpCo8M9cGY1W6rQ==
   dependencies:
-    "@opentelemetry/semantic-conventions" "1.27.0"
+    "@opentelemetry/semantic-conventions" "1.28.0"
 
-"@opentelemetry/core@1.28.0", "@opentelemetry/core@^1.1.0", "@opentelemetry/core@^1.25.1", "@opentelemetry/core@^1.8.0":
+"@opentelemetry/core@^1.1.0", "@opentelemetry/core@^1.8.0":
   version "1.28.0"
   resolved "https://registry.yarnpkg.com/@opentelemetry/core/-/core-1.28.0.tgz#e97290a3e36c59480ffb2287fe2713c66749274c"
   integrity sha512-ZLwRMV+fNDpVmF2WYUdBHlq0eOWtEaUJSusrzjGnBt7iSRvfjFE3RXYUZJrqou/wIDWV0DwQ5KIfYe9WXg9Xqw==
   dependencies:
     "@opentelemetry/semantic-conventions" "1.27.0"
 
-"@opentelemetry/instrumentation-amqplib@^0.42.0":
-  version "0.42.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-amqplib/-/instrumentation-amqplib-0.42.0.tgz#b3cab5a7207736a30d769962eed3af3838f986c4"
-  integrity sha512-fiuU6OKsqHJiydHWgTRQ7MnIrJ2lEqsdgFtNIH4LbAUJl/5XmrIeoDzDnox+hfkgWK65jsleFuQDtYb5hW1koQ==
+"@opentelemetry/instrumentation-amqplib@^0.46.0":
+  version "0.46.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-amqplib/-/instrumentation-amqplib-0.46.0.tgz#8b0c61213034780a79c16216c62eee0ce1457ddf"
+  integrity sha512-04VHHV1KIN/c1wLWwzmLI02d/welgscBJ4BuDqrHaxd+ZIdlVXK9UYQsYf3JwSeF52z/4YoSzr8bfdVBSWoMAg==
   dependencies:
     "@opentelemetry/core" "^1.8.0"
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/semantic-conventions" "^1.27.0"
 
-"@opentelemetry/instrumentation-connect@0.40.0":
-  version "0.40.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-connect/-/instrumentation-connect-0.40.0.tgz#cb151b860ad8a711ebce4d7e025dcde95e4ba2c5"
-  integrity sha512-3aR/3YBQ160siitwwRLjwqrv2KBT16897+bo6yz8wIfel6nWOxTZBJudcbsK3p42pTC7qrbotJ9t/1wRLpv79Q==
+"@opentelemetry/instrumentation-connect@0.43.0":
+  version "0.43.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-connect/-/instrumentation-connect-0.43.0.tgz#411035f4a8f2e498dbfa7300e545c58586a062e2"
+  integrity sha512-Q57JGpH6T4dkYHo9tKXONgLtxzsh1ZEW5M9A/OwKrZFyEpLqWgjhcZ3hIuVvDlhb426iDF1f9FPToV/mi5rpeA==
   dependencies:
     "@opentelemetry/core" "^1.8.0"
-    "@opentelemetry/instrumentation" "^0.54.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/semantic-conventions" "^1.27.0"
     "@types/connect" "3.4.36"
 
-"@opentelemetry/instrumentation-dataloader@0.12.0":
-  version "0.12.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-dataloader/-/instrumentation-dataloader-0.12.0.tgz#de03a3948dec4f15fed80aa424d6bd5d6a8d10c7"
-  integrity sha512-pnPxatoFE0OXIZDQhL2okF//dmbiWFzcSc8pUg9TqofCLYZySSxDCgQc69CJBo5JnI3Gz1KP+mOjS4WAeRIH4g==
+"@opentelemetry/instrumentation-dataloader@0.16.0":
+  version "0.16.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-dataloader/-/instrumentation-dataloader-0.16.0.tgz#913345c335f67bf8e17a9b38c227dba741fe488b"
+  integrity sha512-88+qCHZC02up8PwKHk0UQKLLqGGURzS3hFQBZC7PnGwReuoKjHXS1o29H58S+QkXJpkTr2GACbx8j6mUoGjNPA==
   dependencies:
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
 
-"@opentelemetry/instrumentation-express@0.44.0":
-  version "0.44.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-express/-/instrumentation-express-0.44.0.tgz#51dc11e3152ffbee1c4e389298aac30231c8270a"
-  integrity sha512-GWgibp6Q0wxyFaaU8ERIgMMYgzcHmGrw3ILUtGchLtLncHNOKk0SNoWGqiylXWWT4HTn5XdV8MGawUgpZh80cA==
+"@opentelemetry/instrumentation-express@0.47.0":
+  version "0.47.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-express/-/instrumentation-express-0.47.0.tgz#f0477db3b1f4b342beb9ecd08edc26c470566724"
+  integrity sha512-XFWVx6k0XlU8lu6cBlCa29ONtVt6ADEjmxtyAyeF2+rifk8uBJbk1La0yIVfI0DoKURGbaEDTNelaXG9l/lNNQ==
   dependencies:
     "@opentelemetry/core" "^1.8.0"
-    "@opentelemetry/instrumentation" "^0.54.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/semantic-conventions" "^1.27.0"
 
-"@opentelemetry/instrumentation-fastify@0.40.0":
-  version "0.40.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-fastify/-/instrumentation-fastify-0.40.0.tgz#0c57608ac202337d56b53338f1fc9369d224306b"
-  integrity sha512-74qj4nG3zPtU7g2x4sm2T4R3/pBMyrYstTsqSZwdlhQk1SD4l8OSY9sPRX1qkhfxOuW3U4KZQAV/Cymb3fB6hg==
+"@opentelemetry/instrumentation-fastify@0.44.1":
+  version "0.44.1"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-fastify/-/instrumentation-fastify-0.44.1.tgz#c8080f24a6fbdd14689c619ad7b14fe189b10f28"
+  integrity sha512-RoVeMGKcNttNfXMSl6W4fsYoCAYP1vi6ZAWIGhBY+o7R9Y0afA7f9JJL0j8LHbyb0P0QhSYk+6O56OwI2k4iRQ==
   dependencies:
     "@opentelemetry/core" "^1.8.0"
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/semantic-conventions" "^1.27.0"
 
-"@opentelemetry/instrumentation-fs@0.16.0":
-  version "0.16.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-fs/-/instrumentation-fs-0.16.0.tgz#aa1cc3aa81011ad9843a0156b200f06f31ffa03e"
-  integrity sha512-hMDRUxV38ln1R3lNz6osj3YjlO32ykbHqVrzG7gEhGXFQfu7LJUx8t9tEwE4r2h3CD4D0Rw4YGDU4yF4mP3ilg==
+"@opentelemetry/instrumentation-fs@0.19.0":
+  version "0.19.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-fs/-/instrumentation-fs-0.19.0.tgz#a44807aea97edc64c597d6a5b5b8637b7ab45057"
+  integrity sha512-JGwmHhBkRT2G/BYNV1aGI+bBjJu4fJUD/5/Jat0EWZa2ftrLV3YE8z84Fiij/wK32oMZ88eS8DI4ecLGZhpqsQ==
   dependencies:
     "@opentelemetry/core" "^1.8.0"
-    "@opentelemetry/instrumentation" "^0.54.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
 
-"@opentelemetry/instrumentation-generic-pool@0.39.0":
-  version "0.39.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-generic-pool/-/instrumentation-generic-pool-0.39.0.tgz#2b9af16ad82d5cbe67125c0125753cecd162a728"
-  integrity sha512-y4v8Y+tSfRB3NNBvHjbjrn7rX/7sdARG7FuK6zR8PGb28CTa0kHpEGCJqvL9L8xkTNvTXo+lM36ajFGUaK1aNw==
+"@opentelemetry/instrumentation-generic-pool@0.43.0":
+  version "0.43.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-generic-pool/-/instrumentation-generic-pool-0.43.0.tgz#b1769eb0e30f2abb764a9cbc811aa3d4560ecc24"
+  integrity sha512-at8GceTtNxD1NfFKGAuwtqM41ot/TpcLh+YsGe4dhf7gvv1HW/ZWdq6nfRtS6UjIvZJOokViqLPJ3GVtZItAnQ==
   dependencies:
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
 
-"@opentelemetry/instrumentation-graphql@0.43.0":
-  version "0.43.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-graphql/-/instrumentation-graphql-0.43.0.tgz#71bb94ea775c70dbd388c739b397ec1418f3f170"
-  integrity sha512-aI3YMmC2McGd8KW5du1a2gBA0iOMOGLqg4s9YjzwbjFwjlmMNFSK1P3AIg374GWg823RPUGfVTIgZ/juk9CVOA==
+"@opentelemetry/instrumentation-graphql@0.47.0":
+  version "0.47.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-graphql/-/instrumentation-graphql-0.47.0.tgz#271807e21a6224bd1986a3e9887650f1858ee733"
+  integrity sha512-Cc8SMf+nLqp0fi8oAnooNEfwZWFnzMiBHCGmDFYqmgjPylyLmi83b+NiTns/rKGwlErpW0AGPt0sMpkbNlzn8w==
   dependencies:
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
 
-"@opentelemetry/instrumentation-hapi@0.41.0":
-  version "0.41.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-hapi/-/instrumentation-hapi-0.41.0.tgz#de8711907256d8fae1b5faf71fc825cef4a7ddbb"
-  integrity sha512-jKDrxPNXDByPlYcMdZjNPYCvw0SQJjN+B1A+QH+sx+sAHsKSAf9hwFiJSrI6C4XdOls43V/f/fkp9ITkHhKFbQ==
+"@opentelemetry/instrumentation-hapi@0.45.1":
+  version "0.45.1"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-hapi/-/instrumentation-hapi-0.45.1.tgz#5edf982549070d95e20152d568279548ad44d662"
+  integrity sha512-VH6mU3YqAKTePPfUPwfq4/xr049774qWtfTuJqVHoVspCLiT3bW+fCQ1toZxt6cxRPYASoYaBsMA3CWo8B8rcw==
   dependencies:
     "@opentelemetry/core" "^1.8.0"
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/semantic-conventions" "^1.27.0"
 
-"@opentelemetry/instrumentation-http@0.53.0":
-  version "0.53.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-http/-/instrumentation-http-0.53.0.tgz#0d806adf1b3aba036bc46e16162e3c0dbb8a6b60"
-  integrity sha512-H74ErMeDuZfj7KgYCTOFGWF5W9AfaPnqLQQxeFq85+D29wwV2yqHbz2IKLYpkOh7EI6QwDEl7rZCIxjJLyc/CQ==
+"@opentelemetry/instrumentation-http@0.57.1":
+  version "0.57.1"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-http/-/instrumentation-http-0.57.1.tgz#2d8b395df62191475e76fa0eb7bf60079ea886b9"
+  integrity sha512-ThLmzAQDs7b/tdKI3BV2+yawuF09jF111OFsovqT1Qj3D8vjwKBwhi/rDE5xethwn4tSXtZcJ9hBsVAlWFQZ7g==
   dependencies:
-    "@opentelemetry/core" "1.26.0"
-    "@opentelemetry/instrumentation" "0.53.0"
-    "@opentelemetry/semantic-conventions" "1.27.0"
+    "@opentelemetry/core" "1.30.1"
+    "@opentelemetry/instrumentation" "0.57.1"
+    "@opentelemetry/semantic-conventions" "1.28.0"
+    forwarded-parse "2.1.2"
     semver "^7.5.2"
 
-"@opentelemetry/instrumentation-ioredis@0.43.0":
-  version "0.43.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-ioredis/-/instrumentation-ioredis-0.43.0.tgz#dbadabaeefc4cb47c406f878444f1bcac774fa89"
-  integrity sha512-i3Dke/LdhZbiUAEImmRG3i7Dimm/BD7t8pDDzwepSvIQ6s2X6FPia7561gw+64w+nx0+G9X14D7rEfaMEmmjig==
+"@opentelemetry/instrumentation-ioredis@0.47.0":
+  version "0.47.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-ioredis/-/instrumentation-ioredis-0.47.0.tgz#f83bd133d36d137d2d0b58bfbdfe12ed6fe5ab2f"
+  integrity sha512-4HqP9IBC8e7pW9p90P3q4ox0XlbLGme65YTrA3UTLvqvo4Z6b0puqZQP203YFu8m9rE/luLfaG7/xrwwqMUpJw==
   dependencies:
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/redis-common" "^0.36.2"
     "@opentelemetry/semantic-conventions" "^1.27.0"
 
-"@opentelemetry/instrumentation-kafkajs@0.4.0":
-  version "0.4.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-kafkajs/-/instrumentation-kafkajs-0.4.0.tgz#c1fe0de45a65a66581be0d7422f6828cc806b3bb"
-  integrity sha512-I9VwDG314g7SDL4t8kD/7+1ytaDBRbZQjhVaQaVIDR8K+mlsoBhLsWH79yHxhHQKvwCSZwqXF+TiTOhoQVUt7A==
+"@opentelemetry/instrumentation-kafkajs@0.7.0":
+  version "0.7.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-kafkajs/-/instrumentation-kafkajs-0.7.0.tgz#079b949ec814b42e49d23bb4d4f73735fe460d52"
+  integrity sha512-LB+3xiNzc034zHfCtgs4ITWhq6Xvdo8bsq7amR058jZlf2aXXDrN9SV4si4z2ya9QX4tz6r4eZJwDkXOp14/AQ==
   dependencies:
-    "@opentelemetry/instrumentation" "^0.54.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/semantic-conventions" "^1.27.0"
 
-"@opentelemetry/instrumentation-koa@0.43.0":
-  version "0.43.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-koa/-/instrumentation-koa-0.43.0.tgz#963fd192a1b5f6cbae5dabf4ec82e3105cbb23b1"
-  integrity sha512-lDAhSnmoTIN6ELKmLJBplXzT/Jqs5jGZehuG22EdSMaTwgjMpxMDI1YtlKEhiWPWkrz5LUsd0aOO0ZRc9vn3AQ==
+"@opentelemetry/instrumentation-knex@0.44.0":
+  version "0.44.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-knex/-/instrumentation-knex-0.44.0.tgz#af251ed38f06a2f248812c5addf0266697b6149a"
+  integrity sha512-SlT0+bLA0Lg3VthGje+bSZatlGHw/vwgQywx0R/5u9QC59FddTQSPJeWNw29M6f8ScORMeUOOTwihlQAn4GkJQ==
+  dependencies:
+    "@opentelemetry/instrumentation" "^0.57.0"
+    "@opentelemetry/semantic-conventions" "^1.27.0"
+
+"@opentelemetry/instrumentation-koa@0.47.0":
+  version "0.47.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-koa/-/instrumentation-koa-0.47.0.tgz#a74b35809ba95d0f9db49e8c3f214bde475b095a"
+  integrity sha512-HFdvqf2+w8sWOuwtEXayGzdZ2vWpCKEQv5F7+2DSA74Te/Cv4rvb2E5So5/lh+ok4/RAIPuvCbCb/SHQFzMmbw==
   dependencies:
     "@opentelemetry/core" "^1.8.0"
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/semantic-conventions" "^1.27.0"
 
-"@opentelemetry/instrumentation-lru-memoizer@0.40.0":
-  version "0.40.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-lru-memoizer/-/instrumentation-lru-memoizer-0.40.0.tgz#dc60d7fdfd2a0c681cb23e7ed4f314d1506ccdc0"
-  integrity sha512-21xRwZsEdMPnROu/QsaOIODmzw59IYpGFmuC4aFWvMj6stA8+Ei1tX67nkarJttlNjoM94um0N4X26AD7ff54A==
+"@opentelemetry/instrumentation-lru-memoizer@0.44.0":
+  version "0.44.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-lru-memoizer/-/instrumentation-lru-memoizer-0.44.0.tgz#c22e770d950c165f80c657a9c790c9843baaa65b"
+  integrity sha512-Tn7emHAlvYDFik3vGU0mdwvWJDwtITtkJ+5eT2cUquct6nIs+H8M47sqMJkCpyPe5QIBJoTOHxmc6mj9lz6zDw==
   dependencies:
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
 
-"@opentelemetry/instrumentation-mongodb@0.47.0":
-  version "0.47.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-mongodb/-/instrumentation-mongodb-0.47.0.tgz#f8107d878281433905e717f223fb4c0f10356a7b"
-  integrity sha512-yqyXRx2SulEURjgOQyJzhCECSh5i1uM49NUaq9TqLd6fA7g26OahyJfsr9NE38HFqGRHpi4loyrnfYGdrsoVjQ==
+"@opentelemetry/instrumentation-mongodb@0.51.0":
+  version "0.51.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-mongodb/-/instrumentation-mongodb-0.51.0.tgz#8a323c2fb4cb2c93bf95f1b1c0fcb30952d12a08"
+  integrity sha512-cMKASxCX4aFxesoj3WK8uoQ0YUrRvnfxaO72QWI2xLu5ZtgX/QvdGBlU3Ehdond5eb74c2s1cqRQUIptBnKz1g==
   dependencies:
-    "@opentelemetry/instrumentation" "^0.53.0"
-    "@opentelemetry/sdk-metrics" "^1.9.1"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/semantic-conventions" "^1.27.0"
 
-"@opentelemetry/instrumentation-mongoose@0.42.0":
-  version "0.42.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-mongoose/-/instrumentation-mongoose-0.42.0.tgz#375afd21adfcd897a8f521c1ffd2d91e6a428705"
-  integrity sha512-AnWv+RaR86uG3qNEMwt3plKX1ueRM7AspfszJYVkvkehiicC3bHQA6vWdb6Zvy5HAE14RyFbu9+2hUUjR2NSyg==
+"@opentelemetry/instrumentation-mongoose@0.46.0":
+  version "0.46.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-mongoose/-/instrumentation-mongoose-0.46.0.tgz#c3a5f69e1a5b950b542cf84650fbbd3e31bd681e"
+  integrity sha512-mtVv6UeaaSaWTeZtLo4cx4P5/ING2obSqfWGItIFSunQBrYROfhuVe7wdIrFUs2RH1tn2YYpAJyMaRe/bnTTIQ==
   dependencies:
     "@opentelemetry/core" "^1.8.0"
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/semantic-conventions" "^1.27.0"
 
-"@opentelemetry/instrumentation-mysql2@0.41.0":
-  version "0.41.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-mysql2/-/instrumentation-mysql2-0.41.0.tgz#6377b6e2d2487fd88e1d79aa03658db6c8d51651"
-  integrity sha512-REQB0x+IzVTpoNgVmy5b+UnH1/mDByrneimP6sbDHkp1j8QOl1HyWOrBH/6YWR0nrbU3l825Em5PlybjT3232g==
+"@opentelemetry/instrumentation-mysql2@0.45.0":
+  version "0.45.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-mysql2/-/instrumentation-mysql2-0.45.0.tgz#95501759d470dbc7038670e91205e8ed601ec402"
+  integrity sha512-qLslv/EPuLj0IXFvcE3b0EqhWI8LKmrgRPIa4gUd8DllbBpqJAvLNJSv3cC6vWwovpbSI3bagNO/3Q2SuXv2xA==
   dependencies:
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/semantic-conventions" "^1.27.0"
     "@opentelemetry/sql-common" "^0.40.1"
 
-"@opentelemetry/instrumentation-mysql@0.41.0":
-  version "0.41.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-mysql/-/instrumentation-mysql-0.41.0.tgz#2d50691ead5219774bd36d66c35d5b4681485dd7"
-  integrity sha512-jnvrV6BsQWyHS2qb2fkfbfSb1R/lmYwqEZITwufuRl37apTopswu9izc0b1CYRp/34tUG/4k/V39PND6eyiNvw==
+"@opentelemetry/instrumentation-mysql@0.45.0":
+  version "0.45.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-mysql/-/instrumentation-mysql-0.45.0.tgz#e4df8bc709c0c8b0ff90bbef92fb36e92ebe0d19"
+  integrity sha512-tWWyymgwYcTwZ4t8/rLDfPYbOTF3oYB8SxnYMtIQ1zEf5uDm90Ku3i6U/vhaMyfHNlIHvDhvJh+qx5Nc4Z3Acg==
   dependencies:
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/semantic-conventions" "^1.27.0"
     "@types/mysql" "2.15.26"
 
-"@opentelemetry/instrumentation-nestjs-core@0.40.0":
-  version "0.40.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-nestjs-core/-/instrumentation-nestjs-core-0.40.0.tgz#2c0e6405b56caaec32747d55c57ff9a034668ea8"
-  integrity sha512-WF1hCUed07vKmf5BzEkL0wSPinqJgH7kGzOjjMAiTGacofNXjb/y4KQ8loj2sNsh5C/NN7s1zxQuCgbWbVTGKg==
-  dependencies:
-    "@opentelemetry/instrumentation" "^0.53.0"
-    "@opentelemetry/semantic-conventions" "^1.27.0"
-
-"@opentelemetry/instrumentation-pg@0.44.0":
-  version "0.44.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-pg/-/instrumentation-pg-0.44.0.tgz#1e97a0aeb2dca068ee23ce75884a0a0063a7ce3f"
-  integrity sha512-oTWVyzKqXud1BYEGX1loo2o4k4vaU1elr3vPO8NZolrBtFvQ34nx4HgUaexUDuEog00qQt+MLR5gws/p+JXMLQ==
+"@opentelemetry/instrumentation-pg@0.50.0":
+  version "0.50.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-pg/-/instrumentation-pg-0.50.0.tgz#525ecf683c349529539a14f2be47164f4e3eb0f5"
+  integrity sha512-TtLxDdYZmBhFswm8UIsrDjh/HFBeDXd4BLmE8h2MxirNHewLJ0VS9UUddKKEverb5Sm2qFVjqRjcU+8Iw4FJ3w==
   dependencies:
-    "@opentelemetry/instrumentation" "^0.53.0"
-    "@opentelemetry/semantic-conventions" "^1.27.0"
+    "@opentelemetry/core" "^1.26.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
+    "@opentelemetry/semantic-conventions" "1.27.0"
     "@opentelemetry/sql-common" "^0.40.1"
     "@types/pg" "8.6.1"
     "@types/pg-pool" "2.0.6"
 
-"@opentelemetry/instrumentation-redis-4@0.42.0":
-  version "0.42.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-redis-4/-/instrumentation-redis-4-0.42.0.tgz#fc01104cfe884c7546385eaae03c57a47edd19d1"
-  integrity sha512-NaD+t2JNcOzX/Qa7kMy68JbmoVIV37fT/fJYzLKu2Wwd+0NCxt+K2OOsOakA8GVg8lSpFdbx4V/suzZZ2Pvdjg==
+"@opentelemetry/instrumentation-redis-4@0.46.0":
+  version "0.46.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-redis-4/-/instrumentation-redis-4-0.46.0.tgz#828704b8134f023730ac508bcf3a38ca4d5d697c"
+  integrity sha512-aTUWbzbFMFeRODn3720TZO0tsh/49T8H3h8vVnVKJ+yE36AeW38Uj/8zykQ/9nO8Vrtjr5yKuX3uMiG/W8FKNw==
   dependencies:
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
     "@opentelemetry/redis-common" "^0.36.2"
     "@opentelemetry/semantic-conventions" "^1.27.0"
 
-"@opentelemetry/instrumentation-undici@0.6.0":
-  version "0.6.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-undici/-/instrumentation-undici-0.6.0.tgz#9436ee155c8dcb0b760b66947c0e0f347688a5ef"
-  integrity sha512-ABJBhm5OdhGmbh0S/fOTE4N69IZ00CsHC5ijMYfzbw3E5NwLgpQk5xsljaECrJ8wz1SfXbO03FiSuu5AyRAkvQ==
+"@opentelemetry/instrumentation-tedious@0.18.0":
+  version "0.18.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-tedious/-/instrumentation-tedious-0.18.0.tgz#636745423db28e303b4e0289b8f69685cb36f807"
+  integrity sha512-9zhjDpUDOtD+coeADnYEJQ0IeLVCj7w/hqzIutdp5NqS1VqTAanaEfsEcSypyvYv5DX3YOsTUoF+nr2wDXPETA==
+  dependencies:
+    "@opentelemetry/instrumentation" "^0.57.0"
+    "@opentelemetry/semantic-conventions" "^1.27.0"
+    "@types/tedious" "^4.0.14"
+
+"@opentelemetry/instrumentation-undici@0.10.0":
+  version "0.10.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation-undici/-/instrumentation-undici-0.10.0.tgz#99cba213a6e9d47a82896b6c782c3f2d60e0edb5"
+  integrity sha512-vm+V255NGw9gaSsPD6CP0oGo8L55BffBc8KnxqsMuc6XiAD1L8SFNzsW0RHhxJFqy9CJaJh+YiJ5EHXuZ5rZBw==
   dependencies:
     "@opentelemetry/core" "^1.8.0"
-    "@opentelemetry/instrumentation" "^0.53.0"
+    "@opentelemetry/instrumentation" "^0.57.0"
 
-"@opentelemetry/instrumentation@0.53.0", "@opentelemetry/instrumentation@^0.53.0":
-  version "0.53.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation/-/instrumentation-0.53.0.tgz#e6369e4015eb5112468a4d45d38dcada7dad892d"
-  integrity sha512-DMwg0hy4wzf7K73JJtl95m/e0boSoWhH07rfvHvYzQtBD3Bmv0Wc1x733vyZBqmFm8OjJD0/pfiUg1W3JjFX0A==
+"@opentelemetry/instrumentation@0.57.1", "@opentelemetry/instrumentation@^0.57.0", "@opentelemetry/instrumentation@^0.57.1":
+  version "0.57.1"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation/-/instrumentation-0.57.1.tgz#5aea772be8783a35d69d643da46582f381ba1810"
+  integrity sha512-SgHEKXoVxOjc20ZYusPG3Fh+RLIZTSa4x8QtD3NfgAUDyqdFFS9W1F2ZVbZkqDCdyMcQG02Ok4duUGLHJXHgbA==
   dependencies:
-    "@opentelemetry/api-logs" "0.53.0"
+    "@opentelemetry/api-logs" "0.57.1"
     "@types/shimmer" "^1.2.0"
     import-in-the-middle "^1.8.1"
     require-in-the-middle "^7.1.1"
     semver "^7.5.2"
     shimmer "^1.2.1"
 
-"@opentelemetry/instrumentation@^0.49 || ^0.50 || ^0.51 || ^0.52.0":
-  version "0.52.1"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation/-/instrumentation-0.52.1.tgz#2e7e46a38bd7afbf03cf688c862b0b43418b7f48"
-  integrity sha512-uXJbYU/5/MBHjMp1FqrILLRuiJCs3Ofk0MeRDk8g1S1gD47U8X3JnSwcMO1rtRo1x1a7zKaQHaoYu49p/4eSKw==
+"@opentelemetry/instrumentation@^0.49 || ^0.50 || ^0.51 || ^0.52.0 || ^0.53.0":
+  version "0.53.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation/-/instrumentation-0.53.0.tgz#e6369e4015eb5112468a4d45d38dcada7dad892d"
+  integrity sha512-DMwg0hy4wzf7K73JJtl95m/e0boSoWhH07rfvHvYzQtBD3Bmv0Wc1x733vyZBqmFm8OjJD0/pfiUg1W3JjFX0A==
   dependencies:
-    "@opentelemetry/api-logs" "0.52.1"
-    "@types/shimmer" "^1.0.2"
+    "@opentelemetry/api-logs" "0.53.0"
+    "@types/shimmer" "^1.2.0"
     import-in-the-middle "^1.8.1"
     require-in-the-middle "^7.1.1"
     semver "^7.5.2"
     shimmer "^1.2.1"
 
-"@opentelemetry/instrumentation@^0.54.0":
-  version "0.54.2"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation/-/instrumentation-0.54.2.tgz#29693a33bbaaf0156634ac5d9e774636b8f17f73"
-  integrity sha512-go6zpOVoZVztT9r1aPd79Fr3OWiD4N24bCPJsIKkBses8oyFo12F/Ew3UBTdIu6hsW4HC4MVEJygG6TEyJI/lg==
+"@opentelemetry/instrumentation@^0.52.0 || ^0.53.0 || ^0.54.0 || ^0.55.0 || ^0.56.0":
+  version "0.56.0"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/instrumentation/-/instrumentation-0.56.0.tgz#3330ce16d9235a548efa1019a4a7f01414edd44a"
+  integrity sha512-2KkGBKE+FPXU1F0zKww+stnlUxUTlBvLCiWdP63Z9sqXYeNI/ziNzsxAp4LAdUcTQmXjw1IWgvm5CAb/BHy99w==
   dependencies:
-    "@opentelemetry/api-logs" "0.54.2"
+    "@opentelemetry/api-logs" "0.56.0"
     "@types/shimmer" "^1.2.0"
     import-in-the-middle "^1.8.1"
     require-in-the-middle "^7.1.1"
@@ -2096,37 +2107,29 @@
   resolved "https://registry.yarnpkg.com/@opentelemetry/redis-common/-/redis-common-0.36.2.tgz#906ac8e4d804d4109f3ebd5c224ac988276fdc47"
   integrity sha512-faYX1N0gpLhej/6nyp6bgRjzAKXn5GOEMYY7YhciSfCoITAktLUtQ36d24QEWNA1/WA1y6qQunCe0OhHRkVl9g==
 
-"@opentelemetry/resources@1.28.0", "@opentelemetry/resources@^1.26.0":
-  version "1.28.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/resources/-/resources-1.28.0.tgz#c8c27ae7559c817f9d117f1bf96d76f893fb29f5"
-  integrity sha512-cIyXSVJjGeTICENN40YSvLDAq4Y2502hGK3iN7tfdynQLKWb3XWZQEkPc+eSx47kiy11YeFAlYkEfXwR1w8kfw==
+"@opentelemetry/resources@1.30.1", "@opentelemetry/resources@^1.30.1":
+  version "1.30.1"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/resources/-/resources-1.30.1.tgz#a4eae17ebd96947fdc7a64f931ca4b71e18ce964"
+  integrity sha512-5UxZqiAgLYGFjS4s9qm5mBVo433u+dSPUFWVWXmLAD4wB65oMCoXaJP1KJa9DIYYMeHu3z4BZcStG3LC593cWA==
   dependencies:
-    "@opentelemetry/core" "1.28.0"
-    "@opentelemetry/semantic-conventions" "1.27.0"
+    "@opentelemetry/core" "1.30.1"
+    "@opentelemetry/semantic-conventions" "1.28.0"
 
-"@opentelemetry/sdk-metrics@^1.9.1":
-  version "1.28.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/sdk-metrics/-/sdk-metrics-1.28.0.tgz#257b5295bbe9de1ad31c5e8cb43a660c25911d20"
-  integrity sha512-43tqMK/0BcKTyOvm15/WQ3HLr0Vu/ucAl/D84NO7iSlv6O4eOprxSHa3sUtmYkaZWHqdDJV0AHVz/R6u4JALVQ==
+"@opentelemetry/sdk-trace-base@^1.22", "@opentelemetry/sdk-trace-base@^1.30.1":
+  version "1.30.1"
+  resolved "https://registry.yarnpkg.com/@opentelemetry/sdk-trace-base/-/sdk-trace-base-1.30.1.tgz#41a42234096dc98e8f454d24551fc80b816feb34"
+  integrity sha512-jVPgBbH1gCy2Lb7X0AVQ8XAfgg0pJ4nvl8/IiQA6nxOsPvS+0zMJaFSs2ltXe0J6C8dqjcnpyqINDJmU30+uOg==
   dependencies:
-    "@opentelemetry/core" "1.28.0"
-    "@opentelemetry/resources" "1.28.0"
-
-"@opentelemetry/sdk-trace-base@^1.22", "@opentelemetry/sdk-trace-base@^1.26.0":
-  version "1.28.0"
-  resolved "https://registry.yarnpkg.com/@opentelemetry/sdk-trace-base/-/sdk-trace-base-1.28.0.tgz#6195dc8cd78bd74394cf54c67c5cbd8d1528516c"
-  integrity sha512-ceUVWuCpIao7Y5xE02Xs3nQi0tOGmMea17ecBdwtCvdo9ekmO+ijc9RFDgfifMl7XCBf41zne/1POM3LqSTZDA==
-  dependencies:
-    "@opentelemetry/core" "1.28.0"
-    "@opentelemetry/resources" "1.28.0"
-    "@opentelemetry/semantic-conventions" "1.27.0"
+    "@opentelemetry/core" "1.30.1"
+    "@opentelemetry/resources" "1.30.1"
+    "@opentelemetry/semantic-conventions" "1.28.0"
 
 "@opentelemetry/semantic-conventions@1.27.0":
   version "1.27.0"
   resolved "https://registry.yarnpkg.com/@opentelemetry/semantic-conventions/-/semantic-conventions-1.27.0.tgz#1a857dcc95a5ab30122e04417148211e6f945e6c"
   integrity sha512-sAay1RrB+ONOem0OZanAR1ZI/k7yDpnOQSQmTMuGImUQb2y8EbSaCJ94FQluM74xoU03vlb2d2U90hZluL6nQg==
 
-"@opentelemetry/semantic-conventions@^1.27.0":
+"@opentelemetry/semantic-conventions@1.28.0", "@opentelemetry/semantic-conventions@^1.27.0", "@opentelemetry/semantic-conventions@^1.28.0":
   version "1.28.0"
   resolved "https://registry.yarnpkg.com/@opentelemetry/semantic-conventions/-/semantic-conventions-1.28.0.tgz#337fb2bca0453d0726696e745f50064411f646d6"
   integrity sha512-lp4qAiMTD4sNWW4DbKLBkfiMZ4jbAboJIGOQr5DvciMRI494OapieI9qiODpOt0XBr1LjIDy1xAGAnVs5supTA==
@@ -2290,13 +2293,20 @@
   dependencies:
     "@prisma/debug" "5.22.0"
 
-"@prisma/instrumentation@5.19.1":
-  version "5.19.1"
-  resolved "https://registry.yarnpkg.com/@prisma/instrumentation/-/instrumentation-5.19.1.tgz#146319cf85f22b7a43296f0f40cfeac55516e66e"
-  integrity sha512-VLnzMQq7CWroL5AeaW0Py2huiNKeoMfCH3SUxstdzPrlWQi6UQ9UrfcbUkNHlVFqOMacqy8X/8YtE0kuKDpD9w==
+"@prisma/instrumentation@6.2.1":
+  version "6.2.1"
+  resolved "https://registry.yarnpkg.com/@prisma/instrumentation/-/instrumentation-6.2.1.tgz#261b885467d36759b7ca01d1b2ca4e1120bda886"
+  integrity sha512-QrcWRAwNHXX4nHXB+Q94nfm701gPQsR4zkaxYV6qCiENopRi8yYvXt6FNIvxbuwEiWW5Zid6DoWwIsBKJ/5r5w==
+  dependencies:
+    "@opentelemetry/instrumentation" "^0.52.0 || ^0.53.0 || ^0.54.0 || ^0.55.0 || ^0.56.0"
+
+"@prisma/instrumentation@^5.8.1":
+  version "5.22.0"
+  resolved "https://registry.yarnpkg.com/@prisma/instrumentation/-/instrumentation-5.22.0.tgz#c39941046e9886e17bdb47dbac45946c24d579aa"
+  integrity sha512-LxccF392NN37ISGxIurUljZSh1YWnphO34V5a0+T7FVQG2u9bhAXRTJpgmQ3483woVhkraQZFF7cbRrpbw/F4Q==
   dependencies:
     "@opentelemetry/api" "^1.8"
-    "@opentelemetry/instrumentation" "^0.49 || ^0.50 || ^0.51 || ^0.52.0"
+    "@opentelemetry/instrumentation" "^0.49 || ^0.50 || ^0.51 || ^0.52.0 || ^0.53.0"
     "@opentelemetry/sdk-trace-base" "^1.22"
 
 "@radix-ui/colors@^3.0.0":
@@ -2903,17 +2913,18 @@
     classnames "^2.3.2"
     react-remove-scroll-bar "^2.3.6"
 
-"@rollup/plugin-commonjs@26.0.1":
-  version "26.0.1"
-  resolved "https://registry.yarnpkg.com/@rollup/plugin-commonjs/-/plugin-commonjs-26.0.1.tgz#16d4d6e54fa63021249a292b50f27c0b0f1a30d8"
-  integrity sha512-UnsKoZK6/aGIH6AdkptXhNvhaqftcjq3zZdT+LY5Ftms6JR06nADcDsYp5hTU9E2lbJUEOhdlY5J4DNTneM+jQ==
+"@rollup/plugin-commonjs@28.0.1":
+  version "28.0.1"
+  resolved "https://registry.yarnpkg.com/@rollup/plugin-commonjs/-/plugin-commonjs-28.0.1.tgz#e2138e31cc0637676dc3d5cae7739131f7cd565e"
+  integrity sha512-+tNWdlWKbpB3WgBN7ijjYkq9X5uhjmcvyjEght4NmH5fAU++zfQzAJ6wumLS+dNcvwEZhKx2Z+skY8m7v0wGSA==
   dependencies:
     "@rollup/pluginutils" "^5.0.1"
     commondir "^1.0.1"
     estree-walker "^2.0.2"
-    glob "^10.4.1"
+    fdir "^6.2.0"
     is-reference "1.2.1"
     magic-string "^0.30.3"
+    picomatch "^4.0.2"
 
 "@rollup/pluginutils@^5.0.1":
   version "5.1.3"
@@ -3024,23 +3035,19 @@
   resolved "https://registry.yarnpkg.com/@rushstack/eslint-patch/-/eslint-patch-1.10.4.tgz#427d5549943a9c6fce808e39ea64dbe60d4047f1"
   integrity sha512-WJgX9nzTqknM393q1QJDJmoW28kUfEnybeTfVNcNAPnIx210RXm2DiXiHzfNPJNIUUb1tJnz/l4QGtJ30PgWmA==
 
-"@sentry-internal/browser-utils@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry-internal/browser-utils/-/browser-utils-8.36.0.tgz#c6a1b6d7eb2ccfc2f9c189504d94b3996367ccbf"
-  integrity sha512-AVJ9GmQW7jYxaal6hjQnnktsDNype01ajVC4q1RyOn1SfzSnXg6mXwj4xm4ovuJV+aBI7fAZJ55vEX5ASuP0ZA==
+"@sentry-internal/browser-utils@9.0.0-alpha.0":
+  version "9.0.0-alpha.0"
+  resolved "https://registry.yarnpkg.com/@sentry-internal/browser-utils/-/browser-utils-9.0.0-alpha.0.tgz#45ea11a7fcf04fca190a965fff2b08f75be67b52"
+  integrity sha512-JtBKl88Wsm+FGZIbsZ1PmcdX+y/8dZvJPMsBqyxJd55rs4g0vCX9LaUUuRnzF4wZzSX1otjmdpqVN5xxQ28Jpg==
   dependencies:
-    "@sentry/core" "8.36.0"
-    "@sentry/types" "8.36.0"
-    "@sentry/utils" "8.36.0"
+    "@sentry/core" "9.0.0-alpha.0"
 
-"@sentry-internal/feedback@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry-internal/feedback/-/feedback-8.36.0.tgz#2cda799f921543522aa5cbf8f9c3300209b54825"
-  integrity sha512-aAMTm3uDBj8Ta7FwoohpLmJOpWzpWXvvtTbtmSgkeCtPJLUS8DZDCTZ9uCILUkpuYrv2savRUHsdPkxNjgL8FA==
+"@sentry-internal/feedback@9.0.0-alpha.0":
+  version "9.0.0-alpha.0"
+  resolved "https://registry.yarnpkg.com/@sentry-internal/feedback/-/feedback-9.0.0-alpha.0.tgz#ec544527ecab131694a1ebe1224a8ebcb6d09db6"
+  integrity sha512-FRdnDQjIiNj771MdawXN6amsmD3AdMq+Lbf/OcbD+DUszl4KSHMXYERHOw6/5oVeVgZ/t5RpN0Pn97OUsr33Zw==
   dependencies:
-    "@sentry/core" "8.36.0"
-    "@sentry/types" "8.36.0"
-    "@sentry/utils" "8.36.0"
+    "@sentry/core" "9.0.0-alpha.0"
 
 "@sentry-internal/global-search@^1.1.0":
   version "1.1.0"
@@ -3056,97 +3063,91 @@
     htmlparser2 "^4.1.0"
     title-case "^3.0.2"
 
-"@sentry-internal/replay-canvas@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry-internal/replay-canvas/-/replay-canvas-8.36.0.tgz#557c8677f6c386cf79b5f8ab7485b31f4347a6cb"
-  integrity sha512-KJPLf+qYdrQdmouoAqIPZ2KeapIBlHWbzNdQqNxJFWLHFFjpLUtt0b+87ruvbA/q3NYy2fDwD7EB0tGS1RHBaA==
-  dependencies:
-    "@sentry-internal/replay" "8.36.0"
-    "@sentry/core" "8.36.0"
-    "@sentry/types" "8.36.0"
-    "@sentry/utils" "8.36.0"
-
-"@sentry-internal/replay@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry-internal/replay/-/replay-8.36.0.tgz#8f5dccab0bcc3429650a461c46a01085f2f8b782"
-  integrity sha512-lbic98GsSkDeinQDix54tBFEgHUlmBtO+HjXECk9jIE0vOzR4As20/s5ta46t1rKMLlnxOtJuT5jKXeUYogBUw==
-  dependencies:
-    "@sentry-internal/browser-utils" "8.36.0"
-    "@sentry/core" "8.36.0"
-    "@sentry/types" "8.36.0"
-    "@sentry/utils" "8.36.0"
-
-"@sentry/babel-plugin-component-annotate@2.22.6":
-  version "2.22.6"
-  resolved "https://registry.yarnpkg.com/@sentry/babel-plugin-component-annotate/-/babel-plugin-component-annotate-2.22.6.tgz#829d6caf2c95c1c46108336de4e1049e6521435e"
-  integrity sha512-V2g1Y1I5eSe7dtUVMBvAJr8BaLRr4CLrgNgtPaZyMT4Rnps82SrZ5zqmEkLXPumlXhLUWR6qzoMNN2u+RXVXfQ==
-
-"@sentry/browser@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry/browser/-/browser-8.36.0.tgz#da8977b37e56e5436cf3ea2c2e4a098f480ab115"
-  integrity sha512-bLrQNe+wD4DkCfB8OD5TF3Rr8KA2+aTo5wF3t3Bf6KVn8//iX1ia1hhtptYiRnbRkG/0AEPxlqL6XfPZYVPQ5A==
-  dependencies:
-    "@sentry-internal/browser-utils" "8.36.0"
-    "@sentry-internal/feedback" "8.36.0"
-    "@sentry-internal/replay" "8.36.0"
-    "@sentry-internal/replay-canvas" "8.36.0"
-    "@sentry/core" "8.36.0"
-    "@sentry/types" "8.36.0"
-    "@sentry/utils" "8.36.0"
-
-"@sentry/bundler-plugin-core@2.22.6":
-  version "2.22.6"
-  resolved "https://registry.yarnpkg.com/@sentry/bundler-plugin-core/-/bundler-plugin-core-2.22.6.tgz#a1ea1fd43700a3ece9e7db016997e79a2782b87d"
-  integrity sha512-1esQdgSUCww9XAntO4pr7uAM5cfGhLsgTK9MEwAKNfvpMYJi9NUTYa3A7AZmdA8V6107Lo4OD7peIPrDRbaDCg==
+"@sentry-internal/replay-canvas@9.0.0-alpha.0":
+  version "9.0.0-alpha.0"
+  resolved "https://registry.yarnpkg.com/@sentry-internal/replay-canvas/-/replay-canvas-9.0.0-alpha.0.tgz#453b9084528704e0879ae3c5db576767357ccee7"
+  integrity sha512-xwIt8pIW2jVIDwAOJDcuxrlva6YggToBups8EDTQ/WgGMJXxfUyg9Vb/oSTFR+vnRqgvu2gfeCH6YMNbn5tbtQ==
+  dependencies:
+    "@sentry-internal/replay" "9.0.0-alpha.0"
+    "@sentry/core" "9.0.0-alpha.0"
+
+"@sentry-internal/replay@9.0.0-alpha.0":
+  version "9.0.0-alpha.0"
+  resolved "https://registry.yarnpkg.com/@sentry-internal/replay/-/replay-9.0.0-alpha.0.tgz#438dbca34f72408237c942bc1c800fd23484a13d"
+  integrity sha512-G0+w1eULHHHWPc1F0TNzNszmLX8zi8vEjnhzyRJvIJVdjxJ6T/8rpZVDqUabfWChFTBpbjtjoFTAoWfURycsyw==
+  dependencies:
+    "@sentry-internal/browser-utils" "9.0.0-alpha.0"
+    "@sentry/core" "9.0.0-alpha.0"
+
+"@sentry/babel-plugin-component-annotate@2.22.7":
+  version "2.22.7"
+  resolved "https://registry.yarnpkg.com/@sentry/babel-plugin-component-annotate/-/babel-plugin-component-annotate-2.22.7.tgz#604c7e33d48528a13477e7af597c4d5fca51b8bd"
+  integrity sha512-aa7XKgZMVl6l04NY+3X7BP7yvQ/s8scn8KzQfTLrGRarziTlMGrsCOBQtCNWXOPEbtxAIHpZ9dsrAn5EJSivOQ==
+
+"@sentry/browser@9.0.0-alpha.0":
+  version "9.0.0-alpha.0"
+  resolved "https://registry.yarnpkg.com/@sentry/browser/-/browser-9.0.0-alpha.0.tgz#b354e8151831929bf61012b14e2f4be07ccfa18a"
+  integrity sha512-aWzgJa4PvK5oDcTgZEI6VOtrA2vOBXuAGxjidwdy2EwcMUFmvI5P0K2l9VcHhhIC/lnBWBY4jEYkgbLqvCL5Ow==
+  dependencies:
+    "@sentry-internal/browser-utils" "9.0.0-alpha.0"
+    "@sentry-internal/feedback" "9.0.0-alpha.0"
+    "@sentry-internal/replay" "9.0.0-alpha.0"
+    "@sentry-internal/replay-canvas" "9.0.0-alpha.0"
+    "@sentry/core" "9.0.0-alpha.0"
+
+"@sentry/bundler-plugin-core@2.22.7":
+  version "2.22.7"
+  resolved "https://registry.yarnpkg.com/@sentry/bundler-plugin-core/-/bundler-plugin-core-2.22.7.tgz#28204a224cd1fef58d157e5beeb2493947a9bc35"
+  integrity sha512-ouQh5sqcB8vsJ8yTTe0rf+iaUkwmeUlGNFi35IkCFUQlWJ22qS6OfvNjOqFI19e6eGUXks0c/2ieFC4+9wJ+1g==
   dependencies:
     "@babel/core" "^7.18.5"
-    "@sentry/babel-plugin-component-annotate" "2.22.6"
-    "@sentry/cli" "^2.36.1"
+    "@sentry/babel-plugin-component-annotate" "2.22.7"
+    "@sentry/cli" "2.39.1"
     dotenv "^16.3.1"
     find-up "^5.0.0"
     glob "^9.3.2"
     magic-string "0.30.8"
     unplugin "1.0.1"
 
-"@sentry/cli-darwin@2.38.2":
-  version "2.38.2"
-  resolved "https://registry.yarnpkg.com/@sentry/cli-darwin/-/cli-darwin-2.38.2.tgz#2a53028e143d0cfed607588b87e04906ef5317e7"
-  integrity sha512-21ywIcJCCFrCTyiF1o1PaT7rbelFC2fWmayKYgFElnQ55IzNYkcn8BYhbh/QknE0l1NBRaeWMXwTTdeoqETCCg==
-
-"@sentry/cli-linux-arm64@2.38.2":
-  version "2.38.2"
-  resolved "https://registry.yarnpkg.com/@sentry/cli-linux-arm64/-/cli-linux-arm64-2.38.2.tgz#1b45de7e4f5e1a953b88b0b811d789de1fc708aa"
-  integrity sha512-4Fp/jjQpNZj4Th+ZckMQvldAuuP0ZcyJ9tJCP1CCOn5poIKPYtY6zcbTP036R7Te14PS4ALOcDNX3VNKfpsifA==
-
-"@sentry/cli-linux-arm@2.38.2":
-  version "2.38.2"
-  resolved "https://registry.yarnpkg.com/@sentry/cli-linux-arm/-/cli-linux-arm-2.38.2.tgz#91f73c251f1d4b591fa98af10ee3889c9b93d208"
-  integrity sha512-+AiKDBQKIdQe4NhBiHSHGl0KR+b//HHTrnfK1SaTrOm9HtM4ELXAkjkRF3bmbpSzSQCS5WzcbIxxCJOeaUaO0A==
-
-"@sentry/cli-linux-i686@2.38.2":
-  version "2.38.2"
-  resolved "https://registry.yarnpkg.com/@sentry/cli-linux-i686/-/cli-linux-i686-2.38.2.tgz#26e30a9bc358f910e21d812359294dd4c6103fda"
-  integrity sha512-6zVJN10dHIn4R1v+fxuzlblzVBhIVwsaN/S7aBED6Vn1HhAyAcNG2tIzeCLGeDfieYjXlE2sCI82sZkQBCbAGw==
-
-"@sentry/cli-linux-x64@2.38.2":
-  version "2.38.2"
-  resolved "https://registry.yarnpkg.com/@sentry/cli-linux-x64/-/cli-linux-x64-2.38.2.tgz#18728bbb20e28315c4368baded677786f2dba70a"
-  integrity sha512-4UiLu9zdVtqPeltELR5MDGKcuqAdQY9xz3emISuA6bm+MXGbt2W1WgX+XY3GElwjZbmH8qpyLUEd34sw6sdcbQ==
-
-"@sentry/cli-win32-i686@2.38.2":
-  version "2.38.2"
-  resolved "https://registry.yarnpkg.com/@sentry/cli-win32-i686/-/cli-win32-i686-2.38.2.tgz#dfe268b041c3e3db556290dba745455d0b2c0d72"
-  integrity sha512-DYfSvd5qLPerLpIxj3Xu2rRe3CIlpGOOfGSNI6xvJ5D8j6hqbOHlCzvfC4oBWYVYGtxnwQLMeDGJ7o7RMYulig==
-
-"@sentry/cli-win32-x64@2.38.2":
-  version "2.38.2"
-  resolved "https://registry.yarnpkg.com/@sentry/cli-win32-x64/-/cli-win32-x64-2.38.2.tgz#e7b5744026ff5f7e84971512bee228620ba5857d"
-  integrity sha512-W5UX58PKY1hNUHo9YJxWNhGvgvv2uOYHI27KchRiUvFYBIqlUUcIdPZDfyzetDfd8qBCxlAsFnkL2VJSNdpA9A==
-
-"@sentry/cli@^2.36.1":
-  version "2.38.2"
-  resolved "https://registry.yarnpkg.com/@sentry/cli/-/cli-2.38.2.tgz#e9a7a9bbeaaade4557de91704d50d131760345d3"
-  integrity sha512-CR0oujpAnhegK2pBAv6ZReMqbFTuNJLDZLvoD1B+syrKZX+R+oxkgT2e1htsBbht+wGxAsluVWsIAydSws1GAA==
+"@sentry/cli-darwin@2.39.1":
+  version "2.39.1"
+  resolved "https://registry.yarnpkg.com/@sentry/cli-darwin/-/cli-darwin-2.39.1.tgz#75c338a53834b4cf72f57599f4c72ffb36cf0781"
+  integrity sha512-kiNGNSAkg46LNGatfNH5tfsmI/kCAaPA62KQuFZloZiemTNzhy9/6NJP8HZ/GxGs8GDMxic6wNrV9CkVEgFLJQ==
+
+"@sentry/cli-linux-arm64@2.39.1":
+  version "2.39.1"
+  resolved "https://registry.yarnpkg.com/@sentry/cli-linux-arm64/-/cli-linux-arm64-2.39.1.tgz#27db44700c33fcb1e8966257020b43f8494373e6"
+  integrity sha512-5VbVJDatolDrWOgaffsEM7znjs0cR8bHt9Bq0mStM3tBolgAeSDHE89NgHggfZR+DJ2VWOy4vgCwkObrUD6NQw==
+
+"@sentry/cli-linux-arm@2.39.1":
+  version "2.39.1"
+  resolved "https://registry.yarnpkg.com/@sentry/cli-linux-arm/-/cli-linux-arm-2.39.1.tgz#451683fa9a5a60b1359d104ec71334ed16f4b63c"
+  integrity sha512-DkENbxyRxUrfLnJLXTA4s5UL/GoctU5Cm4ER1eB7XN7p9WsamFJd/yf2KpltkjEyiTuplv0yAbdjl1KX3vKmEQ==
+
+"@sentry/cli-linux-i686@2.39.1":
+  version "2.39.1"
+  resolved "https://registry.yarnpkg.com/@sentry/cli-linux-i686/-/cli-linux-i686-2.39.1.tgz#9965a81f97a94e8b6d1d15589e43fee158e35201"
+  integrity sha512-pXWVoKXCRrY7N8vc9H7mETiV9ZCz+zSnX65JQCzZxgYrayQPJTc+NPRnZTdYdk5RlAupXaFicBI2GwOCRqVRkg==
+
+"@sentry/cli-linux-x64@2.39.1":
+  version "2.39.1"
+  resolved "https://registry.yarnpkg.com/@sentry/cli-linux-x64/-/cli-linux-x64-2.39.1.tgz#31fe008b02f92769543dc9919e2a5cbc4cda7889"
+  integrity sha512-IwayNZy+it7FWG4M9LayyUmG1a/8kT9+/IEm67sT5+7dkMIMcpmHDqL8rWcPojOXuTKaOBBjkVdNMBTXy0mXlA==
+
+"@sentry/cli-win32-i686@2.39.1":
+  version "2.39.1"
+  resolved "https://registry.yarnpkg.com/@sentry/cli-win32-i686/-/cli-win32-i686-2.39.1.tgz#609e8790c49414011445e397130560c777850b35"
+  integrity sha512-NglnNoqHSmE+Dz/wHeIVRnV2bLMx7tIn3IQ8vXGO5HWA2f8zYJGktbkLq1Lg23PaQmeZLPGlja3gBQfZYSG10Q==
+
+"@sentry/cli-win32-x64@2.39.1":
+  version "2.39.1"
+  resolved "https://registry.yarnpkg.com/@sentry/cli-win32-x64/-/cli-win32-x64-2.39.1.tgz#1a874a5570c6d162b35d9d001c96e5389d07d2cb"
+  integrity sha512-xv0R2CMf/X1Fte3cMWie1NXuHmUyQPDBfCyIt6k6RPFPxAYUgcqgMPznYwVMwWEA1W43PaOkSn3d8ZylsDaETw==
+
+"@sentry/cli@2.39.1":
+  version "2.39.1"
+  resolved "https://registry.yarnpkg.com/@sentry/cli/-/cli-2.39.1.tgz#916bb5b7567ccf7fdf94ef6cf8a2b9ab78370d29"
+  integrity sha512-JIb3e9vh0+OmQ0KxmexMXg9oZsR/G7HMwxt5BUIKAXZ9m17Xll4ETXTRnRUBT3sf7EpNGAmlQk1xEmVN9pYZYQ==
   dependencies:
     https-proxy-agent "^5.0.0"
     node-fetch "^2.6.7"
@@ -3154,134 +3155,114 @@
     proxy-from-env "^1.1.0"
     which "^2.0.2"
   optionalDependencies:
-    "@sentry/cli-darwin" "2.38.2"
-    "@sentry/cli-linux-arm" "2.38.2"
-    "@sentry/cli-linux-arm64" "2.38.2"
-    "@sentry/cli-linux-i686" "2.38.2"
-    "@sentry/cli-linux-x64" "2.38.2"
-    "@sentry/cli-win32-i686" "2.38.2"
-    "@sentry/cli-win32-x64" "2.38.2"
-
-"@sentry/core@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry/core/-/core-8.36.0.tgz#34276354f0cd2298803c2f8d86ba571473435ff1"
-  integrity sha512-cbq1WQyRqc/+YpPhjwQxfniUM3ZxmO3Pm1oisTB8dw6mlbgQfGD6aznEIjXWWJY6k6acewJlMUx09N7DnprtBw==
-  dependencies:
-    "@sentry/types" "8.36.0"
-    "@sentry/utils" "8.36.0"
-
-"@sentry/nextjs@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry/nextjs/-/nextjs-8.36.0.tgz#2a4a3f320a7533d90bfe9f5dc8e5935ead43bf11"
-  integrity sha512-JLPK5ZSZdGyIPVx40qnOomHV04TB3p+HymYvfQwX7C7/Ocm8U0Q7v+0164IXHu0FVR/BfqhbE84s+mpAEnHvig==
+    "@sentry/cli-darwin" "2.39.1"
+    "@sentry/cli-linux-arm" "2.39.1"
+    "@sentry/cli-linux-arm64" "2.39.1"
+    "@sentry/cli-linux-i686" "2.39.1"
+    "@sentry/cli-linux-x64" "2.39.1"
+    "@sentry/cli-win32-i686" "2.39.1"
+    "@sentry/cli-win32-x64" "2.39.1"
+
+"@sentry/core@9.0.0-alpha.0":
+  version "9.0.0-alpha.0"
+  resolved "https://registry.yarnpkg.com/@sentry/core/-/core-9.0.0-alpha.0.tgz#2347326f7808bfc4523f2093de79f5f306c2d302"
+  integrity sha512-rznbdRvLTbb3zvujXAhaYRgcwB5P8GSmyR/2Qdr6RdGu6qWWQMG2j4iIcolLlXj1DUJfSTCFmbeRB+sk3WqaPQ==
+
+"@sentry/core@^8.42.0":
+  version "8.51.0"
+  resolved "https://registry.yarnpkg.com/@sentry/core/-/core-8.51.0.tgz#d0c73dfe3489788911b7ce784d3ef8458344482c"
+  integrity sha512-Go0KxCYLw+OBIlLSv5YsYX+x9NW43fNVcyB6rhkSp2Q5Zme3tAE6KtZFvyu4SO7G/903wisW5Q6qV6UuK/ee4A==
+
+"@sentry/nextjs@9.0.0-alpha.0":
+  version "9.0.0-alpha.0"
+  resolved "https://registry.yarnpkg.com/@sentry/nextjs/-/nextjs-9.0.0-alpha.0.tgz#02af24c05edb6d5d3e33638437fc66c5a5edc991"
+  integrity sha512-TxwSe8msFKZOOj+eUKUmxck6P8+NSfSqg129URwkFMuRo4lVRHN8KdrUYJOERHGp/GO7tGTrWH9Efr/XeH+3Vw==
   dependencies:
     "@opentelemetry/api" "^1.9.0"
-    "@opentelemetry/instrumentation-http" "0.53.0"
-    "@opentelemetry/semantic-conventions" "^1.27.0"
-    "@rollup/plugin-commonjs" "26.0.1"
-    "@sentry-internal/browser-utils" "8.36.0"
-    "@sentry/core" "8.36.0"
-    "@sentry/node" "8.36.0"
-    "@sentry/opentelemetry" "8.36.0"
-    "@sentry/react" "8.36.0"
-    "@sentry/types" "8.36.0"
-    "@sentry/utils" "8.36.0"
-    "@sentry/vercel-edge" "8.36.0"
-    "@sentry/webpack-plugin" "2.22.6"
+    "@opentelemetry/semantic-conventions" "^1.28.0"
+    "@rollup/plugin-commonjs" "28.0.1"
+    "@sentry-internal/browser-utils" "9.0.0-alpha.0"
+    "@sentry/core" "9.0.0-alpha.0"
+    "@sentry/node" "9.0.0-alpha.0"
+    "@sentry/opentelemetry" "9.0.0-alpha.0"
+    "@sentry/react" "9.0.0-alpha.0"
+    "@sentry/vercel-edge" "9.0.0-alpha.0"
+    "@sentry/webpack-plugin" "2.22.7"
     chalk "3.0.0"
     resolve "1.22.8"
     rollup "3.29.5"
     stacktrace-parser "^0.1.10"
 
-"@sentry/node@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry/node/-/node-8.36.0.tgz#6b4b6714c6c925e353e7c7eff0e45f8675bb530e"
-  integrity sha512-2RRbSck90TGpVz8F3OaNbq5Q9RXgeRlq5leGWHU7NfQOl3LmkG+vkzTbOqPDPZLtiYcw5KQ3G5G+vybrDS6AGg==
+"@sentry/node@9.0.0-alpha.0":
+  version "9.0.0-alpha.0"
+  resolved "https://registry.yarnpkg.com/@sentry/node/-/node-9.0.0-alpha.0.tgz#868069ac1bbd129ee69cc9c60965a73d565b51e1"
+  integrity sha512-yKRD7v8fL+7zUfgQ3rvIeT4BiVvHEY3AT8m7wsTneRhN2uGqlbnAeLoPazVeX2ntBxHma8gGcVK1XglNRIq4iw==
   dependencies:
     "@opentelemetry/api" "^1.9.0"
-    "@opentelemetry/context-async-hooks" "^1.25.1"
-    "@opentelemetry/core" "^1.25.1"
-    "@opentelemetry/instrumentation" "^0.53.0"
-    "@opentelemetry/instrumentation-amqplib" "^0.42.0"
-    "@opentelemetry/instrumentation-connect" "0.40.0"
-    "@opentelemetry/instrumentation-dataloader" "0.12.0"
-    "@opentelemetry/instrumentation-express" "0.44.0"
-    "@opentelemetry/instrumentation-fastify" "0.40.0"
-    "@opentelemetry/instrumentation-fs" "0.16.0"
-    "@opentelemetry/instrumentation-generic-pool" "0.39.0"
-    "@opentelemetry/instrumentation-graphql" "0.43.0"
-    "@opentelemetry/instrumentation-hapi" "0.41.0"
-    "@opentelemetry/instrumentation-http" "0.53.0"
-    "@opentelemetry/instrumentation-ioredis" "0.43.0"
-    "@opentelemetry/instrumentation-kafkajs" "0.4.0"
-    "@opentelemetry/instrumentation-koa" "0.43.0"
-    "@opentelemetry/instrumentation-lru-memoizer" "0.40.0"
-    "@opentelemetry/instrumentation-mongodb" "0.47.0"
-    "@opentelemetry/instrumentation-mongoose" "0.42.0"
-    "@opentelemetry/instrumentation-mysql" "0.41.0"
-    "@opentelemetry/instrumentation-mysql2" "0.41.0"
-    "@opentelemetry/instrumentation-nestjs-core" "0.40.0"
-    "@opentelemetry/instrumentation-pg" "0.44.0"
-    "@opentelemetry/instrumentation-redis-4" "0.42.0"
-    "@opentelemetry/instrumentation-undici" "0.6.0"
-    "@opentelemetry/resources" "^1.26.0"
-    "@opentelemetry/sdk-trace-base" "^1.26.0"
-    "@opentelemetry/semantic-conventions" "^1.27.0"
-    "@prisma/instrumentation" "5.19.1"
-    "@sentry/core" "8.36.0"
-    "@sentry/opentelemetry" "8.36.0"
-    "@sentry/types" "8.36.0"
-    "@sentry/utils" "8.36.0"
-    import-in-the-middle "^1.11.2"
-
-"@sentry/opentelemetry@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry/opentelemetry/-/opentelemetry-8.36.0.tgz#4e4330fa67cfeb7f2e23d4e078659ac61806b3b0"
-  integrity sha512-pMKMphH0j1Mh8zknLWEEUaaaxeYn76rniGOxKLoQVk1pCUhhzkFEJdxKC41aR8yin/uN8X3CGWQb9vp/przwSg==
-  dependencies:
-    "@sentry/core" "8.36.0"
-    "@sentry/types" "8.36.0"
-    "@sentry/utils" "8.36.0"
-
-"@sentry/react@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry/react/-/react-8.36.0.tgz#cb08298bacaddc585e8b655e7d859299cf597254"
-  integrity sha512-YIJZUx7Q5aulK034cRri0p/7MeP3tdLfdP6vMJMwrVlqoWQI9gKZXikmLIqHUQegZdMRYX5tr03gTWJu3dhYwg==
-  dependencies:
-    "@sentry/browser" "8.36.0"
-    "@sentry/core" "8.36.0"
-    "@sentry/types" "8.36.0"
-    "@sentry/utils" "8.36.0"
+    "@opentelemetry/context-async-hooks" "^1.30.1"
+    "@opentelemetry/core" "^1.30.1"
+    "@opentelemetry/instrumentation" "^0.57.1"
+    "@opentelemetry/instrumentation-amqplib" "^0.46.0"
+    "@opentelemetry/instrumentation-connect" "0.43.0"
+    "@opentelemetry/instrumentation-dataloader" "0.16.0"
+    "@opentelemetry/instrumentation-express" "0.47.0"
+    "@opentelemetry/instrumentation-fastify" "0.44.1"
+    "@opentelemetry/instrumentation-fs" "0.19.0"
+    "@opentelemetry/instrumentation-generic-pool" "0.43.0"
+    "@opentelemetry/instrumentation-graphql" "0.47.0"
+    "@opentelemetry/instrumentation-hapi" "0.45.1"
+    "@opentelemetry/instrumentation-http" "0.57.1"
+    "@opentelemetry/instrumentation-ioredis" "0.47.0"
+    "@opentelemetry/instrumentation-kafkajs" "0.7.0"
+    "@opentelemetry/instrumentation-knex" "0.44.0"
+    "@opentelemetry/instrumentation-koa" "0.47.0"
+    "@opentelemetry/instrumentation-lru-memoizer" "0.44.0"
+    "@opentelemetry/instrumentation-mongodb" "0.51.0"
+    "@opentelemetry/instrumentation-mongoose" "0.46.0"
+    "@opentelemetry/instrumentation-mysql" "0.45.0"
+    "@opentelemetry/instrumentation-mysql2" "0.45.0"
+    "@opentelemetry/instrumentation-pg" "0.50.0"
+    "@opentelemetry/instrumentation-redis-4" "0.46.0"
+    "@opentelemetry/instrumentation-tedious" "0.18.0"
+    "@opentelemetry/instrumentation-undici" "0.10.0"
+    "@opentelemetry/resources" "^1.30.1"
+    "@opentelemetry/sdk-trace-base" "^1.30.1"
+    "@opentelemetry/semantic-conventions" "^1.28.0"
+    "@prisma/instrumentation" "6.2.1"
+    "@sentry/core" "9.0.0-alpha.0"
+    "@sentry/opentelemetry" "9.0.0-alpha.0"
+    import-in-the-middle "^1.12.0"
+
+"@sentry/opentelemetry@9.0.0-alpha.0":
+  version "9.0.0-alpha.0"
+  resolved "https://registry.yarnpkg.com/@sentry/opentelemetry/-/opentelemetry-9.0.0-alpha.0.tgz#dc7367c283f308403c6b8df2e3a2eb52a8005b39"
+  integrity sha512-guXuLRNiitJw7Nd4y6LgoDUW5EMDyDYkRskOBV74l/cpnSi0Udyr7b6x/2htq45SqqmO/s6h8Z0tssQRzX7dSQ==
+  dependencies:
+    "@sentry/core" "9.0.0-alpha.0"
+
+"@sentry/react@9.0.0-alpha.0":
+  version "9.0.0-alpha.0"
+  resolved "https://registry.yarnpkg.com/@sentry/react/-/react-9.0.0-alpha.0.tgz#92913b94ebe009e2bb354517fce36a87294c3bce"
+  integrity sha512-htdEGJh87/ErRk1SwVJhIxVsL8FhST/hXMNQxzOjUCOt8I7/B88pVU6Nsktg8XfgLGOnEGzQthx6ezvgCjw/fQ==
+  dependencies:
+    "@sentry/browser" "9.0.0-alpha.0"
+    "@sentry/core" "9.0.0-alpha.0"
     hoist-non-react-statics "^3.3.2"
 
-"@sentry/types@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry/types/-/types-8.36.0.tgz#b58397eb672d896b65b06103feb59dba74da9d39"
-  integrity sha512-K1pVFfdGHw115RzGHpwSOqoEPeayn4N1F9IfM0kxrYpQSbFT1X29eak88GBfC8gPiLEF0iFGlSaQ4ERmF7oRcA==
-
-"@sentry/utils@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry/utils/-/utils-8.36.0.tgz#e733042ae231fdeeafe6970e49283dcd9ac9700f"
-  integrity sha512-oJ3EDPj0I00z+AwC3EWBpSidXYUoKW0Id8MfMQP5Hflniz3gif7UEReblT+FJgPEVo6+6uNzAncY0MuNMxmDKQ==
-  dependencies:
-    "@sentry/types" "8.36.0"
-
-"@sentry/vercel-edge@8.36.0":
-  version "8.36.0"
-  resolved "https://registry.yarnpkg.com/@sentry/vercel-edge/-/vercel-edge-8.36.0.tgz#d5767337762bbbaef4e502ee078ab920f2663bc0"
-  integrity sha512-5zSw+5JniztTkiOXU4pUXypD9opPVf91Gd71/khrFfDbDBT8gF/LlClp21ACt/c3jc1Bbk79j+lyYEXVe8/jIg==
+"@sentry/vercel-edge@9.0.0-alpha.0":
+  version "9.0.0-alpha.0"
+  resolved "https://registry.yarnpkg.com/@sentry/vercel-edge/-/vercel-edge-9.0.0-alpha.0.tgz#891518e6807b91d461afad161e49b5b4b22072fd"
+  integrity sha512-uoLWqlqch4TVfIzqJ7fxPYwgrjyBNGM8pD+vFcHpwUhe0Gb3jI0k7okzvhv0FvyrJiN3liip9rwexT90f3zOcA==
   dependencies:
     "@opentelemetry/api" "^1.9.0"
-    "@sentry/core" "8.36.0"
-    "@sentry/types" "8.36.0"
-    "@sentry/utils" "8.36.0"
+    "@sentry/core" "9.0.0-alpha.0"
 
-"@sentry/webpack-plugin@2.22.6":
-  version "2.22.6"
-  resolved "https://registry.yarnpkg.com/@sentry/webpack-plugin/-/webpack-plugin-2.22.6.tgz#8c9d27d5cd89153a5b6e08cc9dcb3048b122ffbc"
-  integrity sha512-BiLhAzQYAz/9kCXKj2LeUKWf/9GBVn2dD0DeYK89s+sjDEaxjbcLBBiLlLrzT7eC9QVj2tUZRKOi6puCfc8ysw==
+"@sentry/webpack-plugin@2.22.7":
+  version "2.22.7"
+  resolved "https://registry.yarnpkg.com/@sentry/webpack-plugin/-/webpack-plugin-2.22.7.tgz#992c6c782c736f22e72eb318745e28cc24aabad7"
+  integrity sha512-j5h5LZHWDlm/FQCCmEghQ9FzYXwfZdlOf3FE/X6rK6lrtx0JCAkq+uhMSasoyP4XYKL4P4vRS6WFSos4jxf/UA==
   dependencies:
-    "@sentry/bundler-plugin-core" "2.22.6"
+    "@sentry/bundler-plugin-core" "2.22.7"
     unplugin "1.0.1"
     uuid "^9.0.0"
 
@@ -3889,7 +3870,7 @@
   resolved "https://registry.yarnpkg.com/@types/semver/-/semver-7.5.8.tgz#8268a8c57a3e4abd25c165ecd36237db7948a55e"
   integrity sha512-I8EUhyrgfLrcTkzV3TSsGyl1tSuPrEDzr0yd5m90UgNxQkyDXULk3b6MlQqTCpZpNtWe1K0hzclnZkTcLBe2UQ==
 
-"@types/shimmer@^1.0.2", "@types/shimmer@^1.2.0":
+"@types/shimmer@^1.2.0":
   version "1.2.0"
   resolved "https://registry.yarnpkg.com/@types/shimmer/-/shimmer-1.2.0.tgz#9b706af96fa06416828842397a70dfbbf1c14ded"
   integrity sha512-UE7oxhQLLd9gub6JKIAhDq06T0F6FnztwMNRvYgjeQSBeMc1ZG/tA47EwfduvkuQS8apbkM/lpLpWsaCeYsXVg==
@@ -3899,6 +3880,13 @@
   resolved "https://registry.yarnpkg.com/@types/stack-utils/-/stack-utils-2.0.3.tgz#6209321eb2c1712a7e7466422b8cb1fc0d9dd5d8"
   integrity sha512-9aEbYZ3TbYMznPdcdr3SmIrLXwC/AKZXQeCf9Pgao5CKb8CyHuEX5jzWPTkvregvhRJHcpRO6BFoGW9ycaOkYw==
 
+"@types/tedious@^4.0.14":
+  version "4.0.14"
+  resolved "https://registry.yarnpkg.com/@types/tedious/-/tedious-4.0.14.tgz#868118e7a67808258c05158e9cad89ca58a2aec1"
+  integrity sha512-KHPsfX/FoVbUGbyYvk1q9MMQHLPeRZhRJZdO45Q4YjvFkv4hMNghCWTvy7rdKessBsmtz4euWCWAB6/tVpI1Iw==
+  dependencies:
+    "@types/node" "*"
+
 "@types/tough-cookie@*":
   version "4.0.5"
   resolved "https://registry.yarnpkg.com/@types/tough-cookie/-/tough-cookie-4.0.5.tgz#cb6e2a691b70cb177c6e3ae9c1d2e8b2ea8cd304"
@@ -6626,6 +6614,11 @@ fb-watchman@^2.0.0:
   dependencies:
     bser "2.1.1"
 
+fdir@^6.2.0:
+  version "6.4.3"
+  resolved "https://registry.yarnpkg.com/fdir/-/fdir-6.4.3.tgz#011cdacf837eca9b811c89dbb902df714273db72"
+  integrity sha512-PMXmW2y1hDDfTSRc9gaXIuCCRpuoz3Kaz8cUelp3smouvfT632ozg2vrT6lJsHKKOF59YLbOGfAWGUcKEfRMQw==
+
 file-entry-cache@^6.0.1:
   version "6.0.1"
   resolved "https://registry.yarnpkg.com/file-entry-cache/-/file-entry-cache-6.0.1.tgz#211b2dd9659cb0394b073e7323ac3c933d522027"
@@ -6728,6 +6721,11 @@ format@^0.2.0:
   resolved "https://registry.yarnpkg.com/format/-/format-0.2.2.tgz#d6170107e9efdc4ed30c9dc39016df942b5cb58b"
   integrity sha512-wzsgA6WOq+09wrU1tsJ09udeR/YZRaeArL9e1wPbFg3GG2yDnC2ldKpxs4xunpFF9DgqCqOIra3bc1HWrJ37Ww==
 
+forwarded-parse@2.1.2:
+  version "2.1.2"
+  resolved "https://registry.yarnpkg.com/forwarded-parse/-/forwarded-parse-2.1.2.tgz#08511eddaaa2ddfd56ba11138eee7df117a09325"
+  integrity sha512-alTFZZQDKMporBH77856pXgzhEzaUVmLCDk+egLgIgHst3Tpndzz8MnKe+GzRJRfvVdn69HhpW7cmXzvtLvJAw==
+
 fraction.js@^4.3.7:
   version "4.3.7"
   resolved "https://registry.yarnpkg.com/fraction.js/-/fraction.js-4.3.7.tgz#06ca0085157e42fda7f9e726e79fefc4068840f7"
@@ -6862,7 +6860,7 @@ glob-parent@^6.0.2:
   dependencies:
     is-glob "^4.0.3"
 
-glob@^10.3.10, glob@^10.4.1:
+glob@^10.3.10:
   version "10.4.5"
   resolved "https://registry.yarnpkg.com/glob/-/glob-10.4.5.tgz#f4d9f0b90ffdbab09c9d77f5f29b4262517b0956"
   integrity sha512-7Bv8RF0k6xjo7d4A/PxYLbUCfb6c+Vpd2/mB2yRDlew7Jb5hEXiCD9ibfO7wpk8i4sevK6DFny9h7EYbM3/sHg==
@@ -7427,7 +7425,17 @@ import-fresh@^3.2.1:
     parent-module "^1.0.0"
     resolve-from "^4.0.0"
 
-import-in-the-middle@^1.11.2, import-in-the-middle@^1.8.1:
+import-in-the-middle@^1.12.0:
+  version "1.12.0"
+  resolved "https://registry.yarnpkg.com/import-in-the-middle/-/import-in-the-middle-1.12.0.tgz#80d6536a01d0708a6f119f30d22447d4eb9e5c63"
+  integrity sha512-yAgSE7GmtRcu4ZUSFX/4v69UGXwugFFSdIQJ14LHPOPPQrWv8Y7O9PHsw8Ovk7bKCLe4sjXMbZFqGFcLHpZ89w==
+  dependencies:
+    acorn "^8.8.2"
+    acorn-import-attributes "^1.9.5"
+    cjs-module-lexer "^1.2.2"
+    module-details-from-path "^1.0.3"
+
+import-in-the-middle@^1.8.1:
   version "1.11.2"
   resolved "https://registry.yarnpkg.com/import-in-the-middle/-/import-in-the-middle-1.11.2.tgz#dd848e72b63ca6cd7c34df8b8d97fc9baee6174f"
   integrity sha512-gK6Rr6EykBcc6cVWRSBR5TWf8nn6hZMYSRYqCcHa0l0d1fPK7JSYo6+Mlmck76jIX9aL/IZ71c06U2VpFwl1zA==