From 4226f9400d329467bf87b6bae2c9c57571250cb9 Mon Sep 17 00:00:00 2001
From: Benoit Germain <benoit.germain@ubisoft.com>
Date: Thu, 20 Jun 2024 12:36:38 +0200
Subject: Revert overzealous upvalue check on on_state_create

---
 docs/index.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'docs')

diff --git a/docs/index.html b/docs/index.html
index ca91273..6e2b4ed 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -358,6 +358,7 @@
 			<td>
 				If provided, will be called in every created Lua state right after initializing the base libraries, with a single string argument, either <tt>"lane"</tt> or <tt>"keeper"</tt>.<br />
 				If it is a C function, a C closure will be reconstructed in the created state from the C pointer. Lanes will raise an error if the function has upvalues.<br />
+				If it is a Lua function, it will be transfered normally before the call.<br />
 				Keeper states will call it as well, but only if it is a C function (<a href="#keepers">Keeper states</a> are not able to execute any user Lua code).<br />
 				Typical usage is twofold:
 				<ul>
@@ -365,7 +366,6 @@
 					<li>Load some additional C functions in the global space (of course only a C function will be able to do this).</li>
 				</ul>
 				That way, all changes in the state can be properly taken into account when building the function lookup database. Default is <tt>nil</tt>.<br />
-				If <tt>on_state_create()</tt> is a Lua function, it will be transfered normally before the call.<br />
 			</td>
 		</tr>
 
-- 
cgit v1.2.3-55-g6feb