[latex3-commits] [latex3/latex2e] ltmarks-enhance: minor wording adjustments (7d8f90f9)

[github at latex-project.org]

Repository : https://github.com/latex3/latex2e
On branch  : ltmarks-enhance
Link       : https://github.com/latex3/latex2e/commit/7d8f90f907b7c011eb7cc854003433b70efc1ac2

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

commit 7d8f90f907b7c011eb7cc854003433b70efc1ac2
Author: David Carlisle <d.p.carlisle at gmail.com>
Date:   Wed Nov 15 16:56:07 2023 +0000

    minor wording adjustments


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

7d8f90f907b7c011eb7cc854003433b70efc1ac2
 base/doc/ltnews39.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/base/doc/ltnews39.tex b/base/doc/ltnews39.tex
index 8bb3ecb3..c64d4421 100644
--- a/base/doc/ltnews39.tex
+++ b/base/doc/ltnews39.tex
@@ -157,7 +157,7 @@ page data it was necessary to \cs{vsplit} that data artificially so
 that \TeX{} would produce split marks that the mechanism could then
 use. Unfortunately, \TeX{} gets very upset if it finds infinite
 negative glue (e.g., from \cs{vss}) within this data. This is not
-totally surprising because such glue would allow to split off any
+totally surprising because such glue would allow splitting off any
 amount of material as such glue would hide the size of it. \TeX{}
 therefore responds with an error message if it find such glue while
 doing a \cs{vsplit} operation (and it does so even if a later glue
@@ -193,7 +193,7 @@ Not perfect (especially the somewhat unmotivated \texttt{<argument>}),
 but you can only do so much if error messages and their texts are
 hard-wired in the engine.
 
-So why all this? There are two reasons: we do not loose marks in edge
+So why all this? There are two reasons: we do not lose marks in edge
 cases any longer and perhaps more importantly we are now also reliably
 able to extract marks from arbitrarily boxed data, something that
 wasn't possible at all before. This is, for example, necessary to