Fix terminate concurrency mode description

_docs/products/configure-product-settings.md

@@ -250,7 +250,7 @@ Configure the promotion behavior when multiple promotions are triggered for the
 1. Click the **Promotion Concurrency** tab.
 1. Select one of the options:
     1. **Queue releases**: Start the new release only after the currently active release is completed.  
-    1. **Terminate release**: Terminate the currently active release and start the new release.
+    1. **Terminate release**: If the new release is promoting to an environment with an ongoing promotion, terminate the currently active release and start the new release.
 
 
 {% include

_docs/products/promotion-concurrency.md

@@ -15,10 +15,7 @@ By managing concurrency per product, teams can prevent deployment conflicts, red
 
 
 ##### Why use promotion concurrency?
-* **Improved reliability**  
-  Ensures that each release completes before the next one begins, preventing conflicts and incomplete deployments.
-* **Operational consistency**  
-  Ensures that ongoing releases are not abruptly terminated, preserving deployment stability.
+Adopt the promotion strategy that best matches the product. Always promote the latest changes for products in development, while enforcing sequential promotions for production environments ensuring that releases to production are not terminated abruptly.
 
 ##### Where can you configure promotion concurrency for products? 
 In **Product > Settings > Promotion Concurrency**.
@@ -37,15 +34,18 @@ In **Product > Settings > Promotion Concurrency**.
 When a promotion starts for a product, it follows one of two concurrency policies:
 
 ### Queue releases (default)
-With this policy, new releases are queued and wait until the ongoing release completes execution.
+With the queue concurrency policy, new releases are queued and wait for the ongoing release to complete execution.  
 * If a release is already in progress, the new release enters a **QUEUED** state.
 * The new release starts automatically once all previous releases reach a final state: successful, failed, terminated, or error.
 * The default predefined queue limit for pending releases is 50 releases, ensuring releases do not accumulate indefinitely.
-* If the release queue exceeds the limit for pending releases, older releases are terminated in order from first to last (configurable).
+* If the release queue exceeds the limit for pending releases, older releases are terminated first.
 
 ### Terminate releases
-The second concurrency policy is to terminate releases. With this policy, when a new release is created, the ongoing release is automatically terminated.  
-With this policy, only one release is active for a product at any one time. 
+With the terminate concurrency policy, ongoing releases are terminated when a new release is created for the same product and environment.
+* If a new release promotes to the same environment as an active release, the active release is automatically terminated to allow the new one to proceed.  
+  For example, if the ongoing release is currently promoting to `staging` and the new release also advances to `staging`, the ongoing release is terminated.
+* Only one release can be active for a product at any given time.
+
 
 
 ## Related articles

_docs/promotions/product-promotion-props.md

@@ -95,7 +95,7 @@ Manage this by configuring the behavior for concurrent promotions.
   The new promotion will wait until the current one completes before starting.
 
 * **Terminate active promotion**  
-  The current promotion will be stopped immediately, and the new promotion will begin.
+  If the new promotion targets the same environment being currently updated, the current promotion is terminated immediately, and the new promotion will begin.
 
 For details, see [Configuring promotion concurrency for products]({{site.baseurl}}/docs/products/promotion-concurrency/).