fixup! docs: design doc for the revamp of the running time calculation

content/docs/reference/design-docs/train-sim-v3/driving-instruction.en.md

@@ -40,6 +40,14 @@ Compiler --> ConcreteDrivingInstruction
 ```
 
 
+{{% pageinfo color="warning" %}}
+After reviewing the design document, the necessity to distinguish between abstract and concrete driving instructions was questioned.
+
+Indeed, it isn't clear whether the limit curves are used for the driving instructions interpretation algorithm.
+If it isn't, the computation of limit curves could be moved inside the [driver behavior module]({{< ref "driver-behavior-modules" >}}).
+{{% /pageinfo %}}
+
+
 ## Interpreting driving instructions
 
 During the simulation, driving instructions are partitioned into 4 sets:
@@ -84,7 +92,7 @@ These sets evolve as follows:
 - when simulation state exceeds an instruction's retirement position, it becomes `RETIRED`
 
 
-#### Overrides
+### Overrides
 
 When an instruction transitions to the `RECEIVED` or `ENFORCED` state, it can disable active instructions
 which match some metadata predicate. There are two metadata attributes which can be relied on for overrides:
@@ -97,7 +105,7 @@ This is required to implement a number of signaling features, as well as stops,
 by the restart instruction.
 
 
-#### Data model
+### Data model