Merge pull request #5934 from toddwest/patch-1

Update wording to clarify the impact of adaptive sampling in agents

src/content/docs/distributed-tracing/enable-configure/language-agents-enable-distributed-tracing.mdx

@@ -12,7 +12,7 @@ redirects:
   - /docs/understand-dependencies/distributed-tracing/enable-configure/enable-distributed-tracing
   - /docs/new-relic-solutions/best-practices-guides/full-stack-observability/best-practices-enable-distributed-tracing
   - /docs/understand-dependencies/distributed-tracing/enable-configure/language-agents-enable-distributed-tracing
----
+--- 
 import clogo from './images/clogo.png'
 
 import gologo from './images/gologo.png'
@@ -159,7 +159,7 @@ For more help finding your traces in the UI:
 
 ## Set up Infinite Tracing (advanced option) [#infinite-tracing] 
 
-Standard distributed tracing for APM agents (above) captures up to 10% of your traces, but if you want us to analyze all your data and find the most relevant traces, you can set up Infinite Tracing. This alternative to standard distributed tracing is available for all APM language agents except C SDK. 
+Standard distributed tracing for APM agents (above) use [adaptive sampling](/docs/distributed-tracing/concepts/how-new-relic-distributed-tracing-works/#trace-origin-sampling) to capture up to 10 traces per minute, but if you want us to analyze all your data and find the most relevant traces, you can set up Infinite Tracing. This alternative to standard distributed tracing is available for all APM language agents except C SDK. 
 
 <Callout variant="tip">
 To learn more about this feature, see [Infinite Tracing](/docs/understand-dependencies/distributed-tracing/infinite-tracing/introduction-infinite-tracing).