From be03262a49c66864ce59124325a00632cf74f8d8 Mon Sep 17 00:00:00 2001
From: Torsten Sommer <torsten.sommer@3ds.com>
Date: Wed, 14 Aug 2024 09:47:17 +0000
Subject: [PATCH] Add missing blank lines

---
 docs/2_2_common_mechanisms.adoc | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/2_2_common_mechanisms.adoc b/docs/2_2_common_mechanisms.adoc
index b77e1fb6..7ac34dbd 100644
--- a/docs/2_2_common_mechanisms.adoc
+++ b/docs/2_2_common_mechanisms.adoc
@@ -1029,8 +1029,10 @@ Depending on the phase of the solver algorithm, different FMU variables need to
 FMI allows selective retrieval of FMU variables with specific get functions (e.g. <<get-and-set-variable-values,`fmi3Get{VariableType}`>>, <<fmi3GetEventIndicators>>, <<fmi3GetContinuousStateDerivatives>>).
 This enables computation on demand with subsequent calls returning the same value until some set operation requires re-computation.
 
-For example:
+For example,
+
 * during the iteration of an integrator step, only the state derivatives need to be computed, provided the <<output>> of an FMU is not connected, or
+
 * when localizing <<state-event,state events>>, only the computation of event indicators may be required.
 
 Because specific set functions exist (<<get-and-set-variable-values,`fmi3Set{VariableType}`>>, <<fmi3SetTime>>, <<fmi3SetContinuousStates>>), caching algorithms can be applied to reuse already computed values.