summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html
index 440367ae596..3937df6fbcc 100644
--- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html
+++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-filename.html
@@ -15,8 +15,8 @@ most significant documents will be held in a bunch of files, and
TeX makes no attempt to keep track of files input to the
<em>job</em>. So the user has to keep track, himself &mdash; the only way
is to patch the input commands and cause them to retain details of the
-file name. This is particularly difficult in the case of Plain
-TeX, since the syntax of the <code>\</code><code>input</code> command is so peculiar.
+file name. This is particularly difficult in the case of Plain TeX,
+since the syntax of the <code>\</code><code>input</code> command is so peculiar.
<p/>In the case of LaTeX, the input commands have pretty regular
syntax, and the simplest <a href="FAQ-patch.html">patching techniques</a> can be
used on them.