summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html5
1 files changed, 3 insertions, 2 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html
index 1a2720a3b15..4bbeb620fe9 100644
--- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html
+++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-endingroup.html
@@ -16,8 +16,9 @@ and you’ll get the diagnostic.
<p/>TeX itself doesn&rsquo;t tell you where your problem is, but you can
often spot it by looking at the typeset output in a previewer.
Otherwise, you can usually find mismatched braces using an intelligent
-editor (at least <code>emacs</code> and <i>winedt</i> offer this facility).
-However, groups are not <em>only</em> created by matching <code>{</code> with <code>}</code>:
+editor (at least <i>emacs</i> and <i>winedt</i> offer this facility).
+However, groups are not <em>only</em> created by matching
+<code>{</code> with <code>}</code>:
other grouping commands are discussed elsewhere in these FAQs,
and are also a potential source of unclosed group.
<p/><code>\</code><code>begin{&lt;<i>environment</i>&gt;}</code> encloses the environment&rsquo;s body