- fix ster description formatting

Signed-off-by: arpechenin <[email protected]>

Author: arpechenin

proposals/separate-standalone-driver/README.md

@@ -25,29 +25,35 @@ Resource availability problems: There's no guarantee the Kubernetes cluster has
 
 Let's take a look at the copy of [hello_world.yaml](hello_world.yaml)  generated by the argo compiler tests.
 
-Execution Order:
-1. entrypoint
-   Type: DAG
-The root DAG represents the entire pipeline run.
-2. root-driver (template: system-dag-driver)
-   Type: Container
-   Purpose: Initializes the root DAG. Creates an MLMD execution for the DAG.
-Outputs:
-execution-id – ID of the DAG execution (created during root-driver execution)
-
-Tasks inside:
-- hello-world-driver (template: system-container-driver)
-  Purpose: Check for the existence of an execution in the cache, if no prepare the MLMD execution of the hello-world container task, and generate the appropriate pod-spec-patch.
-Outputs:
-pod-spec-patch – patch for the system-container-executor pod; inserts the correct image and command for the main container. 
-cached-decision – if true, the next step will be skipped
-- hello-world (template: system-container-executor)
-   Depends on: hello-world-driver.Succeeded
-   Purpose: Executes the hello-world component
-Inputs:
-pod-spec-patch — patch for the pod generated in the previous step
-cached-decision — used as a skip condition
-The system-container-executor template defines the main container that runs the user-defined code.
+**Execution Order:**
+
+1. **entrypoint**  
+   *Type:* DAG  
+   The root DAG represents the entire pipeline run.
+
+2. **root-driver** *(template: system-dag-driver)*  
+   *Type:* Container  
+   *Purpose:* Initializes the root DAG. Creates an MLMD execution for the DAG.  
+   **Outputs:**
+    - `execution-id` – ID of the DAG execution (created during root-driver execution)
+
+   **Tasks inside:**
+
+    - **hello-world-driver** *(template: system-container-driver)*  
+      *Purpose:* Check for the existence of an execution in the cache. If it does not exist, prepare the MLMD execution of the hello-world container task, and generate the appropriate pod-spec-patch.  
+      **Outputs:**
+        - `pod-spec-patch` – patch for the system-container-executor pod; inserts the correct image and command for the main container
+        - `cached-decision` – if true, the next step will be skipped
+
+    - **hello-world** *(template: system-container-executor)*  
+      *Depends on:* `hello-world-driver.Succeeded`  
+      *Purpose:* Executes the hello-world component  
+      **Inputs:**
+        - `pod-spec-patch` — patch for the pod generated in the previous step
+        - `cached-decision` — used as a skip condition
+
+      The `system-container-executor` template defines the main container that runs the user-defined code.
+
 
 Overview of the Argo workflow node structure for the container-driver
 ```yaml