Update content/docs/reference/design-docs/stdcm/pathfinding_module/conflict_detection/index.en.md

Co-authored-by: Alwenn Charpentier <[email protected]>

Author: eckter

content/docs/reference/design-docs/stdcm/pathfinding_module/conflict_detection/index.en.md

@@ -18,7 +18,7 @@ when it's not restrictive anymore.
 
 The complex part is that we need to do the conflict detection *incrementally*
 Which means that:
-1. When running simulations up to t=x, we need to know all conflicts
+1. When running simulations up to t=x, we need to know all of the conflicts
    that happen before x, *even if they're indirectly caused by a
    signal seen at t > x* down the path.
 2. We need to know the conflicts and resource uses right as they start