Replaced depricated note components

Author: Alex Krawiec

docs/product/insights/retention-priorities.mdx

@@ -17,11 +17,11 @@ redirect_from:
 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.
 
@@ -64,11 +64,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.
 
@@ -115,9 +115,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>