[latex3-commits] [git/LaTeX3-latex3-latex2e] copyedits-chris: ltnews34: limited permutations (2afc50f1)

[Chris Rowley]

Repository : https://github.com/latex3/latex2e
On branch  : copyedits-chris
Link       : https://github.com/latex3/latex2e/commit/2afc50f125b18887709dc6fa73bbf2615a351d97

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

commit 2afc50f125b18887709dc6fa73bbf2615a351d97
Author: Chris Rowley <car222222 at users.noreply.github.com>
Date:   Wed Oct 20 16:55:28 2021 +0700

    ltnews34: limited permutations
    
    Plus a few tweaks and corrections


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

2afc50f125b18887709dc6fa73bbf2615a351d97
 base/doc/ltnews34.tex                 | 261 +++++++++++++++++-----------------
 base/doc/ltnews34.tex => ltnews34.tex |  60 ++++----
 2 files changed, 161 insertions(+), 160 deletions(-)

diff --git a/base/doc/ltnews34.tex b/base/doc/ltnews34.tex
index 0c7442b6..f94ca32b 100644
--- a/base/doc/ltnews34.tex
+++ b/base/doc/ltnews34.tex
@@ -5,7 +5,7 @@
 % in this file.
 %
 % This file is part of the LaTeX base system.
-% -------------------------------------------
+% -——————————————
 %
 % It may be distributed and/or modified under the
 % conditions of the LaTeX Project Public License, either version 1.3c
@@ -15,7 +15,7 @@
 % and version 1.3c or later is part of all distributions of LaTeX
 % version 2008 or later.
 %
-% This file has the LPPL maintenance status "maintained".
+% This file has the LPPL maintenance status “maintained”.
 %
 % The list of all files belonging to the LaTeX base distribution is
 % given in the file `manifest.txt'. See also `legal.txt' for additional
@@ -35,7 +35,7 @@
 \documentclass{ltnews}
 
 %%  Temporary definition for Chris' inadequate system:  CCC
-\providecommand\Dash {\unskip ---}
+\providecommand\Dash {\unskip \textemdash}
 
 %% NOTE:  Chris' preferred hyphens!
 %%\showhyphens{parameters}
@@ -117,8 +117,8 @@
 \tubcommand{\input{tubltmac}}
 
 \publicationmonth{November}
-\publicationyear{2021 --- Third Draft Version 
-                     (not quite cmplete, eg needs Intro?)} %% CCC
+\publicationyear{2021 \Dash Third Draft Version, 
+                     not quite complete, eg needs Intro?)} %% CCC
 
 \publicationissue{34}
 
@@ -212,60 +212,6 @@ after which all German words would be colored blue in the text.
 
 Note that a generic hook produced in this way is always a normal hook.
 
-
-
-
-\subsection{Clearing extra hook code for the next invocation}
-
-There are a few use cases where it is helpful if one can cancel
-an earlier use of \cs{AddToHookNext}: for example, when a page is
-discarded with \cs{DiscardShipoutBox} because only some pages of the
-document are printed. For such situations the new command
-\cs{ClearHookNext} is now provided.
-%
-\githubissue{565}
-
-
-\subsection{Cleaning up after \cs{UseOneTimeHook}}
-
-Some hooks are meant to be used only once in a document, and any
-further attempt to add code to one of these will 
-cause the code to be executed
-immediately instead of being added to the hook.  
-%
-The initial implementation of
-this concept was very simple and didn't anticipate that packages may try to
-execute a one-time hook several times, resulting in the hook code
-being executed repeatedly.  Thus the implementation was fine for
-simple cases (such as the \hook{begindocument} hook) but it causes
-trouble if the one-time hook was intended, for example, as an
-initialization hook that is used just once (when a command is first
-called) but is then ignored in further calls.
-
-This deficiency has been addressed, and now a one-time 
-hook will only be executed once, with
-its code being removed after use to free up some memory.
-%
-\githubissue{565}
-
-
-
-\subsection{Some file hooks made one-time}
-
-Classes, packages and included files can only be loaded once in a
-\LaTeX{} document. For this reason, the hooks that are specific to loading such
-files have been made one-time hooks. Beside being more efficient, this
-supports the following important use case
-\begin{verbatim}
-  \AddToHook{package/varioref/after}
-   {... apply when the package gets loaded, 
-    or apply now (if it is already loaded) ...}
-\end{verbatim}
-without the need to first test whether the package is already loaded.
-%
-\githubissue{623}
-
-
 \subsection{Standardizing the names of generic hooks}
 
 The initial set of generic hooks provided by the kernel had
@@ -315,6 +261,57 @@ then removed completely.
 \githubissue{648}
 
 
+\subsection{Some file hooks made one-time}
+
+Classes, packages and included files can only be loaded once in a
+\LaTeX{} document. For this reason, the hooks that are specific to loading such
+files have been made one-time hooks. Beside being more efficient, this
+supports the following important use case
+\begin{verbatim}
+  \AddToHook{package/varioref/after}
+   {... apply when the package gets loaded, 
+    or apply now (if it is already loaded) ...}
+\end{verbatim}
+without the need to first test whether the package is already loaded.
+%
+\githubissue{623}
+
+
+\subsection{Clearing extra hook code for the next invocation}
+
+There are a few use cases where it is helpful if one can cancel
+an earlier use of \cs{AddToHookNext}: for example, when a page is
+discarded with \cs{DiscardShipoutBox} because only some pages of the
+document are printed. For such situations the new command
+\cs{ClearHookNext} is now provided.
+%
+\githubissue{565}
+
+
+\subsection{Cleaning up after \cs{UseOneTimeHook}}
+
+Some hooks are meant to be used only once in a document, and any
+further attempt to add code to one of these will 
+cause the code to be executed
+immediately instead of being added to the hook.  
+%
+The initial implementation of
+this concept was very simple and didn't anticipate that packages may try to
+execute a one-time hook several times, resulting in the hook code
+being executed repeatedly.  Thus the implementation was fine for
+simple cases (such as the \hook{begindocument} hook) but it causes
+trouble if the one-time hook was intended, for example, as an
+initialization hook that is used just once (when a command is first
+called) but is then ignored in further calls.
+
+This deficiency has been addressed, and now a one-time 
+hook will only be executed once, with
+its code being removed after use to free up some memory.
+%
+\githubissue{565}
+
+
+
 \subsection{\cs{RemoveFromHook} with a missing code label}
 
 In the first version of \cs{RemoveFromHook}, when the code label
@@ -375,6 +372,29 @@ new commands: \cs{ClassNote} and \cs{ClassNoteNoLine}.
 \githubissue{613}
 
 
+\subsection{New \cs{ShowFloat} command}
+
+The package \pkg{fltrace} offers a (fairly low-level but very
+detailed) way to trace \LaTeX's float mechanism. This can help in
+understanding why a certain float is placed into a certain 
+region, or why it shows up unexpectedly on a later page.  
+\LaTeX{} stores floats in registers named \cs{bx at A}, \cs{bx at B}, etc., 
+and these names show up in the tracing information.
+
+To display the contents of a float register, you can now say
+\verb=\ShowFloat{=\textit{identifier}\verb=}= where
+\textit{identifier} is the uppercase letter (or letters) after
+\texttt{bx@} in the register name shown in the tracing.  
+If additional
+registers have been allocated (with \cs{extrafloats}), the
+\textit{identifier} can also be a number. The command is generally
+available, whether or not you have loaded \pkg{fltrace}, because 
+it is also useful when interpreting the tracing output of the
+\pkg{fewerfloatpages} package.
+
+
+
+
 \subsection{New argument for \cs{counterwithin/without}}
 
 The commands \cs{counterwithout} and \cs{counterwithin} each now has
@@ -386,29 +406,6 @@ specifies the format of the counter, such as \cs{roman},
 the default value being \cs{arabic}.
 
 
-\subsection{New default value for \cs{tracinglostchars}}
-
-In 2021 all \TeX{} engines were enhanced so that \cs{tracinglostchars} 
-supported the extra value \texttt{3}, that turns missing
-characters into errors and not just warnings. 
-%
-This engine change made us
-realize that \LaTeX{} should set a better default value for this parameter
-(previously, the warning was written only to the transcript file).
-Using the now available value of \texttt{3} as the default
-would really be best, but for
-compatibility reasons we have only increased it to \texttt{2} in the kernel.
-%
-However, we recommend setting \cs{tracinglostchars}\texttt{=3}, 
-in either a package or the
-preamble of your documents: this is because having missing glyphs 
-in the output is definitely an error and should therefore be 
-flagged as such (to ensure that it gets proper attention).
-Further reasons, related especially to Unicode engines, for making 
-this recommended change can be found later in this newsletter 
-(in connection with the misuse of text accents in mathmode).
-
-
 \subsection{Tests for package and class loading}
 
 To test whether a package has been loaded you can now use \cs{IfPackageLoadedTF}
@@ -421,7 +418,7 @@ with certain options. This is done with
 It uses the \meta{false} code if at least one option in 
 the \meta{option-list} was 
 not specified when loading the package, or if the package 
-hasn't been loaded at all.
+has never been.
 %
 Both commands can be used anywhere in the document, i.e., 
 they are not restricted to the preamble.%
@@ -435,27 +432,6 @@ For classes, similar commands (with \texttt{Package} replaced by
 \githubissue{621}
 
 
-\subsection{New \cs{ShowFloat} command}
-
-The package \pkg{fltrace} offers a (fairly low-level but very
-detailed) way to trace \LaTeX's float mechanism. This can help in
-understanding why a certain float is placed into a certain 
-region, or why it shows up unexpectedly on a later page.  
-\LaTeX{} stores floats in registers named \cs{bx at A}, \cs{bx at B}, etc., 
-and these names show up in the tracing information.
-
-To display the contents of a float register, you can now say
-\verb=\ShowFloat{=\textit{identifier}\verb=}= where
-\textit{identifier} is the uppercase letter (or letters) after
-\texttt{bx@} in the register name shown in the tracing.  
-If additional
-registers have been allocated (with \cs{extrafloats}), the
-\textit{identifier} can also be a number. The command is generally
-available, whether or not you have loaded \pkg{fltrace}, because 
-it is also useful when interpreting the tracing output of the
-\pkg{fewerfloatpages} package.
-
-
 \subsection{\cs{NewCommandCopy}, \cs{ShowCommand} now in \pkg{ltcmd}}
 
 Since the 2020-10-01 release (see~\cite{34:ltnews32}), \LaTeX{} 
@@ -474,7 +450,6 @@ can be easily shown on the terminal without the need for ``\cs{csname} gymnastic
 \githubissue{569}
 
 
-
 \subsection{Undo math alphabet allocations if necessary}
 
 \TeX{}, or more exactly the 8-bit versions of \TeX, such as \pdfTeX{}
@@ -526,10 +501,46 @@ file hooks from \cs{InputIfFileExists} are run).
 \githubissue{645}
 
 
+\subsection{New default value for \cs{tracinglostchars}}
+
+In 2021 all \TeX{} engines were enhanced so that \cs{tracinglostchars} 
+supported the extra value \texttt{3}, that turns missing
+characters into errors and not just warnings. 
+%
+This engine change made us
+realize that \LaTeX{} should set a better default value for this parameter
+(previously, the warning was written only to the transcript file).
+Using the now available value of \texttt{3} as the default
+would really be best, but for
+compatibility reasons we have only increased it to \texttt{2} in the kernel.
+%
+However, we recommend setting \cs{tracinglostchars}\texttt{=3}, 
+in either a package or the
+preamble of your documents: this is because having missing glyphs 
+in the output is definitely an error and should therefore be 
+flagged as such (to ensure that it gets proper attention).
+Further reasons, related especially to Unicode engines, for making 
+this recommended change can be found later in this newsletter 
+(in connection with the misuse of text accents in mathmode).
+
 
 \section{Code improvements}
 
-\subsection{Check ``\cs{endfoo}'' in \cs{NewDocumentEnvironment}}
+
+\subsection{Use OpenType version of Latin Modern Upright Italic font}
+When a Latin Modern font is used with the TU encoding under \XeTeX\ or \LuaTeX\
+and fontshape \texttt{ui} is requested, \LaTeX\ now uses the OpenType
+version of the font instead of substituting the (T1-encoded) Type 1 version.
+
+
+\subsection{Additional Extended Latin characters predefined}
+More characters, such as \'k (U+1E131), are now pre-defined and
+do not need a \verb|\DeclareUnicodeCharacter| declaration.
+%
+\githubissue{593}
+
+
+\subsection{Check \cs{endfoo} in \cs{NewDocumentEnvironment}}
 
 The \cs{newenvironment} command has always checked that neither \cs{foo} nor
 \cs{endfoo} exists before creating a \texttt{foo} environment. 
@@ -542,7 +553,7 @@ of \cs{newenvironment}, except that it gives distinct errors
 concerning the existence of \cs{foo} and \cs{endfoo}.
 
 
-\subsection{Improve the error message ``\cs{begin} ended by''}
+\subsection{Improve the error message \texttt{\cs{begin} ended by \textellipsis}}
 
 In the past it was possible to get an error message something
 like \verb=\begin{foo} ended by \end{foo}=. This could happen when the
@@ -556,20 +567,6 @@ message in this instance.
 \githubissue{587}
 
 
-
-\subsection{Additional Extended Latin characters predefined}
-More characters, such as \'k (U+1E131), are now pre-defined and
-do not need a \verb|\DeclareUnicodeCharacter| declaration.
-%
-\githubissue{593}
-
-
-\subsection{Use OpenType version of Latin Modern Upright Italic font}
-When a Latin Modern font is used with the TU encoding under \XeTeX\ or \LuaTeX\
-and fontshape \texttt{ui} is requested, \LaTeX\ now uses the OpenType
-version of the font instead of substituting the (T1-encoded) Type 1 version.
-
-
 \subsection{Pick up all arguments to \cs{contentsline}}
 
 A \cs{contentsline} command in the TOC file is always followed by
@@ -588,7 +585,7 @@ fourth being saved away so that it can be used by \pkg{hyperref}.
 \githubissue{633}
 
 
-\subsection{Fix dropping math lists in \LuaTeX\ callbacks}
+\subsection{Allow dropping a math list in \LuaTeX\ callback}
 
 The \LuaTeX\ callbacks \texttt{pre\_mlist\_to\_hlist\_filter}
 and \texttt{post\_mlist\_to\_hlist\_filter} no longer create an error when 
@@ -596,7 +593,7 @@ the callback handler indicates removal of the entire math list.
 %
 \githubissue{644}
 
-\subsection{Extended label handling in Package code}
+\subsection{Extended label handling in package code}
 
 Since 2020, as noted in \LaTeX News 32~\cite{34:ltnews32}, \LaTeX\ has
 recorded the name of the counter associated with the current label in
@@ -628,10 +625,10 @@ Using text accents like \verb|\^| in math does not work
 (and \TeX{} explicitly provides math accents such as \cs{hat} 
 for accessing such symbols in mathmode). Therefore LaTeX issued a 
 warning when such a wrongly placed accent was encountered 
-and, in many cases, this was followed by a strange, and apparently 
+and this was often followed by a strange, and apparently 
 unrelated, low-level error.  
 %
-This has now been changed so that the message generated by this 
+This has now been changed so that the message from this 
 error is at least about accents, which we hope is less puzzling. 
 
 Discussion of such warnings or errors reminds us to reinforce 
@@ -641,7 +638,7 @@ of the item on the value of \cs{tracinglostchars}.
 Using \TeX\ implementations from 2020 onwards, any warning that 
 concerns missing characters can be
 converted to an error by setting \cs{tracinglostchars} to 3; we therefore 
-now strongly recommend changing this setting to 3, especially for 
+now recommend changing this setting to 3, especially for 
 Unicode engines where such missing characters are common (because 
 no font supports the full Unicode range).
 %
@@ -673,7 +670,7 @@ will now correctly apply \cs{TrimSpaces} to both arguments.
 
 
 
-\subsection{Case changing for \cs{ij} and \cs{IJ} fixed}
+\subsection{Correct case changing of \cs{ij} and \cs{IJ}}
 
 
 The ligatures \enquote{\ij} and \enquote{\IJ}, as used in Dutch,
@@ -709,8 +706,10 @@ for all meta families in one go. This alteration cannot be done when the
 time \cs{bfseries} or \cs{mdseries} was executed.
 %
 However, the problem with that
-approach was that any call to \cs{DeclareFontSeriesDefault} in the meantime was overwritten, thus these two approaches didn't
-work well side by side.  There was a problem because older font packages
+approach was that any call to \cs{DeclareFontSeriesDefault} in 
+the meantime was overwritten, thus these two approaches didn't
+work well side by side.  
+There was a problem because older font packages
 use the legacy method while newer ones use
 \cs{DeclareFontSeriesDefault}. 
 
@@ -754,7 +753,9 @@ Since it is not in fact a math formula,
 no extra space from \cs{mathsuround} should be added 
 (the spacing around the \env{tabular} should not get changed). 
 %
-Note that this bug has been present ``forever’’, which shows that  \cs{mathsurround} is never used, or at least its use is never noticed.  Anyhow, this bug has now finally gotten fixed.
+Note that this bug has been present ``forever'', which shows that  \cs{mathsurround} 
+is never used, or at least its use is never noticed.  
+Anyhow, this bug has now finally gotten fixed.
 %
 \githubissue{614}
 
diff --git a/base/doc/ltnews34.tex b/ltnews34.tex
similarity index 94%
copy from base/doc/ltnews34.tex
copy to ltnews34.tex
index 0c7442b6..64da537f 100644
--- a/base/doc/ltnews34.tex
+++ b/ltnews34.tex
@@ -5,7 +5,7 @@
 % in this file.
 %
 % This file is part of the LaTeX base system.
-% -------------------------------------------
+% -——————————————
 %
 % It may be distributed and/or modified under the
 % conditions of the LaTeX Project Public License, either version 1.3c
@@ -15,10 +15,10 @@
 % and version 1.3c or later is part of all distributions of LaTeX
 % version 2008 or later.
 %
-% This file has the LPPL maintenance status "maintained".
+% This file has the LPPL maintenance status “maintained”.
 %
 % The list of all files belonging to the LaTeX base distribution is
-% given in the file `manifest.txt'. See also `legal.txt' for additional
+% given in the file `manifest.txt’. See also `legal.txt’ for additional
 % information.
 %
 % The list of derived (unpacked) files belonging to the distribution
@@ -34,10 +34,10 @@
 
 \documentclass{ltnews}
 
-%%  Temporary definition for Chris' inadequate system:  CCC
-\providecommand\Dash {\unskip ---}
+%%  Temporary definition for Chris’ inadequate system:  CCC
+\providecommand\Dash {\unskip —}
 
-%% NOTE:  Chris' preferred hyphens!
+%% NOTE:  Chris’ preferred hyphens!
 %%\showhyphens{parameters}
 %%  \hyphenation{because parameters parameter}
 
@@ -96,7 +96,7 @@
 
 
 \makeatletter
-% maybe not the greatest design but normally we wouldn't have subsubsections
+% maybe not the greatest design but normally we wouldn’t have subsubsections
 \renewcommand{\subsubsection}{%
    \@startsection      {subsubsection}{2}{0pt}{1.5ex \@plus 1ex \@minus .2ex}%
       {-1em}{\@subheadingfont\colonize}%
@@ -106,7 +106,7 @@
 
 \let\finalvspace\vspace          % for document layout fixes
 
-% Undo ltnews's \verbatim at font with active < and >
+% Undo ltnews’s \verbatim at font with active < and >
 \makeatletter
 \def\verbatim at font{%
   \normalsize\ttfamily}
@@ -117,7 +117,7 @@
 \tubcommand{\input{tubltmac}}
 
 \publicationmonth{November}
-\publicationyear{2021 --- Third Draft Version 
+\publicationyear{2021 — Third Draft Version 
                      (not quite cmplete, eg needs Intro?)} %% CCC
 
 \publicationissue{34}
@@ -181,7 +181,7 @@ It is also possible to offer such generic hooks in
 packages if, for example, hooks are needed that depend on the 
 current language and therefore need the
 language name as part of the hook name (but you probably 
-don't know beforehand all the necessary names).
+don’t know beforehand all the necessary names).
 
 If you want to offer such generic hooks, you can now 
 do this by using
@@ -196,7 +196,7 @@ activate the generic hook by using \cs{ActivateGenericHook}.\footnote{Note
   to deprecate it and now offer \cs{ActivateGenericHook} instead.}
 
 Assuming
-that you don't know all the different hook names up front, it will
+that you don’t know all the different hook names up front, it will
 remain the task of the users of your package to activate the hook
 themselves before adding code to it. For example, Babel offers hooks
 such as \hook{babel/\meta{language}/afterextras} 
@@ -234,7 +234,7 @@ cause the code to be executed
 immediately instead of being added to the hook.  
 %
 The initial implementation of
-this concept was very simple and didn't anticipate that packages may try to
+this concept was very simple and didn’t anticipate that packages may try to
 execute a one-time hook several times, resulting in the hook code
 being executed repeatedly.  Thus the implementation was fine for
 simple cases (such as the \hook{begindocument} hook) but it causes
@@ -318,13 +318,13 @@ then removed completely.
 \subsection{\cs{RemoveFromHook} with a missing code label}
 
 In the first version of \cs{RemoveFromHook}, when the code label
-to be removed didn't exist in the hook a ``removal order'' would be
+to be removed didn’t exist in the hook a ``removal order’’ would be
 queued; and then, the next time something tried to add that label to the hook,
 this \cs{AddToHook} action would be cancelled by the removal order, so that no code
 would be added that one time.  This was so that, in principle, package loading
-order wouldn't matter.  
+order wouldn’t matter.  
 %
-However, this implementation didn't work as
+However, this implementation didn’t work as
 intended because, while two \cs{AddToHook} actions with a given label would be
 removed by a single \cs{RemoveFromHook}, one \cs{RemoveFromHook} could
 not cancel two \cs{AddToHook} actions for that label; this caused
@@ -362,7 +362,7 @@ What has not existed up to now is a way to provide
 information on the terminal that identifies itself as coming from
 a specific package but which does not claim to be a warning. 
 (Packages that wanted to write to the terminal used \cs{PackageWarning}
-even though the information wasn't really a warning.)  
+even though the information wasn’t really a warning.)  
 
 We have therefore now added \cs{PackageNote} (and the closely 
 related \cs{PackageNoteNoLine}): these identify
@@ -421,7 +421,7 @@ with certain options. This is done with
 It uses the \meta{false} code if at least one option in 
 the \meta{option-list} was 
 not specified when loading the package, or if the package 
-hasn't been loaded at all.
+hasn’t been loaded at all.
 %
 Both commands can be used anywhere in the document, i.e., 
 they are not restricted to the preamble.%
@@ -438,7 +438,7 @@ For classes, similar commands (with \texttt{Package} replaced by
 \subsection{New \cs{ShowFloat} command}
 
 The package \pkg{fltrace} offers a (fairly low-level but very
-detailed) way to trace \LaTeX's float mechanism. This can help in
+detailed) way to trace \LaTeX’s float mechanism. This can help in
 understanding why a certain float is placed into a certain 
 region, or why it shows up unexpectedly on a later page.  
 \LaTeX{} stores floats in registers named \cs{bx at A}, \cs{bx at B}, etc., 
@@ -469,7 +469,7 @@ However, the extended support for \cs{NewCommandCopy} and
 \cs{ShowCommand} was not implemented in \pkg{ltcmd}.  The present
 \LaTeX{} release implements this support, so now commands
 defined with \pkg{xparse}/\pkg{ltcmd} can be copied, and their definitions
-can be easily shown on the terminal without the need for ``\cs{csname} gymnastics''.
+can be easily shown on the terminal without the need for ``\cs{csname} gymnastics’’.
 %
 \githubissue{569}
 
@@ -529,7 +529,7 @@ file hooks from \cs{InputIfFileExists} are run).
 
 \section{Code improvements}
 
-\subsection{Check ``\cs{endfoo}'' in \cs{NewDocumentEnvironment}}
+\subsection{Check ``\cs{endfoo}’’ in \cs{NewDocumentEnvironment}}
 
 The \cs{newenvironment} command has always checked that neither \cs{foo} nor
 \cs{endfoo} exists before creating a \texttt{foo} environment. 
@@ -542,7 +542,7 @@ of \cs{newenvironment}, except that it gives distinct errors
 concerning the existence of \cs{foo} and \cs{endfoo}.
 
 
-\subsection{Improve the error message ``\cs{begin} ended by''}
+\subsection{Improve the error message ``\cs{begin} ended by’’}
 
 In the past it was possible to get an error message something
 like \verb=\begin{foo} ended by \end{foo}=. This could happen when the
@@ -558,7 +558,7 @@ message in this instance.
 
 
 \subsection{Additional Extended Latin characters predefined}
-More characters, such as \'k (U+1E131), are now pre-defined and
+More characters, such as \’k (U+1E131), are now pre-defined and
 do not need a \verb|\DeclareUnicodeCharacter| declaration.
 %
 \githubissue{593}
@@ -588,7 +588,7 @@ fourth being saved away so that it can be used by \pkg{hyperref}.
 \githubissue{633}
 
 
-\subsection{Fix dropping math lists in \LuaTeX\ callbacks}
+\subsection{Allow dropping a math list in \LuaTeX\ callback}
 
 The \LuaTeX\ callbacks \texttt{pre\_mlist\_to\_hlist\_filter}
 and \texttt{post\_mlist\_to\_hlist\_filter} no longer create an error when 
@@ -596,7 +596,7 @@ the callback handler indicates removal of the entire math list.
 %
 \githubissue{644}
 
-\subsection{Extended label handling in Package code}
+\subsection{Extended label handling in package code}
 
 Since 2020, as noted in \LaTeX News 32~\cite{34:ltnews32}, \LaTeX\ has
 recorded the name of the counter associated with the current label in
@@ -628,10 +628,10 @@ Using text accents like \verb|\^| in math does not work
 (and \TeX{} explicitly provides math accents such as \cs{hat} 
 for accessing such symbols in mathmode). Therefore LaTeX issued a 
 warning when such a wrongly placed accent was encountered 
-and, in many cases, this was followed by a strange, and apparently 
+and this was often followed by a strange, and apparently 
 unrelated, low-level error.  
 %
-This has now been changed so that the message generated by this 
+This has now been changed so that the message from this 
 error is at least about accents, which we hope is less puzzling. 
 
 Discussion of such warnings or errors reminds us to reinforce 
@@ -641,7 +641,7 @@ of the item on the value of \cs{tracinglostchars}.
 Using \TeX\ implementations from 2020 onwards, any warning that 
 concerns missing characters can be
 converted to an error by setting \cs{tracinglostchars} to 3; we therefore 
-now strongly recommend changing this setting to 3, especially for 
+now recommend changing this setting to 3, especially for 
 Unicode engines where such missing characters are common (because 
 no font supports the full Unicode range).
 %
@@ -673,7 +673,7 @@ will now correctly apply \cs{TrimSpaces} to both arguments.
 
 
 
-\subsection{Case changing for \cs{ij} and \cs{IJ} fixed}
+\subsection{Correct changing of \cs{ij} and \cs{IJ}}
 
 
 The ligatures \enquote{\ij} and \enquote{\IJ}, as used in Dutch,
@@ -709,7 +709,7 @@ for all meta families in one go. This alteration cannot be done when the
 time \cs{bfseries} or \cs{mdseries} was executed.
 %
 However, the problem with that
-approach was that any call to \cs{DeclareFontSeriesDefault} in the meantime was overwritten, thus these two approaches didn't
+approach was that any call to \cs{DeclareFontSeriesDefault} in the meantime was overwritten, thus these two approaches didn’t
 work well side by side.  There was a problem because older font packages
 use the legacy method while newer ones use
 \cs{DeclareFontSeriesDefault}. 
@@ -808,7 +808,7 @@ method used in \pkg{hyperref} to change the \env{equation} environment.
 For simplicity, an explicit, low-level (hence possibly temporary) 
 patch has been added to \pkg{amsmath}: this consists of an extra, empty (hence invisible)
 \cs{mathopen} atom (with no mathematical meaning) at the start of the 
-environment's mathematical content.
+environment’s mathematical content.
 %
 \githubissue{652}