[latex3-commits] [latex3/latex2e] cmd-args: Typos and note on timing (b107f6bd)

[github at latex-project.org]

Repository : https://github.com/latex3/latex2e
On branch  : cmd-args
Link       : https://github.com/latex3/latex2e/commit/b107f6bd8e123af70ba9576160d5f533b232889d

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

commit b107f6bd8e123af70ba9576160d5f533b232889d
Author: PhelypeOleinik <phelype.oleinik at latex-project.org>
Date:   Mon May 22 09:32:08 2023 -0300

    Typos and note on timing


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

b107f6bd8e123af70ba9576160d5f533b232889d
 base/ltcmdhooks.dtx | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/base/ltcmdhooks.dtx b/base/ltcmdhooks.dtx
index 346059c7..27907af6 100644
--- a/base/ltcmdhooks.dtx
+++ b/base/ltcmdhooks.dtx
@@ -87,7 +87,10 @@
 %    \end{description}
 %
 %    The hooks are not physically present before
-%    \verb=\begin{document}= (i.e., using a command in the preamble
+%    \verb=\begin{document}=\footnote{More specifically, they are
+%    inserted in the commands after the \hook{begindocument} hook, so
+%    they are also not present while \LaTeX{} is reading the
+%    \texttt{.aux} file.} (i.e., using a command in the preamble
 %    will never execute the hook) and if nobody has declared any code
 %    for them, then they are not added to the command code ever.  For
 %    example, if we have the following definition
@@ -294,19 +297,19 @@
 % \label{sec:redef-warn}
 %
 % The code in \pkg{ltcmdhooks} does its best to find out how many
-% arguments a given command has, an to insert the appropriate call to
+% arguments a given command has, and to insert the appropriate call to
 % \cs{UseHookWithArguments}, so that the arguments seen by the hook are
 % exactly those grabbed by the command (the hook, after all, is a macro
 % call, so the arguments have to be placed in the right order, or they
 % won't match).
 %
-% When using the package writer interface, as dicussed in
+% When using the package writer interface, as discussed in
 % section~\ref{sec:pkg-author}, to change the position of the hooks in
 % your commands, you are also free to change how the hook code in your
 % command sees its arguments.  When a \hook{cmd} hook is declared with
 % \cs{NewHook} (or \cs{NewHookWithArguments} or other variations of
 % that), it loses its \enquote{generic} nature and works as a regular
-% hook.  This means that if you may choose to declare it without
+% hook.  This means that you may choose to declare it without
 % arguments regardless if the command takes arguments or not, or
 % declare it with arguments, even if the command takes none.
 %