Health checks priority docs updates (#6475)

Author: ale-cota

src/docs/product/data-management-settings/dynamic-sampling/dynamic-sampling.png

@@ -32,7 +32,7 @@ When your data reaches high volumes, Sentry begins to automatically prioritize y
 
 <!-- prettier-ignore-start -->
 
-| Prioritize           | Ignore        |
+| Prioritize           | Deprioritize  |
 |----------------------|---------------|
 | Latest Release       | Health Checks |
 | Dev Environments     |               |
@@ -58,7 +58,7 @@ Typically, for most projects there are only a few transactions that you really c
 
 ### 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.
+_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. For this reason, we keep fewer samples of these types of transactions and instead prioritize retaining more samples of your other more valuable transactions.
 
 ## Dynamic Sampling & SDK Sampling