harden runtime config and docs

site/doc/pages/session_destroy.txt

@@ -8,9 +8,9 @@ session_name : the name of the session
 >session
 
 :content
-Deletes the cookie specified by `session_name` and clears the data stored under the current session ID.
+Deletes the cookie specified by `session_name`, removes the matching server-side session file, and clears the data stored under the current session ID.
 
-This also empties `context.session_id` and `context.session`.
+This also empties `context.session_id`, `context.session_name`, and `context.session`.
 
 
 :example

site/doc/pages/session_start.txt

@@ -11,7 +11,7 @@ return value : the current session ID
 :content
 Starts a session or reconnects to an existing one.
 
-If the cookie named by `session_name` does not exist, UCE creates it and fills it with a new unique session ID. The function then loads the session data for that ID.
+If the cookie named by `session_name` does not exist, UCE creates it and fills it with a new unique session ID. The function then loads the session data for that ID. Session cookies are emitted with `Path=/`, `HttpOnly`, `SameSite=Lax`, and `Secure` when `SESSION_COOKIE_SECURE=1` is set in the runtime config.
 
 After `session_start()` completes, the following `context` fields are populated:
 

site/doc/pages/socket_connect.txt

@@ -2,7 +2,7 @@
 u64 socket_connect(String host, u16 port)
 
 :params
-host : host name
+host : IPv4 address (for example `127.0.0.1`), as a dotted-quad string
 port : port number
 return value : the socket handle
 
@@ -12,7 +12,7 @@ return value : the socket handle
 :content
 Opens a socket connection to the given `host` and `port`.
 
-The returned socket handle is then used with `socket_read()`, `socket_write()`, and `socket_close()`.
+The returned socket handle is then used with `socket_read()`, `socket_write()`, and `socket_close()`. Currently this helper accepts IPv4 dotted-quad addresses in socket calls and does not perform hostname resolution.
 
 :example
 u64 fd = socket_connect("127.0.0.1", 80);