tm: typos

src/modules/tm/doc/params.xml

@@ -298,7 +298,7 @@ modparam("tm", "restart_fr_on_each_reply", 0)
 	<section id="tm.p.auto_inv_100">
 	<title><varname>auto_inv_100</varname> (integer)</title>
 	<para>
-		If set (default) tm will automatically send and 100 reply to INVITEs.
+		If set (default) tm will automatically send a 100 reply to INVITEs.
 	</para>
 	<para>
 		Setting it to 0 can be used to enable first running some tests or
@@ -577,7 +577,7 @@ modparam("tm", "blst_503_max_timeout", 604800)
 		Check parser/msg_parser.h for farther details.
 	</para>
 	<para>
-		Change the value carefully, because requests that doesn't get
+		Change the value carefully, because requests that don't get
 		a provisional response (everything but INVITE) can easily
 		cause the next hop to be inserted into the blocklist
 		by mistake. For example the next hop is a proxy, it is alive,
@@ -1581,15 +1581,15 @@ modparam("tm", "exec_time_check", 0)
 	<section id="tm.p.reply_relay_mode">
 		<title><varname>reply_relay_mode</varname> (int)</title>
 		<para>
-			If set to 1, a received 200ok response that was suspeneded is no
+			If set to 1, a received 200 OK response that was suspeneded is no
 			longer forwarded in the transactional context if another final
-			response was forward while 200ok was suspended. Forwarding the 200ok,
+			response was forward while 200 OK was suspended. Forwarding the 200 OK,
 			even it was received first, results in overwritting the transaction
 			response buffer that can impact matching of incoming ACKs.
 		</para>
 		<para>
 			Set it to 0 in order to disable this behaviour and attempt to forward
-			suspended 200ok in the transaction context. This was the behaviour
+			suspended 200 OK in the transaction context. This was the behaviour
 			before the commit 18410da0.
 		</para>
 		<para>

src/modules/tm/doc/tm.xml

@@ -163,7 +163,7 @@
 		also known as the <quote>q value</quote>. The q value is a floating
 		point number in a range 0 to 1.0. The higher the q value number,
 		the more priority is given to the particular branch in the destination set.
-		Branches with q value 1.0 have maximum priority, such branches should be always
+		Branches with q value 1.0 have maximum priority, such branches should always
 		be tried first in serial forking. Branches with q value 0 have the lowest
 		priority and they should by tried after all other branches with higher
 		priority in the destination set.
@@ -334,7 +334,7 @@ failure_route["serial"]
 	    <listitem>
 		<para>
 		    Possibly, performance could be improved by not parsing
-		    non-INVITEs, as they do not be replied with 100, and do not
+		    non-INVITEs, as they are not replied with 100, and do not
 		    result in ACK/CANCELs, and other things which take
 		    parsing. However, we need to rethink whether we don't need
 		    parsed headers later for something else. Remember, when we