update key transactions with starred (#5849)

* update key transactions with starred

* Update screenshot

Author: andriisoldatenko

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

@@ -26,11 +26,11 @@ When your data reaches high volumes, Sentry begins to automatically prioritize y
 
 <!-- prettier-ignore-start -->
 
-| Prioritize       | Ignore        |
-|------------------|---------------|
-| Latest Release   | Health Checks |
-| Dev Environments |               |
-| Key Transactions |               |
+| Prioritize           | Ignore        |
+|----------------------|---------------|
+| Latest Release       | Health Checks |
+| Dev Environments     |               |
+| Starred Transactions |               |
 
 <!-- prettier-ignore-end -->
 
@@ -44,9 +44,9 @@ While prioritizing data from the latest release, we also take into consideration
 
 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.
 
-### Key Transactions
+### Starred Transactions
 
-Typically, for most projects there are only a few transactions that you really care about. We prioritize [key transactions](/product/performance/transaction-summary/#starring-key-transactions) over others, so you can have more visibility into your important data.
+Typically, for most projects there are only a few transactions that you really care about. We prioritize [starred transactions](/product/performance/transaction-summary/#starring-key-transactions) over others, so you can have more visibility into your important data.
 
 ### Health Checks