Update docs/organization/dynamic-sampling/index.mdx

Co-authored-by: Jan Michael Auer <[email protected]>

Author: constantinius

docs/organization/dynamic-sampling/index.mdx

@@ -84,7 +84,9 @@ Like in automatic mode, [Dynamic Sampling Priorities](#dynamic-sampling-prioriti
 
 ## Sample Rates for Distributed Traces
 
-It is important to understand how sample rates affect behavior of sampling distributed traces. Sometimes spans originate in one project, but are connected to spans in another project. For example, the sample rate of the frontend project will also affect the sampling of the connected backend application, as the whole span will not propagate.
+It is important to understand how sample rates affect projects connected through distributed traces. Traces can originate in one project and include spans in one ore more other projects. Sentry **always applies the sample rate of the origin project**. For example, the sample rate of your frontend will also affect spans in a connected backend application. At the same time, the backend may start its own traces where the sample rate of the backend project applies.
+
+The numbers shown in the project preview and span breakdowns are always accumulated to the origin project, including all span counts from propagated traces in connected other projects. This gives you a direct view on how many spans will be affected by the sample rates you configure. To see the span counts broken down by the project they belong to click the expand icon to the left of each project in the preview.
 
 {/* TODO: replace with custom graphic */}