minor doc edits

base/doc/ltnews39.tex

@@ -242,7 +242,7 @@ \subsection{Optimize creation of simple document commands}
 \subsection{Declaring appropriate sub-encodings for \texttt{TS1} symbol fonts}
 
 In 2020 we incorporated support for the \texttt{TS1} symbol encoding
-directly into the kernel and this way removed the need to load the
+directly into the kernel and in this way removed the need to load the
 \pkg{textcomp} package~\cite{39:ltnews31} to make commands such as
 \cs{texteuro} available.
 
@@ -254,7 +254,7 @@ \subsection{Declaring appropriate sub-encodings for \texttt{TS1} symbol fonts}
 \cs{textohm} (\textohm) are no longer printed in your document, just
 because you altered your text font family.
 
-To mediate this problem, we also introduced in 2020 the declaration
+To mitigate this problem, we also introduced in 2020 the declaration
 \cs{DeclareEncodingSubset}. This declaration is supposed to be used in
 font definition files for the \texttt{TS1} encoding to specify which
 subset (we have defined 10 common ones) a specific font implements. If
@@ -283,7 +283,7 @@ \subsection{Declaring appropriate sub-encodings for \texttt{TS1} symbol fonts}
 process. As we do not maintain the fonts we do not have the
 information that something has changed, and to regularly check the
 ever growing font support bundles is simply not possible. It is
-therefore very important that maintainers of font packages to not only
+therefore very important that maintainers of font packages do not only
 provide \texttt{.fd} files but also add such a declaration to every
 \texttt{TS1...fd} font definition file that they distribute.
 

base/lttextcomp.dtx

@@ -985,10 +985,10 @@
 \DeclareEncodingSubset{TS1}{lmssq}   {1}
 \DeclareEncodingSubset{TS1}{lmvtt}   {1}
 %    \end{macrocode}
-%    The lmtt family is missing TM, SM, and perthausand for some
+%    The lmtt family is missing TM, SM, and perthousand for some
 %    reason, so the first safe sub-encoding would be 2, but that is
 %    then missing out a huge number of glyphs that are available, so
-%    we claim it is sub-encoding 1 even if this can lead to missing glyphs.s
+%    we claim it is sub-encoding 1 even if this can lead to missing glyphs.
 %    \begin{macrocode}
 \DeclareEncodingSubset{TS1}{lmtt}    {1} % missing TM, SM and pertenthousand
 %    \end{macrocode}
@@ -1004,7 +1004,7 @@
 %    The next set are the early PostScript font implementations, these
 %    days there are better alternatives, but \ldots. Note that, their
 %    virtual fonts contain a lot of ``tofu'' in form of black squares,
-%    this they don't even give a missing character warning if you
+%    thus they don't even give a missing character warning if you
 %    select such a glyph. This is why they are set as sub-encoding 5.
 %    \begin{macrocode}
 \DeclareEncodingSubset{TS1}{bch} {5} % tofu for blank, ohm
@@ -1025,7 +1025,7 @@
 %    \end{macrocode}
 %
 %    The next set suffers from the same problem and they contain even
-%    less real glyphs.
+%    fewer real glyphs.
 %    \begin{macrocode}
 \DeclareEncodingSubset{TS1}{dayroms}{6} % tofu for blank, interrobang/down, ohm
 \DeclareEncodingSubset{TS1}{dayrom} {6} % tofu for blank, interrobang/down, ohm
@@ -1064,7 +1064,7 @@
 %    avoid that a large number of available chars are unnecessarily
 %    substituted).
 %
-%    Encoding declarations for those font family shouldn't really be
+%    Encoding declarations for these font families shouldn't really be
 %    in the kernel, but part of the \texttt{.fd} files for the
 %    family. When we introduced the concept in 2021 we had some hope
 %    that this would happen over time and that we could take the