typos and improvements to language

- from PR #25

docs/cookbooks/3.2.x/core.md

@@ -1175,7 +1175,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -1712,7 +1712,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -1872,7 +1872,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -1886,10 +1886,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -1950,8 +1950,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -1997,7 +1997,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -2318,7 +2318,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Usefull if
-you want to send all the trafic to port_alias through the same
+you want to send all the traffic to port_alias through the same
 connection this request came from \[it could help for firewall or nat traversal\]. With no parameters adds the port from the message via as
 the alias. When the "aliased" connection is closed (e.g. it's idle for
 too much time), all the port aliases are removed.

docs/cookbooks/3.3.x/core.md

@@ -1035,7 +1035,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -1373,7 +1373,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -1930,7 +1930,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -2106,7 +2106,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -2120,10 +2120,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -2184,8 +2184,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -2231,7 +2231,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -2552,7 +2552,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Usefull if
-you want to send all the trafic to port_alias through the same
+you want to send all the traffic to port_alias through the same
 connection this request came from \[it could help for firewall or nat traversal\]. With no parameters adds the port from the message via as
 the alias. When the "aliased" connection is closed (e.g. it's idle for
 too much time), all the port aliases are removed.

docs/cookbooks/4.0.x/core.md

@@ -1084,7 +1084,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -1422,7 +1422,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -1979,7 +1979,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -2165,7 +2165,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -2179,10 +2179,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -2243,8 +2243,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -2290,7 +2290,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -2610,7 +2610,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Usefull if
-you want to send all the trafic to port_alias through the same
+you want to send all the traffic to port_alias through the same
 connection this request came from \[it could help for firewall or nat traversal\]. With no parameters adds the port from the message via as
 the alias. When the "aliased" connection is closed (e.g. it's idle for
 too much time), all the port aliases are removed.

docs/cookbooks/4.1.x/core.md

@@ -1087,7 +1087,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -1395,7 +1395,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -1960,7 +1960,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -2144,7 +2144,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -2158,10 +2158,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -2222,8 +2222,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -2269,7 +2269,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -2589,7 +2589,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Usefull if
-you want to send all the trafic to port_alias through the same
+you want to send all the traffic to port_alias through the same
 connection this request came from \[it could help for firewall or nat traversal\]. With no parameters adds the port from the message via as
 the alias. When the "aliased" connection is closed (e.g. it's idle for
 too much time), all the port aliases are removed.

docs/cookbooks/4.2.x/core.md

@@ -1123,7 +1123,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -1438,7 +1438,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -2007,7 +2007,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -2191,7 +2191,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -2205,10 +2205,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -2269,8 +2269,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -2316,7 +2316,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -2569,7 +2569,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Usefull if
-you want to send all the trafic to port_alias through the same
+you want to send all the traffic to port_alias through the same
 connection this request came from \[it could help for firewall or nat traversal\]. With no parameters adds the port from the message via as
 the alias. When the "aliased" connection is closed (e.g. it's idle for
 too much time), all the port aliases are removed.

docs/cookbooks/4.3.x/core.md

@@ -1127,7 +1127,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -1454,7 +1454,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -2034,7 +2034,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -2218,7 +2218,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -2232,10 +2232,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -2296,8 +2296,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -2343,7 +2343,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -2596,7 +2596,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Usefull if
-you want to send all the trafic to port_alias through the same
+you want to send all the traffic to port_alias through the same
 connection this request came from \[it could help for firewall or nat traversal\]. With no parameters adds the port from the message via as
 the alias. When the "aliased" connection is closed (e.g. it's idle for
 too much time), all the port aliases are removed.
@@ -3194,8 +3194,8 @@ routing block can be also identified by 'onreply_route {...}' or
 ### onreply_route
 
 SIP reply routing block executed by **tm** module. It contains a set of
-actions to be taken for SIP replies in the contect of an active
-transaction..
+actions to be taken for SIP replies in the context of an active
+transaction.
 
 The 'onreply_route' must be armed for the SIP requests whose replies
 should be processed within it, via t_on_reply("onreply_route_index").

docs/cookbooks/4.4.x/core.md

@@ -1351,7 +1351,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -1691,7 +1691,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -2271,7 +2271,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -2455,7 +2455,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -2469,10 +2469,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -2533,8 +2533,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -2580,7 +2580,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -2834,7 +2834,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Usefull if
-you want to send all the trafic to port_alias through the same
+you want to send all the traffic to port_alias through the same
 connection this request came from \[it could help for firewall or nat traversal\]. With no parameters adds the port from the message via as
 the alias. When the "aliased" connection is closed (e.g. it's idle for
 too much time), all the port aliases are removed.
@@ -3463,8 +3463,8 @@ routing block can be also identified by 'onreply_route {...}' or
 ### onreply_route
 
 SIP reply routing block executed by **tm** module. It contains a set of
-actions to be taken for SIP replies in the contect of an active
-transaction..
+actions to be taken for SIP replies in the context of an active
+transaction.
 
 The 'onreply_route' must be armed for the SIP requests whose replies
 should be processed within it, via t_on_reply("onreply_route_index").

docs/cookbooks/5.0.x/core.md

@@ -1402,7 +1402,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -1762,7 +1762,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -2356,7 +2356,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -2540,7 +2540,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -2554,10 +2554,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -2618,8 +2618,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -2665,7 +2665,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -2919,7 +2919,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Useful if you
-want to send all the trafic to port_alias through the same connection
+want to send all the traffic to port_alias through the same connection
 this request came from \[it could help for firewall or nat traversal\].
 With no parameters adds the port from the message via as the alias. When
 the "aliased" connection is closed (e.g. it's idle for too much time),
@@ -3550,8 +3550,8 @@ routing block can be also identified by 'onreply_route {...}' or
 ### onreply_route
 
 SIP reply routing block executed by **tm** module. It contains a set of
-actions to be taken for SIP replies in the contect of an active
-transaction..
+actions to be taken for SIP replies in the context of an active
+transaction.
 
 The 'onreply_route' must be armed for the SIP requests whose replies
 should be processed within it, via t_on_reply("onreply_route_index").

docs/cookbooks/5.1.x/core.md

@@ -1439,7 +1439,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -1809,7 +1809,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -2428,7 +2428,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -2623,7 +2623,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -2637,10 +2637,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -2701,8 +2701,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -2748,7 +2748,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -3002,7 +3002,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Useful if you
-want to send all the trafic to port_alias through the same connection
+want to send all the traffic to port_alias through the same connection
 this request came from \[it could help for firewall or nat traversal\].
 With no parameters adds the port from the message via as the alias. When
 the "aliased" connection is closed (e.g. it's idle for too much time),
@@ -3640,8 +3640,8 @@ routing block can be also identified by 'onreply_route {...}' or
 ### onreply_route
 
 SIP reply routing block executed by **tm** module. It contains a set of
-actions to be taken for SIP replies in the contect of an active
-transaction..
+actions to be taken for SIP replies in the context of an active
+transaction.
 
 The 'onreply_route' must be armed for the SIP requests whose replies
 should be processed within it, via t_on_reply("onreply_route_index").

docs/cookbooks/5.2.x/core.md

@@ -1127,7 +1127,7 @@ function.
 Example:
 
 ``` c
-kemi.onsend_route_callback="ksr_my_reply_route"
+kemi.reply_route_callback="ksr_my_reply_route"
 ```
 
 ### latency_cfg_log
@@ -1511,7 +1511,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -1899,7 +1899,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -2556,7 +2556,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -2751,7 +2751,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -2765,10 +2765,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -2829,8 +2829,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -2876,7 +2876,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -3130,7 +3130,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Useful if you
-want to send all the trafic to port_alias through the same connection
+want to send all the traffic to port_alias through the same connection
 this request came from \[it could help for firewall or nat traversal\].
 With no parameters adds the port from the message via as the alias. When
 the "aliased" connection is closed (e.g. it's idle for too much time),
@@ -3770,7 +3770,7 @@ routing block can be also identified by 'onreply_route {...}' or
 ### onreply_route
 
 SIP reply routing block executed by **tm** module. It contains a set of
-actions to be taken for SIP replies in the contect of an active
+actions to be taken for SIP replies in the context of an active
 transaction.
 
 The 'onreply_route' must be armed for the SIP requests whose replies

docs/cookbooks/5.3.x/core.md

@@ -1168,7 +1168,7 @@ function.
 Example:
 
 ``` c
-kemi.onsend_route_callback="ksr_my_reply_route"
+kemi.reply_route_callback="ksr_my_reply_route"
 ```
 
 ### latency_cfg_log
@@ -1559,7 +1559,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -1976,7 +1976,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -2679,7 +2679,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -2874,7 +2874,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -2888,10 +2888,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -2952,8 +2952,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -2999,7 +2999,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -3256,7 +3256,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Useful if you
-want to send all the trafic to port_alias through the same connection
+want to send all the traffic to port_alias through the same connection
 this request came from \[it could help for firewall or nat traversal\].
 With no parameters adds the port from the message via as the alias. When
 the "aliased" connection is closed (e.g. it's idle for too much time),
@@ -3898,7 +3898,7 @@ routing block can be also identified by 'onreply_route {...}' or
 ### onreply_route
 
 SIP reply routing block executed by **tm** module. It contains a set of
-actions to be taken for SIP replies in the contect of an active
+actions to be taken for SIP replies in the context of an active
 transaction.
 
 The 'onreply_route' must be armed for the SIP requests whose replies

docs/cookbooks/5.4.x/core.md

@@ -1193,7 +1193,7 @@ function.
 Example:
 
 ``` c
-kemi.onsend_route_callback="ksr_my_reply_route"
+kemi.reply_route_callback="ksr_my_reply_route"
 ```
 
 ### latency_cfg_log
@@ -1607,7 +1607,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -2039,7 +2039,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -2750,7 +2750,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -2945,7 +2945,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -2959,10 +2959,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -3023,8 +3023,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -3070,7 +3070,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -3327,7 +3327,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Useful if you
-want to send all the trafic to port_alias through the same connection
+want to send all the traffic to port_alias through the same connection
 this request came from \[it could help for firewall or nat traversal\].
 With no parameters adds the port from the message via as the alias. When
 the "aliased" connection is closed (e.g. it's idle for too much time),
@@ -3969,7 +3969,7 @@ routing block can be also identified by 'onreply_route {...}' or
 ### onreply_route
 
 SIP reply routing block executed by **tm** module. It contains a set of
-actions to be taken for SIP replies in the contect of an active
+actions to be taken for SIP replies in the context of an active
 transaction.
 
 The 'onreply_route' must be armed for the SIP requests whose replies

docs/cookbooks/5.5.x/core.md

@@ -1286,7 +1286,7 @@ function.
 Example:
 
 ``` c
-kemi.onsend_route_callback="ksr_my_reply_route"
+kemi.reply_route_callback="ksr_my_reply_route"
 ```
 
 ### kemi.pre_routing_callback
@@ -1735,7 +1735,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -2200,7 +2200,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -2952,7 +2952,7 @@ linux tcp(7) TCP_SYNCNT). Linux only.
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -3147,7 +3147,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -3161,10 +3161,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -3225,8 +3225,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -3272,7 +3272,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -3529,7 +3529,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Useful if you
-want to send all the trafic to port_alias through the same connection
+want to send all the traffic to port_alias through the same connection
 this request came from \[it could help for firewall or nat traversal\].
 With no parameters adds the port from the message via as the alias. When
 the "aliased" connection is closed (e.g. it's idle for too much time),
@@ -4200,7 +4200,7 @@ routing block can be also identified by 'onreply_route {...}' or
 ### onreply_route
 
 SIP reply routing block executed by **tm** module. It contains a set of
-actions to be taken for SIP replies in the contect of an active
+actions to be taken for SIP replies in the context of an active
 transaction.
 
 The 'onreply_route' must be armed for the SIP requests whose replies

docs/cookbooks/5.6.x/core.md

@@ -1324,7 +1324,7 @@ function.
 Example:
 
 ``` c
-kemi.onsend_route_callback="ksr_my_reply_route"
+kemi.reply_route_callback="ksr_my_reply_route"
 ```
 
 ### kemi.pre_routing_callback
@@ -1804,7 +1804,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -2270,7 +2270,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (udp_mtu_try_proto must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: 1300. Default: 0 (off).
@@ -3056,7 +3056,7 @@ tcp_wait_data = 10000
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -3240,7 +3240,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay will cause lots of
+WARNING: values lower than the sctp sack_delay will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -3254,10 +3254,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp sack_delay of any peer might cause
+WARNING: values lower than the sctp sack_delay of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the sack_delay should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their sack_delay is higher or their sack_freq
 is 1.
 
@@ -3318,8 +3318,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the sack_delay
 value should be between 200 and 500 ms.
 
@@ -3365,7 +3365,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with CAP_NET_RAW). udp4_raw can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with -DUSE_RAW_SOCKS. On Linux one
 should also set udp4_raw_mtu if the MTU on any network interface that
-could be used for sending is smaller then 1500.
+could be used for sending is smaller than 1500.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (core.udp4_raw).
@@ -3622,7 +3622,7 @@ Example of usage:
 force_tcp_alias(port)
 
 adds a tcp port alias for the current connection (if tcp). Useful if you
-want to send all the trafic to port_alias through the same connection
+want to send all the traffic to port_alias through the same connection
 this request came from \[it could help for firewall or nat traversal\].
 With no parameters adds the port from the message via as the alias. When
 the "aliased" connection is closed (e.g. it's idle for too much time),
@@ -4291,7 +4291,7 @@ routing block can be also identified by `onreply_route {...}` or
 ### onreply_route
 
 SIP reply routing block executed by **tm** module. It contains a set of
-actions to be taken for SIP replies in the contect of an active
+actions to be taken for SIP replies in the context of an active
 transaction.
 
 The `onreply_route` must be armed for the SIP requests whose replies

docs/cookbooks/devel/core.md

@@ -1570,7 +1570,7 @@ function.
 Example:
 
 ``` c
-kemi.onsend_route_callback="ksr_my_reply_route"
+kemi.reply_route_callback="ksr_my_reply_route"
 ```
 
 ### kemi.pre_routing_callback
@@ -2095,7 +2095,7 @@ Please see also [#memdbg](#memdbg) and [#debug](#debug).
 
 ### mem_join
 
-If set to 1, memory manger (e.g., q_malloc) does join of free fragments.
+If set to 1, memory manager (e.g., q_malloc) does join of free fragments.
 It is effective if MEM_JOIN_FREE compile option is defined.
 
 It can be set via config reload framework.
@@ -2681,7 +2681,7 @@ Example of usage:
 ### udp_mtu
 
 Fallback to another protocol (`udp_mtu_try_proto` must be set also either
-globally or per packet) if the constructed request size is greater then
+globally or per packet) if the constructed request size is greater than
 udp_mtu.
 
 RFC 3261 specified size: `1300`. Default: `0` (off).
@@ -3583,7 +3583,7 @@ tcp_wait_data = 10000
 ### tcp_wq_blk_size
 
 Block size used for tcp async writes. It should be big enough to hold a
-few datagrams. If it's smaller then a datagram (in fact a tcp write())
+few datagrams. If it's smaller than a datagram (in fact a tcp write())
 size, it will be rounded up. It has no influenced on the number of
 datagrams queued (for that see tcp_conn_wq_max or tcp_wq_max). It has
 mostly debugging and testing value (can be ignored).
@@ -3801,7 +3801,7 @@ new associations.
 Maximum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp `sack_delay` will cause lots of
+WARNING: values lower than the sctp `sack_delay` will cause lots of
 retransmissions and connection instability (see sctp_srto_min for more
 details).
 
@@ -3817,10 +3817,10 @@ associations.
 Minimum value of the retransmission timeout (RTO) (default: OS
 specific).
 
-WARNING: values lower then the sctp `sack_delay` of any peer might cause
+WARNING: values lower than the sctp `sack_delay` of any peer might cause
 retransmissions and possible interoperability problems. According to the
 standard the `sack_delay` should be between 200 and 500 ms, so avoid
-trying values lower then 500 ms unless you control all the possible sctp
+trying values lower than 500 ms unless you control all the possible sctp
 peers and you do make sure their `sack_delay` is higher or their sack_freq
 is 1.
 
@@ -3893,8 +3893,8 @@ associations.
 Delay until an ACK is generated after receiving a packet. Default: OS
 specific.
 
-WARNING: a value higher then srto_min can cause a lot of retransmissions
-(and strange problems). A value higher then srto_max will result in very
+WARNING: a value higher than srto_min can cause a lot of retransmissions
+(and strange problems). A value higher than srto_max will result in very
 high connections instability. According to the standard the `sack_delay`
 value should be between 200 and 500 ms.
 
@@ -3946,7 +3946,7 @@ In "auto" mode it will be enabled if possible (sr started as root or
 with `CAP_NET_RAW`). `udp4_raw` can be used on Linux and FreeBSD. For other
 BSDs and Darwin one must compile with `-DUSE_RAW_SOCKS`. On Linux one
 should also set `udp4_raw_mtu` if the MTU on any network interface that
-could be used for sending is smaller then `1500`.
+could be used for sending is smaller than `1500`.
 
 The parameter can be set at runtime as long as sr was started with
 enough privileges (`core.udp4_raw`).
@@ -4251,7 +4251,7 @@ Example of usage:
 `force_tcp_alias(port)`
 
 adds a tcp port alias for the current connection (if tcp). Useful if you
-want to send all the trafic to port_alias through the same connection
+want to send all the traffic to port_alias through the same connection
 this request came from (it could help for firewall or nat traversal).
 With no parameters adds the port from the message via as the alias. When
 the "aliased" connection is closed (e.g. it's idle for too much time),
@@ -4968,7 +4968,7 @@ routing block can be also identified by `onreply_route {...}` or
 ### onreply_route
 
 SIP reply routing block executed by **tm** module. It contains a set of
-actions to be taken for SIP replies in the contect of an active
+actions to be taken for SIP replies in the context of an active
 transaction.
 
 The `onreply_route` must be armed for the SIP requests whose replies

docs/devel/irc-meetings/2014alog.md

@@ -849,7 +849,7 @@ but only because cassandra has CQL, which resembles a poor SQL
 embedded?  
 \[2014-05-14 18:16:25\] \<caruizdiaz> usrloc for example: it has some
 plain sql queries that make it impossible to use with a dbms that does
-not suport sql  
+not support sql  
 \[2014-05-14 18:16:33\] \<eZz> what about hadoop?  
 \[2014-05-14 18:16:47\] \<miconda> caruizdiaz: iirc, that is for db only
 mode  
@@ -1002,7 +1002,7 @@ some opinions and hints
 discussion  
 \[2014-05-14 18:38:41\] \<stangrze> i'd like someone to suggest me a
 name for that broadsoft as-feature-sync module  
-\[2014-05-14 18:38:57\] \<stangrze> this is generaly presence related  
+\[2014-05-14 18:38:57\] \<stangrze> this is generally presence related  
 \[2014-05-14 18:39:11\] \<miconda> isn’t that like sca module?  
 \[2014-05-14 18:39:16\] \<miconda> or something else?  
 \[2014-05-14 18:39:21\] \<linuxmaniac> I have to leave, see you!  

docs/devel/irc-meetings/2016a-minutes.md

@@ -276,7 +276,7 @@ http:*lists.sip-router.org/pipermail/sr-users/2016-April/092510.html
 **miconda:** ycaner is involved in it  
 **ycaner:** hello  
 **linuxmaniac:** return code?? should be http 4XX doesn't it?  
-**miconda: to summarize:** the complain is that some rpc comands don’t
+**miconda: to summarize:** the complain is that some rpc commands don’t
 return data  
 **miconda:** specially the reload ones  
 **ycaner:** http return code and rpc return code is different in my
@@ -1609,7 +1609,7 @@ Kamailio people are" support it.
 modules don't get as much maintenance or use. Human nature.  
 **qxork:** unless someone offers to take ownership  
 **qxork:** developers leave, retire, move on...  
-**qxork:** if noone wants to take it, it's like a hobbiest module  
+**qxork:** if no one wants to take it, it's like a hobbiest module  
 **miconda:** on the other hand, adding officially maintained means
 pressure on devs  
 **miconda:** there are many lcr modules, developed/used by various

docs/devel/irc-meetings/2016b.md

@@ -92,7 +92,7 @@ Tuning Kamailio 5.0
 -   07:05 miconda: ok — I guess we can start
 -   07:05 qxork: =)
 -   07:05 miconda: as usual, first are the major issues
--   07:05 miconda: if there is someting that people feel is not working
+-   07:05 miconda: if there is something that people feel is not working
     as it should
 -   07:05 miconda: code or admin wise
 -   07:06 miconda: ok … so nothing reported here
@@ -107,7 +107,7 @@ Tuning Kamailio 5.0
 -   07:07 abalashov: I can also just post about it later if now is not
     the appropriate time.
 -   07:08 miconda: abalashov: you can describe it shortly, let’s see if
-    we can get someting now
+    we can get something now
 -   07:08 miconda: if not, later ...
 -   07:09 abalashov: Basically, if an interface has a primary and a
     secondary IP both on the same subnet.
@@ -163,7 +163,7 @@ Tuning Kamailio 5.0
 -   07:15 abalashov: qxork: The desire would be to have Kamailio just do
     the right thing magically, assisted by the local routing table's
     policy routing rules.
--   07:15 miconda: there was a pull requiest recently on updating the
+-   07:15 miconda: there was a pull request recently on updating the
     rpm specs for centos
 -   07:15 abalashov: qxork: Becomes important in a lot of weird "cloud"
     and "SBC" applications of Kamailio.
@@ -480,7 +480,7 @@ Tuning Kamailio 5.0
 -   07:51 miconda: the execution of the base c functions is done the
     same
 -   07:52 abalashov: qxork: Can we get Oracle to pay for it?
--   07:52 miconda: the lokup of failure/branc/onreply_route blcoks is
+-   07:52 miconda: the lookup of failure/branc/onreply_route blcoks is
     very fast
 -   07:52 miconda: because typically a kamailiocfg has only few of them
 -   07:52 abalashov: nods
@@ -526,7 +526,7 @@ Tuning Kamailio 5.0
     I need to drop. :/ (It pertains to transactions for which I've
     already sent 2xx replies from Kam, and then suspended to wake up
     later...)
--   07:57 miconda: it’s open source, if someting is not there, then a PR
+-   07:57 miconda: it’s open source, if something is not there, then a PR
     was not received :-)
 -   07:58 miconda: I am sure it can be addressed
 -   07:58 abalashov: So is there some technical reason why 2xx replies

docs/devel/irc-meetings/2017b.md

@@ -177,7 +177,7 @@ Kamailio 5.1 (next major release):
     we do it properly, right now is a bit foggy in this area
 -   15:21 linuxmaniac: maybe trying to migrate the configuration to
     ansible can be good too
--   15:21 miconda: people do not know who to aproach in some situations
+-   15:21 miconda: people do not know who to approach in some situations
 -   15:21 miconda: linuxmaniac: that would be great if we can automate
 -   15:21 miconda: but needs time
 -   15:22 linuxmaniac: sure
@@ -510,7 +510,7 @@ Kamailio 5.1 (next major release):
 -   16:26 miconda: Sergey: I can probably add something in the next days
     as an example
 -   16:27 Sergey: miconda understand.
--   16:28 miconda: Sergey: really apreciating your efforts here, it's
+-   16:28 miconda: Sergey: really appreciating your efforts here, it's
     been a long time when rpm specs were not properly maintained
 -   16:28 miconda: so we do need a cleanup
 -   16:29 Sergey: I can simple remove not supported dists like fedora

docs/devel/irc-meetings/2019a.md

@@ -277,7 +277,7 @@ Note: Times are in EDT (UTC -4)
     12:16 miconda: that's why I keep this topic about community interaction on each irc meeting
     12:17 qxork: yup. and we can always add more.
     12:17 abalashov: I personally like the idea of a Stack Overflow-style Q&A vehicle as the main go-to for Kamailio questions and recipes very much, but I just don't see how to get everyone to start using it. Custom, habit, folk traditions... all play a very big role. Not to mention the virtue of mailing lists in that they are primarily passive rather than active, you don't have to really go out and check the mailing list to see if anything new has popped up.
-    12:18 miconda: verticelo: maybe you can summarize your proposal and sugest some solutions in an email addressed to [email protected]
+    12:18 miconda: verticelo: maybe you can summarize your proposal and suggest some solutions in an email addressed to [email protected]
     12:18 abalashov: Indeed, I think that would be a great discussion to have.
     12:18 verticelo: yes
     12:19 verticelo: abalashov - i think we could place some of the burden on the person asking the question.. but then, we should have an extremely easy way for users to answer it, such as an email reply etc

docs/devel/irc-meetings/2021a.md

@@ -159,7 +159,7 @@ Collaborative Projects:
     2021-12-15 10:41:17 -0500 EST @miconda:matrix.kamailio.dev  * anyone that upgraded debian servers running mailman, apache2, exim4, ... and spotted any major issue?
     2021-12-15 10:41:48 -0500 EST @miconda:matrix.kamailio.dev then we will check the internet when preparing the upgrade
     2021-12-15 10:42:23 -0500 EST @oej:matrix.kamailio.dev > <@miconda:matrix.kamailio.dev> then let's hope for a better and more relaxed 2020 ...
-    Are you so far behind? :-) The rest of us is loking forward to 2022
+    Are you so far behind? :-) The rest of us is looking forward to 2022
     2021-12-15 10:42:28 -0500 EST @miconda:matrix.kamailio.dev second subtopic, the usual community interactions, communication channels, mailing lists ...
     2021-12-15 10:42:54 -0500 EST @miconda:matrix.kamailio.dev @oej :-) you are right!
     2021-12-15 10:43:02 -0500 EST @miconda:matrix.kamailio.dev  * then let's hope for a better and more relaxed 2022 ...

docs/embeddedapi/4.2.x/lua.md

@@ -356,7 +356,7 @@ param is optional and it choose between get all the values of a key ( 0,
 default) or just the first ones (1)
 
 If second param is nil will return all indexes. If second param is \<0
-will return the index counting from then end ( -1 is the last value )
+will return the index counting from the end ( -1 is the last value )
 
 Prototype
 

docs/embeddedapi/4.3.x/lua.md

@@ -356,7 +356,7 @@ param is optional and it choose between get all the values of a key ( 0,
 default) or just the first ones (1)
 
 If second param is nil will return all indexes. If second param is \<0
-will return the index counting from then end ( -1 is the last value )
+will return the index counting from the end ( -1 is the last value )
 
 Prototype
 

docs/embeddedapi/devel/lua.md

@@ -363,7 +363,7 @@ param is optional and it choose between get all the values of a key ( 0,
 default) or just the first ones (1)
 
 If second param is nil will return all indexes. If second param is \<0
-will return the index counting from then end ( -1 is the last value )
+will return the index counting from the end ( -1 is the last value )
 
 Prototype
 

docs/features/new-in-3.2.x.md

@@ -175,7 +175,7 @@ xlog("foo is $var(foo)");
     which are used by several components of the OpenIMS-core: They are
     used as Cx-Interface for the I-/S-CSCF and for the Rx-Interface for
     the P-CSCF. The modules may be used in other ways, too (e.g. for an
-    Sh-Interface for a Kamailio-based aplication server)
+    Sh-Interface for a Kamailio-based application server)
 
 ### IMS: P-CSCF
 

docs/features/new-in-4.1.x.md

@@ -435,7 +435,7 @@ source code repository.*\</fc>
 -   added two new rpc commands ul.db_users and ul.db_contacts - for
     accessing number of different AoRs and contacts in a location table
 -   new command ul.db_expired_contacts tells number of expired contacts
--   detect lost tcp connnections on timer and set associated contact as
+-   detect lost tcp connections on timer and set associated contact as
     expired
     -   new module parameter to control this feature: handle_lost_tcp
 

docs/features/new-in-5.4.x.md

@@ -459,7 +459,7 @@ Add **xavp_rcd_mask** parameter to control what values to skip
 ### janssonrpcc
 
 -   remove redundant str trim implementation and use the one from core
--   replaced str dup wrapers with the functions from core
+-   replaced str dup wrappers with the functions from core
 
 ### jsonrpcc
 
@@ -601,7 +601,7 @@ Add **xavp_rcd_mask** parameter to control what values to skip
     modules
 -   add core support for xavi and xavu PVs
 -   add core support to assign names to listen sockets
--   KEMI suport for ARRAY and DICT types
+-   KEMI support for ARRAY and DICT types
 -   implementation for executing route blocks on send out events moved
     to onsend.c
 

docs/history/09-years-ser-kamailio.md

@@ -685,7 +685,7 @@ modparam("acc_db", "log_flag", "FLAG_ACC")
 #modparam("tm", "restart_fr_on_each_reply", "0")
 
 # -- xmlrpc params --
-# using a sub-route from the module is a lot safer then relying on the
+# using a sub-route from the module is a lot safer than relying on the
 # request method to distinguish HTTP from SIP
 modparam("xmlrpc", "route", "RPC");
 

docs/install/3.2.x/git.md

@@ -243,7 +243,7 @@ is provided at:
     /usr/local/src/kamailio-3.2/kamailio/pkg/kamailio/deb/debian/kamailio.init
 
 Just copy the init file into the /etc/init.d/kamailio. Then change the
-permisions:
+permission:
 
       chmod 755 /etc/init.d/kamailio 
 

docs/install/3.3.x/git.md

@@ -248,7 +248,7 @@ is provided at:
     /usr/local/src/kamailio-3.3/kamailio/pkg/kamailio/deb/debian/kamailio.init
 
 Just copy the init file into the /etc/init.d/kamailio. Then change the
-permisions:
+permission:
 
       chmod 755 /etc/init.d/kamailio 
 

docs/install/4.1.x/git.md

@@ -239,7 +239,7 @@ nicer way. A sample of init.d script for Kamailio is provided at:
     /usr/local/src/kamailio-4.1/kamailio/pkg/kamailio/deb/debian/kamailio.init
 
 Just copy the init file into the /etc/init.d/kamailio. Then change the
-permisions:
+permission:
 
       cp /usr/local/src/kamailio-4.1/kamailio/pkg/kamailio/deb/debian/kamailio.init /etc/init.d/kamailio
       chmod 755 /etc/init.d/kamailio 

docs/install/4.2.x/git.md

@@ -239,7 +239,7 @@ nicer way. A sample of init.d script for Kamailio is provided at:
     /usr/local/src/kamailio-4.2/kamailio/pkg/kamailio/deb/debian/kamailio.init
 
 Just copy the init file into the /etc/init.d/kamailio. Then change the
-permisions:
+permission:
 
       cp /usr/local/src/kamailio-4.2/kamailio/pkg/kamailio/deb/debian/kamailio.init /etc/init.d/kamailio
       chmod 755 /etc/init.d/kamailio 

docs/install/4.3.x/git.md

@@ -246,7 +246,7 @@ nicer way. A sample of init.d script for Kamailio is provided at:
     /usr/local/src/kamailio-4.3/kamailio/pkg/kamailio/deb/debian/kamailio.init
 
 Just copy the init file into the /etc/init.d/kamailio. Then change the
-permisions:
+permission:
 
       cp /usr/local/src/kamailio-4.3/kamailio/pkg/kamailio/deb/debian/kamailio.init /etc/init.d/kamailio
       chmod 755 /etc/init.d/kamailio 

docs/install/devel/git.md

@@ -240,7 +240,7 @@ nicer way. A sample of init.d script for Kamailio is provided at:
     /usr/local/src/kamailio-devel/kamailio/pkg/kamailio/deb/debian/kamailio.init
 
 Just copy the init file into the /etc/init.d/kamailio. Then change the
-permisions:
+permission:
 
       chmod 755 /etc/init.d/kamailio 
 

docs/tutorials/dns/dnssec.md

@@ -18,7 +18,7 @@ initial version of this tutorial. For any assistance, email to
 **sr-users (at) lists.kamailio.org** -- it is a public mailing list
 that requires subscription, see more details at:
 
--   [https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users](https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users)
+-   [https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio.org/](https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio.org/)
 
 **Note:** Ubuntu 12.04 was chosen because dnssec tools devel library are
 provided for this distribution, making the installation of the required

docs/tutorials/faq/main.md

@@ -516,7 +516,7 @@ to:
 
 -   business \[at\] lists.kamailio.org
 -   mailing list web page:
-    -   <http://lists.kamailio.org/cgi-bin/mailman/listinfo/business>
+    -   <https://lists.kamailio.org/mailman3/postorius/lists/business.lists.kamailio.org/>
 
 ### Where I can report an issue?