add links to updated quota management docs

src/docs/product/accounts/quotas/index.mdx

@@ -18,7 +18,7 @@ Let’s clarify a few terms to start:
 - **Event** - An event is one instance of you sending data to Sentry. Generally, this data is an error or a transaction.
 - **Issue** - An issue is a grouping of similar error events. Every error event has a set of characteristics called its fingerprint, which is what Sentry uses for grouping. For example, Sentry groups events together when they are triggered by the same part of your code. Learn more in our full [Issue Grouping documentation](/product/data-management-settings/event-grouping/).
 - **Attachment** - Attachments are files uploaded in the same request, such as log files. Unless the option to store crash reports is enabled, Sentry will use these files only to create an event, and then drop them.
-- **Transaction** - A transaction represents a single instance of a service being called to support an operation you want to measure or track, like a page load. Transaction events are grouped by the transaction name.
+- **Transaction** - A [transaction](/product/performance/transaction-summary/#what-is-a-transaction) represents a single instance of a service being called to support an operation you want to measure or track, like a page load. Transaction events are grouped by the transaction name.
 - **Quota** - Your quota is the monthly number of events — errors, attachments, and transactions — that you pay Sentry to track.
 
 ## What Counts Toward My Quota, an Overview
@@ -27,7 +27,7 @@ Sentry completes a thorough evaluation of each event to determine if it counts t
 
 1. **SDK configuration**
 
-   The SDK configuration either allows the event or filters the event out. For more information, see [Manage Your Event Stream](/product/accounts/quotas/manage-event-stream-guide/) or [Filtering Events](/platform-redirect/?next=/configuration/filtering/).
+   The SDK configuration either allows the event or filters the event out. Learn more in [errors](/product/accounts/quotas/manage-event-stream-guide/) and [transactions](/product/accounts/quotas/manage-transaction-quota/) quota management docs or in the [filtering docs for your specific SDK](/platform-redirect/?next=/configuration/filtering/).
 
 2. **SDK sample rate**
 
@@ -194,13 +194,17 @@ Per-key rate limits allow you to set the maximum volume of error events a key wi
 
 For example, you may have a project in production that generates a lot of noise. A rate limit allows you to set the maximum amount of data to “500 events per minute”. Additionally, you can create a second key for the same project for your staging environment, which is unlimited, ensuring your QA process is still untouched.
 
-To set up rate limits, navigate to **[Project] » Client Keys » Configure**. Select an individual key or create a new one, then you’ll be able to define a rate limit as well as view a breakdown of events received by that key. For additional information and examples, see [Rate Limiting in our guide to Manage Your Event Stream](/product/accounts/quotas/manage-event-stream-guide/#6-rate-limiting).
+To set up rate limits, navigate to **[Project] > Settings > Client Keys** and click "Configure"**". Select an individual key or create a new one, then you’ll be able to define a rate limit as well as view a breakdown of events received by that key. For additional information and examples, see [Rate Limiting in our guide to managing your error quota](/product/accounts/quotas/manage-event-stream-guide/#6-rate-limiting).
 
-<Alert>Per-key rate limiting is available only for Business plans.</Alert>
+<Note>
+
+This feature is available only if your organization is on a Business plan.
+
+</Note>
 
 ### Attachment Limits
 
-If you have enabled the storage of crash reports, you may set limits for the maximum number of crash reports that will be stored per issue. To set up these limits, use the slider in the "Store Native Crash Reports" option for your organization's **Security and Privacy Settings**.
+If you have enabled the storage of crash reports, you may set limits for the maximum number of crash reports that will be stored per issue. To set up these limits, use the slider in the "Store Native Crash Reports" option in your organization's "Security & Privacy" settings.
 
 ## Inbound Filters {#inbound-data-filters}
 
@@ -216,35 +220,43 @@ Inbound filters include:
 - From specific release versions of your code
 - From certain IP addresses.
 
-Explore these by navigating to **[Project] » Project Settings » Inbound Filters**. Commonly-set filters are discussed here for your quick reference. For additional information and examples, see [Inbound Data Filters in our guide to Manage Your Event Stream](/product/accounts/quotas/manage-event-stream-guide/#3-inbound-data-filters). Commonly-set filters include:
+Explore these by navigating to **[Project] > Settings > Inbound Filters**. Commonly-set filters are discussed here for your quick reference. For additional information and examples, see [Inbound Data Filters in our guide to managing your error quota](/product/accounts/quotas/manage-event-stream-guide/#3-inbound-data-filters). Commonly-set filters include:
 
 ### IP Filters
 
-If you have a rogue client, Sentry supports blocking an IP from sending data. Navigate to **[Project] » Project Settings » Inbound Filters** to add the IP addresses (or subnets) to **Filter errors from these IP addresses**.
+If you have a rogue client, Sentry supports blocking an IP from sending data. Navigate to **[Project] > Settings > Inbound Filters** to add the IP addresses (or subnets) in the "IP Addresses" field.
 
 ### Filter by Release
 
-<Alert level="info">Filter by release is available on the Business plan.</Alert>
+<Note>
+
+This feature is available only if your organization is on a Business plan.
+
+</Note>
 
-If you discover a problematic release causing excessive noise, Sentry supports ignoring all events from that release. Navigate to **[Project] » Project Settings » Inbound Filters**, then add the releases to **Filter errors from these releases**.
+If you discover a problematic release causing excessive noise, Sentry supports ignoring all events from that release. Navigate to **[Project] > Settings > Inbound Filters**, then add the releases to the "Releases" field
 
 ### Filter by Error Message
 
-<Alert level="info">
-  Filter by error message is available on the Business plan.
-</Alert>
+<Note>
+
+This feature is available only if your organization is on a Business plan.
 
-Sentry supports filtering out a specific or certain kind of error as well. Navigate to **[Project] » Project Settings » Inbound Filters**, then add the error message to **Filter errors by error message**.
+</Note>
+
+Sentry supports filtering out a specific or certain kind of error as well. Navigate to **[Project] > Settings > Inbound Filters**, then add the error message to the "Error Message" field.
 
 ### Filter by Issue
 
-<Alert level="info">
-  Delete and Discard is available on the Business plan.
-</Alert>
+<Note>
+
+This feature is available only if your organization is on a Business plan.
+
+</Note>
 
 When you are unable to take immediate action on an issue, but it continues to occur, Sentry supports deleting and discarding that issue, which you can do from the **Issue Details** page. Navigate to the issue you would like to filter, click on the drop-down menu next to the bin icon, and select “Delete and discard future events”. This setting deletes most data associated with the issue and filters out new matching events before they count against your quota.
 
-You can view and restore previously discarded issues by navigating to **[Project] » Project Settings » Inbound Filters » Discarded Issues**.
+You can view and restore previously discarded issues by navigating to the "Discarded Issues" tab of **[Project] > Settings > Inbound Filters**.
 
 ## Spike Protection
 

src/docs/product/accounts/quotas/manage-transaction-quota.mdx

@@ -5,7 +5,7 @@ sidebar_order: 20
 description: "Learn how to use the tools Sentry provides to control the type and amount of transactions that are monitored."
 ---
 
-In most cases, sending all transaction events to Sentry would generate more performance data than you might find useful and might use up your transactions quota too quickly. Sentry provides tools to control the _type_ and _amount_ of transactions that are monitored. This allows you to have transaction data that's actionable and meaningful, and to manage your quota. Applying the proper SDK configuration is an iterative and on-going process, but these tips will show you how to best use Sentry's tools to get the most out of your transaction events.
+In most cases, sending all [transaction](/product/performance/transaction-summary/#what-is-a-transaction) events to Sentry would generate more performance data than you might find useful and might use up your transactions quota too quickly. Sentry provides tools to control the _type_ and _amount_ of transactions that are monitored. This allows you to have transaction data that's actionable and meaningful, and to manage your quota. Applying the proper SDK configuration is an iterative and on-going process, but these tips will show you how to best use Sentry's tools to get the most out of your transaction events.
 
 ## 1. SDK Filtering: beforeSend
 

src/docs/product/issues/index.mdx

@@ -10,7 +10,13 @@ The **Issues** page displays information about errors in your application. Filte
 
 ![Issues homepage](issues-homepage.png)
 
-A typical application sends a large number of events to Sentry. You can think of an <SandboxLink scenario="oneIssue" projectSlug="react">issue</SandboxLink> as a single bug or problem with your app. To make them manageable, we group similar events into issues based on the event stack trace and other information. This grouping of events into issues allows you to see how frequently a problem is happening and how many users it's affecting.
+A typical application sends a large number of events to Sentry. You can think of an <SandboxLink scenario="oneIssue" projectSlug="react">issue</SandboxLink> as a single bug or problem with your app. To make them manageable, we [group similar error events into issues](/product/data-management-settings/event-grouping/) based on the event stack trace and other information. This grouping of events into issues allows you to see how frequently a problem is happening and how many users it's affecting.
+
+<Note>
+
+Sentry provides tools to control the type and amount of errors that are monitored. Learn more in [Manage Your Error Quota](/product/accounts/quotas/manage-event-stream-guide/).
+
+</Note>
 
 For each issue, the page displays:
 

src/docs/product/performance/transaction-summary.mdx

@@ -20,7 +20,7 @@ Learn more about setting transaction names in our [SDK documentation](/platform-
 
 </Note>
 
-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/).
+Learn about how to control the type and amount of transactions you send to Sentry, in [Manage Your Transaction Quota](/product/accounts/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/).
 
 ## Overview