Clarification for calling fmi3UpdateDiscreteStates

docs/2_3_common_states.adoc

@@ -575,9 +575,13 @@ The importer can set a Clock to `fmi3ClockInactive` only if the Clock has the at
 Any Clock active during <<fmi3UpdateDiscreteStates>> must be deactivated by the FMU itself. +
 <<periodic-clock,Periodic Clocks>> must not be active for more than one call of <<fmi3UpdateDiscreteStates>> per <<EventMode>>.
 This restriction does not apply to <<triggered,triggered Clocks>>, nor does it apply to <<aperiodic-clock,aperiodic Clocks>>, for which latexmath:[T_{\mathit{interval}} = 0] can be returned by <<fmi3GetInterval>>. +
-_[The event iteration for handling discontinuities of the continuous part of the FMU should precede handling of time-based Clocks._
-_No further constraints on activations of <<time-based-clock,time-based Clocks>> are defined, e.g. activating at the first instant of super-dense time._
-_If the semantics of some Clocks require any specific treatment, e.g. activation at the same super-dense time instant, only the importer will know and must therefore enforce proper activation of the respective Clocks.]_
+_[The event mode may consist of several super-dense time instants.
+Each super-dense time instant represents a distinct event occurring at the same simulation time.
+If any event corresponding to the continuous part of the FMU is present, its event iteration must be performed during the first super-dense time instant.
+Each super-dense time instant must conclude with a call to <<fmi3UpdateDiscreteStates>>.
+Super-dense time instants that handle <<time-based-clock, time-based Clocks>> are initiated by setting the corresponding Clocks using <<fmi3SetClock>>.
+No further constraints are imposed on the activation of <<time-based-clock, time-based Clocks>> (for example, activation during the first instant of a super-dense time, the order of handling multiple clocks, or handling multiple Clocks within the same super-dense time instant).
+If the semantics of certain Clocks require specific handling—such as simultaneous activation within the same super-dense time instant—this must be ensured by the importer.]_
 
 Function <<fmi3GetClock>>::
 is used to inquire the status of <<Clock,Clocks>>.