[latex3-commits] [git/LaTeX3-latex3-latex2e] gh479: Doc improvements (74d4b879)

[PhelypeOleinik]

Repository : https://github.com/latex3/latex2e
On branch  : gh479
Link       : https://github.com/latex3/latex2e/commit/74d4b879db2de6c656794e393ea352eee7d66ce5

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

commit 74d4b879db2de6c656794e393ea352eee7d66ce5
Author: PhelypeOleinik <phelype.oleinik at latex-project.org>
Date:   Mon Mar 22 16:11:38 2021 -0300

    Doc improvements


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

74d4b879db2de6c656794e393ea352eee7d66ce5
 base/latexrelease.dtx | 27 +++++++++++++++------------
 1 file changed, 15 insertions(+), 12 deletions(-)

diff --git a/base/latexrelease.dtx b/base/latexrelease.dtx
index 5209e848..6bca5462 100644
--- a/base/latexrelease.dtx
+++ b/base/latexrelease.dtx
@@ -374,13 +374,14 @@
 % and, as with all changes to the kernel, it was added to
 % \pkg{latexrelease}.  However rolling back from a future date to the
 % 2020-10-01 release didn't work because \pkg{latexrelease} would try to
-% define again all those commands, which would result in many errors.
+% define again all those commands, which would result in many
+% \enquote{already defined} errors and similar issues.
 %
 % To solve that problem, completely new modules can be defined in
 % \pkg{latexrelease} using the commands:
 % \begin{quote}
 %   \cs{NewModuleRelease}%^^A
-%     \verb|{|\meta{name}\verb|}{|\meta{release date}\verb|}|\\
+%     \verb|{|\meta{name}\verb|}{|\meta{initial release date}\verb|}|\\
 %   \null\quad\meta{module code}\\
 %   \cs{IncludeInRelease}%^^A
 %     \verb|{0000/00/00}{|\meta{name}\verb|}{|\meta{message}\verb|}|\\
@@ -388,17 +389,18 @@
 %   \cs{EndModuleRelease}
 % \end{quote}
 % With that setup, the module \meta{name} will be declared to exist only
-% in releases equal or later \meta{release date}.
+% in releases equal or later \meta{initial release date}.
 %
 % If \pkg{latexrelease} is rolling backwards or forwards between dates
-% after \meta{release date}, then all the \meta{module code} is skipped,
-% except when inside \meta{IncludeInRelease} guards, in which case the
-% code is applied or skipped as discussed above.
+% after \meta{initial release date}, then all the \meta{module code} is
+% skipped, except when inside \meta{IncludeInRelease} guards, in which
+% case the code is applied or skipped as discussed above.
 %
-% If rolling forward from a date before the module's \meta{release date}
-% to a date after that, then all the \meta{module code} is executed to
-% define the module, and \cs{IncludeInRelease} guards are executed
-% accordingly, depending on the date declared and the target date.
+% If rolling forward from a date before the module's \meta{initial
+% release date} to a date after that, then all the \meta{module code} is
+% executed to define the module, and \cs{IncludeInRelease} guards are
+% executed accordingly, depending on the date declared and the target
+% date.
 %
 % If \pkg{latexrelease} is rolling back to a date before \meta{release
 % date}, then the code in the \cs{IncludeInRelease} guard dated
@@ -407,8 +409,9 @@
 % instead by \cs{EndModuleRelease}.
 %
 % Finally, if rolling backwards or forwards between dates both before
-% \meta{release date}, the entire code between \meta{NewModuleRelease}
-% and \meta{EndModuleRelease} is entirely skipped.
+% \meta{initial release date}, the entire code between
+% \meta{NewModuleRelease} and \meta{EndModuleRelease} is entirely
+% skipped.
 %
 % \subsection{Example}
 %