5 files changed, 10 insertions, 14 deletions

diff --git a/doc/changes.html b/doc/changes.html
index 43c1f84e..51027a93 100644
--- a/doc/changes.html
+++ b/doc/changes.html
@@ -59,7 +59,7 @@ div.major { max-width: 600px; padding: 1em; margin: 1em 0 1em 0; }
 <div id="main">
 <p>
 This is a list of changes between the released versions of LuaJIT.<br>
-The current <span style="color: #c00000;">development version</span> is <strong>LuaJIT&nbsp;2.0.0-beta8</strong>.<br>
+The current <span style="color: #c00000;">development version</span> is <strong>LuaJIT&nbsp;2.0.0-beta9</strong>.<br>
 The current <span style="color: #0000c0;">stable version</span> is <strong>LuaJIT&nbsp;1.1.7</strong>.
 </p>
 <p>
diff --git a/doc/ext_ffi_semantics.html b/doc/ext_ffi_semantics.html
index b111ed5d..661b0b4c 100644
--- a/doc/ext_ffi_semantics.html
+++ b/doc/ext_ffi_semantics.html
@@ -942,8 +942,8 @@ GUI application, which waits for user input most of the time, anyway.
 For new designs <b>avoid push-style APIs</b> (C&nbsp;function repeatedly
 calling a callback for each result). Instead <b>use pull-style APIs</b>
 (call a C&nbsp;function repeatedly to get a new result). Calls from Lua
-to C via the FFI are much faster than the other way round. Most well
-designed libraries already use pull-style APIs (read/write, get/put).
+to C via the FFI are much faster than the other way round. Most well-designed
+libraries already use pull-style APIs (read/write, get/put).
 </p>
 
 <h2 id="clib">C Library Namespaces</h2>
diff --git a/doc/install.html b/doc/install.html
index 6a9a2c9f..4e226d17 100644
--- a/doc/install.html
+++ b/doc/install.html
@@ -178,8 +178,8 @@ open a terminal window and change to this directory. Now unpack the archive
 and change to the newly created directory:
 </p>
 <pre class="code">
-tar zxf LuaJIT-2.0.0-beta8.tar.gz
-cd LuaJIT-2.0.0-beta8</pre>
+tar zxf LuaJIT-2.0.0-beta9.tar.gz
+cd LuaJIT-2.0.0-beta9</pre>
 <h3>Building LuaJIT</h3>
 <p>
 The supplied Makefiles try to auto-detect the settings needed for your
@@ -229,11 +229,11 @@ Obviously the prefixes given during build and installation need to be the same.
 <p style="color: #c00000;">
 Note: to avoid overwriting a previous version, the beta test releases
 only install the LuaJIT executable under the versioned name (i.e.
-<tt>luajit-2.0.0-beta8</tt>). You probably want to create a symlink
+<tt>luajit-2.0.0-beta9</tt>). You probably want to create a symlink
 for convenience, with a command like this:
 </p>
 <pre class="code" style="color: #c00000;">
-sudo ln -sf luajit-2.0.0-beta8&nbsp;/usr/local/bin/luajit
+sudo ln -sf luajit-2.0.0-beta9&nbsp;/usr/local/bin/luajit
 </pre>
 
 <h2 id="windows">Windows Systems</h2>
diff --git a/doc/running.html b/doc/running.html
index 109df5df..e2afdeef 100644
--- a/doc/running.html
+++ b/doc/running.html
@@ -85,11 +85,11 @@ interactive mode, too.
 <p class="indent" style="color: #c00000;">
 Note: the beta test releases only install under the versioned name on
 POSIX systems (to avoid overwriting a previous version). You either need
-to type <tt>luajit-2.0.0-beta8</tt> to start it or create a symlink
+to type <tt>luajit-2.0.0-beta9</tt> to start it or create a symlink
 with a command like this:
 </p>
 <pre class="code" style="color: #c00000;">
-sudo ln -sf luajit-2.0.0-beta8&nbsp;/usr/local/bin/luajit
+sudo ln -sf luajit-2.0.0-beta9&nbsp;/usr/local/bin/luajit
 </pre>
 <p>
 Unlike previous versions <b>optimization is turned on by default</b> in
@@ -195,7 +195,7 @@ itself. For a description of their options and output format, please
 read the comment block at the start of their source.
 They can be found in the <tt>lib</tt> directory of the source
 distribution or installed under the <tt>jit</tt> directory. By default
-this is <tt>/usr/local/share/luajit-2.0.0-beta8/jit</tt> on POSIX
+this is <tt>/usr/local/share/luajit-2.0.0-beta9/jit</tt> on POSIX
 systems.
 </p>
 
diff --git a/doc/status.html b/doc/status.html
index 5f8fa463..d9cffe03 100644
--- a/doc/status.html
+++ b/doc/status.html
@@ -148,10 +148,6 @@ with me, before writing major improvements, to avoid duplication of
 effort.
 </li>
 <li>
-<b>Trace management</b> needs more tuning: less drastic countermeasures
-against trace explosion and better heuristics in general.
-</li>
-<li>
 Some checks are missing in the JIT-compiled code for obscure situations
 with <b>open upvalues aliasing</b> one of the SSA slots later on (or
 vice versa). Bonus points, if you can find a real world test case for