diff --git a/src/helpers/component_completion.jl b/src/helpers/component_completion.jl
index 7ed5a0217..364b7944e 100644
--- a/src/helpers/component_completion.jl
+++ b/src/helpers/component_completion.jl
@@ -4,10 +4,10 @@ $(TYPEDSIGNATURES)
 Complete missing resolution components using the registry.
 
 This function orchestrates the component completion workflow:
-1. Extract symbols from provided components using `_build_partial_description`
-2. Complete the method description using `_complete_description`
-3. Resolve method with parameter information using `CTBase.Orchestration.resolve_method`
-4. Build or use strategies for each family using `_build_or_use_strategy`
+- Extract symbols from provided components using `_build_partial_description`
+- Complete the method description using `_complete_description`
+- Resolve method with parameter information using `CTBase.Orchestration.resolve_method`
+- Build or use strategies for each family using `_build_or_use_strategy`
 
 # Arguments
 - `discretizer::Union{CTSolvers.DOCP.AbstractDiscretizer, Nothing}`: Discretization strategy or `nothing`
diff --git a/src/solve/dispatch.jl b/src/solve/dispatch.jl
index f02bfcd8b..4dfe71fdb 100644
--- a/src/solve/dispatch.jl
+++ b/src/solve/dispatch.jl
@@ -4,9 +4,9 @@ $(TYPEDSIGNATURES)
 Main entry point for optimal control problem resolution.
 
 This function orchestrates the complete solve workflow by:
-1. Detecting the resolution mode (explicit vs descriptive) from arguments
-2. Extracting or creating the strategy registry for component completion
-3. Dispatching to the appropriate Layer 2 solver based on the detected mode
+- Detecting the resolution mode (explicit vs descriptive) from arguments
+- Extracting or creating the strategy registry for component completion
+- Dispatching to the appropriate Layer 2 solver based on the detected mode
 
 # Arguments
 - `ocp::CTModels.AbstractModel`: The optimal control problem to solve