getsentry · scttcper · Jul 17, 2023 · Jul 14, 2023 · Jul 17, 2023 · Jul 17, 2023
diff --git a/src/docs/product/accounts/early-adopter.mdx b/src/docs/product/accounts/early-adopter.mdx
@@ -19,6 +19,5 @@ Limitations:
 
 - [Issue Status](https://sentry-docs-git-update-beta-test-archiving.sentry.dev/product/issues/states-triage/) tags, including [Escalating Issues](https://sentry-docs-git-update-beta-test-archiving.sentry.dev/product/issues/states-triage/escalating-issues/)
 - [Priority Sort](/product/issues#issue-sort) algorithm improvements
-- [Grouping Breakdown](/product/data-management-settings/event-grouping/grouping-breakdown/)
 - [Issue Reprocessing](/product/issues/reprocessing/)
 - [Span Summary](/product/performance/transaction-summary/#span-summary)
diff --git a/...ta-management-settings/event-grouping/grouping-breakdown/breakdown_level_01.png b/...ta-management-settings/event-grouping/grouping-breakdown/breakdown_level_01.png
diff --git a/...ta-management-settings/event-grouping/grouping-breakdown/breakdown_level_02.png b/...ta-management-settings/event-grouping/grouping-breakdown/breakdown_level_02.png
diff --git a/...ta-management-settings/event-grouping/grouping-breakdown/breakdown_level_03.png b/...ta-management-settings/event-grouping/grouping-breakdown/breakdown_level_03.png
diff --git a/...ent-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_01.png b/...ent-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_01.png
diff --git a/...ent-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_02.png b/...ent-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_02.png
diff --git a/...ent-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_03.png b/...ent-settings/event-grouping/grouping-breakdown/breakdown_sentinels_level_03.png
diff --git a/...cs/product/data-management-settings/event-grouping/grouping-breakdown/index.mdx b/...cs/product/data-management-settings/event-grouping/grouping-breakdown/index.mdx
diff --git a/src/docs/product/data-management-settings/event-grouping/index.mdx b/src/docs/product/data-management-settings/event-grouping/index.mdx
@@ -60,8 +60,6 @@ This grouping usually works well, but two specific situations can throw it off:
 1. Minimized JavaScript source code will destroy the grouping in detrimental ways. To avoid this, ensure that Sentry can access your [Source Maps](/platforms/javascript/sourcemaps/).
 2. Modifying your stack trace by introducing a new level through decorators changes your stack trace, so the grouping will also change. To handle this, many SDKs support hiding irrelevant stack trace frames. For example, the Python SDK will skip all stack frames with a local variable called `__traceback_hide__` set to _True_.
 
-You can also see what events would group together if a larger or smaller amount of stack trace frames were taken into account using the updated [Grouping Breakdown](/product/data-management-settings/event-grouping/grouping-breakdown/) (Early Adopters only).
-
 ### Grouping By Exception
 
 If the stack trace is not available, but exception information is, then the grouping will consider the `type` and `value` of the exception if both pieces of data are present on the event. This grouping is a lot less reliable because of changing error messages.

diff --git a/src/docs/product/data-management-settings/event-grouping/stack-trace-rules.mdx b/src/docs/product/data-management-settings/event-grouping/stack-trace-rules.mdx
@@ -114,7 +114,7 @@ category:telemetry -group
 
 #### Built-in Categories
 
-Frame categorization is heavily used by our newest grouping algorithm, so [if you have it enabled](/product/data-management-settings/event-grouping/grouping-breakdown#enable-the-grouping-breakdown-beta), you can match on a variety of categories, including:
+Frame categorization is heavily used by our newest grouping algorithm. You can match on a variety of categories, including:
 
 - `system` - detected system libraries
 - `std` - detected standard libraries