Description: Fix spelling errors found by lintian
Author: Carsten Leonhardt <leo@debian.org>
Last-Update: 2018-11-29

--- a/pstoimg.pin
+++ b/pstoimg.pin
@@ -1818,7 +1818,7 @@
 =head1 BUGS
 
 This is a major enhancement release, so there may be a few bugs. As
-the user inteface changed a bit, some of your tools that were using
+the user interface changed a bit, some of your tools that were using
 pstoimg may not work any more. 
 
 Please report bugs to latex2html@tug.org, stating the (debug) output
--- a/texexpand.pin
+++ b/texexpand.pin
@@ -87,7 +87,7 @@
 #     has to be on a separate line.
 # 11. Everything behind a `%' that isn't preceded by a `\' is regarded as
 #     a comment, i.e. it is printed but not interpreted.
-# 12. If any command listed in 10. is preceded by an occurence of `\verb' or
+# 12. If any command listed in 10. is preceded by an occurrence of `\verb' or
 #    `\latex' then it is NOT interpreted. This crashes on lines like this:
 #        blah blah \verb+foo foo+ \input{bar} % bar won't be loaded!
 # 13. Packages provided via \usepackage are handled the same way as
@@ -603,7 +603,7 @@
 #     => $active false, $mute false
 #
 # Any environment may extend over several include files.
-# Any environement except verbatim and latexonly may have its
+# Any environment except verbatim and latexonly may have its
 # opening or closing tag on different input levels.
 # The comment and verbatim environments cannot be nested, as
 # is with LaTeX.
--- a/texexpand.1
+++ b/texexpand.1
@@ -242,7 +242,7 @@
 11. Everything behind a `%\*(R' that isn't preceded by a `\e\*(R' is regarded as
 a comment, i.e. it is printed but not interpreted.
 .PP
-12. If any command listed in 10. is preceded by an occurence of `\everb\*(R' or
+12. If any command listed in 10. is preceded by an occurrence of `\everb\*(R' or
 `\elatex\*(R' then it is \s-1NOT\s0 interpreted. This crashes on lines like this:
 blah blah \everb+foo foo+ \einput{bar} % bar won't be loaded!
 .PP
@@ -296,7 +296,7 @@
 \&=> $active false, $mute false
 .Ve
 Any environment may extend over several include files.
-Any environement except verbatim and latexonly may have its
+Any environment except verbatim and latexonly may have its
 opening or closing tag on different input levels.
 The comment and verbatim environments cannot be nested, as
 is with LaTeX.
