From 078f6fd0a5cd694512396e779ca796a8abb76740 Mon Sep 17 00:00:00 2001
From: Christophe Geuzaine <cgeuzaine@ulg.ac.be>
Date: Sun, 29 Sep 2013 05:57:34 +0000
Subject: [PATCH]
---
doc/texinfo/gmsh.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/texinfo/gmsh.texi b/doc/texinfo/gmsh.texi
index 75acb832b2..edc45e05f8 100644
--- a/doc/texinfo/gmsh.texi
+++ b/doc/texinfo/gmsh.texi
@@ -986,10 +986,10 @@ parsing of the script file:
@end example
Such @w{@var{expression}s} are used in most of Gmsh's scripting
-commands. When @code{~@{@var{expression-cst}@}} is appended to a string
+commands. When @code{~@{@var{expression}@}} is appended to a string
@var{string}, the result is a new string formed by the concatenation of
@var{string}, @code{_} (an underscore) and the value of the
-@var{expression-cst}. This is most useful in loops (@pxref{Loops and
+@var{expression}. This is most useful in loops (@pxref{Loops and
conditionals}), where it permits to define unique strings
automatically. For example,
@example
--
GitLab