Changes in 0.4.5 (DOC-99) (#142)

* End Workflow -> Stop Execution

* AI assistance review (mostly updated images)

Author: gorohoroh

ai-assistance/overview.mdx

@@ -48,6 +48,8 @@ Whenever you work with an [action](/workflow-management/actions) that requires w
 When you click **Generate with AI**, use the AI chat window to describe the outcome you want the command or query to achieve, and your LLM will generate it for you:
 ![AI chat window](/images/access-llm-chat.png)
 
+Click **Inject command** in the AI chat window to insert the generated command into the action's **Command** field.
+
 ### Generating code steps
 
 When existing no-code actions aren't a good fit for your workflow, you can use AI assistance to generate JavaScript code for custom code steps.

images/access-llm-assistant.png

@@ -24,7 +24,7 @@ These actions help control the sequence of operations in your workflow and make
 * **Split**: split the workflow into multiple branches based on a [condition](/workflow-management/conditional-branching/).
 * **Loop on Items**: iterates sequentially over a list. Each iteration runs independently and may finish, fail, or pause, but the loop continues with the next item. After all iterations, the loop's final state reflects the outcomes: if any iterations fail, the loop fails; if any pause, the loop pauses until they resume. Workflow-wide limits (timeouts or size limits) can also halt execution.
 * **Delay**: pause workflow execution for a specified time period or until a specific time.
-* **End Workflow**: stop workflow execution. This is useful in [conditional branching](/workflow-management/conditional-branching/) when a branch represents a condition that ends the workflow early. When used inside a loop, this action skips to the next iteration of the loop.
+**Stop Execution**: stops the execution of the current scope. When used inside a loop, this action skips to the next iteration; otherwise, it ends the entire workflow. This is useful in [conditional branching](/workflow-management/conditional-branching/) when a branch represents a condition that ends the workflow early.
 
 ## Get data
 

images/access-llm-chat.png

@@ -73,7 +73,7 @@ Click the **+** icon under the trigger, and a pop-up menu will display a list of
 
 OpenOps provides a total of [120+ actions](/workflow-management/actions/). One way to make sense of them is to classify them by intent:
 * To **get data** for your workflow to process, look at cloud provider integration actions like **AWS**, **Azure** or **Google Cloud**, recommendation provider actions such as **Umbrella**, **Archera** and **AWS Compute Optimizer**, or generic **HTTP** actions.
-* To **control the execution of your workflow**, use actions grouped under **Condition** and **Split**, **Loop on items**, **Delay**, and **End Workflow**.
+* To **control the execution of your workflow**, use actions grouped under **Condition** and **Split**, **Loop on items**, **Delay**, and **Stop Execution**.
 * To **process data obtained in previous steps**, use **Date, List, Math, and Text operations**, **Data mapper** for advanced transformations, and **Code** for transformations that you can't express with available no-code actions.
 * To **request human intervention**, use **Approval** or **Slack**.
 * To **make or request changes to cloud resources**, use cloud provider actions, IaC integration actions like **AWS CloudFormation** and **Terraform**, and the **GitHub** action.