diff --git a/docs/concepts/data-management/event-grouping/index.mdx b/docs/concepts/data-management/event-grouping/index.mdx
index 7d5792def0193..85325f3fb0192 100644
--- a/docs/concepts/data-management/event-grouping/index.mdx
+++ b/docs/concepts/data-management/event-grouping/index.mdx
@@ -10,12 +10,10 @@ By default, Sentry will run one of our built-in grouping algorithms to generate
 
 ## Default Error Grouping Algorithms
 
-Each time default error grouping behavior is modified, Sentry releases it as a new version. As a result, modifications to the default behavior do not affect the grouping of existing issues.
+Each time default error grouping behavior is modified, Sentry releases it as a new version, which is only applied to new events going forward. As a result, modifications to the default behavior do not affect the grouping of existing issues.
 
 When you create a Sentry project, the most recent version of the error grouping algorithm is automatically selected. This ensures that grouping behavior is consistent within a project.
 
-To upgrade an existing project to a new error grouping algorithm version, navigate to **Settings > Projects > [project] > Issue Grouping > Upgrade Grouping**. After upgrading to a new error grouping algorithm, you will very likely see new groups being created.
-
 All versions consider the `fingerprint` first, the `stack trace` next, then the `exception`, and then finally the `message`.
 
 To see how an isssue was grouped, go to its **Issue Details** page and scroll down to "Event Grouping Information". There, you'll see if it was grouped by a fingerprint, stack trace, exception, or message.