Content qa

_data/argohub-home-content.yml

@@ -82,8 +82,6 @@
   links:
     - title: About promotions
       localurl: /gitops/promotions/promotions-overview/
-    - title: Getting started
-      localurl: /gitops/promotions/getting-started/
     - title: Promotion building blocks
       localurl: /gitops/promotions/promotion-components/
     - title: Promotion setup guidelines

_data/home-content.yml

@@ -50,8 +50,6 @@
   links:
     - title: About promotions
       localurl: /docs/promotions/promotions-overview/
-    - title: Getting started
-      localurl: /docs/promotions/getting-started/
     - title: Promotion building blocks
       localurl: /docs/promotions/promotion-components/
     - title: Promotion setup guidelines

_docs/promotions/create-promotion-sequence.md

@@ -24,8 +24,7 @@ Promotions are a critical part of continuous delivery, enabling you to move chan
 1. [User permissions]({{site.baseurl}}/docs/administration/account-user-management/gitops-abac/)  
   Users need permissions to create Promotion Workflows, configure promotion settings for products, and trigger promotions.
 
-## Tasks
-1. [Create Environments]({{site.baseurl}}/docs/environments/create-manage-environments/#create-environments)  
+1. [Create environments]({{site.baseurl}}/docs/environments/create-manage-environments/#create-environments)  
   Environments define the starting point and destination of promotions.   
   A promotion requires at least two environments:
     * Trigger environment, the source of the changes being promoted
@@ -72,7 +71,6 @@ Promotions are a critical part of continuous delivery, enabling you to move chan
 ## Related articles
 [About promotions]({{site.baseurl}}/docs/promotions/promotions-overview/)  
 [Promotion building blocks]({{site.baseurl}}/docs/promotions/promotion-components/)  
-[Promotion quick starts]({{site.baseurl}}/docs/gitops-quick-start/create-app-ui/)   
 [Trigger promotions]({{site.baseurl}}/docs/promotions/trigger-promotions/)  
 [Tracking product releases]({{site.baseurl}}/docs/promotions/product-releases/)  
 

_docs/promotions/promotion-policy.md

@@ -322,7 +322,8 @@ Deleting a Promotion Policy removes it from all the products and environments it
 
 ## Visualize Promotion Workflows in Releases
 
-When a product is promoted manually or automatically, the promotion mechanism create a release for the product with a unique Release ID. The release provides a graphical representation of the promotion orchestration across the environments defined for it.
+When a product is promoted manually or automatically, the promotion mechanism create a release for the product. The release provides a graphical representation of the promotion orchestration across the environments defined for it.
+
 The visualization includes the Pre- and Post-Action Promotion Workflows within the environments, more specifically, the steps within the workflows.
 
 {% include 

_docs/promotions/promotions-overview.md

@@ -23,20 +23,16 @@ max-width="60%"
 Watch this video to see a promotion in action:  
 {::nomarkdown}<img src=../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Drag-and-drop Promotion](https://www.youtube.com/watch?v=4isYoutmRco&t=1s){:target="\_blank"}
 
-Watch this video to learn how to configure an automated Promotion Flow:  
-{::nomarkdown}<img src=../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Promotion Flows](https://www.youtube.com/watch?v=M8G-AY7FIIg&t=76s){:target="\_blank"}
 
 
-### Why use GitOps promotions in Codefresh?
-Codefresh extends Argo CD’s deployment model fby introducing structured promotion flow with additional context and automation:
+### Why use Codefresh's GitOps promotions?
+Codefresh extends Argo CD’s deployment model by introducing structured promotion flows with additional context and automation:
 
 * **Declarative and version-controlled**  
-  Every promotion is tracked in Git, tied to a commit, ensuring full traceability. Teams can see who approved or triggered a promotion and why.
-
-
+  Every promotion is tracked in Git, tied to a commit, ensuring full traceability. Teams can see who triggered a promotion and why.
 
 * **Context and visibility**  
-While Argo CD manages deployments at the application level, Codefresh GitOps goes beyond this with:
+  While Argo CD manages deployments at the application level, promotions with Codefresh GitOps goes beyond this offering:
   * **Environments**:  
     Represent stages in the software lifecyle, allowing teams to easily track application progression.  
     Read more on [Environments]({{site.baseurl}}/docs/dashboards/gitops-environments/). 
@@ -58,15 +54,15 @@ max-width="65%"
 %}
 
 >**NOTE**  
-GitOps promotions require Runtime version 0.13.4 or higher. Ensure your runtime is updated to access  promotion features.
+Promotions in Codefresh GitOps require Runtime version 0.13.4 or higher. Ensure your runtime is updated to access  promotion features.
 
 
-## Key GitOps promotion entities
-Codefresh  GitOps provides specialized functionality to streamline and automate promotions while maintaining consistency and control without the need for custom scripts. These capabilities enable predictable reusable delivery lifecycles with built-in validations, reducing operational overhead.
+## Key features with GitOps promotions
+Codefresh GitOps provides specialized functionality to streamline and automate promotions while maintaining consistency and control without the need for custom scripts. These capabilities enable predictable and reusable delivery lifecycles with built-in validations, reducing operational overhead.
 
 * **Predefine properties to promote**  
   Control which application properties are promoted to avoid unnecessary changes.  
-  See [Configuring version and promotable properties for Products]({{site.baseurl}}/docs/products/promotion-version-properties/). 
+  See [Configuring version and promotable properties for products]({{site.baseurl}}/docs/products/promotion-version-properties/). 
 
 * **Enforce environment-specific checks**  
   Automate validations, compliance, and performance checks for different environments at different stages of promotions.    
@@ -91,9 +87,12 @@ Use these quick start guides to begin using promotions in Codefresh GitOps:
     * [Multi-environment Promotion Flow]({{site.baseurl}}/docs/gitops-quick-start/multi-env-sequential-flow/)
 
 * **Advanced promotions**  
-    * [Promotion Workflows]({{site.baseurl}}/docs/gitops-quick-start/policy-multi-env-promotion/)
+    * [Promotions with Promotion Workflows]({{site.baseurl}}/docs/gitops-quick-start/policy-multi-env-promotion/)
     * [Environment dependencies]({{site.baseurl}}/docs/gitops-quick-start/dependency-multi-env-promotion/)
 
+Watch this video to learn how to configure an automated Promotion Flow:  
+{::nomarkdown}<img src=../../../images/icons/video-play-icon-blue.svg?display=inline-block>{:/} [Promotion Flows](https://www.youtube.com/watch?v=M8G-AY7FIIg&t=76s){:target="\_blank"}
+
 
 ##### Understand the building blocks
 Learn how promotions work by exploring their core components. See [Promotion building blocks]({{site.baseurl}}/docs/promotions/promotion-components/).