docu fix for #1458

base/ltdefns.dtx

@@ -32,7 +32,7 @@
 %<*driver>
 % \fi
 \ProvidesFile{ltdefns.dtx}
-             [2024/04/17 v1.5t LaTeX Kernel (definition commands)]
+             [2024/09/06 v1.5t LaTeX Kernel (definition commands)]
 % \iffalse
 \documentclass{ltxdoc}
 \GetFileInfo{ltdefns.dtx}
@@ -1772,11 +1772,11 @@
 %
 %   Most of the machinery defined for \cs{NewCommandCopy} can be used to show
 %   the definition of a robust command, in a similar fashion to \texttt{texdef}.
-%   The difference is that after the command's is detected to has a given type
+%   The difference is that after the command is detected to have a given type
 %   of robustness, rather than making a copy, we use a separate routine to show
 %   its definition.
 %
-%   With all the machinery in place, \cs{ShowCommand} itself is quite simple:
+%   With all the machinery in place, \cs{ShowCommand} itself is quite simple: we
 %   use \cs{robust@command@act} to iterate through the \cs{@showcommandlisthook}
 %   list, and if nothing is found, fallback to \cs{show}.
 %    \begin{macrocode}
@@ -1837,7 +1837,8 @@
 %   tests are heavily based on Heiko's \cs{LetLtxMacro}, but chopped into
 %   separate macros.
 %
-%   \cs{@if@DeclareRobustCommand} checks if a command \verb=\cmd= was defined by
+%   The command \cs{@if@DeclareRobustCommand} checks if a command
+%   \verb=\cmd= was defined by 
 %   \cs{DeclareRobustCommand}.  The test returns true if the expansion of
 %   \verb=\cmd= is exactly \verb*=\protect\cmd =.
 %

required/latex-lab/latex-lab-block.dtx

@@ -9,7 +9,7 @@
 %
 %    https://www.latex-project.org/lppl.txt
 %
-\def\ltlabblockdate{2024-09-03}
+\def\ltlabblockdate{2024-09-06}
 \def\ltlabblockversion{0.8q}
 %<*driver>
 \documentclass[kernel]{l3doc}