From 1a27b856d548737ea824e9f09404c3d44ef9c933 Mon Sep 17 00:00:00 2001
From: Luca Forstner <luca.forstner@sentry.io>
Date: Wed, 22 Jun 2022 15:34:10 +0200
Subject: [PATCH] Reword traces sampling options

---
 src/docs/sdk/performance/dynamic-sampling-context.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/docs/sdk/performance/dynamic-sampling-context.mdx b/src/docs/sdk/performance/dynamic-sampling-context.mdx
index a1c6b82f75..59a7eab235 100644
--- a/src/docs/sdk/performance/dynamic-sampling-context.mdx
+++ b/src/docs/sdk/performance/dynamic-sampling-context.mdx
@@ -10,7 +10,7 @@ Anything that sounds fishy probably is.
 
 </Alert>
 
-Until now, traces sampling was only done through a `traces_sample_rate` option in the SDKs.
+Until now, traces sampling was only done through the <Link to="/sdk/performance/#tracessamplerate">`tracesSampleRate`</Link> or <Link to="/sdk/performance/#tracessampler">`tracesSampler`</Link> options in the SDKs.
 This has quite a few drawbacks for users of Sentry SDKs:
 
 - Changing the sampling rate involved either redeploying applications (which is problematic in case of applications that are not updated automatically, i.e., mobile apps or physically distributed software) or building complex systems to dynamically fetch a sampling rate.