Say 'conversion specifier'

As suggested by Hans.

Co-authored-by: Hans Olsson <HansOlsson@users.noreply.github.com>

chapters/operatorsandexpressions.tex

@@ -533,8 +533,8 @@ \subsection{Numeric Functions and Conversion Functions}\label{numeric-functions-
 
 The ANSI-C style \lstinline!format! string (which cannot be combined with any of the other named arguments) consists of a single conversion specification without the leading \%.
 It shall not contain a length field specifier, and shall not use `\lstinline!*!' for width and/or precision.
-For all numeric values the type field specifiers `\lstinline!f!', `\lstinline!e!', `\lstinline!E!', `\lstinline!g!', `\lstinline!G!' are allowed.
-For integral values it is also allowed to use the `\lstinline!d!', `\lstinline!i!', `\lstinline!o!', `\lstinline!x!', `\lstinline!X!', `\lstinline!u!', and `\lstinline!c!' type field specifiers (for non-integral values a tool may round, truncate or use a different format if the integer conversion characters are used).
+For all numeric values the conversion specifiers `\lstinline!f!', `\lstinline!e!', `\lstinline!E!', `\lstinline!g!', `\lstinline!G!' are allowed.
+For integral values it is also allowed to use the `\lstinline!d!', `\lstinline!i!', `\lstinline!o!', `\lstinline!x!', `\lstinline!X!', `\lstinline!u!', and `\lstinline!c!' conversion specifiers (for non-integral values a tool may round, truncate or use a different format if the integer conversion specifiers are used).
 
 The `\lstinline!x!'/`\lstinline!X!' formats (hexa-decimal) and \lstinline!c! (character) for \lstinline!Integer! values give results that do not agree with the Modelica grammar.
 \end{semantics}