Merge pull request #3765 from henrikt-ma/cleanup/into-the-future

Use consistent language when talking about scheduling clock ticks

Author: HansOlsson

chapters/synchronous.tex

@@ -344,8 +344,8 @@ \section{Clock Constructors}\label{clock-constructors}
 The result is of base type \lstinline!Clock! that ticks when \lstinline!time! becomes $t_{\mathrm{start}}$, $t_{\mathrm{start}} + \mathit{interval}_{1}$, $t_{\mathrm{start}} + \mathit{interval}_{1} + \mathit{interval}_{2}$, \@\ldots{}
 The clock starts at the start of the simulation $t_{\mathrm{start}}$ or when the controller is switched on.
 At the start of the simulation, \lstinline!previous($\mathit{intervalCounter}$)! = \lstinline!$\mathit{intervalCounter}$.start! and the clocks ticks the first time.
-At the first clock tick $\mathit{intervalCounter}$ must be computed and the second clock tick is then triggered at $\mathit{interval}_{1} = \mathit{intervalCounter}/\mathit{resolution}$.
-At the second clock tick at time $t_{\mathrm{start}} + \mathit{interval}_{1}$, a new value for $\mathit{intervalCounter}$ must be computed and the next clock tick is scheduled at $\mathit{interval}_{2} = \mathit{intervalCounter}/\mathit{resolution}$, and so on.
+At the first clock tick, $\mathit{intervalCounter}$ must be computed and the second clock tick is scheduled $\mathit{interval}_{1} = \mathit{intervalCounter}/\mathit{resolution}$ into the future.
+At the second clock tick at time $t_{\mathrm{start}} + \mathit{interval}_{1}$, a new value for $\mathit{intervalCounter}$ must be computed and the next clock tick is scheduled $\mathit{interval}_{2} = \mathit{intervalCounter}/\mathit{resolution}$ into the future, and so on.
 
 
 \begin{nonnormative}
@@ -388,7 +388,7 @@ \section{Clock Constructors}\label{clock-constructors}
 The $\mathit{interval}$ must be strictly positive ($\mathit{interval} > 0$) of type \lstinline!Real! with \lstinline!unit = "s"!.
 The result is of base type \lstinline!Clock! that ticks when \lstinline!time! becomes $t_{\mathrm{start}}$, $t_{\mathrm{start}} + \mathit{interval}_{1}$, $t_{\mathit{start}} + \mathit{interval}_{1} + \mathit{interval}_{2}$, \@\ldots{}
 The clock starts at the start of the simulation $t_{\mathrm{start}}$ or when the controller is switched on.
-Here the next clock tick is scheduled at $\mathit{interval}_{1}$ = \lstinline!$\mathit{interval}$!.
+Here the second clock tick is scheduled $\mathit{interval}_{1}$ = \lstinline!$\mathit{interval}$! into the future.
 At the second clock tick at time $t_{\mathrm{start}} + \mathit{interval}_{1}$, the next clock tick is scheduled $\mathit{interval}_{2}$ = \lstinline!$\mathit{interval}$! into the future, and so on.
 If $\mathit{interval}$ is a parameter expression, the clock defines a periodic clock.