fix(dynamic-sampling): improved overview and description of dynamic sampling settings

Author: constantinius

docs/organization/dynamic-sampling/index.mdx

@@ -1,24 +1,24 @@
 ---
 title: Dynamic Sampling
 sidebar_order: 30
-description: "Dynamic Sampling allows users make the most of their quota by dynamically determine a target sample rate from the given volumes of the projects."
+description: "Dynamic Sampling allows users make the most of their quota by dynamically sample events from the overall volume."
 ---
 
-
 ## Overview
 
-Dynamic Sampling provides a benefit to organizations with project of varying event volumes. It aims to provide a representative set of samples for events. High volume projects are sampled at a lower rate, while low volume projects are sampled at a higher rate, so that each has a similar set of significant events to investigate.
-
-## Sampling mode
-
-The sampling mode can be set at the organization level. This will apply to all projects within the organization. The available options are:
+When you are dealing with projects that generate high volumes of events, your quotas might be consumed quickly. Additionally, high volume projects will eat up a bigger portion of it, leaving less for other projects.
 
-*   **`organization`**: This is the default setting. It means that the sample rate is determined automatically at the organization level. This mode is also called "automatic", as the individual project sample rates are calculated by the volume of events in the project.
+Many events may be redundant or not useful for debugging. Dynamic Sampling allows you to make the most of your quota by dynamically determining a target sample rate from the given volumes of the projects.
 
-    When set to this mode, the project specific sample rates are continuously recalibrated, depending on the relative volumes of the projects.
+When you use Dynamic Sampling, your projects within an organization are sampled according to their event volumes of the past period. Higher volume projects are sampled at a lower rate, while lower volume projects are sampled at a higher rate or not sampled at all. This way, each project has a similar set of significant events to investigate, granting more visibility to the spans that actually matter.
 
-* **`project`**: This means that the sample rate is configured at the project level. This is useful if you want to have specific sample rates for different projects.
+A sample rate is a percentage from 0% (no events are passed on) to 100% (all events are passed on). 
 
+## Modes
 
+When you are using Dynamic Sampling for a specific organization, you can set the mode in which it operates. You can either choose the manual mode or the automatic mode:
 
+    * **`automatic`**: This is the default setting and it means that the sample rate for each project in the organization determined automatically. When you chose this mode, the project sample rates are calculated according to the relative volumes of the projects so that the projected sampled events fill organization quota, boosting low volume projects. This recalibration happens in regular intervals.
+    When you set the mode to `automatic`, any manually set project sample rates are overridden.
 
+    * **`manual`**: In this mode, you can specifically set the sample rate for each project in the organization. This mode is useful when you want to have exact control over the sample rates of your projects. In this mode, no automatic recalibration happens.