ref(perf): Cleanup EA notes on suspect spans (#4709)

Suspect spans GA means the EA notes no longer apply, cleaning these up.

Author: k-fish

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

@@ -61,13 +61,6 @@ Currently, only transaction data — the transaction name and any attributes the
 
 ### Suspect Spans
 
-<Note>
-
-This feature is available only if you're in the Early Adopter program. Features available to Early Adopters are still in-progress and may have bugs. We recognize the irony.
-If you’re interested in being an Early Adopter, you can turn your organization’s Early Adopter status on/off in General Settings. This will affect all users in your organization and can be turned back off just as easily.
-
-</Note>
-
 The transaction summary includes a list of suspect spans that correspond to where most of the time in a transaction is spent. By default, we sort spans by the total exclusive time. When you click the "Example Transaction" event, it takes you directly to the span in question.
 
 ### Suspect Tags
@@ -90,7 +83,6 @@ This table will show you all related issues. In other words, any errors that are
 
 The sidebar contains helpful supplementary information about this transaction's [User Misery](/product/performance/metrics/#user-misery), [Apdex](/product/performance/metrics/#apdex), [Throughput](/product/performance/metrics/#throughput-total-tpm-tps), [Latency](/product/performance/metrics/#latency), and more. You'll also find a Tag Summary (facet map) for a list of common tags related to this transaction.
 
-
 ## Web Vitals
 
 Frontend transactions will have a "Web Vitals" tab. Clicking on the tab will take you to the [Web Vitals page](/product/performance/web-vitals), where you can see a detailed view of the web vitals associated with this transaction.
@@ -107,20 +99,14 @@ The table in **All Events** tab offers a full list of transactions broken down s
 
 ## Spans
 
-<Note>
-
-This feature is available only if you're in the Early Adopter program. Features available to Early Adopters are still in-progress and may have bugs. We recognize the irony.
-If you’re interested in being an Early Adopter, you can turn your organization’s Early Adopter status on/off in General Settings. This will affect all users in your organization and can be turned back off just as easily.
-
-</Note>
-
 The "Spans" tab displays a list of suspect spans that correspond to where most of the time in a transaction is being spent, and it can help you find spans where performance problems lie.
 
 Choose from one of several [metrics](#metrics) to sort spans and identify different types of problems. Filter spans to only see the span operation type you're interested in.
 
 Clicking on a span will give you more details about the specific span [group](#grouping). You can see the performance of the span over time and see a list of transaction events that contain the span.
 
 ### Exclusive Time
+
 Suspect spans are determined using a span's exclusive time rather than its duration. To calculate a span's exclusive time, take the interval of the span and subtract the intervals of any child spans. The duration of the remaining interval is the span's exclusive time.
 
 In the example below, the exclusive time of each span is highlighted by the darker areas. For example, the `http.server` has an exclusive time of 10ms + 15ms = 25ms.
@@ -148,4 +134,5 @@ Spans with the same operation and description are grouped together into a single
 If you find an important transaction you want to return to, click "Star for Team" in the upper right corner and mark it as a key transaction for any of your teams. This will be saved so you can view this from your [Performance Homepage](/product/performance/). The key transactions you mark will be shared with members of the same team and each team can have up to 100 key transactions.
 
 ### Creating Alerts
+
 To create a metric alert rule for this transaction, click [Create Alert](/product/alerts-notifications/metric-alerts/) at the top of the page.