summaryrefslogtreecommitdiff
path: root/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html')
-rw-r--r--Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html
index 0cd08e801f5..bb6f760af39 100644
--- a/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html
+++ b/Master/texmf-doc/doc/english/FAQ-en/html/FAQ-dtx.html
@@ -6,8 +6,8 @@
<a href="FAQ-lit.html">literate programming</a> style,
with source and documentation in the
-same file. This format, known as 'doc', in fact originated before the
-days of the LaTeX project as one of the "Mainz" series of
+same file. This format, known as &lsquo;doc&rsquo;, in fact originated before the
+days of the LaTeX project as one of the &ldquo;Mainz&rdquo; series of
packages. The documented sources conventionally have the suffix
<code>.dtx</code>, and should normally be stripped of documentation
before use with LaTeX. Alternatively you can run LaTeX on a
@@ -24,7 +24,7 @@ write <code>.dtx</code> files; the format is explained in
available from CTAN (which comes with skeleton <code>.dtx</code> and
<code>.ins</code> files).
<p>Composition of <code>.dtx</code> files is supported in <i>emacs</i> by
-Matt Swift's <i>swiftex</i> system: it provides a
+Matt Swift&rsquo;s <i>swiftex</i> system: it provides a
<code>doc-tex</code> mode which treats <code>.dtx</code> files rather
better than <a href="FAQ-editors.html">AUC-TeX</a> manages.
<p>Another useful way of generating <code>.dtx</code> files is to write the