2021-11-26 10:43:00

6 files changed, 19 insertions, 17 deletions

diff --git a/doc/context/documents/general/manuals/luametatex.pdf b/doc/context/documents/general/manuals/luametatex.pdf
index 822146908..49347ca50 100644
--- a/doc/context/documents/general/manuals/luametatex.pdf
+++ b/doc/context/documents/general/manuals/luametatex.pdf
diff --git a/doc/context/sources/general/manuals/luametatex/luametatex-building.tex b/doc/context/sources/general/manuals/luametatex/luametatex-building.tex
index 61b11b18d..357e2ed41 100644
--- a/doc/context/sources/general/manuals/luametatex/luametatex-building.tex
+++ b/doc/context/sources/general/manuals/luametatex/luametatex-building.tex
@@ -73,7 +73,7 @@ column. If there are three columns, the first two will store inserts. Then when
 the last column is dealt with \prm {insertstoring} can be set to 2 and that will
 signal the builder that we will inject the inserts. In both cases, the value of
 this register will be set to zero so that it doesn't influence further
-processing. You can use \prm {ifinsert} to check if am insert box is void. More
+processing. You can use \prm {ifinsert} to check if an insert box is void. More
 details about these (probably experimental for a while) features can be found in
 documents that come with \CONTEXT.
 
@@ -118,14 +118,14 @@ The \LUAMETATEX\ engine has some tracing built in that is enabled by setting \pr
 \startsection[title={Adjusts}]
 
 The \prm {vadjust} primitive injects something in the vertical list after the
-lien where it ends up. In \PDFTEX\ the \type {pre} keyword was added so that one
+line where it ends up. In \PDFTEX\ the \type {pre} keyword was added so that one
 could force something before a previous line (actually this was something that we
 needed in \CONTEXT\ \MKII). The \LUAMETATEX\ engine also supports the \type {post}
 keyword.
 
 We support a few more keywords: \type {before} will prepend the adjustment to the
 already given one, and \type {after} will append it. The \type {index} keyword
-expects an integer and relate that to the current adjustment. This index is
+expects an integer and relates that to the current adjustment. This index is
 passed to an (optional) callback when the adjustment is finally moved to the
 vertical list. That move is actually delayed because like inserts and marks these
 (vertical) adjustments can migrate to the \quote {outer} vertical level.
@@ -158,7 +158,7 @@ and inserts bubble up to the outer level.
 \LL
 \stoptabulate
 
-If you want to migrate marks and inserts you need to set al these flags. Migrated
+If you want to migrate marks and inserts you need to set all these flags. Migrated
 marks and inserts end up as post|-|box properties and will be handled in the page
 builder as such. At the \LUA\ end you can add pre- and post|-|box material too.
 
@@ -166,9 +166,9 @@ builder as such. At the \LUA\ end you can add pre- and post|-|box material too.
 
 \startsection[title={Pages}]
 
-The page builder can triggered by (for instance) a penalty but you can also use
-\prm {pageboundary}. This will trigger the page builder but not leave anything
-behind.
+The page builder can be triggered by (for instance) a penalty but you can also
+use \prm {pageboundary}. This will trigger the page builder but not leave
+anything behind.
 
 \stopsection
 
@@ -177,10 +177,10 @@ behind.
 As far as I know the \OMEGA/\ALEPH\ local box mechanism is mostly in those
 engines in order to support repetitive quotes. In \LUATEX\ this mechanism has
 been made more robust and in \LUAMETATEX\ it became more tightly integrated in
-the paragraph properties. In order for it to be a more generic useful feature it
-got more features. For instance it is a bit painful to manage with respect to
+the paragraph properties. In order for it to be more generic and useful, it got
+more features. For instance it is a bit painful to manage with respect to
 grouping (which is a reason why it's not that much used). The most interesting
-property is that the dimensions are taking into account when a paragraph is
+property is that the dimensions are taken into account when a paragraph is
 broken into lines.
 
 There are three commands: \prm {localleftbox}, \prm {localrightbox} and the
@@ -190,7 +190,7 @@ used the index but this was a cheap extra signal so we keep it).
 
 These commands take optional keywords. The \type {index} keyword has to be
 followed by an integer. This index determines the order which doesn't introduce a
-significant compatibility issue: local boxes are hardly used and originally have
+significant compatibility issue: local boxes are hardly used and originally had
 only one instance.
 
 The \type {par} keyword forces the box to be added to the current paragraph head.
@@ -202,7 +202,7 @@ The \type {local} keyword tells this mechanism not to update the registers that
 keep these boxes. In that case a next paragraph will start fresh. The \type
 {keep} option will do the opposite and retain the box after a group ends.
 
-There commands: \prm {localleftboxbox}, \prm {localrightboxbox} and \prm
+The commands: \prm {localleftboxbox}, \prm {localrightboxbox} and \prm
 {localmiddleboxbox} return a copy of the current related register content.
 
 \stopsection
diff --git a/doc/context/sources/general/manuals/luametatex/luametatex-enhancements.tex b/doc/context/sources/general/manuals/luametatex/luametatex-enhancements.tex
index 9a03654d8..121ffe216 100644
--- a/doc/context/sources/general/manuals/luametatex/luametatex-enhancements.tex
+++ b/doc/context/sources/general/manuals/luametatex/luametatex-enhancements.tex
@@ -115,7 +115,7 @@ understand it (apart from maybe a few real dirty low level helpers that are also
 dirty because of performance reasons). Just take this into account when reading on.
 
 And yes, there are still a few possibilities I want to explore \unknown\ some might
-show up temporary so don't be surprises. I'm also aware that some new features can
+show up temporarily so don't be surprised. I'm also aware that some new features can
 have bugs or side effects that didn't show up in \CONTEXT, which after all is the
 benchmark and environment in which all this evolves.
 
@@ -2568,7 +2568,7 @@ introduce incompatibilities.
 
 The \prm {numexpression} and \prm {dimexpression} primitives are equivalent but
 offer more. The first one operates in the integer domain and the second one
-assumes scaled values. Often the second one can act like the first when one
+assumes scaled values. Often the second one can act like the first when
 serialized with \prm {number} in front. This is because when \TEX\ sees a
 symbolic reference to an integer or dimension it can treat them as it likes.
 
@@ -2602,7 +2602,7 @@ alternatives so that we can get around catcode issues.
 \LL
 \stoptabulate
 
-Here are some things that \prm {numexpr} is not suitable:
+Here are some things that \prm {numexpr} is not suitable for:
 
 \starttyping
 \scratchcounter = \numexpression
diff --git a/doc/context/sources/general/manuals/luametatex/luametatex-fonts.tex b/doc/context/sources/general/manuals/luametatex/luametatex-fonts.tex
index 83336ffd1..4e85a1b20 100644
--- a/doc/context/sources/general/manuals/luametatex/luametatex-fonts.tex
+++ b/doc/context/sources/general/manuals/luametatex/luametatex-fonts.tex
@@ -125,6 +125,7 @@ has no ligatures and kerns and is normally not processed at all.
 \NC \type {kerns}            \NC table   \NC kerning information \NC\NR
 \NC \type {ligatures}        \NC table   \NC ligaturing information \NC\NR
 \NC \type {mathkern}         \NC table   \NC math cut-in specifications \NC\NR
+\NC \type {smaller}          \NC number  \NC the next smaller math size character \NC\NR
 \LL
 \stoptabulate
 
diff --git a/doc/context/sources/general/manuals/luametatex/luametatex-math.tex b/doc/context/sources/general/manuals/luametatex/luametatex-math.tex
index af34af92b..30ce11c3b 100644
--- a/doc/context/sources/general/manuals/luametatex/luametatex-math.tex
+++ b/doc/context/sources/general/manuals/luametatex/luametatex-math.tex
@@ -28,7 +28,7 @@ You might be surprised that we don't use all these new control features in
 reason for adding so much is that I decided it made more sense to be complete now
 than gradually add more and more. At some point we should be able to say \quote
 {This is it}. Also, when looking at these features, you need to keep in mind that
-when it comes to math \LATEX\ is the dominant macro package and it never needed
+when it comes to math, \LATEX\ is the dominant macro package and it never needed
 these engine features, so most are probably just here for exploration purposes.
 
 \stopsection
diff --git a/doc/context/sources/general/manuals/luametatex/luametatex-modifications.tex b/doc/context/sources/general/manuals/luametatex/luametatex-modifications.tex
index cc08bc9c6..083fa732a 100644
--- a/doc/context/sources/general/manuals/luametatex/luametatex-modifications.tex
+++ b/doc/context/sources/general/manuals/luametatex/luametatex-modifications.tex
@@ -251,7 +251,8 @@ don't expect \LUAMETATEX\ to be compatible.
     related primitives \prm {lpcode}, \prm {rpcode}, \prm {efcode}, \prm
     {leftmarginkern}, \prm {rightmarginkern} are promoted to core primitives. The
     two commands \prm {protrudechars} and \prm {adjustspacing} control these
-    processes.
+    processes. The protrusion and kern related primitives are now dimensions
+    while expansion is still one of these 1000 based scales.
 \stopitem
 
 \startitem