feat(docs): Improve docs for dynamic sampling biases. [TET-559] (#5824)

Author: iambriccardo

src/docs/product/data-management-settings/dynamic-sampling/index.mdx

@@ -28,13 +28,23 @@ When your data reaches high volumes, Sentry begins to automatically prioritize y
 
 | Prioritize | Ignore |
 |------------|--------|
-| Latest release | Health checks |
-| Dev environments | |
+| Latest Release | Health Checks |
+| Dev Environments | |
 
 <!-- prettier-ignore-end -->
 
+### Latest Release
+
+When you create a new release, you'll likely want to have more visibility during the early adoption phase. To improve your ability to catch new issues as soon as your release is being adopted, we prioritize data from the latest release.
+
+While prioritizing data from the latest release, we also take into consideration your environment because you might deploy the same release in different environments. If we see this, we'll assume you want to have more visibility for those transactions as well.
+
+### Dev Environments
+
 We prioritize data from development environments because these environments typically generate a relatively small number of transactions compared to your production environments. As a result, to gain meaningful insights during your testing phase, we prioritize transaction data from these environments.
 
+### Health Checks
+
 _Health check_ type transactions, while important for checking the stability of your application, don't have any value for you beyond the task associated with them. They also tend to be high in volume, potentially using up a lot of you quota if retained. To avoid using up your volume on this type of transactions, we ignore these when sampling your data.
 
 ## Dynamic Sampling & SDK Sampling