Changes

Add missing {} after \ldots

Use \emph when introducing notation (that doesn't seem to deserve \firstuse)

Clean up styling in clocked sample example

Say 'applied to', not 'applied on'

There are also situations where 'applied on' is correct, but I don't think we have any of these in the specification.

Clean up formatting related to 'SolverMethod' and 'solverMethod'

The use \lstinline!SolverMethod! is meant to be a sloppy way of referring to the type defined in ModelicaServices.

Insert some whitespace in synchronous listings

Improve styling in synchronous "Semantics"

Put \@ in front of \ldots{} ending sentence

Add missing \lstinline on 'Clock(1.0)'

Say 'parameter expression' instead of using undefined term 'parametric'

Say 'clock variables' instead of 'Clock-variables'

Turn too long \lstinline into lstlisting

Say 'clock variable', not '\lstinline!Clock! variable'

Use lstlisting instead of \lstinline for complete element

Fix 'if of type' -> 'is of type'

Turn 'Sorting of a simulation model' into non-normative \subsubsection

Add white-space around '<'

Say 'Clocked When-Clause' instead of 'Clocked When Clause'

Use \firstuse when defining clock partitioning terminology

Avoid engineering format of numbers in normal text and fix lexer rule name

Use math where appropriate in description of clock partitioning

Align comments in listings

Say 'nor any', nor 'nor one'

Add missing \lstinline on 'choices'

Say 'may also support', not 'may support also'

Add missing semicolon in listing

Rewrite without use of "we"

Consistent use of white-space around modifier '='

Break some long lines in listings

Remove outdated link

Only link to GitHub repository of MSL

Add space between commas in listing

Add cross references to description of assignment to subscripted array variables

Use definition of 'component expression' in the normal way

Add comment with warning about possible accidental misuse of 'component expression'

Change 'repeated subscripts

Change 'same type of' -> 'same type as'

Remove "plain wrong" statement about sub-clock partition interval

Improve sm (#2735)

* Clarify the merging of connections to multiple outputs.
1. It doesn't make sense to require them to connected to one "input", it makes more sense that they combine as one "source".
2. The merging according to previous section doesn't make sense as an explanation:
* The "v" variable is one and not one per state so it doesn't apply.
* The "v" is not even an "outer output".
* And finally I don't see how the first variant simplifies anything.
* The intermediate algorithm will require a start-value even if we are always in one of the states.
* The extra code is an algorithm, and we generally try to avoid that.
3.  List the exception also for connections.

Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>

Remove new text and add heading to examples as suggested.
Also change comment indentation.

Add missing {} after \ldots

Use \emph when introducing notation (that doesn't seem to deserve \firstuse)

Clean up styling in clocked sample example

Say 'applied to', not 'applied on'

There are also situations where 'applied on' is correct, but I don't think we have any of these in the specification.

Clean up formatting related to 'SolverMethod' and 'solverMethod'

The use \lstinline!SolverMethod! is meant to be a sloppy way of referring to the type defined in ModelicaServices.

Insert some whitespace in synchronous listings

Improve styling in synchronous "Semantics"

Put \@ in front of \ldots{} ending sentence

Add missing \lstinline on 'Clock(1.0)'

Say 'parameter expression' instead of using undefined term 'parametric'

Say 'clock variables' instead of 'Clock-variables'

Turn too long \lstinline into lstlisting

Say 'clock variable', not '\lstinline!Clock! variable'

Use lstlisting instead of \lstinline for complete element

Fix 'if of type' -> 'is of type'

Turn 'Sorting of a simulation model' into non-normative \subsubsection

Add white-space around '<'

Say 'Clocked When-Clause' instead of 'Clocked When Clause'

Use \firstuse when defining clock partitioning terminology

Avoid engineering format of numbers in normal text and fix lexer rule name

Use math where appropriate in description of clock partitioning

Align comments in listings

Say 'nor any', nor 'nor one'

Add missing \lstinline on 'choices'

Say 'may also support', not 'may support also'

Add missing semicolon in listing

Rewrite without use of "we"

Consistent use of white-space around modifier '='

Break some long lines in listings

Remove outdated link

Only link to GitHub repository of MSL

Add space between commas in listing

Add cross references to description of assignment to subscripted array variables

Use definition of 'component expression' in the normal way

Add comment with warning about possible accidental misuse of 'component expression'

Change 'repeated subscripts

Change 'same type of' -> 'same type as'

Remove "plain wrong" statement about sub-clock partition interval

Improve sm (#2735)

* Clarify the merging of connections to multiple outputs.
1. It doesn't make sense to require them to connected to one "input", it makes more sense that they combine as one "source".
2. The merging according to previous section doesn't make sense as an explanation:
* The "v" variable is one and not one per state so it doesn't apply.
* The "v" is not even an "outer output".
* And finally I don't see how the first variant simplifies anything.
* The intermediate algorithm will require a start-value even if we are always in one of the states.
* The extra code is an algorithm, and we generally try to avoid that.
3.  List the exception also for connections.

Co-authored-by: Henrik Tidefelt <henrikt@wolfram.com>

Remove new text and add heading to examples as suggested.
Also change comment indentation.