diff --git a/manual/luatex-nodes.tex b/manual/luatex-nodes.tex
index 9b72fdf2c17b105249a1657a240de0db682154d1..347987d412ac916e8f1403910906707b0dd5b252 100644
--- a/manual/luatex-nodes.tex
+++ b/manual/luatex-nodes.tex
@@ -2391,7 +2391,7 @@ consistency. You can of course always define additional accessors using \type
 \supported {mlist_to_hlist}          \yes \nop
 \supported {new}                     \yes \yes
 \supported {next}                    \yes \nop
-\supported {prepend_prevdepth}       \nop \yes
+\supported {prepend_prevdepth}       \yes \yes
 \supported {prev}                    \yes \nop
 \supported {protect_glyphs}          \yes \yes
 \supported {protect_glyph}           \yes \yes
diff --git a/manual/luatex.pdf b/manual/luatex.pdf
index e2f5fe0e983e59ad87ed68dfe19cf2d077011987..cd2b45d0beab19cbeb80f54cbf2e589c687f2808 100644
Binary files a/manual/luatex.pdf and b/manual/luatex.pdf differ
diff --git a/source/texk/web2c/luatexdir/luatex_svnversion.h b/source/texk/web2c/luatexdir/luatex_svnversion.h
index 2648b75c37dc5503804749314cb55ca28ad4b261..52afadaa05c54e70f669723e517d6e9115292a06 100644
--- a/source/texk/web2c/luatexdir/luatex_svnversion.h
+++ b/source/texk/web2c/luatexdir/luatex_svnversion.h
@@ -1,4 +1,4 @@
 #ifndef luatex_svn_revision_h
 #define luatex_svn_revision_h
-#define luatex_svn_revision 7572
+#define luatex_svn_revision 7573
 #endif
diff --git a/source/texk/web2c/luatexdir/tex/texnodes.c b/source/texk/web2c/luatexdir/tex/texnodes.c
index 6e0ae1ff8ddba22594405f00e381c2a5408b74da..72f6716dd933f4a570d40af3feff548d7e36fc7d 100644
--- a/source/texk/web2c/luatexdir/tex/texnodes.c
+++ b/source/texk/web2c/luatexdir/tex/texnodes.c
@@ -1203,7 +1203,7 @@ void l_set_whatsit_data(void) {
     the original one as a metatable. After some experiments (that also included
     timing) with these scenarios I decided that a deep copy made no sense, nor
     did nilling. In the end both the shallow copy and the metatable variant were
-    both ok, although the second ons is slower. The most important aspect to keep
+    both ok, although the second one is slower. The most important aspect to keep
     in mind is that references to other nodes in properties no longer can be
     valid for that copy. We could use two tables (one unique and one shared) or
     metatables but that only complicates matters.