small typos

Makefile

@@ -102,7 +102,7 @@ doc/memoize.pdf: $(manual-source) $(examples-src) $(PACKAGES.edtx)
 
 
 
-# Maintanence
+# Maintenance
 
 test.tex = $(wildcard test*.tex)
 

advice.edtx

@@ -228,7 +228,7 @@
     % submission is funky, because the run conditions handler actually hacks
     % the standard handling procedure.  Note that if |\begin| is not
     % activated, environments will not be handled, and that the automatic
-    % activation might be deffered.
+    % activation might be deferred.
     %<latex>#1/#2=\begin{run conditions=\advice@begin@rc},
   }%
 }
@@ -564,7 +564,7 @@
         \advice@activate@error@activated{#1}{#2}{Command}{already}%
       }{%
         % We don't recognize the current definition as our own code (despite
-        % the fact that we have surely activated the commmand before, given the
+        % the fact that we have surely activated the command before, given the
         % result of the first safety check).  It appears that someone else was
         % playing fast and loose with the same command, and redefined it after
         % our activation.  (In fact, if that someone else was another instance

collargs.edtx

@@ -557,7 +557,7 @@
 % 
 % \begin{macro}{\collargs@@@}
 %   This macro is where modifier handlers reenter the central loop --- we don't
-%   want modifers to open a group, because their settings should remain in
+%   want modifiers to open a group, because their settings should remain in
 %   effect until the next argument.  Furthermore, modifiers do not trigger
 %   category code fixes.
 \def\collargs@@@#1{%
@@ -1474,7 +1474,7 @@
 % \begin{macro}{\collargs@v}
 %   Verbatim argument.  The code is executed in the group, deploying
 %   |\collargsVerbatim|.  The grouping characters are always set to braces, to
-%   mimick |xparse| perfectly.
+%   mimic |xparse| perfectly.
 \def\collargs@v#1.{%
   \begingroup
   \collargsBraces{{}}%
@@ -2328,7 +2328,7 @@
 }
 \fi
 \def\collargs@make@no@verbatim@char#1{%
-  % The original category code of a characted was stored into
+  % The original category code of a character was stored into
   % |\collargs@cc@|\meta{character code} by |\collargs@make@verbatim|. (We don't
   % use |\collargs@cc|, because we have a number.)
   \ifcsname collargs@cc@#1\endcsname

doc/memoize-doc.tex

@@ -800,7 +800,7 @@ \subsection{Memoizing by hand}
 automemoization of the \cs{tikz} command, as explained at the end of
 section~\ref{sec:tut:test}), but that you want to easily memoize selected
 pictures.  You could define a memoized variant of the \cs{tikz} command, as shown
-below (and similary for the environment).  (Note the |%| comment characters in
+below (and similarly for the environment).  (Note the |%| comment characters in
 the definition of |\mmztikz|.  The definition was intentionally broken into
 several lines to remind you that the spaces around the argument of \refcmd{mmz}
 matter.)
@@ -1634,7 +1634,7 @@ \subsection{When stuff sticks out}
 if you're not bothered by a large extern, you can just use
 \Emph{\refmmz{padding}}, which sets all four sides at once.  By the way, having
 too much padding (almost) never hurts, and as you see, you can use (simple)
-arithmetics in the value of these keys.
+arithmetic in the value of these keys.
 
 \tcbinputexample[.tex][.c4]{
   after title pre={\ (memoization with extra padding)},
@@ -1736,7 +1736,7 @@ \subsection{The final version of your document}
 \end{itemize}
 
 Below, we list several ways of fully disabling Memoize.  You're of course
-already familar with the first two ways, but what's this \refpkg{nomemoize}
+already familiar with the first two ways, but what's this \refpkg{nomemoize}
 package?  The rationale behind this package is that if you want to be
 absolutely sure that there is no trace of memoization in your document (for
 example, see the \refmmz{disable} -- \refmmz{enable} pitfall in
@@ -1887,7 +1887,7 @@ \subsection{Good to know}
   environment normally in your document, or when some macro expands so that it
   produces both \cs{begin}\meta{environment name} and \cs{end}\meta{environment
     name} simultaneously --- so there would be no problem above if
-  |\end{minipage}| occured in the beginning code of \env{sectionbox}.  The idiom
+  |\end{minipage}| occurred in the beginning code of \env{sectionbox}.  The idiom
 presented above is problematic for memoization because at the time \hologo{TeX}
 executes |\begin{sectionbox}|, putting |\begin{minipage}| into the input
     stream, |\end{sectionbox}| is not yet executed and remains as it is.  The
@@ -2169,7 +2169,7 @@ \subsection{Extraction methods and modes}
 Out of the box, Memoize stores memos and externs in a separate directory,
 \code{\meta{document name}.memo.dir}, creating this directory if it does not
 exist.  This behaviour, illustrated in section~\ref{sec:tut:memodir}, is
-trigerred by key \refmmz{memo dir}, which is in effect by default since Memoize
+triggered by key \refmmz{memo dir}, which is in effect by default since Memoize
 version~1.3.0.
 
 It is however worth noting that something rather unusual is happening behind
@@ -2216,7 +2216,7 @@ \subsection{Extraction methods and modes}
 works with the built-in Perl).  Of course, this situation is undesirable in and
 of itself, as it forces the author to fall back to the slower
 \hologo{TeX}-based extraction by issuing
-\code{\refmmz{extract}=\refmmz{extract=tex}}, but note that it will additionaly
+\code{\refmmz{extract}=\refmmz{extract=tex}}, but note that it will additionally
 prevent the execution of the default \refmmz{mkdir command}.  Possible
 workarounds include either undoing the effect of \refmmz{memo dir} by issuing
 \refmmz{no memo dir}, or changing the \refmmz{mkdir command} to a command like
@@ -2348,7 +2348,7 @@ \subsection{From cross-references to the context}
 
 Key \refmmzauto{ref} only works for commands which operate on a single
 reference key.  However, that single key (which must be enclosed in braces) may
-be preceded by optional argumen(s) of any kind.  Extensions to \refcmd{ref},
+be preceded by optional argument(s) of any kind.  Extensions to \refcmd{ref},
 e.g.\ the \pkg{hyperref}'s variant, which accepts an optional |*|, work out of
 the box.  Furthermore, Memoize offers support for cross-referencing commands
 which work on multireferences and reference ranges, such as \pkg{cleveref}'s
@@ -2849,7 +2849,7 @@ \subsubsection{Memoizable design}
 \refcmd{mmzset} command will not work unless surrounded by |\makeatletter| and
 |\makeatother|, as it refers to an internal control sequence containing |@|.
 Well, Memoize offers \refmmz{auto csname}, \refmmz{activate csname} and
-\refmmz{deactivate csname}, so that |@| catagory code manipulations can be
+\refmmz{deactivate csname}, so that |@| category code manipulations can be
 omitted by writing \refcmd{mmzset}\bracestt{\refmmz{deactivate
     csname}|=@poormansbox|}, but still.
 
@@ -4100,7 +4100,7 @@ \subsubsection{Pure memoization}
 surprise here, as we want the effect of memoization and utilization to be the
 same.  In the embellished version, we advertise another way to achieve the same
 effect, a way which might be useful for complicated drivers: we simply smuggle
-out the entire cc-memo.  The idea works even when memoization procudes externs;
+out the entire cc-memo.  The idea works even when memoization produces externs;
 in that case, however, the driver also has to say \cs{mmzkeepexternstrue} ---
 conditional \refcmd{ifmmzkeepexterns} decides whether Memoize keeps the externs
 around, in memory, even after shipping them out (but they are always gone at
@@ -4525,7 +4525,7 @@ \subsection{Automemoization}
 it makes sense to separate them out as an independent component of the
 framework, with the added bonus that the system can make sure that an
 invocation of a advised command which does not satisfy the run conditions
-will incur as litte overhead as possible.
+will incur as little overhead as possible.
 
 \paragraph{Bailout handler}
 An automemoized command applies the next-options (set by \refcmd{mmznext}), but
@@ -5202,7 +5202,7 @@ \subsection{Loading and initialization}
 using key \refmmz{extract}; I recommend doing this immediately after loading
 the package.  This key may be invoked with or without a value.  In the latter
 case, Memoize will extract using the package default method
-\refmmz{extract=perl}, unless its has been overriden from
+\refmmz{extract=perl}, unless its has been overridden from
 \reffile{memoize.cfg}.
 
 Furthermore, as \hologo{plainTeX} has no concept of a document body, the text
@@ -5920,7 +5920,7 @@ \subsubsection{Inside the memoization process}
 \begin{doc}{
     cmd={name=mmzExternalizeBox, par=\marg{box}\marg{token register}},
   }
-  This macro is indended to be called by memoization drivers to produce an
+  This macro is intended to be called by memoization drivers to produce an
   extern page.  The given \meta{box} is dumped into the document as a separate
   extern page, while the \meta{token register} receives the cc-memo extern
   inclusion code.
@@ -5977,7 +5977,7 @@ \subsubsection{Inside the memoization process}
   defined to include the extern file into the document.  However, it sometimes
   makes sense to execute the cc-memo contents immediately after memoization;
   for example, if memoization produces several externs, intricately integrated
-  into the surrouding environment, it might be cumbersome to replicate their
+  into the surrounding environment, it might be cumbersome to replicate their
   typesetting both in the memoizing compilation and in the cc-memo code ---
   easier to build up the cc-memo code and execute it right after memoization.
   This is why Memoize, just before executing the contents of \refmmz{after
@@ -6640,7 +6640,7 @@ \subsubsection{Perl- and Python-based extraction}
     using \hologo{TeX}-based extraction, externalization using Memoize is
     extremely fast compared to the \TikZ's externalization library.  Adding
     the regular compilation time of one minute to the above numbers, we arrive
-    at the maximum externalization time of about two minues, whereas my
+    at the maximum externalization time of about two minutes, whereas my
     estimate for the production of all 160 externs using \TikZ's
     externalization would be an \emph{hour} or more.
   \item The Python script cannot extract externs out of PDFs created without
@@ -6901,7 +6901,7 @@ \subsubsection{The clean-up scripts}
     }
     When given this option, the script removes \emph{all} memos and externs
     belonging to the document, not just the stale ones, i.e.\ it effectively
-    ignores the occurences of \refcmd{mmzUsedCMemo} and friends in the \dmmz
+    ignores the occurrences of \refcmd{mmzUsedCMemo} and friends in the \dmmz
     file.
   \end{doc}
   \begin{doc}{
@@ -7263,7 +7263,7 @@ \subsubsection{Package Advice}
 
   As the advice is normally automatically activated upon declaration with
   \refmmz{auto}, explicit activation is rarely needed, but see \refmmz{auto'}.
-  The effect of these keys under the deffered activation regime is described in
+  The effect of these keys under the deferred activation regime is described in
   \refmmz{activation}.
 
   Note that I sometimes speak of (de)activating a command, and sometimes of
@@ -8005,7 +8005,7 @@ \subsubsection{Package Advice}
   This command collects the arguments in the format expected by \refcmd{tikz}, and
   executes macro \refcmd{AdviceInnerHandler} with the collected arguments given
   as a single braced argument.  The collector supports both the group and the
-  semicolor invocation of |\tikz|, i.e.\ both |\tikz{...}| and |\tikz...;|.
+  semicolon invocation of |\tikz|, i.e.\ both |\tikz{...}| and |\tikz...;|.
 
   This command is only available upon |\input|ting file
   \docaux{file}{advice-tikz.code.tex}.
@@ -8949,7 +8949,7 @@ \subsubsection{Package CollArgs}
 collect |[{]}]| with \refcmd{CollectArguments}|[|\refmmz{verbatim}|]{o}|, we
 will get |{| (and most likely an error, as well), because in the
   \refmmz{verbatim} mode, braces do not have their grouping function.  Using
-  the \refmmz{verb} mode solves the problem: occuring within braces, the first
+  the \refmmz{verb} mode solves the problem: occurring within braces, the first
   |]| is ``invisible'' to \refcmd{CollectArguments}|[|\refmmz{verb}|]|, so the
 optional argument is correctly recognized as ending at the second |]|.
 
@@ -9654,7 +9654,7 @@ \subsection{Troubleshooting}
   combination with the paranoid \docref{openout_any} setting (which is the
   default).
 
-  If the source of the error remains a mistery, I suggest inspecting the
+  If the source of the error remains a mystery, I suggest inspecting the
   following sources of information, to help you with your investigation:
   \begin{itemize}
   \item Can you can run the extraction script by hand?  Open the terminal, go

doc/memoize-extract.1.md

@@ -121,7 +121,7 @@ values of these variables by executing '**kpsewhich** -var-value=openin_any' and
 
 **11**
 : An error also reported back to the compilation when given option
-  **\--format**. Currently, either: (i) a currupted document PDF, or (ii)
+  **\--format**. Currently, either: (i) a corrupted document PDF, or (ii)
   a kpathsea permission error.
 
 Other exit codes are as produced by the underlying scripting language (Perl of

memoize.edtx

@@ -3551,7 +3551,7 @@
 \edef\memoizeresetatcatcode{\catcode`\noexpand\@\the\catcode`\@\relax}%
 \catcode`\@=11
 \mmzset{%
-  % Advise macro |\entry| occuring in |.bbl| files to collect the entry,
+  % Advise macro |\entry| occurring in |.bbl| files to collect the entry,
   % verbatim. |args|: |m| = citation key, |&&{...}u| = the entry, verbatim,
   % braced --- so |\blx@bbl@entry| will receive two mandatory arguments.
   auto=\blx@bbl@entry{