fix(dsl): fix a few issues in dsl and dsl-reference

Signed-off-by: Gilles Barbier <gilles@infinitic.io>

Author: geomagilles

.DS_Store

@@ -96,16 +96,16 @@ A [workflow](#workflow) serves as a blueprint outlining the series of [tasks](#t
 
 #### Properties
 
-| Name | Type | Required | Description|
-|:--|:---:|:---:|:---|
-| document | [`document`](#document) | `yes` | Documents the defined workflow. |
-| input | [`input`](#input) | `no` | Configures the workflow's input. |
-| use | [`use`](#use) | `no` | Defines the workflow's reusable components, if any. |
-| do | [`map[string, task][]`](#task) | `yes` | The [task(s)](#task) that must be performed by the [workflow](#workflow). |
+| Name |               Type                | Required | Description|
+|:--|:---------------------------------:|:---:|:---|
+| document |      [`document`](#document)      | `yes` | Documents the defined workflow. |
+| input |         [`input`](#input)         | `no` | Configures the workflow's input. |
+| use |           [`use`](#use)           | `no` | Defines the workflow's reusable components, if any. |
+| do |    [`map[string, task`](#task)    | `yes` | The [task(s)](#task) that must be performed by the [workflow](#workflow). |
 | timeout | `string`<br>[`timeout`](#timeout) | `no` | The configuration, if any, of the workflow's timeout.<br>*If a `string`, must be the name of a [timeout](#timeout) defined in the [workflow's reusable components](#use).* |
-| output | [`output`](#output) | `no` | Configures the workflow's output. |
-| schedule | [`schedule`](#schedule) | `no` | Configures the workflow's schedule, if any. |
-| evaluate | [`evaluate`](#evaluate) | `no` | Configures runtime expression evaluation. |
+| output |        [`output`](#output)        | `no` | Configures the workflow's output. |
+| schedule |      [`schedule`](#schedule)      | `no` | Configures the workflow's schedule, if any. |
+| evaluate |      [`evaluate`](#evaluate)      | `no` | Configures runtime expression evaluation. |
 
 #### Document
 
@@ -588,13 +588,13 @@ Allows workflows to iterate over a collection of items, executing a defined set
 
 ##### Properties
 
-| Name | Type | Required | Description|
-|:--|:---:|:---:|:---|
-| for.each | `string` | `no` | The name of the variable used to store the current item being enumerated.<br>Defaults to `item`. |
-| for.in | `string` | `yes` | A [runtime expression](dsl.md#runtime-expressions) used to get the collection to enumerate. |
-| for.at | `string` | `no` | The name of the variable used to store the index of the current item being enumerated.<br>Defaults to `index`. |
-| while | `string` | `no` | A [runtime expression](dsl.md#runtime-expressions) that represents the condition, if any, that must be met for the iteration to continue. |
-| do | [`task`](#task) | `yes` | The task to perform for each item in the collection. |
+| Name |             Type             | Required | Description|
+|:--|:----------------------------:|:---:|:---|
+| for.each |           `string`           | `no` | The name of the variable used to store the current item being enumerated.<br>Defaults to `item`. |
+| for.in |           `string`           | `yes` | A [runtime expression](dsl.md#runtime-expressions) used to get the collection to enumerate. |
+| for.at |           `string`           | `no` | The name of the variable used to store the index of the current item being enumerated.<br>Defaults to `index`. |
+| while |           `string`           | `no` | A [runtime expression](dsl.md#runtime-expressions) that represents the condition, if any, that must be met for the iteration to continue. |
+| do | [`map[string, task]`](#task) | `yes` | The [task(s)](#task) to perform for each item in the collection. |
 
 ##### Examples
 
@@ -1157,6 +1157,9 @@ Flow Directives are commands within a workflow that dictate its progression.
 | `"end"` | Provides a graceful conclusion to the workflow execution, signaling its completion explicitly. |
 | `string` | Continues the workflow at the task with the specified name |
 
+> [!WARNING]
+> Flow directives may only redirect to tasks declared within their own scope. In other words, they cannot target tasks at a different depth.
+
 ### Lifecycle Events
 
 Lifecycle events are [cloud events](https://github.com/cloudevents/spec) used to notify users and external services about key state changes in workflows and tasks.
@@ -1540,9 +1543,6 @@ updatedAt: '2024-07-26T16:59:57-05:00'
 status: completed
 ```
 
-> [!WARNING] 
-> Flow directives may only redirect to tasks declared within their own scope. In other words, they cannot target tasks at a different depth.
-
 ### External Resource
 
 Defines an external resource.

dsl-reference.md

@@ -241,7 +241,7 @@ Before the workflow starts, the input data provided to the workflow can be valid
 The execution only proceeds if the input is valid. Otherwise, it will fault with a [ValidationError (https://serverlessworkflow.io/spec/1.0.0/errors/validation)](dsl-reference.md#error).
 
 2. **Transform Workflow Input**
-Before the workflow starts, the input data provided to the workflow can be transformed to ensure only relevant data in the expected format is passed into the workflow context. This can be done using the top level `input.from` expression. It evaluates on the raw workflow input and defaults to the identity expression which leaves the input unchanged. This step allows the workflow to start with a clean and focused dataset, reducing potential overhead and complexity in subsequent tasks. The result of this expression will set as the initial value for the `$context` runtime expression argument and be passed to the first task.
+Before the workflow starts, the input data provided to the workflow can be transformed to ensure only relevant data in the expected format is passed into the workflow context. This can be done using the top level `input.from` expression. It evaluates on the raw workflow input and defaults to the identity expression which leaves the input unchanged. This step allows the workflow to start with a clean and focused dataset, reducing potential overhead and complexity in subsequent tasks. The result of this expression will set as the initial value for the `$input` runtime expression argument and be passed to the first task.
 
 *Example: If the workflow receives a JSON object as input, a transformation can be applied to remove unnecessary fields and retain only those that are required for the workflow's execution.*