fix(trends): Add a mention of the confidence function (#3480)

Co-authored-by: Fiona <[email protected]>
Co-authored-by: Alberto Leal <[email protected]>

Author: 3 people

src/docs/product/performance/trends.mdx

@@ -9,7 +9,9 @@ From the Performance homepage, you can find the Trends View by toggling the tab
 ![trends Homepage](trend-lists.png)
 
 Trending transactions are calculated first by filtering out transactions with large [throughput](/product/performance/metrics/#throughput-total-tpm-tps) fluctuations, determining the baselines of the two halves of the duration, and calculating their percentage change. Regressions are any percentage changes greater than zero, while improvements are percentage changes less than zero.
-Sentry uses a [t-test](https://academic.oup.com/beheco/article/17/4/688/215960) to compare the before and after periods of the transaction and assign a confidence score. Only high confidence, statistically significant results are shown.
+Sentry uses a [t-test](https://academic.oup.com/beheco/article/17/4/688/215960) to compare the before and after periods of the transaction and assign a confidence score.
+
+This confidence score is unbounded, and by default Sentry shows trends with a high confidence score. To view trends regardless of the confidence score, add `confidence():>0` to the search bar.
 
 For example, looking at a transaction over two weeks with the default [P50](/product/performance/metrics/#average-transaction-duration) baseline, if the first week had a `p(50)=100s`, and the second a `p(50)=110s`, the percentage is `(110/100)-1 = 0.1`. The example transaction had a performance regression of `10%`.