summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html
diff options
context:
space:
mode:
Diffstat (limited to 'Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html')
-rw-r--r--Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html
index 434e2c018a4..7d7858e1403 100644
--- a/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html
+++ b/Master/texmf-dist/doc/generic/FAQ-en/html/FAQ-plainvltx.html
@@ -2,7 +2,7 @@
<title>UK TeX FAQ -- question label plainvltx</title>
</head><body>
<h3>Should I use Plain TeX or LaTeX?</h3>
-<p/>There&rsquo;s no straightforward answer to this question. Many people swear
+<p/>There&#8217;s no straightforward answer to this question. Many people swear
by Plain TeX, and produce highly respectable documents using it
(Knuth is an example of this, of course). But equally, many people
are happy to let someone else take the design decisions for them,
@@ -12,7 +12,7 @@ accepting a small loss of flexibility in exchange for a saving of
heat, without offering much by way of light; your best bet may be to
find out what those around you are using, and to follow them in the
hope of some support. Later on, you can always switch your
-allegiance; don&rsquo;t bother about it.
+allegiance; don&#8217;t bother about it.
<p/>If you are preparing a manuscript for a publisher or journal, ask them
what markup they want before you
develop your own; many big publishers have developed their own