diff --git a/src/include/d_options.rec b/src/include/d_options.rec
index ba52836b..8eb09cb9 100644
--- a/src/include/d_options.rec
+++ b/src/include/d_options.rec
@@ -72,7 +72,7 @@ Argument1: size_t sa_len
 Description1: the size of the socket address pointed by @a sa.
 Argument2: /* const */ struct sockaddr *sa
 Description2: the address to bind to; can be IPv4 (AF_INET), IPv6 (AF_INET6) or even a UNIX domain socket (AF_UNIX)
-Argument3: enum MHD_Bool v_dual
+Argument3: enum MHD_Bool dual
 Description3: When a previous version of the protocol exist (like IPv4 when @a v_sa is IPv6) bind to both protocols (IPv6 and IPv4).
 CustomSetter: /* custom setter */
 +  if (0 != option->val.bind_sa.v_sa_len)
@@ -380,7 +380,7 @@ Comment: Set strong random data to be used by MHD.
 + Sizes larger then 32 (or, probably, larger than 16 - debatable) will not increase the security.
 Argument1: size_t buf_size
 Description1: the size of the buffer
-Argument2: const void *buf
+Argument2: /* const */ void *buf
 Description2: the buffer with strong random data, the content will be copied by MHD
 Type: struct MHD_DaemonOptionEntropySeed
 CustomSetter: /* custom setter */
diff --git a/src/include/r_options.rec b/src/include/r_options.rec
index 4abc6755..af46efc9 100644
--- a/src/include/r_options.rec
+++ b/src/include/r_options.rec
@@ -57,6 +57,11 @@ Comment: Only respond in conservative (dumb) HTTP/1.0-compatible mode.
 + Response still use HTTP/1.1 version in header, but always close the connection after sending the response and do not use chunked encoding for the response.
 + You can also set the #MHD_R_O_HTTP_1_0_SERVER flag to force HTTP/1.0 version in the response.
 + Responses are still compatible with HTTP/1.1.
++ Summary:
++ + declared reply version: HTTP/1.1
++ + keep-alive: no
++ + chunked: no
++
 + This option can be used to communicate with some broken client, which does not implement HTTP/1.1 features, but advertises HTTP/1.1 support.
 
 Name: HTTP_1_0_SERVER
@@ -68,6 +73,11 @@ Comment: Only respond in HTTP/1.0-mode.
 + Chunked encoding will not be used for the response.
 + Due to backward compatibility, responses still can be used with HTTP/1.1 clients.
 + This option can be used to emulate HTTP/1.0 server (for response part only as chunked encoding in requests (if any) is processed by MHD).
++ Summary:
++ + declared reply version: HTTP/1.0
++ + keep-alive: possible
++ + chunked: no
++
 + With this option HTTP/1.0 server is emulated (with support for 'keep-alive' connections).
 
 # Violate HTTP and/or RFCs