Merge branch 'double-words' into develop

base/ltcmdhooks.dtx

@@ -20,7 +20,7 @@
 %<*driver>
 % \fi
 \ProvidesFile{ltcmdhooks.dtx}
-             [2024/10/22 v1.0j LaTeX Kernel (Command hooks)]
+             [2024/1/12 v1.0j LaTeX Kernel (Command hooks)]
 % \iffalse
 %
 \documentclass{l3doc}
@@ -1614,7 +1614,7 @@
           { #### } { \c_hash_str }
       }
 %    \end{macrocode}
-%   Then, make make some things \tn{relax} to avoid lots of
+%   Then, make some things \tn{relax} to avoid lots of
 %   \tn{noexpand} below.
 %    \begin{macrocode}
     \cs_set_eq:NN \kerneltmpDoNotUse \scan_stop:

base/ltfssbas.dtx

@@ -35,7 +35,7 @@
 %
 %
 \ProvidesFile{ltfssbas.dtx}
-             [2024/11/30 v3.2o LaTeX Kernel (NFSS Basic Macros)]
+             [2024/12/12 v3.2o LaTeX Kernel (NFSS Basic Macros)]
 % \iffalse
 \documentclass{ltxdoc}
 \begin{document}
@@ -1196,7 +1196,7 @@
 %    it if we are at \cs{@math@level} one, so that in the typical case
 %    of one bold symbol within the normal version this doesn't
 %    allocate an additional math alphabet.
-%    If if the nesting is deeper we we do nothing, which means
+%    If the nesting is deeper we do nothing, which means
 %    alphabet allocations accumulate until the end of the formula. One
 %    could do slightly better but that would mean keeping track of the
 %    allocations on all levels severately and this is likely to be

base/ltmarks.dtx

@@ -17,7 +17,7 @@
 %<*driver>
 % \fi
 \ProvidesFile{ltmarks.dtx}
-             [2024/12/03 v1.1b LaTeX Kernel (Marks)]
+             [2024/12/12 v1.1b LaTeX Kernel (Marks)]
 % \iffalse
 %
 \documentclass{l3doc}
@@ -797,7 +797,7 @@
 %    If the \meta{source} consists of a single vertical box (plus
 %    possibly followed by some glue but nothing else) then the box is
 %    unpacked and the top-level marks are collected from its
-%    content. However, if it is not a vertical box or there are are
+%    content. However, if it is not a vertical box or there are
 %    other data then nothing is unpacked and you have to do the
 %    unpacking yourself to get at the marks inside.
 %
@@ -1152,7 +1152,7 @@
 %    We are now ready to \cs{vsplit} the box to get at the marks. If
 %    the box contains some infinite negative glue the \TeX{} will
 %    produce an error complaining about it but it will correctly find
-%    the the split marks. Given that we can't prevent that error, we
+%    the split marks. Given that we can't prevent that error, we
 %    hide it from the user and ensure that \TeX{} doesn't stop. The
 %    error message still shows in the log, but even that is mitigated
 %    as best as possible---see the definition of
@@ -1230,7 +1230,7 @@
 %    Then we change them so that no escape char is printed in the
 %    error message (accounts for the missing backslash in front of
 %    \verb/Infinite shrink .../) and we set the interaction to
-%    \cs{nonstopmode} so that the the error (if any) just goes into
+%    \cs{nonstopmode} so that the error (if any) just goes into
 %    the \texttt{.log} file and \TeX{} doesn't stop at that point.
 %    \begin{macrocode}
   \tex_escapechar:D     -1 \scan_stop:
@@ -1684,7 +1684,7 @@
 %
 %  \begin{macro}{\@@_value:nn}
 %    A hidden marker is placed into every mark added by
-%    \cs{mark_insert:nn}. It will will not show up in the output but
+%    \cs{mark_insert:nn}. It will not show up in the output but
 %    its argument (a counter value that is incremented) makes all
 %    marks unique so the test for \enquote{equal} is not fooled by two
 %    different marks having the same mark text.
@@ -2204,7 +2204,7 @@
 %    Updating the \texttt{first} mark for the \texttt{page} region is
 %    more complicated. We first have to find out of there is any mark
 %    in the first column (this can be done by comparing the \texttt{top} and
-%    the \texttt{first} mark of of that region). 
+%    the \texttt{first} mark of that region). 
 % \changes{v1.0f}{2024/05/30}{Correct logic for first mark in page
 %    region if first column contains no marks (gh/1359)}
 %    \begin{macrocode}

required/latex-lab/latex-lab-math.dtx

@@ -19,7 +19,7 @@
 % for those people who are interested or want to report an issue.
 %
 %
-\def\ltlabmathdate{2024-12-01}
+\def\ltlabmathdate{2024-12-12}
 \def\ltlabmathversion{0.6k}
 %
 %<*driver>
@@ -2334,7 +2334,7 @@
      }
   }
 %    \end{macrocode}
-% TODO: the following command is neither documented nor used. Is is needed?
+% TODO: the following command is neither documented nor used. Is it needed?
 %    \begin{macrocode}
 \cs_new_protected:Npn \math_register_odd_env:nn #1#2
   {

required/latex-lab/latex-lab-title.dtx

@@ -16,7 +16,7 @@
 %
 % for those people who are interested or want to report an issue.
 %
-\def\ltlabtitledate{2024-02-09}
+\def\ltlabtitledate{2024-12-12}
 \def\ltlabtitleversion{0.85c}
 
 %<*driver>
@@ -106,7 +106,7 @@
 % \begin{itemize}
 % \item Writing into the Info dictionary needs to convert the input into a PDF string.
 % This is here done with a simple version of hyperref's \cs{pdfstringdef}, similar code
-% exist also in in the generic hyperref driver. This should be moved into a better place
+% exist also in the generic hyperref driver. This should be moved into a better place
 % module. 
 % 
 % \item Is it sensible to enhance \cs{author} and \cs{title} with an optional argument as done here?

required/latex-lab/latex-lab-toc.dtx

@@ -16,7 +16,7 @@
 %
 % for those people who are interested or want to report an issue.
 %
-\def\ltlabtocdate{2024-09-26}
+\def\ltlabtocdate{2024-12-12}
 \def\ltlabtocversion{0.85e}
 %<*driver>
 \documentclass{l3doc}
@@ -114,7 +114,7 @@
 % Defined by tagpdf.
 % \end{variable}
 %
-% We have to to store the relation between
+% We have to store the relation between
 % destination names/\cs{@currentHref} and structure numbers.
 % With a current kernel this is done in \cs{refstepcounter} 
 % through the |recordtarget| socket. If that doesn't exist yet