diff --git a/src/platforms/common/performance/index.mdx b/src/platforms/common/performance/index.mdx
index a2425a9b25320..ae484f48ee977 100644
--- a/src/platforms/common/performance/index.mdx
+++ b/src/platforms/common/performance/index.mdx
@@ -74,6 +74,16 @@ First, enable tracing and configure the sampling rate for transactions. Set the
The two options are meant to be mutually exclusive. If you set both, will take precedence.
+
+
+
+
+The Native SDK doesn't currently support sampling functions ().
+
+
+
+
+
Learn more about how the options work in Sampling Transactions.
@@ -102,6 +112,16 @@ If you leave your sample rate at `1.0`, a transaction will be sent every time a
+
+
+
+
+The Native SDK doesn't currently support sampling functions ().
+
+
+
+
+
`@sentry/react` exports a `withProfiler` higher order component that can be used to capture React related spans for specific React components.
diff --git a/src/platforms/common/performance/instrumentation/custom-instrumentation.mdx b/src/platforms/common/performance/instrumentation/custom-instrumentation.mdx
index 335f78d6b0c46..f2465c3729b91 100644
--- a/src/platforms/common/performance/instrumentation/custom-instrumentation.mdx
+++ b/src/platforms/common/performance/instrumentation/custom-instrumentation.mdx
@@ -37,16 +37,6 @@ To capture transactions customized to your organization's needs, you must first
-
-
-
-
-Performance monitoring is still an experimental, work-in-progress feature, and its API may be unstable. It may also have bugs. Feedback is appreciated, and should be submitted as an issue in the repository linked on the right side of this page.
-
-
-
-
-
To instrument certain regions of your code, you can create transactions to capture them.