valenok -> cesanta

docs/UserManual.md

@@ -258,7 +258,7 @@ directory is commonly referenced as dot (`.`).
 Path to SSL certificate file. This option is only required when at least one
 of the `listening_ports` is SSL. The file must be in PEM format,
 and it must have both private key and certificate, see for example
-[ssl_cert.pem](https://github.com/valenok/mongoose/blob/master/build/ssl_cert.pem)
+[ssl_cert.pem](https://github.com/cesanta/mongoose/blob/master/build/ssl_cert.pem)
 
 ### num_threads `50`
 Number of worker threads. Mongoose handles each incoming connection in a
@@ -332,10 +332,10 @@ are accessible from the Lua code (please check reference manual for details),
 and also information about the request is available in `mg.request_info` object,
 like request method, all headers, etcetera. Please refer to
 `struct mg_request_info` definition in
-[mongoose.h](https://github.com/valenok/mongoose/blob/master/mongoose.h)
+[mongoose.h](https://github.com/cesanta/mongoose/blob/master/mongoose.h)
 to see what kind of information is present in `mg.request_info` object. Also,
-[page.lp](https://github.com/valenok/mongoose/blob/master/test/page.lp) and
-[prime_numbers.lp](https://github.com/valenok/mongoose/blob/master/examples/lua/prime_numbers.lp)
+[page.lp](https://github.com/cesanta/mongoose/blob/master/test/page.lp) and
+[prime_numbers.lp](https://github.com/cesanta/mongoose/blob/master/examples/lua/prime_numbers.lp)
 contains some example code that uses `request_info` and other functions(form submitting for example).
 
 Mongoose exports the following to the Lua server page:
@@ -398,8 +398,8 @@ variable is visible in the block that follows.
 
 # Embedding
 Embedding Mongoose is easy. Copy
-[mongoose.c](https://github.com/valenok/mongoose/blob/master/mongoose.c) and
-[mongoose.h](https://github.com/valenok/mongoose/blob/master/mongoose.h)
+[mongoose.c](https://github.com/cesanta/mongoose/blob/master/mongoose.c) and
+[mongoose.h](https://github.com/cesanta/mongoose/blob/master/mongoose.h)
 to your application's source tree and include them in the build. For
 example, your application's code lives in C file `my_app.c`, then on UNIX
 this command embeds Mongoose:
@@ -424,8 +424,7 @@ To start the embedded web server, call `mg_start()`. To stop it, call
 `mg_stop()`.
 
     // This structure needs to be passed to mg_start(), to let mongoose know
-    // which callbacks to invoke. For detailed description, see
-    // https://github.com/valenok/mongoose/blob/master/UserManual.md
+    // which callbacks to invoke.
     struct mg_callbacks {
       int  (*begin_request)(struct mg_connection *);
       void (*end_request)(const struct mg_connection *, int reply_status_code);
@@ -441,7 +440,7 @@ To start the embedded web server, call `mg_start()`. To stop it, call
       int  (*http_error)(struct mg_connection *, int status);
     };
 
-[hello.c](https://github.com/valenok/mongoose/blob/master/examples/hello.c)
+[hello.c](https://github.com/cesanta/mongoose/blob/master/examples/hello.c)
 provides a minimalistic example.
 
 Common pattern is to implement `begin_request` callback, and serve static files
@@ -502,7 +501,7 @@ limit on number of simultaneous requests that can be handled by mongoose.
 
 When master thread accepts new connection, a new accepted socket (described by
 `struct socket`) it placed into the accepted sockets queue,
-which has size of 20 (see [code](https://github.com/valenok/mongoose/blob/3892e0199e6ca9613b160535d9d107ede09daa43/mongoose.c#L486)). Any idle worker thread
+which has size of 20 (see [code](https://github.com/cesanta/mongoose/blob/3892e0199e6ca9613b160535d9d107ede09daa43/mongoose.c#L486)). Any idle worker thread
 can grab accepted sockets from that queue. If all worker threads are busy,
 master thread can accept and queue up to 20 more TCP connections,
 filling up the queue.