diff --git a/libwebsockets-api-doc.html b/libwebsockets-api-doc.html
index b181dcd..6562149 100644
--- a/libwebsockets-api-doc.html
+++ b/libwebsockets-api-doc.html
@@ -1,67 +1,3 @@
-<h2>callback - User server actions</h2>
-<i>int</i>
-<b>callback</b>
-(<i>struct libwebsocket *</i> <b>wsi</b>,
-<i>enum libwebsocket_callback_reasons</i> <b>reason</b>,
-<i>void *</i> <b>user</b>,
-<i>void *</i> <b>in</b>,
-<i>size_t</i> <b>len</b>)
-<h3>Arguments</h3>
-<dl>
-<dt><b>wsi</b>
-<dd>Opaque websocket instance pointer
-<dt><b>reason</b>
-<dd>The reason for the call
-<dt><b>user</b>
-<dd>Pointer to per-session user data allocated by library
-<dt><b>in</b>
-<dd>Pointer used for some callback reasons
-<dt><b>len</b>
-<dd>Length set for some callback reasons
-</dl>
-<h3>Description</h3>
-<blockquote>
-This callback is the way the user controls what is served.  All the
-protocol detail is hidden and handled by the library.
-<p>
-For each connection / session there is user data allocated that is
-pointed to by "user".  You set the size of this user data area when
-the library is initialized with libwebsocket_create_server.
-<p>
-You get an opportunity to initialize user data when called back with
-LWS_CALLBACK_ESTABLISHED reason.
-</blockquote>
-<h3>LWS_CALLBACK_ESTABLISHED</h3>
-<blockquote>
-after successful websocket handshake
-</blockquote>
-<h3>LWS_CALLBACK_CLOSED</h3>
-<blockquote>
-when the websocket session ends
-</blockquote>
-<h3>LWS_CALLBACK_BROADCAST</h3>
-<blockquote>
-signal to send to client (you would use
-<b>libwebsocket_write</b> taking care about the
-special buffer requirements
-</blockquote>
-<h3>LWS_CALLBACK_RECEIVE</h3>
-<blockquote>
-data has appeared for the server, it can be
-found at *in and is len bytes long
-</blockquote>
-<h3>LWS_CALLBACK_HTTP</h3>
-<blockquote>
-an http request has come from a client that is not
-asking to upgrade the connection to a websocket
-one.  This is a chance to serve http content,
-for example, to send a script to the client
-which will then open the websockets connection.
-<tt><b>in</b></tt> points to the URI path requested and 
-<b>libwebsockets_serve_http_file</b> makes it very
-simple to send back a file to the client.
-</blockquote>
-<hr>
 <h2>libwebsocket_create_server - Create the listening websockets server</h2>
 <i>int</i>
 <b>libwebsocket_create_server</b>
@@ -226,6 +162,70 @@
 local files down the http link in a single step.
 </blockquote>
 <hr>
+<h2>callback - User server actions</h2>
+<i>int</i>
+<b>callback</b>
+(<i>struct libwebsocket *</i> <b>wsi</b>,
+<i>enum libwebsocket_callback_reasons</i> <b>reason</b>,
+<i>void *</i> <b>user</b>,
+<i>void *</i> <b>in</b>,
+<i>size_t</i> <b>len</b>)
+<h3>Arguments</h3>
+<dl>
+<dt><b>wsi</b>
+<dd>Opaque websocket instance pointer
+<dt><b>reason</b>
+<dd>The reason for the call
+<dt><b>user</b>
+<dd>Pointer to per-session user data allocated by library
+<dt><b>in</b>
+<dd>Pointer used for some callback reasons
+<dt><b>len</b>
+<dd>Length set for some callback reasons
+</dl>
+<h3>Description</h3>
+<blockquote>
+This callback is the way the user controls what is served.  All the
+protocol detail is hidden and handled by the library.
+<p>
+For each connection / session there is user data allocated that is
+pointed to by "user".  You set the size of this user data area when
+the library is initialized with libwebsocket_create_server.
+<p>
+You get an opportunity to initialize user data when called back with
+LWS_CALLBACK_ESTABLISHED reason.
+</blockquote>
+<h3>LWS_CALLBACK_ESTABLISHED</h3>
+<blockquote>
+after successful websocket handshake
+</blockquote>
+<h3>LWS_CALLBACK_CLOSED</h3>
+<blockquote>
+when the websocket session ends
+</blockquote>
+<h3>LWS_CALLBACK_BROADCAST</h3>
+<blockquote>
+signal to send to client (you would use
+<b>libwebsocket_write</b> taking care about the
+special buffer requirements
+</blockquote>
+<h3>LWS_CALLBACK_RECEIVE</h3>
+<blockquote>
+data has appeared for the server, it can be
+found at *in and is len bytes long
+</blockquote>
+<h3>LWS_CALLBACK_HTTP</h3>
+<blockquote>
+an http request has come from a client that is not
+asking to upgrade the connection to a websocket
+one.  This is a chance to serve http content,
+for example, to send a script to the client
+which will then open the websockets connection.
+<tt><b>in</b></tt> points to the URI path requested and 
+<b>libwebsockets_serve_http_file</b> makes it very
+simple to send back a file to the client.
+</blockquote>
+<hr>
 <h2>struct libwebsocket_protocols - List of protocols and handlers server supports.</h2>
 <b>struct libwebsocket_protocols</b> {<br>
 &nbsp; &nbsp; <i>const char *</i> <b>name</b>;<br>