Merge pull request #17 from dilyanpalauzov/typos_a_an

Typos a/an/and

docs/cookbooks/3.2.x/core.md

@@ -1338,7 +1338,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -2043,7 +2043,7 @@ entries).
 ### dst_blacklist_init
 
 If off, the blacklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blacklist_init = on | off (default on)
 
@@ -2289,7 +2289,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:
@@ -2888,7 +2888,7 @@ The route is executed in when a SIP request is sent out. Only a limited
 number of commands are allowed (drop, if + all the checks, msg flag
 manipulations, send(), log(), textops::search()).
 
-In this route the final destination of the message is available an can
+In this route the final destination of the message is available and can
 be checked (with snd_ip, snd_port, to_ip, to_port, snd_proto, snd_af).
 
 This route is executed only when forwarding requests - it is not

docs/cookbooks/3.2.x/pseudovariables.md

@@ -92,7 +92,7 @@ The 'name' can be:
 -   flags - return the branch flags value
 -   count - return the number of the branches
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -148,11 +148,11 @@ configuration file (will add a new branch).\</fc>
 
 ### Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### CSeq
 
@@ -162,11 +162,11 @@ $rm to get the methode (works also for responses).
 
 ### Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### Domain of destination URI
 
@@ -626,7 +626,7 @@ Setting a variable to null is actually initializing the value to integer
 
 **Note:** A script variable persists over the SIP-Router process in
 which it was initialized, so be sure of giving it a new value before
-reading it or you'll get the value asigned in any other previous message
+reading it or you'll get the value assigned in any other previous message
 processed by the same SIP-Router process (pid).
 
 \<fc #0000FF>It is R/W variable (you can assign values to it directly in
@@ -913,7 +913,7 @@ The “key” can be:
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -935,7 +935,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in

docs/cookbooks/3.2.x/transformations.md

@@ -83,7 +83,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -294,7 +294,7 @@ Example:
 
 ### {param.valueat,index}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/3.3.x/core.md

@@ -823,7 +823,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise  11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1062,7 +1062,7 @@ mem_safety=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -1538,7 +1538,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -2277,7 +2277,7 @@ entries).
 ### dst_blacklist_init
 
 If off, the blacklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blacklist_init = on | off (default on)
 
@@ -2523,7 +2523,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:
@@ -3122,7 +3122,7 @@ The route is executed in when a SIP request is sent out. Only a limited
 number of commands are allowed (drop, if + all the checks, msg flag
 manipulations, send(), log(), textops::search()).
 
-In this route the final destination of the message is available an can
+In this route the final destination of the message is available and can
 be checked (with snd_ip, snd_port, to_ip, to_port, snd_proto, snd_af).
 
 This route is executed only when forwarding requests - it is not

docs/cookbooks/3.3.x/pseudovariables.md

@@ -92,7 +92,7 @@ The 'name' can be:
 -   flags - return the branch flags value
 -   count - return the number of the branches
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -148,11 +148,11 @@ configuration file (will add a new branch).\</fc>
 
 ### Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### CSeq
 
@@ -162,11 +162,11 @@ $rm to get the methode (works also for responses).
 
 ### Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### Domain of destination URI
 
@@ -628,7 +628,7 @@ Setting a variable to null is actually initializing the value to integer
 
 **Note:** A script variable persists over the SIP-Router process in
 which it was initialized, so be sure of giving it a new value before
-reading it or you'll get the value asigned in any other previous message
+reading it or you'll get the value assigned in any other previous message
 processed by the same SIP-Router process (pid).
 
 \<fc #0000FF>It is R/W variable (you can assign values to it directly in
@@ -953,7 +953,7 @@ The “key” can be:
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -975,7 +975,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in

docs/cookbooks/3.3.x/transformations.md

@@ -83,7 +83,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -328,7 +328,7 @@ Example:
 
 ### {param.valueat,index}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/4.0.x/core.md

@@ -890,7 +890,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise  11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1111,7 +1111,7 @@ mem_safety=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -1587,7 +1587,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -2336,7 +2336,7 @@ entries).
 ### dst_blacklist_init
 
 If off, the blacklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blacklist_init = on | off (default on)
 
@@ -2581,7 +2581,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:
@@ -3180,7 +3180,7 @@ The route is executed in when a SIP request is sent out. Only a limited
 number of commands are allowed (drop, if + all the checks, msg flag
 manipulations, send(), log(), textops::search()).
 
-In this route the final destination of the message is available an can
+In this route the final destination of the message is available and can
 be checked (with snd_ip, snd_port, to_ip, to_port, snd_proto, snd_af).
 
 This route is executed only when forwarding requests - it is not

docs/cookbooks/4.0.x/pseudovariables.md

@@ -93,7 +93,7 @@ The 'name' can be:
 -   flags - return the branch flags value
 -   count - return the number of the branches
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -149,11 +149,11 @@ configuration file (will add a new branch).\</fc>
 
 ### Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### CSeq
 
@@ -163,11 +163,11 @@ $rm to get the methode (works also for responses).
 
 ### Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### Domain of destination URI
 
@@ -691,7 +691,7 @@ Setting a variable to null is actually initializing the value to integer
 
 **Note:** A script variable persists over the SIP-Router process in
 which it was initialized, so be sure of giving it a new value before
-reading it or you'll get the value asigned in any other previous message
+reading it or you'll get the value assigned in any other previous message
 processed by the same SIP-Router process (pid).
 
 \<fc #0000FF>It is R/W variable (you can assign values to it directly in
@@ -1016,7 +1016,7 @@ The “key” can be:
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1038,7 +1038,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in

docs/cookbooks/4.0.x/transformations.md

@@ -83,7 +83,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -328,7 +328,7 @@ Example:
 
 ### {param.valueat,index}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/4.1.x/core.md

@@ -893,7 +893,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise  11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1114,7 +1114,7 @@ mem_safety=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -1560,7 +1560,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -2315,7 +2315,7 @@ entries).
 ### dst_blacklist_init
 
 If off, the blacklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blacklist_init = on | off (default on)
 
@@ -2560,7 +2560,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:
@@ -3118,7 +3118,7 @@ The route is executed in when a SIP request is sent out. Only a limited
 number of commands are allowed (drop, if + all the checks, msg flag
 manipulations, send(), log(), textops::search()).
 
-In this route the final destination of the message is available an can
+In this route the final destination of the message is available and can
 be checked (with snd_ip, snd_port, to_ip, to_port, snd_proto, snd_af).
 
 This route is executed only when forwarding requests - it is not

docs/cookbooks/4.1.x/pseudovariables.md

@@ -106,7 +106,7 @@ The 'name' can be:
 -   ruid - return the ruid of the branch (Record internal Unique ID from
     usrloc)
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -162,11 +162,11 @@ configuration file (will add a new branch).\</fc>
 
 ### $ci - Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### $cl - Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### $conid - TCP Connection ID
 
@@ -181,11 +181,11 @@ $rm to get the method (works also for responses).
 
 ### $ct - Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### $cT - Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### $dd - Domain of destination URI
 
@@ -701,7 +701,7 @@ Setting a variable to null is actually initializing the value to integer
 
 **Note:** A script variable persists over the SIP-Router process in
 which it was initialized, so be sure of giving it a new value before
-reading it or you'll get the value asigned in any other previous message
+reading it or you'll get the value assigned in any other previous message
 processed by the same SIP-Router process (pid).
 
 \<fc #0000FF>It is R/W variable (you can assign values to it directly in
@@ -1044,7 +1044,7 @@ including a custom value at time of assignment.
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1066,7 +1066,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1112,7 +1112,7 @@ Example:
 ### $T_reply_ruid
 
 -   the ruid stored in the current branch of the transaction. The ruid
-    is stored in a branch from the details in a contact binding. In a
+    is stored in a branch from the details in a contact binding. In an
     event_route\[tm:branch-failure\] block, this is the ruid of the
     branch that sent a failure reply. In a failure_route\[\] block, this
     is the ruid of the winning failure response.

docs/cookbooks/4.1.x/transformations.md

@@ -83,7 +83,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -340,7 +340,7 @@ use '&'.
 
 ### {param.valueat,index\[, delimiter\]}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/4.2.x/core.md

@@ -906,7 +906,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise  11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1150,7 +1150,7 @@ mem_safety=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -1603,7 +1603,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -2362,7 +2362,7 @@ entries).
 ### dst_blacklist_init
 
 If off, the blacklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blacklist_init = on | off (default on)
 
@@ -2540,7 +2540,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:
@@ -3098,7 +3098,7 @@ The route is executed in when a SIP request is sent out. Only a limited
 number of commands are allowed (drop, if + all the checks, msg flag
 manipulations, send(), log(), textops::search()).
 
-In this route the final destination of the message is available an can
+In this route the final destination of the message is available and can
 be checked (with snd_ip, snd_port, to_ip, to_port, snd_proto, snd_af).
 
 This route is executed only when forwarding requests - it is not

docs/cookbooks/4.2.x/pseudovariables.md

@@ -110,7 +110,7 @@ The 'name' can be:
 -   ruid - return the ruid of the branch (Record internal Unique ID from
     usrloc)
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -172,11 +172,11 @@ in configuration file)\</fc>
 
 ### $ci - Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### $cl - Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### $cnt(pv) - Count number of pvs
 
@@ -199,11 +199,11 @@ $rm to get the method (works also for responses).
 
 ### $ct - Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### $cT - Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### $dd - Domain of destination URI
 
@@ -731,7 +731,7 @@ Setting a variable to null is actually initializing the value to integer
 
 **Note:** A script variable persists over the SIP-Router process in
 which it was initialized, so be sure of giving it a new value before
-reading it or you'll get the value asigned in any other previous message
+reading it or you'll get the value assigned in any other previous message
 processed by the same SIP-Router process (pid).
 
 \<fc #0000FF>It is a R/W variable (you can assign values to it directly
@@ -1074,7 +1074,7 @@ including a custom value at time of assignment.
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is a R/W variable, you can assign values to it directly
@@ -1096,7 +1096,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is a R/W variable, you can assign values to it directly
@@ -1142,7 +1142,7 @@ Example:
 ### $T_reply_ruid
 
 -   the ruid stored in the current branch of the transaction. The ruid
-    is stored in a branch from the details in a contact binding. In a
+    is stored in a branch from the details in a contact binding. In an
     event_route\[tm:branch-failure\] block, this is the ruid of the
     branch that sent a failure reply. In a failure_route\[\] block, this
     is the ruid of the winning failure response.
@@ -1225,7 +1225,7 @@ Note: the pair (id_index,id_label) uniquely identifies a transaction.
 
 The **name** can be:
 
--   flags - Flags of the branch. In a event_route\[tm:branch-failure\]
+-   flags - Flags of the branch. In an event_route\[tm:branch-failure\]
     block, this is the flags of the branch that sent a failure reply. In
     a failure_route\[\] block, this is the flags of the winning failure
     response.

docs/cookbooks/4.2.x/transformations.md

@@ -101,7 +101,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -358,7 +358,7 @@ use '&'.
 
 ### {param.valueat,index\[, delimiter\]}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/4.3.x/core.md

@@ -907,7 +907,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise  11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1154,7 +1154,7 @@ mem_safety=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -1629,7 +1629,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -2389,7 +2389,7 @@ entries).
 ### dst_blacklist_init
 
 If off, the blacklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blacklist_init = on | off (default on)
 
@@ -2567,7 +2567,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:
@@ -3231,7 +3231,7 @@ The route is executed in when a SIP request is sent out. Only a limited
 number of commands are allowed (drop, if + all the checks, msg flag
 manipulations, send(), log(), textops::search()).
 
-In this route the final destination of the message is available an can
+In this route the final destination of the message is available and can
 be checked (with snd_ip, snd_port, to_ip, to_port, snd_proto, snd_af).
 
 This route is executed only when forwarding requests - it is not

docs/cookbooks/4.3.x/pseudovariables.md

@@ -113,7 +113,7 @@ The 'name' can be:
 -   ruid - return the ruid of the branch (Record internal Unique ID from
     usrloc)
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -175,18 +175,18 @@ configuration file)\</fc>
 
 ### $ci - Call-Id
 
-**$ci** - reference to body of call-id header (R/O)
+**$ci** - reference to the value of call-id header (R/O)
 
 ### $cl - Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### $cnt(pv) - Count number of pvs
 
 **$cnt(avp)** - return the number of avps
 
 ``` c
-xlog("$$avp(x) fount $cnt($avp(x)) times\n");
+xlog("$$avp(x) found $cnt($avp(x)) times\n");
 ```
 
 ### $conid - TCP Connection ID
@@ -202,11 +202,11 @@ $rm to get the method (works also for responses).
 
 ### $ct - Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### $cT - Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### $dd - Domain of destination URI
 
@@ -287,7 +287,7 @@ message.\</fc>
 initial request (e.g., initial INVITE).
 
 The value From tag in the initial request can be in the To tag, if the
-request within the dialog is sent by the callee. This variable detect
+request within the dialog is sent by the callee. This variable detects
 who sent the request within the dialog and returns the proper value that
 was in the From tag of the request initiating the dialog.
 
@@ -602,7 +602,7 @@ SIP response to the initial request (e.g., 200ok to the initial INVITE).
 
 The value To tag in the initial transaction can be in the From tag, if
 the request within the dialog is sent by the callee. This variable
-detect who sent the request within the dialog and returns the proper
+detects who sent the request within the dialog and returns the proper
 value that was in the To tag of the transaction initiating the dialog.
 
 It is exported by **rr** module and has to be used after loose_route().
@@ -868,7 +868,7 @@ if($var(x)==0) { # this is true
 
 **Note:** A script variable persists over the Kamailio process in which
 it was initialized, so be sure of giving it a new value before reading
-it or you'll get the value asigned in any other previous message
+it or you'll get the value assigned in any other previous message
 processed by the same Kamailio process (pid).
 
 \<fc #0000FF>It is R/W variable (you can assign values to it directly in
@@ -1312,7 +1312,7 @@ including a custom value at time of assignment.
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1334,7 +1334,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1380,7 +1380,7 @@ Example:
 ### $T_reply_ruid
 
 -   the ruid stored in the current branch of the transaction. The ruid
-    is stored in a branch from the details in a contact binding. In a
+    is stored in a branch from the details in a contact binding. In an
     event_route\[tm:branch-failure\] block, this is the ruid of the
     branch that sent a failure reply. In a failure_route\[\] block, this
     is the ruid of the winning failure response.
@@ -1463,7 +1463,7 @@ Note: the pair (id_index,id_label) uniquely identifies a transaction.
 
 The **name** can be:
 
--   flags - Flags of the branch. In a event_route\[tm:branch-failure\]
+-   flags - Flags of the branch. In an event_route\[tm:branch-failure\]
     block, this is the flags of the branch that sent a failure reply. In
     a failure_route\[\] block, this is the flags of the winning failure
     response.

docs/cookbooks/4.3.x/transformations.md

@@ -103,7 +103,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -368,7 +368,7 @@ use '&'.
 
 ### {param.valueat,index\[, delimiter\]}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/4.4.x/core.md

@@ -1106,7 +1106,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise  11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1378,7 +1378,7 @@ mem_safety=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -1866,7 +1866,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -2626,7 +2626,7 @@ entries).
 ### dst_blacklist_init
 
 If off, the blacklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blacklist_init = on | off (default on)
 
@@ -3500,7 +3500,7 @@ The route is executed in when a SIP request is sent out. Only a limited
 number of commands are allowed (drop, if + all the checks, msg flag
 manipulations, send(), log(), textops::search()).
 
-In this route the final destination of the message is available an can
+In this route the final destination of the message is available and can
 be checked (with snd_ip, snd_port, to_ip, to_port, snd_proto, snd_af).
 
 This route is executed only when forwarding requests - it is not

docs/cookbooks/4.4.x/pseudovariables.md

@@ -113,7 +113,7 @@ The 'name' can be:
 -   ruid - return the ruid of the branch (Record internal Unique ID from
     usrloc)
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -175,18 +175,18 @@ configuration file)\</fc>
 
 ### $ci - Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### $cl - Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### $cnt(pv) - Count number of pvs
 
 **$cnt(avp)** - return the number of avps
 
 ``` c
-xlog("$$avp(x) fount $cnt($avp(x)) times\n");
+xlog("$$avp(x) found $cnt($avp(x)) times\n");
 ```
 
 ### $conid - TCP Connection ID
@@ -202,11 +202,11 @@ $rm to get the method (works also for responses).
 
 ### $ct - Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### $cT - Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### $dd - Domain of destination URI
 
@@ -287,7 +287,7 @@ message.\</fc>
 initial request (e.g., initial INVITE).
 
 The value From tag in the initial request can be in the To tag, if the
-request within the dialog is sent by the callee. This variable detect
+request within the dialog is sent by the callee. This variable detects
 who sent the request within the dialog and returns the proper value that
 was in the From tag of the request initiating the dialog.
 
@@ -602,7 +602,7 @@ SIP response to the initial request (e.g., 200ok to the initial INVITE).
 
 The value To tag in the initial transaction can be in the From tag, if
 the request within the dialog is sent by the callee. This variable
-detect who sent the request within the dialog and returns the proper
+detects who sent the request within the dialog and returns the proper
 value that was in the To tag of the transaction initiating the dialog.
 
 It is exported by **rr** module and has to be used after loose_route().
@@ -868,7 +868,7 @@ if($var(x)==0) { # this is true
 
 **Note:** A script variable persists over the Kamailio process in which
 it was initialized, so be sure of giving it a new value before reading
-it or you'll get the value asigned in any other previous message
+it or you'll get the value assigned in any other previous message
 processed by the same Kamailio process (pid).
 
 \<fc #0000FF>It is R/W variable (you can assign values to it directly in
@@ -1333,7 +1333,7 @@ including a custom value at time of assignment.
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1355,7 +1355,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1401,7 +1401,7 @@ Example:
 ### $T_reply_ruid
 
 -   the ruid stored in the current branch of the transaction. The ruid
-    is stored in a branch from the details in a contact binding. In a
+    is stored in a branch from the details in a contact binding. In an
     event_route\[tm:branch-failure\] block, this is the ruid of the
     branch that sent a failure reply. In a failure_route\[\] block, this
     is the ruid of the winning failure response.
@@ -1485,7 +1485,7 @@ Note: the pair (id_index,id_label) uniquely identifies a transaction.
 
 The **name** can be:
 
--   flags - Flags of the branch. In a event_route\[tm:branch-failure\]
+-   flags - Flags of the branch. In an event_route\[tm:branch-failure\]
     block, this is the flags of the branch that sent a failure reply. In
     a failure_route\[\] block, this is the flags of the winning failure
     response.

docs/cookbooks/4.4.x/transformations.md

@@ -101,7 +101,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -375,7 +375,7 @@ use '&'.
 
 ### {param.valueat,index\[, delimiter\]}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/5.0.x/core.md

@@ -1125,7 +1125,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise  11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1449,7 +1449,7 @@ mem_status_mode=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -1949,7 +1949,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -2711,7 +2711,7 @@ entries).
 ### dst_blacklist_init
 
 If off, the blacklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blacklist_init = on | off (default on)
 
@@ -2889,7 +2889,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:

docs/cookbooks/5.0.x/pseudovariables.md

@@ -86,7 +86,7 @@ header
 
 **$Au** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username and
-realm ($au@$ar) if exists or From URI ($fu) otherwise.
+realm ($au@$ar) if it exists or From URI ($fu) otherwise.
 
 ### $branch(name) - Branch attributes
 
@@ -113,7 +113,7 @@ The 'name' can be:
 -   ruid - return the ruid of the branch (Record internal Unique ID from
     usrloc)
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -175,18 +175,18 @@ configuration file)\</fc>
 
 ### $ci - Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### $cl - Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### $cnt(pv) - Count number of pvs
 
 **$cnt(avp)** - return the number of avps
 
 ``` c
-xlog("$$avp(x) fount $cnt($avp(x)) times\n");
+xlog("$$avp(x) found $cnt($avp(x)) times\n");
 ```
 
 ### $conid - TCP Connection ID
@@ -202,11 +202,11 @@ $rm to get the method (works also for responses).
 
 ### $ct - Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### $cT - Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### $dd - Domain of destination URI
 
@@ -287,7 +287,7 @@ message.\</fc>
 initial request (e.g., initial INVITE).
 
 The value From tag in the initial request can be in the To tag, if the
-request within the dialog is sent by the callee. This variable detect
+request within the dialog is sent by the callee. This variable detects
 who sent the request within the dialog and returns the proper value that
 was in the From tag of the request initiating the dialog.
 
@@ -603,7 +603,7 @@ SIP response to the initial request (e.g., 200ok to the initial INVITE).
 
 The value To tag in the initial transaction can be in the From tag, if
 the request within the dialog is sent by the callee. This variable
-detect who sent the request within the dialog and returns the proper
+detects who sent the request within the dialog and returns the proper
 value that was in the To tag of the transaction initiating the dialog.
 
 It is exported by **rr** module and has to be used after loose_route().
@@ -869,7 +869,7 @@ if($var(x)==0) { # this is true
 
 **Note:** A script variable persists over the Kamailio process in which
 it was initialized, so be sure of giving it a new value before reading
-it or you'll get the value asigned in any other previous message
+it or you'll get the value assigned in any other previous message
 processed by the same Kamailio process (pid).
 
 \<fc #0000FF>It is R/W variable (you can assign values to it directly in
@@ -1379,7 +1379,7 @@ including a custom value at time of assignment.
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1401,7 +1401,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1447,7 +1447,7 @@ Example:
 ### $T_reply_ruid
 
 -   the ruid stored in the current branch of the transaction. The ruid
-    is stored in a branch from the details in a contact binding. In a
+    is stored in a branch from the details in a contact binding. In an
     event_route\[tm:branch-failure\] block, this is the ruid of the
     branch that sent a failure reply. In a failure_route\[\] block, this
     is the ruid of the winning failure response.
@@ -1531,7 +1531,7 @@ Note: the pair (id_index,id_label) uniquely identifies a transaction.
 
 The **name** can be:
 
--   flags - Flags of the branch. In a event_route\[tm:branch-failure\]
+-   flags - Flags of the branch. In an event_route\[tm:branch-failure\]
     block, this is the flags of the branch that sent a failure reply. In
     a failure_route\[\] block, this is the flags of the winning failure
     response.

docs/cookbooks/5.0.x/transformations.md

@@ -101,7 +101,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -389,7 +389,7 @@ use '&'.
 
 ### {param.valueat,index\[, delimiter\]}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/5.1.x/core.md

@@ -1162,7 +1162,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise  11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1487,7 +1487,7 @@ mem_status_mode=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -2009,7 +2009,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -2794,7 +2794,7 @@ entries).
 ### dst_blacklist_init
 
 If off, the blacklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blacklist_init = on | off (default on)
 
@@ -2972,7 +2972,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:

docs/cookbooks/5.1.x/pseudovariables.md

@@ -86,7 +86,7 @@ header
 
 **$Au** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username and
-realm ($au@$ar) if exists or From URI ($fu) otherwise.
+realm ($au@$ar) if it exists or From URI ($fu) otherwise.
 
 ### $branch(name) - Branch attributes
 
@@ -113,7 +113,7 @@ The 'name' can be:
 -   ruid - return the ruid of the branch (Record internal Unique ID from
     usrloc)
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -175,18 +175,18 @@ configuration file)\</fc>
 
 ### $ci - Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### $cl - Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### $cnt(pv) - Count number of pvs
 
 **$cnt(avp)** - return the number of avps
 
 ``` c
-xlog("$$avp(x) fount $cnt($avp(x)) times\n");
+xlog("$$avp(x) found $cnt($avp(x)) times\n");
 ```
 
 ### $conid - TCP Connection ID
@@ -206,11 +206,11 @@ $rm to get the method (works also for responses).
 
 ### $ct - Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### $cT - Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### $dd - Domain of destination URI
 
@@ -291,7 +291,7 @@ message.\</fc>
 initial request (e.g., initial INVITE).
 
 The value From tag in the initial request can be in the To tag, if the
-request within the dialog is sent by the callee. This variable detect
+request within the dialog is sent by the callee. This variable detects
 who sent the request within the dialog and returns the proper value that
 was in the From tag of the request initiating the dialog.
 
@@ -661,7 +661,7 @@ SIP response to the initial request (e.g., 200ok to the initial INVITE).
 
 The value To tag in the initial transaction can be in the From tag, if
 the request within the dialog is sent by the callee. This variable
-detect who sent the request within the dialog and returns the proper
+detects who sent the request within the dialog and returns the proper
 value that was in the To tag of the transaction initiating the dialog.
 
 It is exported by **rr** module and has to be used after loose_route().
@@ -952,7 +952,7 @@ if($var(x)==0) { # this is true
 
 **Note:** A script variable persists over the Kamailio process in which
 it was initialized, so be sure of giving it a new value before reading
-it or you'll get the value asigned in any other previous message
+it or you'll get the value assigned in any other previous message
 processed by the same Kamailio process (pid).
 
 \<fc #0000FF>It is R/W variable (you can assign values to it directly in
@@ -1462,7 +1462,7 @@ including a custom value at time of assignment.
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1484,7 +1484,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1530,7 +1530,7 @@ Example:
 ### $T_reply_ruid
 
 -   the ruid stored in the current branch of the transaction. The ruid
-    is stored in a branch from the details in a contact binding. In a
+    is stored in a branch from the details in a contact binding. In an
     event_route\[tm:branch-failure\] block, this is the ruid of the
     branch that sent a failure reply. In a failure_route\[\] block, this
     is the ruid of the winning failure response.
@@ -1622,7 +1622,7 @@ Note: the pair (id_index,id_label) uniquely identifies a transaction.
 
 The **name** can be:
 
--   flags - Flags of the branch. In a event_route\[tm:branch-failure\]
+-   flags - Flags of the branch. In an event_route\[tm:branch-failure\]
     block, this is the flags of the branch that sent a failure reply. In
     a failure_route\[\] block, this is the flags of the winning failure
     response.

docs/cookbooks/5.1.x/transformations.md

@@ -101,7 +101,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -419,7 +419,7 @@ use '&'.
 
 ### {param.valueat,index\[, delimiter\]}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/5.2.x/core.md

@@ -1216,7 +1216,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise  11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1559,7 +1559,7 @@ mem_status_mode=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -2137,7 +2137,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -2922,7 +2922,7 @@ entries).
 ### dst_blacklist_init
 
 If off, the blacklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blacklist_init = on | off (default on)
 
@@ -3100,7 +3100,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:

docs/cookbooks/5.2.x/pseudovariables.md

@@ -86,7 +86,7 @@ header
 
 **$Au** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username and
-realm ($au@$ar) if exists or From URI ($fu) otherwise.
+realm ($au@$ar) if it exists or From URI ($fu) otherwise.
 
 ### $branch(name) - Branch attributes
 
@@ -113,7 +113,7 @@ The 'name' can be:
 -   ruid - return the ruid of the branch (Record internal Unique ID from
     usrloc)
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -175,18 +175,18 @@ configuration file)\</fc>
 
 ### $ci - Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### $cl - Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### $cnt(pv) - Count number of pvs
 
 **$cnt(avp)** - return the number of avps
 
 ``` c
-xlog("$$avp(x) fount $cnt($avp(x)) times\n");
+xlog("$$avp(x) found $cnt($avp(x)) times\n");
 ```
 
 ### $conid - TCP Connection ID
@@ -206,11 +206,11 @@ $rm to get the method (works also for responses).
 
 ### $ct - Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### $cT - Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### $dd - Domain of destination URI
 
@@ -291,7 +291,7 @@ message.\</fc>
 initial request (e.g., initial INVITE).
 
 The value From tag in the initial request can be in the To tag, if the
-request within the dialog is sent by the callee. This variable detect
+request within the dialog is sent by the callee. This variable detects
 who sent the request within the dialog and returns the proper value that
 was in the From tag of the request initiating the dialog.
 
@@ -674,7 +674,7 @@ SIP response to the initial request (e.g., 200ok to the initial INVITE).
 
 The value To tag in the initial transaction can be in the From tag, if
 the request within the dialog is sent by the callee. This variable
-detect who sent the request within the dialog and returns the proper
+detects who sent the request within the dialog and returns the proper
 value that was in the To tag of the transaction initiating the dialog.
 
 It is exported by **rr** module and has to be used after loose_route().
@@ -968,7 +968,7 @@ if($var(x)==0) { # this is true
 
 **Note:** A script variable persists over the Kamailio process in which
 it was initialized, so be sure of giving it a new value before reading
-it or you'll get the value asigned in any other previous message
+it or you'll get the value assigned in any other previous message
 processed by the same Kamailio process (pid).
 
 \<fc #0000FF>It is R/W variable (you can assign values to it directly in
@@ -1478,7 +1478,7 @@ including a custom value at time of assignment.
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1500,7 +1500,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1546,7 +1546,7 @@ Example:
 ### $T_reply_ruid
 
 -   the ruid stored in the current branch of the transaction. The ruid
-    is stored in a branch from the details in a contact binding. In a
+    is stored in a branch from the details in a contact binding. In an
     event_route\[tm:branch-failure\] block, this is the ruid of the
     branch that sent a failure reply. In a failure_route\[\] block, this
     is the ruid of the winning failure response.
@@ -1638,7 +1638,7 @@ Note: the pair (id_index,id_label) uniquely identifies a transaction.
 
 The **name** can be:
 
--   flags - Flags of the branch. In a event_route\[tm:branch-failure\]
+-   flags - Flags of the branch. In an event_route\[tm:branch-failure\]
     block, this is the flags of the branch that sent a failure reply. In
     a failure_route\[\] block, this is the flags of the winning failure
     response.

docs/cookbooks/5.2.x/transformations.md

@@ -101,7 +101,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -447,7 +447,7 @@ use '&'.
 
 ### {param.valueat,index\[, delimiter\]}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/5.3.x/core.md

@@ -1257,7 +1257,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise  11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1607,7 +1607,7 @@ mem_status_mode=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -1747,7 +1747,7 @@ taken. Default value is 2048.
 ### pv_cache_action
 
 Specify what action to be done when the size of pv cache is exceeded. If
-0, print an warning log message when the limit is exceeded. If 1,
+0, print a warning log message when the limit is exceeded. If 1,
 warning log messages is printed and the cache systems tries to drop a
 $sht(...) declaration. Default is 0.
 
@@ -2214,7 +2214,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -3045,7 +3045,7 @@ entries).
 ### dst_blacklist_init
 
 If off, the blacklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blacklist_init = on | off (default on)
 
@@ -3223,7 +3223,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:

docs/cookbooks/5.3.x/pseudovariables.md

@@ -87,13 +87,13 @@ header
 
 **$Au** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username and
-realm ($au@$ar) if exists or From URI ($fu) otherwise.
+realm ($au@$ar) if it exists or From URI ($fu) otherwise.
 
 ### $AU - Acc username
 
 **$AU** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username ($au)
-if exists or From user ($fU) otherwise.
+if it exists or From user ($fU) otherwise.
 
 ### $branch(name) - Branch attributes
 
@@ -120,7 +120,7 @@ The 'name' can be:
 -   ruid - return the ruid of the branch (Record internal Unique ID from
     usrloc)
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -182,18 +182,18 @@ configuration file)\</fc>
 
 ### $ci - Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### $cl - Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### $cnt(pv) - Count number of pvs
 
 **$cnt(avp)** - return the number of avps
 
 ``` c
-xlog("$$avp(x) fount $cnt($avp(x)) times\n");
+xlog("$$avp(x) found $cnt($avp(x)) times\n");
 ```
 
 ### $conid - TCP Connection ID
@@ -213,11 +213,11 @@ $rm to get the method (works also for responses).
 
 ### $ct - Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### $cT - Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### $dd - Domain of destination URI
 
@@ -300,7 +300,7 @@ message.\</fc>
 initial request (e.g., initial INVITE).
 
 The value From tag in the initial request can be in the To tag, if the
-request within the dialog is sent by the callee. This variable detect
+request within the dialog is sent by the callee. This variable detects
 who sent the request within the dialog and returns the proper value that
 was in the From tag of the request initiating the dialog.
 
@@ -692,7 +692,7 @@ SIP response to the initial request (e.g., 200ok to the initial INVITE).
 
 The value To tag in the initial transaction can be in the From tag, if
 the request within the dialog is sent by the callee. This variable
-detect who sent the request within the dialog and returns the proper
+detects who sent the request within the dialog and returns the proper
 value that was in the To tag of the transaction initiating the dialog.
 
 It is exported by **rr** module and has to be used after loose_route().
@@ -864,7 +864,7 @@ They work like a stack, similar to AVPs, and are attached to SIP
 transactions and automatically destroyed when the transaction is
 finished.
 
-Each xavp has a string name and can contain a string, and integer or a
+Each xavp has a string name and can contain a string, an integer or a
 list of named values. The structure name (or root list name) and the
 value name (or field name, or child value name) are separated by => like
 $xavp(root=>field) where "root" is the name of the structure and "field"
@@ -1016,7 +1016,7 @@ if($var(x)==0) { # this is true
 
 **Note:** A script variable persists over the Kamailio process in which
 it was initialized, so be sure of giving it a new value before reading
-it or you'll get the value asigned in any other previous message
+it or you'll get the value assigned in any other previous message
 processed by the same Kamailio process (pid).
 
 \<fc #0000FF>It is R/W variable (you can assign values to it directly in
@@ -1554,7 +1554,7 @@ including a custom value at time of assignment.
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1576,7 +1576,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1708,7 +1708,7 @@ Example:
 ### $T_reply_ruid
 
 -   the ruid stored in the current branch of the transaction. The ruid
-    is stored in a branch from the details in a contact binding. In a
+    is stored in a branch from the details in a contact binding. In an
     event_route\[tm:branch-failure\] block, this is the ruid of the
     branch that sent a failure reply. In a failure_route\[\] block, this
     is the ruid of the winning failure response.
@@ -1800,7 +1800,7 @@ Note: the pair (id_index,id_label) uniquely identifies a transaction.
 
 The **name** can be:
 
--   flags - Flags of the branch. In a event_route\[tm:branch-failure\]
+-   flags - Flags of the branch. In an event_route\[tm:branch-failure\]
     block, this is the flags of the branch that sent a failure reply. In
     a failure_route\[\] block, this is the flags of the winning failure
     response.

docs/cookbooks/5.3.x/transformations.md

@@ -101,7 +101,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -463,7 +463,7 @@ use '&'.
 
 ### {param.valueat,index\[, delimiter\]}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/5.4.x/core.md

@@ -1282,7 +1282,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise 11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1655,7 +1655,7 @@ mem_status_mode=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -1795,7 +1795,7 @@ taken. Default value is 2048.
 ### pv_cache_action
 
 Specify what action to be done when the size of pv cache is exceeded. If
-0, print an warning log message when the limit is exceeded. If 1,
+0, print a warning log message when the limit is exceeded. If 1,
 warning log messages is printed and the cache systems tries to drop a
 $sht(...) declaration. Default is 0.
 
@@ -2285,7 +2285,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -3116,7 +3116,7 @@ entries).
 ### dst_blacklist_init
 
 If off, the blacklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blacklist_init = on | off (default on)
 
@@ -3294,7 +3294,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:

docs/cookbooks/5.4.x/pseudovariables.md

@@ -87,13 +87,13 @@ header
 
 **$Au** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username and
-realm ($au@$ar) if exists or From URI ($fu) otherwise.
+realm ($au@$ar) if it exists or From URI ($fu) otherwise.
 
 ### $AU - Acc username
 
 **$AU** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username ($au)
-if exists or From user ($fU) otherwise.
+if it exists or From user ($fU) otherwise.
 
 ### $branch(name) - Branch attributes
 
@@ -185,18 +185,18 @@ configuration file)\</fc>
 
 ### $ci - Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### $cl - Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### $cnt(pv) - Count number of pvs
 
 **$cnt(avp)** - return the number of avps
 
 ``` c
-xlog("$$avp(x) fount $cnt($avp(x)) times\n");
+xlog("$$avp(x) found $cnt($avp(x)) times\n");
 ```
 
 ### $conid - TCP Connection ID
@@ -216,11 +216,11 @@ $rm to get the method (works also for responses).
 
 ### $ct - Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### $cT - Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### $dd - Domain of destination URI
 
@@ -327,7 +327,7 @@ xdbg("name for forced send socket: $fsn\n");
 initial request (e.g., initial INVITE).
 
 The value From tag in the initial request can be in the To tag, if the
-request within the dialog is sent by the callee. This variable detect
+request within the dialog is sent by the callee. This variable detects
 who sent the request within the dialog and returns the proper value that
 was in the From tag of the request initiating the dialog.
 
@@ -722,7 +722,7 @@ SIP response to the initial request (e.g., 200ok to the initial INVITE).
 
 The value To tag in the initial transaction can be in the From tag, if
 the request within the dialog is sent by the callee. This variable
-detect who sent the request within the dialog and returns the proper
+detects who sent the request within the dialog and returns the proper
 value that was in the To tag of the transaction initiating the dialog.
 
 It is exported by **rr** module and has to be used after loose_route().
@@ -898,7 +898,7 @@ They work like a stack, similar to AVPs, and are attached to SIP
 transactions and automatically destroyed when the transaction is
 finished.
 
-Each xavp has a string name and can contain a string, and integer or a
+Each xavp has a string name and can contain a string, an integer or a
 list of named values. The structure name (or root list name) and the
 value name (or field name, or child value name) are separated by => like
 $xavp(root=>field) where "root" is the name of the structure and "field"
@@ -1078,7 +1078,7 @@ if($var(x)==0) { # this is true
 
 **Note:** A script variable persists over the Kamailio process in which
 it was initialized, so be sure of giving it a new value before reading
-it or you'll get the value asigned in any other previous message
+it or you'll get the value assigned in any other previous message
 processed by the same Kamailio process (pid).
 
 \<fc #0000FF>It is R/W variable (you can assign values to it directly in
@@ -1660,7 +1660,7 @@ including a custom value at time of assignment.
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1682,7 +1682,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1814,7 +1814,7 @@ Example:
 ### $T_reply_ruid
 
 -   the ruid stored in the current branch of the transaction. The ruid
-    is stored in a branch from the details in a contact binding. In a
+    is stored in a branch from the details in a contact binding. In an
     event_route\[tm:branch-failure\] block, this is the ruid of the
     branch that sent a failure reply. In a failure_route\[\] block, this
     is the ruid of the winning failure response.
@@ -1906,7 +1906,7 @@ Note: the pair (id_index,id_label) uniquely identifies a transaction.
 
 The **name** can be:
 
--   flags - Flags of the branch. In a event_route\[tm:branch-failure\]
+-   flags - Flags of the branch. In an event_route\[tm:branch-failure\]
     block, this is the flags of the branch that sent a failure reply. In
     a failure_route\[\] block, this is the flags of the winning failure
     response.

docs/cookbooks/5.4.x/transformations.md

@@ -103,7 +103,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -509,7 +509,7 @@ use '&'.
 
 ### {param.valueat,index\[, delimiter\]}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/5.5.x/core.md

@@ -1392,7 +1392,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise 11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1783,7 +1783,7 @@ mem_status_mode=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -1928,7 +1928,7 @@ taken. Default value is 2048.
 ### pv_cache_action
 
 Specify what action to be done when the size of pv cache is exceeded. If
-0, print an warning log message when the limit is exceeded. If 1,
+0, print a warning log message when the limit is exceeded. If 1,
 warning log messages is printed and the cache systems tries to drop a
 $sht(...) declaration. Default is 0.
 
@@ -2487,7 +2487,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -3318,7 +3318,7 @@ entries).
 ### dst_blocklist_init
 
 If off, the blocklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blocklist_init = on | off (default on)
 
@@ -3496,7 +3496,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:
@@ -4340,7 +4340,7 @@ event_route[core:pre-routing] {
 
 ``` c
 event_route[core:receive-parse-error] {
-        xlog("got an parsing error from $si:$sp, message $mb\n");
+        xlog("got a parsing error from $si:$sp, message $mb\n");
 }
 
 ```

docs/cookbooks/5.5.x/pseudovariables.md

@@ -87,13 +87,13 @@ header
 
 **$Au** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username and
-realm ($au@$ar) if exists or From URI ($fu) otherwise.
+realm ($au@$ar) if it exists or From URI ($fu) otherwise.
 
 ### $AU - Acc username
 
 **$AU** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username ($au)
-if exists or From user ($fU) otherwise.
+if it exists or From user ($fU) otherwise.
 
 ### $branch(name) - Branch attributes
 
@@ -120,7 +120,7 @@ The 'name' can be:
 -   ruid - return the ruid of the branch (Record internal Unique ID from
     usrloc)
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -182,18 +182,18 @@ configuration file)\</fc>
 
 ### $ci - Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### $cl - Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### $cnt(pv) - Count number of pvs
 
 **$cnt(avp)** - return the number of avps
 
 ``` c
-xlog("$$avp(x) fount $cnt($avp(x)) times\n");
+xlog("$$avp(x) found $cnt($avp(x)) times\n");
 ```
 
 ### $conid - TCP Connection ID
@@ -213,11 +213,11 @@ $rm to get the method (works also for responses).
 
 ### $ct - Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### $cT - Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### $dd - Domain of destination URI
 
@@ -351,7 +351,7 @@ xdbg("name for forced send socket: $fsn\n");
 initial request (e.g., initial INVITE).
 
 The value From tag in the initial request can be in the To tag, if the
-request within the dialog is sent by the callee. This variable detect
+request within the dialog is sent by the callee. This variable detects
 who sent the request within the dialog and returns the proper value that
 was in the From tag of the request initiating the dialog.
 
@@ -776,7 +776,7 @@ SIP response to the initial request (e.g., 200ok to the initial INVITE).
 
 The value To tag in the initial transaction can be in the From tag, if
 the request within the dialog is sent by the callee. This variable
-detect who sent the request within the dialog and returns the proper
+detects who sent the request within the dialog and returns the proper
 value that was in the To tag of the transaction initiating the dialog.
 
 It is exported by **rr** module and has to be used after loose_route().
@@ -952,7 +952,7 @@ They work like a stack, similar to AVPs, and are attached to SIP
 transactions and automatically destroyed when the transaction is
 finished.
 
-Each xavp has a string name and can contain a string, and integer or a
+Each xavp has a string name and can contain a string, an integer or a
 list of named values. The structure name (or root list name) and the
 value name (or field name, or child value name) are separated by => like
 $xavp(root=>field) where "root" is the name of the structure and "field"
@@ -1132,7 +1132,7 @@ if($var(x)==0) { # this is true
 
 **Note:** A script variable persists over the Kamailio process in which
 it was initialized, so be sure of giving it a new value before reading
-it or you'll get the value asigned in any other previous message
+it or you'll get the value assigned in any other previous message
 processed by the same Kamailio process (pid).
 
 \<fc #0000FF>It is R/W variable (you can assign values to it directly in
@@ -1714,7 +1714,7 @@ including a custom value at time of assignment.
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1736,7 +1736,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 \<fc #0000ff>It is R/W variable, you can assign values to it directly in
@@ -1873,7 +1873,7 @@ Example:
 ### $T_reply_ruid
 
 -   the ruid stored in the current branch of the transaction. The ruid
-    is stored in a branch from the details in a contact binding. In a
+    is stored in a branch from the details in a contact binding. In an
     event_route\[tm:branch-failure\] block, this is the ruid of the
     branch that sent a failure reply. In a failure_route\[\] block, this
     is the ruid of the winning failure response.
@@ -1965,7 +1965,7 @@ Note: the pair (id_index,id_label) uniquely identifies a transaction.
 
 The **name** can be:
 
--   flags - Flags of the branch. In a event_route\[tm:branch-failure\]
+-   flags - Flags of the branch. In an event_route\[tm:branch-failure\]
     block, this is the flags of the branch that sent a failure reply. In
     a failure_route\[\] block, this is the flags of the winning failure
     response.

docs/cookbooks/5.5.x/transformations.md

@@ -103,7 +103,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -567,7 +567,7 @@ use '&'.
 
 ### {param.valueat,index\[, delimiter\]}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/5.6.x/core.md

@@ -1430,7 +1430,7 @@ You can specify an advertise address (like ip:port) per listening socket
     listen=udp:10.10.10.10:5060 advertise 11.11.11.11:5060
 ```
 
-The advertise address must be the format 'address:port', the protocol is
+The advertise address must be in the format 'address:port', the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to advertised_address / advertised_port cfg parameters or
 set_advertised_address() / set_advertised_port() cfg functions.
@@ -1852,7 +1852,7 @@ mem_status_mode=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on exit or SIGUSR1. The value can be composed by following flags:
 
 -   1 - dump all the pkg used blocks (status)
@@ -1998,7 +1998,7 @@ taken. Default value is 2048.
 ### pv_cache_action
 
 Specify what action to be done when the size of pv cache is exceeded. If
-0, print an warning log message when the limit is exceeded. If 1,
+0, print a warning log message when the limit is exceeded. If 1,
 warning log messages is printed and the cache systems tries to drop a
 $sht(...) declaration. Default is 0.
 
@@ -2557,7 +2557,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dns_cache_init = on | off (default on)
 
@@ -3411,7 +3411,7 @@ entries).
 ### dst_blocklist_init
 
 If off, the blocklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
     dst_blocklist_init = on | off (default on)
 
@@ -3589,7 +3589,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:
@@ -4357,7 +4357,7 @@ Example:
 -   msg:len - when used in an onsend_route, msg:len will contain the
     length of the message on the wire (after all the changes in the
     script are applied, Vias are added a.s.o) and not the lentgh of the
-    original messa ge.
+    original message.
 
 ### event_route
 
@@ -4431,7 +4431,7 @@ event_route[core:pre-routing] {
 
 ``` c
 event_route[core:receive-parse-error] {
-        xlog("got an parsing error from $si:$sp, message $mb\n");
+        xlog("got a parsing error from $si:$sp, message $mb\n");
 }
 
 ```

docs/cookbooks/5.6.x/pseudovariables.md

@@ -89,13 +89,13 @@ header
 
 **$Au** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username and
-realm ($au@$ar) if exists or From URI ($fu) otherwise.
+realm ($au@$ar) if it exists or From URI ($fu) otherwise.
 
 ### $AU - Acc username
 
 **$AU** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username ($au)
-if exists or From user ($fU) otherwise.
+if it exists or From user ($fU) otherwise.
 
 ### $branch(name) - Branch attributes
 
@@ -122,7 +122,7 @@ The 'name' can be:
 -   ruid - return the ruid of the branch (Record internal Unique ID from
     usrloc)
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -184,18 +184,18 @@ configuration file)
 
 ### $ci - Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### $cl - Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### $cnt(pv) - Count number of pvs
 
 **$cnt(avp)** - return the number of avps
 
 ``` c
-xlog("$$avp(x) fount $cnt($avp(x)) times\n");
+xlog("$$avp(x) found $cnt($avp(x)) times\n");
 ```
 
 **$cnt(xavp)** - return the number of xavps
@@ -229,11 +229,11 @@ $rm to get the method (works also for responses).
 
 ### $ct - Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### $cT - Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### $dd - Domain of destination URI
 
@@ -370,7 +370,7 @@ xdbg("name for forced send socket: $fsn\n");
 initial request (e.g., initial INVITE).
 
 The value From tag in the initial request can be in the To tag, if the
-request within the dialog is sent by the callee. This variable detect
+request within the dialog is sent by the callee. This variable detects
 who sent the request within the dialog and returns the proper value that
 was in the From tag of the request initiating the dialog.
 
@@ -798,7 +798,7 @@ SIP response to the initial request (e.g., 200ok to the initial INVITE).
 
 The value To tag in the initial transaction can be in the From tag, if
 the request within the dialog is sent by the callee. This variable
-detect who sent the request within the dialog and returns the proper
+detects who sent the request within the dialog and returns the proper
 value that was in the To tag of the transaction initiating the dialog.
 
 It is exported by **rr** module and has to be used after loose_route().
@@ -980,7 +980,7 @@ They work like a stack, similar to AVPs, and are attached to SIP
 transactions and automatically destroyed when the transaction is
 finished.
 
-Each xavp has a string name and can contain a string, and integer or a
+Each xavp has a string name and can contain a string, an integer or a
 list of named values. The structure name (or root list name) and the
 value name (or field name, or child value name) are separated by => like
 $xavp(root=>field) where "root" is the name of the structure and "field"
@@ -1213,7 +1213,7 @@ if($var(x)==0) { # this is true
 
 **Note:** A script variable persists over the Kamailio process in which
 it was initialized, so be sure of giving it a new value before reading
-it or you'll get the value asigned in any other previous message
+it or you'll get the value assigned in any other previous message
 processed by the same Kamailio process (pid).
 
 🔥**IMPORTANT**: It is R/W variable (you can assign values to it directly in
@@ -1934,7 +1934,7 @@ including a custom value at time of assignment.
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 🔥**IMPORTANT**: It is R/W variable, you can assign values to it directly in
@@ -1954,7 +1954,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 🔥**IMPORTANT**: It is R/W variable, you can assign values to it directly in
@@ -2087,7 +2087,7 @@ Example:
 ### $T_reply_ruid
 
 -   the ruid stored in the current branch of the transaction. The ruid
-    is stored in a branch from the details in a contact binding. In a
+    is stored in a branch from the details in a contact binding. In an
     event_route\[tm:branch-failure\] block, this is the ruid of the
     branch that sent a failure reply. In a failure_route\[\] block, this
     is the ruid of the winning failure response.
@@ -2173,7 +2173,7 @@ Note: the pair (id_index,id_label) uniquely identifies a transaction.
 
 The **name** can be:
 
--   flags - Flags of the branch. In a event_route\[tm:branch-failure\]
+-   flags - Flags of the branch. In an event_route\[tm:branch-failure\]
     block, this is the flags of the branch that sent a failure reply. In
     a failure_route\[\] block, this is the flags of the winning failure
     response.

docs/cookbooks/5.6.x/transformations.md

@@ -103,7 +103,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -626,7 +626,7 @@ use '&'.
 
 ### {param.valueat,index\[, delimiter\]}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/cookbooks/devel/core.md

@@ -447,7 +447,7 @@ request_route {
 ### ifexp
 
 Evaluate an expression and if true, then enable first region, otherwise
-enable the `#!else` region (if exists).
+enable the `#!else` region (if it exists).
 
 The expression has to be till the end of the line (no support for multi-line yet).
 
@@ -1676,7 +1676,7 @@ You can specify an advertise address (like `ip:port`) per listening socket
     listen=udp:10.10.10.10:5060 advertise 11.11.11.11:5060
 ```
 
-The advertise address must be the format `address:port`, the protocol is
+The advertise address must be in the format `address:port`, the protocol is
 taken from the bind socket. The advertise address is a convenient
 alternative to `advertised_address` / `advertised_port` config parameters or
 `set_advertised_address()` / `set_advertised_port()` config functions.
@@ -2145,7 +2145,7 @@ mem_status_mode=1
 
 ### mem_summary
 
-Parameter to control printing of mmemory debugging information displayed
+Parameter to control printing of memory debugging information displayed
 on `exit` or `SIGUSR1`. The value can be composed by following flags:
 
 -   `1` - dump all the pkg used blocks (status)
@@ -2263,9 +2263,9 @@ Default value: `1` (enabled)
 ### pmtu_discovery
 
 If set to 1, the don't-fragment (DF) bit will be set in outbound IP
-packets, but not fragmentation from the kernel will be done for IPv4
-and IPv6. This means that packets might be dropped and its up to the
-user to reduce the packet size and try again.
+packets, but no fragmentation from the kernel will be done for IPv4
+and IPv6. This means that packets might be dropped and it is up to
+the user to reduce the packet size and try again.
 
 If set to 2, the kernel will will fragment a packet if needed
 according to the path MTU, or will set the don't-fragment flag
@@ -2326,7 +2326,7 @@ taken. Default value is 2048.
 ### pv_cache_action
 
 Specify what action to be done when the size of pv cache is exceeded. If
-`0`, print an warning log message when the limit is exceeded. If `1`,
+`0`, print a warning log message when the limit is exceeded. If `1`,
 warning log messages is printed and the cache systems tries to drop a
 `$sht(...)` declaration. Default is `0`.
 
@@ -2975,7 +2975,7 @@ Interval in seconds after which the dns cache is garbage collected
 ### dns_cache_init
 
 If off, the dns cache is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
 ```
     dns_cache_init = on | off (default on)
@@ -3979,7 +3979,7 @@ entries).
 ### dst_blocklist_init
 
 If off, the blocklist is not initialized at startup and cannot be
-enabled runtime, that saves some memory.
+enabled at runtime, this saves some memory.
 
 ```
     dst_blocklist_init = on | off (default on)
@@ -4195,7 +4195,7 @@ signaling.
 
 The rport parameter is defined in RFC 3581.
 
-Note: there is also a force_rport parameter which changes the gobal
+Note: there is also a force_rport parameter which changes the global
 behavior of the SIP proxy.
 
 Example of usage:
@@ -4395,7 +4395,7 @@ Note: starting with version `5.7.0-dev`, this behaviour can be changed with
 
 Control the return code evaluation mode:
 
-  - 0 (default) - evaluation is like so far (negative is false, positiv is true)
+  - 0 (default) - evaluation is like so far (negative is false, positive is true)
   - 1 - propagate return value and evaluation has to be done with `>0` or `<0`, otherwise
   `value!=0` is evaluated to true no matter is negative or positive
 
@@ -5015,7 +5015,7 @@ Example:
 -   msg:len - when used in an onsend_route, msg:len will contain the
     length of the message on the wire (after all the changes in the
     script are applied, Vias are added a.s.o) and not the lentgh of the
-    original messa ge.
+    original message.
 
 ### event_route
 
@@ -5089,7 +5089,7 @@ event_route[core:pre-routing] {
 
 ``` c
 event_route[core:receive-parse-error] {
-        xlog("got an parsing error from $si:$sp, message $mb\n");
+        xlog("got a parsing error from $si:$sp, message $mb\n");
 }
 
 ```

docs/cookbooks/devel/pseudovariables.md

@@ -89,13 +89,13 @@ header
 
 **$Au** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username and
-realm ($au@$ar) if exists or From URI ($fu) otherwise.
+realm ($au@$ar) if it exists or From URI ($fu) otherwise.
 
 ### $AU - Acc username
 
 **$AU** - username for accounting purposes. It's a selective pseudo
 variable (inherited from acc module). It returns the auth username ($au)
-if exists or From user ($fU) otherwise.
+if it exists or From user ($fU) otherwise.
 
 ### $branch(name) - Branch attributes
 
@@ -122,7 +122,7 @@ The 'name' can be:
 -   ruid - return the ruid of the branch (Record internal Unique ID from
     usrloc)
 
-The PV can take an index to access a specif branch:
+The PV can take an index to access a specific branch:
 $(branch(name)\[index\])
 
 Example:
@@ -184,18 +184,18 @@ configuration file)
 
 ### $ci - Call-Id
 
-**$ci** - reference to body of call-id header
+**$ci** - reference to the value of call-id header
 
 ### $cl - Content-Length
 
-**$cl** - reference to body of content-length header
+**$cl** - reference to the value of content-length header
 
 ### $cnt(pv) - Count number of pvs
 
 **$cnt(avp)** - return the number of avps
 
 ``` c
-xlog("$$avp(x) fount $cnt($avp(x)) times\n");
+xlog("$$avp(x) found $cnt($avp(x)) times\n");
 ```
 
 **$cnt(xavp)** - return the number of xavps
@@ -229,11 +229,11 @@ $rm to get the method (works also for responses).
 
 ### $ct - Contact header
 
-**$ct** - reference to body of contact header
+**$ct** - reference to the value of contact header
 
 ### $cT - Content-Type
 
-**$cT** - reference to body of content-type header
+**$cT** - reference to the value of content-type header
 
 ### $dd - Domain of destination URI
 
@@ -370,7 +370,7 @@ xdbg("name for forced send socket: $fsn\n");
 initial request (e.g., initial INVITE).
 
 The value From tag in the initial request can be in the To tag, if the
-request within the dialog is sent by the callee. This variable detect
+request within the dialog is sent by the callee. This variable detects
 who sent the request within the dialog and returns the proper value that
 was in the From tag of the request initiating the dialog.
 
@@ -798,7 +798,7 @@ SIP response to the initial request (e.g., 200ok to the initial INVITE).
 
 The value To tag in the initial transaction can be in the From tag, if
 the request within the dialog is sent by the callee. This variable
-detect who sent the request within the dialog and returns the proper
+detects who sent the request within the dialog and returns the proper
 value that was in the To tag of the transaction initiating the dialog.
 
 It is exported by **rr** module and has to be used after loose_route().
@@ -980,7 +980,7 @@ They work like a stack, similar to AVPs, and are attached to SIP
 transactions and automatically destroyed when the transaction is
 finished.
 
-Each xavp has a string name and can contain a string, and integer or a
+Each xavp has a string name and can contain a string, an integer or a
 list of named values. The structure name (or root list name) and the
 value name (or field name, or child value name) are separated by => like
 $xavp(root=>field) where "root" is the name of the structure and "field"
@@ -1213,7 +1213,7 @@ if($var(x)==0) { # this is true
 
 **Note:** A script variable persists over the Kamailio process in which
 it was initialized, so be sure of giving it a new value before reading
-it or you'll get the value asigned in any other previous message
+it or you'll get the value assigned in any other previous message
 processed by the same Kamailio process (pid).
 
 🔥**IMPORTANT**: It is R/W variable (you can assign values to it directly in
@@ -1934,7 +1934,7 @@ including a custom value at time of assignment.
 
 ### $mcinc(key)
 
-Do a atomic increment operation on the value stored in memcached. You
+Do an atomic increment operation on the value stored in memcached. You
 need to add a value previously.
 
 🔥**IMPORTANT**: It is R/W variable, you can assign values to it directly in
@@ -1954,7 +1954,7 @@ The “key” can be:
 
 ### $mcdec(key)
 
-Do a atomic decrement operation on the value stored in memcached. You
+Do an atomic decrement operation on the value stored in memcached. You
 need to add a value previously.
 
 🔥**IMPORTANT**: It is R/W variable, you can assign values to it directly in
@@ -2087,7 +2087,7 @@ Example:
 ### $T_reply_ruid
 
 -   the ruid stored in the current branch of the transaction. The ruid
-    is stored in a branch from the details in a contact binding. In a
+    is stored in a branch from the details in a contact binding. In an
     event_route\[tm:branch-failure\] block, this is the ruid of the
     branch that sent a failure reply. In a failure_route\[\] block, this
     is the ruid of the winning failure response.
@@ -2173,7 +2173,7 @@ Note: the pair (id_index,id_label) uniquely identifies a transaction.
 
 The **name** can be:
 
--   flags - Flags of the branch. In a event_route\[tm:branch-failure\]
+-   flags - Flags of the branch. In an event_route\[tm:branch-failure\]
     block, this is the flags of the branch that sent a failure reply. In
     a failure_route\[\] block, this is the flags of the winning failure
     response.
@@ -2276,7 +2276,7 @@ moment is represented by **seconds.microseconds**.
     retrieved)
 -   $TV(Sn) - string representation seconds.microseconds (not cached,
     taken at that moment)
--   $TV(Sm) - string representation of a always increasing monotonic
+-   $TV(Sm) - string representation of an always increasing monotonic
     counter. Note that even if is based on clock, it starts from an
     unspecified point in time, so should really be treated as an
     opaque counter.

docs/cookbooks/devel/transformations.md

@@ -103,7 +103,7 @@ Example:
 
 Return a field from PV value. The field is selected based on separator
 and index. The separator must be a character used to identify the
-fields. Index must be a integer value or a PV. If index is negative, the
+fields. Index must be an integer value or a PV. If index is negative, the
 count of fields starts from end of PV value, -1 being last field. If
 index is positive, 0 is the first field.
 
@@ -626,7 +626,7 @@ use '&'.
 
 ### {param.valueat,index\[, delimiter\]}
 
-Return the value of parameter at position give by 'index' (0-based
+Return the value of parameter at position given by 'index' (0-based
 index)
 
 Example:

docs/devel/backporting-to-3.2.x.md

@@ -25,7 +25,7 @@ repository with:
 
 Replace **userid** with your developer GIT username.
 
-If you are an user, you can clone the repository with:
+If you are a user, you can clone the repository with:
 
     git clone --depth 1 git://git.sip-router.org/sip-router kamailio-dev
 

docs/devel/git-access.md

@@ -6,7 +6,7 @@ source code repository hosted at git.sip-router.org .
 
 ## Cloning Repository for Write Operations
 
-Each developer has an user ID for accessing the repository via ssh,
+Each developer has a user ID for accessing the repository via ssh,
 which allow push operations. Cloning can be done via command:
 
     git clone ssh://[email protected]/kamailio 

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

@@ -230,7 +230,7 @@ This is pretty much the unedited IRC discussion, split by topics.
     miconda: if any dev has spare time to work on reducing duplicates, write on sr-dev to sync
     aXl: it'll probably need a dev with experience in both projects, at least with the module to be converted, i don't think there are a lot of them 
     osas: there should be a wiki page dedicated to module merging
-    osas: and maybe it make sense to just drop one version and keep the other one (for some modules)
+    osas: and maybe it makes sense to just drop one version and keep the other one (for some modules)
     miconda: when I did it, I looked in readmes to be sure the features are not lost
     miconda: most of complexity comes from different db structure
     osas: for some
@@ -446,7 +446,7 @@ This is pretty much the unedited IRC discussion, split by topics.
     miconda: well, to my understanding so far to websockets (some sporadic reads), it will not be something very complex
     miconda: it starts as an http
     miconda: we have that
-    miconda: then there is an handshake based on some headers
+    miconda: then there is a handshake based on some headers
     miconda: then it is pretty much tcp
     miconda: with packets to be handled based on app id or so ...
     agranig:  what's missing is the WS(S) support in vias... you usually get a client id for a websocket, so you'd need to map a message coming via "normal" sip to the correct socket on the http-side

docs/devel/irc-meetings/2013blog.md

@@ -639,7 +639,7 @@ Github push requests etc for merging.
 \[17:45\] \<pdunkley> carstenbock: there was a discussion on the mailing
 list. But it boils down to better developer management, and merging plus
 integrated tracker that relates issues to commits.  
-\[17:46\] \<linuxmaniac> pdunkley: just a nice web interface an the
+\[17:46\] \<linuxmaniac> pdunkley: just a nice web interface and the
 pull-request are received as mails  
 \[17:46\] \<eloycoto> we can use <http://gitlab.org/> in our server  
 \[17:46\] \<miconda> pdunkley: maybe there are tutorials to do sync two

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

@@ -157,7 +157,7 @@ universe separate from that...
 with uid\_\*  
 **miconda:** cnxcc is not a bad one, but quite useful, just that I never
 got to use it  
-**oej:** I think it's a good idea to have a end-of-life process  
+**oej:** I think it's a good idea to have an end-of-life process
 **qxork:** sometimes you have to cut weight to move forward  
 **miconda:** i try to avoid charging per minute :-)  
 **abalashov:** If for no other reason than to manage your workload
@@ -835,7 +835,7 @@ if there is a general movement toward Lua for config-writing over time.
 It's not a question of being forced to do anything.  
 **miconda:** so far required to write wrappers from scratch for each of
 them  
-**oej:** So I don't see this a a big change in directions, just a way to
+**oej:** So I don't see this as a big change in directions, just a way to
 enable more functionality for lua, python, erlang and what else we
 ahve  
 **miconda:** my goal was write on export to all embedded interpreters  

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

@@ -149,7 +149,7 @@ Kamailio 5.1 (next major release):
 -   15:16 linuxmaniac: yes, there is no much coordination
 -   15:16 linuxmaniac: you are always doing all the work
 -   15:16 miconda: I and qxork do that when we can, I guess
--   15:16 grumvalski: I am available to give an hand on this
+-   15:16 grumvalski: I am available to give a hand on this
 -   15:16 grumvalski: if we want to create an internal group for such
     tasks
 -   15:16 miconda: linuxmaniac: is a backup for access to main server,
@@ -340,7 +340,7 @@ Kamailio 5.1 (next major release):
 -   15:51 linuxmaniac: asterisk has something like that
 -   15:51 miconda: Sergey: we will get to pkg and docker in the next
     topics
--   15:51 linuxmaniac: there is a asterisk-dev package with everything
+-   15:51 linuxmaniac: there is an asterisk-dev package with everything
     you need to build a module
 -   15:51 lazedo: same for freeswitch
 -   15:52 lazedo: and since they loadable modules, we can even doing it

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

@@ -261,7 +261,7 @@ Note: Times are in EDT (UTC -4)
     [11:07am] qxork: and/or getting with someone for a weekly “open question” conference call
     [11:07am] miconda: qxork: self hosted?
     [11:08am] qxork: miconda: yes, we could give another box for it.
-    [11:08am] miconda: qxork: each box has to come with an human admin
+    [11:08am] miconda: qxork: each box has to come with a human admin
     [11:08am] miconda: :-)
     [11:08am] qxork: I’d offer to do so
     [11:09am] miconda: ok, we can discuss further on mailing lists and get feedback about who wants to be involved in coordinating such sessions

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

@@ -121,7 +121,7 @@ Collaborative Projects:
     2021-12-15 10:15:22 -0500 EST @miconda:matrix.kamailio.dev that should facilitate deploying rtpengine along side kamailio, they are both in the same repo
     2021-12-15 10:15:53 -0500 EST @henning:matrix.kamailio.dev great news
     2021-12-15 10:16:59 -0500 EST @oej:matrix.kamailio.dev Huge thanks to Víctor Seva !!!!
-    2021-12-15 10:17:28 -0500 EST @khorsmann:matrix.org question: rtpengine + kamailio then in the same repo - and if i need an diffrent rtpengine? would two repos better so i can deactivate "kamailio-flaivor rtpengine"?
+    2021-12-15 10:17:28 -0500 EST @khorsmann:matrix.org question: rtpengine + kamailio then in the same repo - and if i need a different rtpengine? would two repos better so i can deactivate "kamailio-flaivor rtpengine"?
     2021-12-15 10:17:44 -0500 EST @miconda:matrix.kamailio.dev also, for the records, if someone missed the news about archiving packages for releases: https://www.kamailio.org/w/2021/09/apt-debian-packages-archive/
     2021-12-15 10:18:32 -0500 EST @miconda:matrix.kamailio.dev Karsten Horsmann: I think you can have policies for packages, but I am not sure
     2021-12-15 10:19:53 -0500 EST @miconda:matrix.kamailio.dev anyhow, I am not really sure if it's going to be same repo, but use the same platform to build the debs

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

@@ -171,11 +171,11 @@ xlog("foo is $var(foo)");
 
 ### IMS: CDP / CDP-AVP
 
--   The CDP (C-Diameter-Peer) modules provide an Diameter-interface,
+-   The CDP (C-Diameter-Peer) modules provide a Diameter-interface,
     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 an Kamailio-based aplication server)
+    Sh-Interface for a Kamailio-based aplication server)
 
 ### IMS: P-CSCF
 
@@ -188,7 +188,7 @@ xlog("foo is $var(foo)");
 
 ### IMS: I-CSCF
 
--   The Interrogating-CSCF is a kind of “Loadbalancer” or a entry Proxy
+-   The Interrogating-CSCF is a kind of “Loadbalancer” or an entry Proxy
     for the “home-network” of an IMS setup. The I-CSCF will retrieve the
     location for a user from the HSS, it will check, where a user is
     registered or where it should register (based on user-settings,

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

@@ -635,7 +635,7 @@ the past).
 -   use add_contact_alias()/handle_uri_alias() for NATed calls
 -   test if DBURL is already defined before defining it - allow to set
     it via command line with -A DBURL='...'
--   kamailio-local.cfg is attempted to be loaded if exists in the same
-    folder, allowing to set defines/paramters inside it without changing
+-   kamailio-local.cfg is attempted to be loaded if it exists in the same
+    folder, allowing to set defines/parameters inside it without changing
     main kamailio.cfg
 -   add option to set pstn gw port

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

@@ -60,7 +60,7 @@ Presence User Agent implementation with JSON messages.
     -   reload feature enabbled by default, set to 0 to disable
 -   new module parameter - log_mode
     -   control what is printed in log messages by module
-    -   if bit 1 is set, the it prints the KEMI exports
+    -   if bit 1 is set, then it prints the KEMI exports
 
 ### app_python
 
@@ -511,7 +511,7 @@ Presence User Agent implementation with JSON messages.
     -   pv_cache_limit - the limit how many pv declarations in the cache
         after which an action is taken. Default value is 2048
     -   pv_cache_action - specify what action to be done when the size
-        of pv cache is exceeded. If 0, print an warning log message when
+        of pv cache is exceeded. If 0, print a warning log message when
         the limit is exceeded. If 1, warning log messages is printed and
         the cache systems tries to drop a $sht(...) declaration. Default
         is 0

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

@@ -167,7 +167,7 @@ Add support for multiple TCP connections to the ims_usrloc_pcscf module.
 
 ### ims_isc
 
-Add functionality to a add-on to third party registration in S-CSCF. The
+Add functionality to an add-on to third party registration in S-CSCF. The
 feature assumes two new flags in HSS database, where additional to the
 "Service Info XML" an "insertRegisterRequest" flag or an
 "insertRegisterResponse" flag can be set. These flags are sent with the

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

@@ -347,8 +347,8 @@ Pseudo-module providing per-proces STIR/SHAKEN API from libsecsipid.
 
 ### pv
 
--   new transformation {uri.suri} to get the simple routing uri, keep
-    only transport parameter, if exists
+-   new transformation {uri.suri} to get the simple routing uri, keeping
+    only transport parameter, if it exists
 -   new transformation {uri.duri} to get the uri needed for destination
     address (e.g., <sip:host:port;transport=tcp>)
 -   new transformation {uri.saor} to get the sip aor

docs/tutorials/dns/dnssec.md

@@ -311,7 +311,7 @@ Then [email protected] can call `[email protected]`. Kamailio instance
 serving `domainA.com` will do DNS lookup do discover the IP address of
 `domainB.com`
 
-One easy way to test is to use a Open DNS resolver that provides
+One easy way to test is to use an Open DNS resolver that provides
 Recursive DNSSEC capabilities. One of those is `8.8.8.8` ( Google Open
 DNS). As per the FAQ, DNSSEC support is enabled
 (<https://developers.google.com/speed/public-dns/faq#dnssec>)

docs/tutorials/faq/main.md

@@ -1,6 +1,6 @@
 # Frequently Asked Questions
 
-This page is open for contributions, you must create an user account via
+This page is open for contributions, you must create a user account via
 registration form:
 
 -   <https://www.kamailio.org/wiki/start?do=register>
@@ -203,7 +203,7 @@ applied immediately, use **msg_apply_changes()** from textopsx module:
 Be careful with it and don't use it after record_route(), because this
 function has to insert a header containing the IP address from the local
 socket that is going to be used for forwarding - the socket is not yet
-know during configuration file execution.
+known during configuration file execution.
 
 For example, considering that X-Hdr does not exist in incoming message,
 here are some cases:
@@ -287,7 +287,7 @@ using functions such as uac_replace_from() or uac_replace_to().
 The configuration file does an operation that changes parts in the
 headers or body many times. For example, if the body has two
 concatenated IP addresses for media stream, then likely the rtpproxy
-function is used twice, or, if the SDP appears two time, then the
+function is used twice, or, if the SDP appears two times, then the
 rtpengine function is used two times.
 
 If the update has to be done many times, use **msg_apply_changes()** in
@@ -363,7 +363,7 @@ outgoing branches.
 ### How to remove a single header field when a header appears multiple times?
 
 📃 SIP allows that certain header fields may appear multiple times in a
-SIP message. This header fields (e.g. Via, Route, Record-Route, Contact)
+SIP message. These header fields (e.g. Via, Route, Record-Route, Contact)
 may be written either on a single line (with comma separated) or on
 multiple lines (see [RFC 3261 section 7.3](http://tools.ietf.org/html/rfc3261#section-7.3) for details).
 
@@ -564,8 +564,7 @@ compared with a string:
 📃 Yes. There is nothing special to do for that in configuration file,
 MESSAGE requests are simply routed as any other SIP request.
 
-### Can it store instant messages for offline users and deliver them
-when the users become online?
+### Can it store instant messages for offline users and deliver them when the users become online?
 
 📃 Yes. See msilo module.
 
@@ -595,8 +594,7 @@ PUBLISH and SUBSCRIBE requests.
 📃 Yes. See pua module and its extensions named with 'pua\_' prefix
 (such as pua_usrloc, pua_dialoginfo, etc.).
 
-### Can it handle subscription requests for dialog states (aka, blinking
-lamps)?
+### Can it handle subscription requests for dialog states (aka, blinking lamps)?
 
 📃 Yes. You have to use dialog module together with presence_dialoginfo
 and pua_dialoginfo modules.

docs/tutorials/kamailio-and-mongodb.md

@@ -79,7 +79,7 @@ The corresponding database URL in kamailio.cfg:
 
     #!define DBURL "mongodb://localhost/kamailio"
 
--   if MongoDB is on local host and there is an username and password to
+-   if MongoDB is on local host and there is a username and password to
     connect to it:
 
 <!-- -->

docs/tutorials/kamailio-flag-operations.md

@@ -188,7 +188,7 @@ Example 6. accounting config file
 ### Optimizations
 
 Flags may be used to optimize Kamailio's routing logic, avoiding
-duplicated rutines or executions of same security checks over database.
+duplicated routines or executions of same security checks over database.
 
 Example 7. optimization of config file
 

docs/tutorials/security/kamailio-security.md

@@ -170,7 +170,7 @@ thousands of packets passing over your screen. (stealing content from
 ### Pike
 
 The pike module tracks the number of SIP messages per source IP address,
-per period. Pike is a very easy to add to your config:
+per period. Pike is very easy to add to your config:
 
     loadmodule "pike.so"
      

docs/tutorials/troubleshooting/coredumpfile.md

@@ -66,7 +66,7 @@ the core file generation. Just run:
 
     ulimit -c unlimited
 
-in the shell where you started the server. If you run from a init script
+in the shell where you started the server. If you run from an init script
 it should normally already take care of this. If its still not create a
 core file then perhaps the server has no permissions to write into its
 working directory, check its permissions and the startup option "-w".