fix events and attachments references

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

@@ -45,12 +45,12 @@ This list of strategies for managing your quota is ordered from easiest or least
 
 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.
+- **Event** - An event is one instance of you sending data to Sentry, excluding attachments. Generally, this data is an error or a transaction.
 - **Error** - What counts as an error varies by platform, but in general, if there's something that looks like an exception, it can be captured as an error in Sentry. Sentry automatically captures errors, uncaught exceptions, and unhandled rejections, as well as other types of errors, depending on platform. A grouping of similar errors makes [an issue](/product/issues/).
 - **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.
-- **Attachment** - Attachments are stored additional files, such as config files, log files, or stored mini-dumps that are attached to an error event. Unless the option to store crash reports is enabled, Sentry will use these files only to create an event, and then drop them.
+- **Attachment** - Attachments are stored additional files, such as config files, log files, or stored mini-dumps, that are related to an error event. Unless the option to store crash reports is enabled, Sentry will use these files only to create an event, and then drop them.
 - **Data** - Anything you send to Sentry. This includes, events (errors or transactions), attachments, and event metadata.
-- **Quota** - Your quota is the amount of data (events, transactions, attachments) that you pay Sentry to track.
+- **Quota** - Your quota is the amount of data (errors, transactions, attachments) that you pay Sentry to track.
 
 ## Manage Your Quota - Overview {#what-counts-toward-my-quota-an-overview}
 
@@ -60,7 +60,7 @@ Before completing any of these evaluations, Sentry confirms that each event incl
 
 <Note>
 
-This list is ordered from easiest or least time-consuming to most challenging or potentially time-consuming. This isn't the order in which evaluations take place. 
+This list is ordered from easiest or least time-consuming to most challenging or potentially time-consuming. This isn't the order in which evaluations take place.
 
 </Note>
 

src/docs/product/stats/index.mdx

@@ -8,11 +8,11 @@ description: "Learn about projects and teams across your organization."
 
 The **Stats** page has three tabs: [Usage](#usage-stats), [Issues](#issue-stats), and [Health](#health-stats).
 
-The "Usage" tab shows your organization’s event usage, while also providing a high-level overview of how different projects are using Sentry. The "Issues" tab shows a breakdown of the issues assigned to your team and how they triaged them, whilst the "Health" tab provides an overview of your team’s project health.
+The "Usage" tab shows your organization’s event and attachments usage, while also providing a high-level overview of how different projects are using Sentry. The "Issues" tab shows a breakdown of the issues assigned to your team and how they triaged them, while the "Health" tab provides an overview of your team’s project health.
 
 ## Usage Stats {#usage-stats}
 
-The "Usage" tab shows you the events Sentry has received across your entire organization along with a list of all projects and their consumption of errors, transactions, and attachments. Events fall into one of three categories: _Accepted_, _Filtered_, or _Dropped_. Filtered events are events that were blocked due to your [inbound data filter](/product/data-management-settings/filtering/) rules. Dropped events are ones the system dropped or discarded due to rate limits, quotas, spike protection, or because of invalid data.
+The "Usage" tab shows you the events (errors and transactions) and attachments Sentry has received across your entire organization along with a list of all projects and their consumption of each of those. Your usage falls into one of three categories: _Accepted_, _Filtered_, or _Dropped_. Filtered events and attachments are ones that were blocked due to your [inbound data filter](/product/data-management-settings/filtering/) rules. Dropped events and attachments are ones the system dropped or discarded due to rate limits, quotas, spike protection, or because of invalid data.
 
 You can see which projects have had a recent spike or are the most active and may need more attention. On this page, you can also control the date range that’s displayed, allowing you to focus on a smaller period of time or zoom out for a longer view. The page is designed for org admins, but is available to all team members. This is helpful if a team member who isn't an admin is tasked with reviewing these statistics. Also, this allows team members associated with specific projects to use this page to investigate why their events are being dropped.
 
@@ -26,17 +26,17 @@ With the dropdowns at the top of the page, you can set whether the page displays
 
 ### Usage Cards
 
-The cards on the page provide high-level usage stats about events, including the total number of events for the period, as well as which ones were accepted, filtered, or dropped.
+The cards on the page provide high-level usage stats about events and attachments, including the total number of either for the period, as well as which ones were accepted, filtered, or dropped.
 
 ### Summary Chart
 
-The chart on this page displays a breakdown of events over the selected date range. Depending on the date range that you set the chart to display, each bar in the chart represents a different amount of time or interval. For example, if you set the chart to display seven days, each bar in the chart represents one hour, but if you set it to display 90 days, each bar represents one day. You can also use the “Type” dropdown to set whether the chart shows a cumulative count of events or a daily (or hourly) count.
+The chart on this page displays a breakdown of events and attachments over the selected date range. Depending on the date range that you set the chart to display, each bar in the chart represents a different amount of time or interval. For example, if you set the chart to display seven days, each bar in the chart represents one hour, but if you set it to display 90 days, each bar represents one day. You can also use the “Type” dropdown to set whether the chart shows a cumulative count of events or attachments, or a daily (or hourly) count.
 
 When you set a date range that results in intervals of one day or more, the time zone is displayed in UTC to ensure consistency for users across different time zones. For time periods with intervals of less than 24 hours, the time zone is based on your "Timezone" setting in **User Settings > Account Details**.
 
 ### Project Usage Stats Table
 
-The “Project Usage Stats” table provides insight into per-project usage of your errors, transactions, and attachments over time. The table shows you the total errors, transactions, or attachments. Those events are further broken down into the accepted, filtered, and dropped categories.
+The “Project” table provides insight into per-project usage of your errors, transactions, and attachments over time. The table shows you the total errors, transactions, or attachments. Those are further broken down into the accepted, filtered, and dropped categories.
 
 Each project in the table has individual settings, which you can access from by clicking the settings icon (gear wheel) next to the name of the project. For instance, you might want to go to the project settings so you can limit the quota consumed by its DSNs. Clicking the name of the project takes you to the **Project Details** page.