ltnews34: last minute edits

of the new item, for gh697 plus a tweak

base/doc/ltnews34.tex

@@ -213,7 +213,7 @@ \subsection{Provide \cs{ActivateGenericHook}}
 
 Note that a generic hook produced in this way is always a normal hook.
 
-\subsection{Standardizing the names of generic hooks}
+\subsection{Standardized names for the generic hooks}
 
 The initial set of generic hooks provided by the kernel had
 two patterns of names:\\
@@ -314,7 +314,6 @@ \subsection{Cleaning up after \cs{UseOneTimeHook}}
 \githubissue{565}
 
 
-
 \subsection{\cs{RemoveFromHook} with a missing code label}
 
 In the first version of \cs{RemoveFromHook}, when the code label
@@ -346,21 +345,20 @@ \subsection{\cs{RemoveFromHook} with a missing code label}
 %
 \githubissue{625}
 
+\subsection{Patching commands that contain parameter tokens}
 
-\subsection{Fix patching of commands that contain parameter tokens}
-
-In the previous release, \LaTeX's hook mechanism was extended to add
+In the last release, \LaTeX's hook mechanism was extended to add
 support for hooking into commands using generic \hook{cmd} hooks
-(see~\cite{34:ltnews33}).  The initial version had a bug, in which the
-patching of some commands with a parameter token (normally \verb|#|) in
-their definition would fail with a low-level \TeX{} error.  The bug has
-been fixed, and now patching works for those commands as well.
+(see~\cite{34:ltnews33}).  That version of the extension had a bug: the
+patching of some commands that contained a parameter token
+(normally \verb|#|) in
+their definition would fail with a low-level \TeX{} error.  This has now
+been fixed so that patching now works for those commands as well.
 %
 \githubissue{697}
 
 
 
-
 \section{New or improved commands}