[latex3-commits] [git/LaTeX3-latex3-latex2e] lthooks-doc-updates: corrected a few typos adnd used US spelling in various places (c4790cfa)

[Frank Mittelbach]

Repository : https://github.com/latex3/latex2e
On branch  : lthooks-doc-updates
Link       : https://github.com/latex3/latex2e/commit/c4790cfa2caf8828a433a2e41463ecedf4f8f9a7

>---------------------------------------------------------------

commit c4790cfa2caf8828a433a2e41463ecedf4f8f9a7
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date:   Tue Jul 27 19:18:05 2021 +0200

    corrected  a few typos adnd used US spelling in various places


>---------------------------------------------------------------

c4790cfa2caf8828a433a2e41463ecedf4f8f9a7
 base/lthooks.dtx | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/base/lthooks.dtx b/base/lthooks.dtx
index d2ba16a9..9508dd8b 100644
--- a/base/lthooks.dtx
+++ b/base/lthooks.dtx
@@ -278,9 +278,9 @@
 %
 %    Using \cs{UseOneTimeHook} several times with the same
 %    \Arg{hook} means that it only executes the first time, for
-%    example, if used in a command that can be called several time
+%    example, if used in a command that can be called several times
 %    then the hook executes only during the first invocation allowing
-%    to use it as an \enquote{inizialization} hook.
+%    to use it as an \enquote{initialization} hook.
 %
 %    \fmi{Last statement is not yet implemented!}
 %
@@ -395,12 +395,12 @@
 %    executed in the order in which it was declared.\footnotemark
 %
 %    If this command is used with a one-time hook the code is only
-%    ever used if we arebefore the hook execution, i.e., in contrast
+%    ever used if we are before the hook execution, i.e., in contrast
 %    to \cs{AddToHook} the code is not executed immediately if the
-%    hook execution already happened---in other words it truely
+%    hook execution already happened---in other words it truly
 %    executes on the next invocation, only there is none in case of a
 %    one-time hook.  This gives you a choice: should my code execute
-%    always or should it only execute only at the point where the
+%    always or should it execute only at the point where the
 %    one-time hook is used and not at all if this is impossible? For
 %    both there are use cases.
 %
@@ -554,7 +554,7 @@
 %   Packages that provide their own package-like interfaces
 %   (Ti\textit{k}Z's \cs{usetikzlibrary}, for example) can use
 %   \cs{PushDefaultHookLabel} and \cs{PopDefaultHookLabel} to set
-%   dedicated labels and emulate \cs{usepackage}-like hook behaviour
+%   dedicated labels and emulate \cs{usepackage}-like hook behavior
 %   within those contexts.
 %
 %   The |top-level| label is treated differently, and is reserved to the
@@ -2195,12 +2195,12 @@
 %       \item [@@_if_disabled:nTF]  returns |false|.
 %     \end{itemize}
 %
-%       The allowed acctions are the same as in the \enquote{not
+%       The allowed actions are the same as in the \enquote{not
 %       existing} state.
 %
 %    \item[declared]
 %
-%       A hook is in this state it is not disabled and was explicity declared (e.g.,
+%       A hook is in this state it is not disabled and was explicitly declared (e.g.,
 %       with \cs{NewHook}). In this case the four tests give the
 %       following results:
 %     \begin{itemize}
@@ -2359,7 +2359,7 @@
 %    (\cs[no-index]{g_@@_\meta{hook}_code_prop}) and the |top-level|
 %    and |next| token lists.  A hook is initialized with
 %    \cs{@@_init_structure:n} the first time anything is added to it.
-%    Inizializing a hook just with \cs{@@_init_structure:n} will not
+%    Initializing a hook just with \cs{@@_init_structure:n} will not
 %    make it usable with \cs{hook_use:n}.
 %    \begin{macrocode}
 \cs_new_protected:Npn \@@_init_structure:n #1
@@ -2690,7 +2690,7 @@
 % \begin{macro}{\@@_normalize_hook_args:Nnn}
 % \begin{macro}{\@@_normalize_hook_rule_args:Nnnnn}
 % \begin{macro}{\@@_normalize_hook_args_aux:Nn}
-%   Standard route for normalising hook and label arguments.  The main
+%   Standard route for normalizing hook and label arguments.  The main
 %   macro does the entire operation within a group so that csnames made
 %   by \cs{@@_make_name:n} are wiped off before continuing.  This means
 %   that this function cannot be used for \cs{hook_use:n}!
@@ -3149,7 +3149,7 @@
 %    for |top-level| because it is hard to reliably know that no code
 %    was added to \cs{@@_toplevel\textvisiblespace\meta{hook}} (granted that
 %    an empty code could be interpreted as that, but then it differs in
-%    behaviour from other labels, in which an empty chunk is still valid
+%    behavior from other labels, in which an empty chunk is still valid
 %    for removal).  Besides, it doesn't make much (if any) sense for
 %    packages to remove |top-level| code.  So here the chunk is just
 %    cleared unconditionally.
@@ -3951,7 +3951,7 @@
 %    \verb=#3= and carry on. We could do a little better and drop
 %    everything for that label since it doesn't matter where we sort
 %    in the empty code. However that would complicate the algorithm a
-%    lot with little gain.\footnote{This also hase the advantage that
+%    lot with little gain.\footnote{This also has the advantage that
 %    the result of the sorting doesn't change which might otherwise
 %    (for unrelated chunks) if we aren't careful.} So we still
 %    unnecessarily try to sort it in and depending on the rules that
@@ -4645,7 +4645,7 @@
   { Unknown~ relationship~ '#3'~
     between~ labels~ '#2'~ and~ '#4'~
     \str_if_eq:nnF {#1} {??} { ~in~hook~'#1' }. ~
-    Perhaps~ a~ missspelling?
+    Perhaps~ a~ misspelling?
   }
   {
     The~ relation~ used~ not~ known~ to~ the~ system.~ Allowed~ values~ are~
@@ -4951,7 +4951,7 @@
 %   \cs{usetikzlibrary} that are wrappers around \cs{input}, so they
 %   inherit the default label currently in force (usually |top-level|,
 %   but it may change if loaded in another package).  To provide a
-%   package-like behaviour also for hooks in these files, we provide
+%   package-like behavior also for hooks in these files, we provide
 %   high-level access to the default label stack.
 %    \begin{macrocode}
 \NewDocumentCommand \PushDefaultHookLabel { m }
@@ -5045,7 +5045,7 @@
 % \begin{macro}[EXP]{\IfHookEmptyTF}
 %   Here we avoid the overhead of \pkg{xparse}, since \cs{IfHookEmptyTF}
 %   is used in \cs{end} (that is, every \LaTeX{} environment).  As a
-%   further optimisation, use \cs{let} rather than \cs{def} to avoid one
+%   further optimization, use \cs{let} rather than \cs{def} to avoid one
 %   expansion step.
 %    \begin{macrocode}
 \cs_new_eq:NN \IfHookEmptyTF \hook_if_empty:nTF