doc/tutorials: typos

doc/tutorials/rpc_list/docbook/rpc_core.xml

@@ -79,7 +79,7 @@ RPC Exports for core
 <section id="core.info"><title>core.info</title>
 <para>
         Verbose info, including version number, compile flags,
-        compiler,repository hash a.s.o.
+        compiler, repository hash a.s.o.
 </para>
 <para>
 </para>

doc/tutorials/rpc_list/docbook/rpc_malloc_test.xml

@@ -11,7 +11,7 @@ RPC Exports for malloc_test
 <section id="mt.mem_alloc"><title>mt.mem_alloc</title>
 <para>
         Allocates the specified number of bytes (debugging/test
-        function).Use b|k|m|g to specify the desired size unit
+        function). Use b|k|m|g to specify the desired size unit
 </para>
 <para>
 </para>
@@ -22,7 +22,7 @@ RPC Exports for malloc_test
         Frees the specified number of bytes, previously allocated by
         one of the other malloc_test functions (e.g. mt.mem_alloc or
         the script mt_mem_alloc). Use b|k|m|g to specify the desired
-        size unit.Returns the number of bytes freed (can be higher or
+        size unit. Returns the number of bytes freed (can be higher or
         smaller then the requested size)
 </para>
 <para>
@@ -36,7 +36,7 @@ RPC Exports for malloc_test
         chunks exists, it will fail. Make sure mt.mem_used is non 0 or
         call mt.mem_alloc prior to calling this function. Returns the
         difference in bytes (&lt;0 if bytes were freed, &gt;0 if more
-        bytes were allocated).Use b|k|m|g to specify the desired size
+        bytes were allocated). Use b|k|m|g to specify the desired size
         unit
 </para>
 <para>
@@ -57,7 +57,7 @@ RPC Exports for malloc_test
 <para>
         Takes 4 parameters: min, max, total_size and an optional unit
         (b|k|m|g). It will allocate total_size memory, in pieces of
-        random size betweenmin .. max (inclusive).
+        random size between min .. max (inclusive).
 </para>
 <para>
 </para>
@@ -71,7 +71,7 @@ RPC Exports for malloc_test
         for test_time ms. At a random interval between min_interval and
         max_interval ms. it will allocate a memory chunk with random
         size, between min and max. Each time total_size is reached, it
-        will free all the memory allocated and start again.Returns the
+        will free all the memory allocated and start again. Returns the
         test id (integer)
 </para>
 <para>
@@ -81,7 +81,7 @@ RPC Exports for malloc_test
 <section id="mt.mem_test_stop"><title>mt.mem_test_stop</title>
 <para>
         Takes 1 parameter: the test id. It will stop the corresponding
-        test.Note: the test is stopped, but not destroyed.
+        test. Note: the test is stopped, but not destroyed.
 </para>
 <para>
 </para>

doc/tutorials/rpc_list/rpc_malloc_test.txt

@@ -31,7 +31,7 @@ RPC Exports for malloc_test
  5. mt.mem_rnd_alloc
         Takes 4 parameters: min, max, total_size and an optional unit
         (b|k|m|g). It will allocate total_size memory, in pieces of
-        random size betweenmin .. max (inclusive).
+        random size between min .. max (inclusive).
 
  6. mt.mem_test_start
         Takes 7 parameters: min, max, total_size, min_interval,

doc/tutorials/serdev/modiface.xml

@@ -527,7 +527,7 @@ struct module_exports exports = {
 			    As the next step, list of all previously loaded
 			    modules will be searched for the same module.  If
 			    such module is found, it means, that user is trying
-			    to load the same module twice. In such case an
+			    to load the same module twice. In such case a
 			    warning will be issued and server will abort.
 			</para>
 		    </listitem>

doc/tutorials/serdev/module_exports.xml

@@ -35,7 +35,7 @@
 struct module_exports{
     char* name;                     /* null terminated module name */
     char** cmd_names;               /* cmd names registered 
-                                     * by this modules */
+                                     * by this module */
     cmd_function* cmd_pointers;     /* pointers to the 
                                      * corresponding functions */
     int* param_no;                  /* number of parameters used by 
@@ -48,7 +48,7 @@ struct module_exports{
                                      * (size of cmd_{names,pointers} 
                                      */
     char** param_names;      /* parameter names registered 
-                              * by this modules */
+                              * by this module */
     modparam_t* param_types; /* Type of parameters */
     void** param_pointers;   /* Pointers to the corresponding 
                               * memory locations */

doc/tutorials/serdev/routing_engine.xml

@@ -29,7 +29,7 @@
 	The routing engine can be found in file <filename>action.c</filename>.
     </para>
     <para>
-	The main function is <function>run_actions.</function> The function
+	The main function is <function>run_actions</function>. The function
 	accepts two parameters. The first parameter is list of actions to be
 	processed (Remember, the config file gets translated into array of
 	linked lists. Each linked list in the array represents one "route" part

doc/tutorials/serdev/startup.xml

@@ -703,7 +703,7 @@ module_stm = "loadmodule" STRING
 		</listitem>
 		<listitem>
 		    <para>
-			Call <function>init_child(0).</function> The function
+			Call <function>init_child(0)</function>. The function
 			performs per-child specific initialization of all
 			loaded modules.  A module can be initialized though
 			<function>mod_init</function> function.  The function

doc/tutorials/seruser/db_fifo.xml

@@ -216,7 +216,7 @@ TABLE_NAME
 		<para>
 		This function sends a raw query directly to the database driver 
 		without trying to understand the command. This command <emphasis>MUST
-		NOT</emphasis> generate any response.Otherwise, the database driver 
+		NOT</emphasis> generate any response. Otherwise, the database driver 
 		can block or desynchronize (depending of the driver).
 		Its syntax is:
 		<programlisting>

doc/tutorials/sip/sip_introduction.xml

@@ -868,7 +868,7 @@ Warning: 392 195.37.77.101:5060 "Noisy feedback tells:
 	    <title>Session Termination</title>
 	    <simpara>
 		Session termination is accomplished by sending a BYE request within dialog
-		established bye INVITE. BYE messages are sent directly from one user agent to
+		established by INVITE. BYE messages are sent directly from one user agent to
 		the other unless a proxy on the path of the INVITE request indicated that it
 		wishes to stay on the path by using record routing (see <xref
 		    linkend="record_routing"/>.
@@ -938,7 +938,7 @@ Warning: 392 195.37.77.101:5060 "Noisy feedback tells:
 		    little bit different way. The Request-URI is no more overwritten, it always
 		    contains URI of the destination user agent. If there are any Route header
 		    field in a message, than the message is sent to the URI from the topmost
-		    Route header field. This is significant change--Request-URI doesn't
+		    Route header field. This is a significant change--Request-URI doesn't
 		    necessarily contain URI to which the request will be sent. In fact, loose
 		    routing is very similar to IP source routing.
 		</simpara>