diff --git a/src/modules/ims_charging/README b/src/modules/ims_charging/README
index 04d00ebb05b..b4668674da0 100644
--- a/src/modules/ims_charging/README
+++ b/src/modules/ims_charging/README
@@ -560,7 +560,7 @@ modparam("ims_charging", "origin_realm", "kamailio-ims.org")
 
    Destination host to be used in Diameter messages to charging-server.
 
-   Default value is "hss.ims.smilecoms.com".
+   Default value is "".
 
    Example 1.15. destination_hostparameter usage
 ...
@@ -571,7 +571,7 @@ modparam("ims_charging", "destination_host", "ocs.kamailio-ims.org")
 
    Destination realm to be used in Diameter messages to charging-server.
 
-   Default value is "ims.smilecoms.com".
+   Default value is "".
 
    Example 1.16. destination_realmparameter usage
 ...
diff --git a/src/modules/pike/README b/src/modules/pike/README
index a7f66697e73..beea746f454 100644
--- a/src/modules/pike/README
+++ b/src/modules/pike/README
@@ -39,6 +39,7 @@ Bogdan-Andrei Iancu
    2. RPC calls
 
         1. pike.top
+        2. pike.list
 
    3. Developer Guide
 
@@ -49,6 +50,7 @@ Bogdan-Andrei Iancu
    1.3. Set remove_latency parameter
    1.4. Set pike_log_level parameter
    1.5. pike_check_req usage
+   2.1. Using pike.top
    3.1. Tree of IP addresses
 
 Chapter 1. Admin Guide
@@ -219,6 +221,7 @@ Chapter 2. RPC calls
    Table of Contents
 
    1. pike.top
+   2. pike.list
 
 1.  pike.top
 
@@ -230,9 +233,9 @@ Chapter 2. RPC calls
 
    Some IPs could be marked as HOT depending on theirs request rates.
 
-   pike.top command takes one string parameter which specifies what kind
-   of nodes you are interested in. Possible values are HOT or ALL. If no
-   argument is given, it behaves as HOT was used.
+   pike.top command can take one string parameter which specifies what
+   kind of nodes you are interested in. Possible values are HOT or ALL. If
+   no argument is given, it behaves as HOT was used.
 
    Marking nodes HOT is done on server side, client only presents given
    data and make some postprocessing like sorting.
@@ -240,6 +243,15 @@ Chapter 2. RPC calls
    Output of this command is a simple dump of ip_tree nodes marked as
    ip-leafs.
 
+   Example 2.1. Using pike.top
+...
+kamcli rpc pike.top ALL
+...
+
+2.  pike.list
+
+   Alias for "pike.top" command.
+
 Chapter 3. Developer Guide
 
    One single tree (for both IPv4 and IPv6) is used. Each node contains a
diff --git a/src/modules/pua/README b/src/modules/pua/README
index e2325902078..3079312646e 100644
--- a/src/modules/pua/README
+++ b/src/modules/pua/README
@@ -193,7 +193,7 @@ modparam("pua", "hash_size", 11)
 
    Example 1.2. Set db_url parameter
 ...
-modparam("pua", "db_url" "dbdriver://username:password@dbhost/dbname")
+modparam("pua", "db_url", "dbdriver://username:password@dbhost/dbname")
 ...
 
 3.3. db_table (str)
diff --git a/src/modules/sqlops/README b/src/modules/sqlops/README
index 3a08072c18b..f915dc33fcd 100644
--- a/src/modules/sqlops/README
+++ b/src/modules/sqlops/README
@@ -194,6 +194,8 @@ modparam("sqlops", "tr_buf_size", 4096)
      * -1 - error in parameters or query execution
      * 1 - query successful, at least one row in resultset (for SELECTs)
      * 2 - query successful, no rows returned
+       3 - query successful, at least one row returned, but result
+       parameter was not given
 
 4.1.  sql_query(connection, query[, result])
 
diff --git a/src/modules/tls/README b/src/modules/tls/README
index ab6688b18e5..844c4bb552f 100644
--- a/src/modules/tls/README
+++ b/src/modules/tls/README
@@ -1423,7 +1423,7 @@ end
 
 10.34. rand_engine (str)
 
-   Set the ranondom number generator engine for libssl.
+   Set the random number generator engine for libssl.
 
    Note: the default random number generator (PRNG) engine of libssl
    v1.1.x is not designed for multi-process applications and can result in
diff --git a/src/modules/topos/README b/src/modules/topos/README
index fd4108765cc..ab4020931c1 100644
--- a/src/modules/topos/README
+++ b/src/modules/topos/README
@@ -86,17 +86,21 @@ Chapter 1. Admin Guide
 
 1. Overview
 
-   This module offers topology hiding by stripping the SIP routing headers
-   that show topology details. The script interpreter gets the SIP
-   messages with full content, so all existing functionality is preserved.
+   This module offers topology hiding for INVITE-based dialogs, by
+   stripping the SIP routing headers that show topology details . The
+   script interpreter gets the SIP messages with full content, so all
+   existing functionality is preserved.
 
    The module is transparent for the configuration writer. It only needs
-   to be loaded (tune the parameters if needed).
+   to be loaded (tune the module parameters if needed).
 
    It also works for SIP MESSAGE or other requests that do not create a
-   call dialog -- record_route() must be used for them as well, the
-   headers are not going to be in the messages sent to the network, they
-   are needed to know local addresses used to communicate with each side.
+   dialog -- record_route() must be used for them as well, the headers are
+   not going to be in the messages sent to the network, they are needed to
+   know local addresses used to communicate with each side. At this moment
+   it is not designed to work for presence (SUBSCRIBE-based) dialogs. The
+   REGISTER and PUBLISH requests are skipped from processing by this
+   module, expected to be terminated on a local SIP server.
 
 2. Dependencies