Replace <Note> with <Alert>

Author: jan-auer

docs/organization/dynamic-sampling/index.mdx

@@ -14,10 +14,10 @@ This process is applied directly on Sentry's servers, which allows you to config
 
 By analyzing incoming traffic patterns, Dynamic Sampling is able to tailor its decisions to both the actual traffic volume as well as the content of accepted spans. For more details, check out the [Dynamic Sampling Priorities](#dynamic-sampling-priorities) section.
 
-<Note>
+<Alert>
   Dynamic Sampling is available for customers on our latest Enterprise plans,
   starting June, 2024.
-</Note>
+</Alert>
 
 ## Prerequisites
 
@@ -69,12 +69,12 @@ The [project preview](https://sentry.io/orgredirect/organizations/:orgslug/setti
 
 Because project rates continuously change, we recommend that you choose the 24-hour preview to get a more accurate view of your current sample rates for real-time analysis. We recommend the 30-day preview for seeing average sample rates in your billing cycle for long-term planning.
 
-<Note>
+<Alert>
   If you switch from advanced to simple mode, the recalibration process will
   start immediatly and the per-project sample rates will be reset to the
   calculated values. There's no way to restore the manually configured project
   sample rates once you've switched to simple mode.
-</Note>
+</Alert>
 
 ### Advanced Mode
 
@@ -120,12 +120,12 @@ SDK sampling uses a static rate set in the SDK configuration. It’s ideal for o
 
 To give Sentry the fullest, most accurate picture of your application’s health, we recommend sending 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, not stored transactions.
 
-<Note>
+<Alert>
   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>
 
 You can use both Dynamic and SDK Sampling together to further optimize your event volume for your specific use case. For example, you can set a low SDK sample rate to ensure that only a certain percentage of events are sent to Sentry, and then use Dynamic Sampling to adjust the sample rate based on the event volume received by Sentry.
 
@@ -154,11 +154,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 dynamic sampling 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.
 
@@ -181,11 +181,11 @@ When you query a transactions either in [Discover](/product/explore/discover-que
 
 ![Investigation Mode in Discover](./img/investigation-bias-discover.png)
 
-<Note>
+<Alert>
 
 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 creates an investigation rule for the query. Once the rule is successfully created, a notification appears, and the button is replaced with a message showing the investigation is in progress and the amount of time it's been active.