Clean up redundant documentation

Author: cmanallen

docs/product/issues/issue-details/index.mdx

@@ -105,33 +105,23 @@ If you’ve enabled [Session Replay](/product/explore/session-replay/), you’ll
 ## Feature Flags
 There are two types of integrations you can configure to integrate feature flag data into your error events.
 
-The first type is **flag evaluation tracking** within the Sentry SDK. To enable it, update the Sentry SDK's `init` method to include one of our supported feature flag integrations. Support varies by language and by provider. Doing so will give you access to the feature flag table, which shows any flags that were evaluated after the Sentry SDK's initialization and before the error event occurred. You will see rows of (flag, evaluation-result) pairs.
+The first integration type is **flag evaluation tracking** within the Sentry SDK. To enable it, update the Sentry SDK's `init` method to include one of our supported feature flag integrations. Support varies by language and by provider. Doing so will give you access to the feature flag table, which shows any flags that were evaluated after the Sentry SDK's initialization and before the error event occurred. You will see rows of (flag, evaluation-result) pairs. Supported integrations include:
 
-The second type is **feature flag change tracking**. This will enable a timeline of feature flag definition changes on the event and user volume chart on the Issue Details page. These annotations can help you diagnose when a feature flag change is related to a new issue. To enable this type of integration, please visit the documentation page of one of our supported providers:
+* LaunchDarkly ([Python](/platforms/python/integrations/launchdarkly/) and [JavaScript](/platforms/javascript/integrations/launchdarkly/))
+* OpenFeature ([Python](/platforms/python/integrations/openfeature/))
+
+The second integration type is **feature flag change tracking**. This will enable a timeline of feature flag definition changes on the event and user volume chart on the Issue Details page. These annotations can help you diagnose when a feature flag change is related to a new issue. To enable this type of integration, please visit the documentation page of one of our supported providers:
 
 * [LaunchDarkly](/organization/integrations/feature-flag/launchdarkly/#change-tracking-integration)
 
-When both integrations are enabled, you'll also see suspect feature flags highlighted in yellow in the feature flag table. Feature flags are marked as "suspect" if they're modified suspiciously close to the detection of a new issue.
+When both integrations are enabled, you'll see suspect feature flags highlighted in yellow in the feature flag table. Feature flags are marked as "suspect" if they're modified suspiciously close to the detection of a new issue.
 
 ![Feature Flags](./img/feature-flags.png)
 
 A timeline of feature flag changes is displayed in the event and user volume chart. It can help you diagnose when a feature flag change has triggered a new error.
 
 ![Feature Flags](./img/suspect-flags-timeline.png)
 
-Additionally, feature flag definition changes may be flagged as "suspect" if they're modified shortly before an error event occurs. Suspect feature flags are highlighted in yellow within the feature flag table.
-
-![Feature Flags](./img/suspect-flags-table.png)
-
-To enable suspect feature flags and feature flag change annotations, click the "Set Up Integration" button on the feature flag table and follow the instructions. If you need more specific instructions, click the "Read Docs" button.
-
-![Feature Flags](./img/feature-flag-modal.png)
-
-To learn more about enabling feature flag change tracking, visit the documentation for one of the supported providers below.
-
-* [LaunchDarkly](/organization/integrations/feature-flag/launchdarkly/#change-tracking-integration)
-
-
 ## Breadcrumbs
 
 ![Breadcrumbs](./img/issue-breadcrumbs.png)