Minor stylistic edits to documentation, and translation of Latinate

language word "desponible" to "available", as "desponible" does not
exist in English.  :-)

modules/xhttp_rpc/README

@@ -10,6 +10,12 @@ Ovidiu Sas
 
    <[email protected]>
 
+Edited by
+
+Alex Balashov
+
+   <[email protected]>
+
    Copyright © 2011 VoIPEmbedded Inc.
      __________________________________________________________________
 
@@ -68,7 +74,7 @@ Chapter 1. Admin Guide
    1.1. Limitations
 
    This module provides an HTTP transport layer implementation for the RPC
-   management interface in a human easy readable format.
+   management interface in a human-readable format.
 
    The xHTTP_RPC module uses the xHTTP module to handle HTTP requests.
    Read the documentation of the xHTTP module for more details.
@@ -85,7 +91,7 @@ Chapter 1. Admin Guide
    At startup, all RPC commands are sorted and grouped based on their
    format. The expected format is [group].[subcommand]. The initial
    xhttp_rpc webpage displays all the retrieved groups. All RPC commands
-   are disponible as submenus of each [group]. If an RPC command is not in
+   are available as sub-menus of each [group]. If an RPC command is not in
    the expected format, it will be dropped from the initial xhttp_rpc home
    page menu.
 
@@ -126,7 +132,7 @@ modparam("xhttp_rpc", "xhttp_rpc_root", "http_rpc")
 3.2. xhttp_rpc_buf_size (str)
 
    It specifies the maximum length of the buffer used to write in the RPC
-   reply information in order to build the html response.
+   reply information in order to build the HTML response.
 
    Default value is 0 (auto set to 1/3 of the size of the configured pkg
    mem).
@@ -142,7 +148,7 @@ modparam("xhttp", "xhttp_rpc_buf_size", )
 
 4.1.  dispatch_xhttp_rpc()
 
-   Handle the HTTP request and generate back a response.
+   Handle the HTTP request and generate a response.
 
    Example 1.3. dispatch_xhttp_rpc usage
 ...

modules/xhttp_rpc/doc/xhttp_rpc.xml

@@ -23,6 +23,11 @@
 		<surname>Sas</surname>
 		<email>[email protected]</email>
 	    </editor>
+	    <editor>
+		<firstname>Alex</firstname>
+		<surname>Balashov</surname>
+		<email>[email protected]</email>
+	    </editor>
 	</authorgroup>
 	<copyright>
 	    <year>2011</year>

modules/xhttp_rpc/doc/xhttp_rpc_admin.xml

@@ -17,7 +17,7 @@
 	<title>Overview</title>
 	<para>
 		This module provides an HTTP transport layer implementation for
-		the RPC management interface in a human easy readable format.
+		the RPC management interface in a human-readable format.
 	<para>
 	</para>
 		The xHTTP_RPC module uses the xHTTP module to handle HTTP requests.
@@ -40,7 +40,7 @@
 		At startup, all RPC commands are sorted and grouped based on
 		their format.  The expected format is [group].[subcommand].
 		The initial xhttp_rpc webpage displays all the retrieved groups.
-		All RPC commands are disponible as submenus of each [group].
+		All RPC commands are available as sub-menus of each [group].
 		If an RPC command is not in the expected format, it will be
 		dropped from the initial xhttp_rpc home page menu.
 	</para>
@@ -106,7 +106,7 @@ modparam("xhttp_rpc", "xhttp_rpc_root", "http_rpc")
 		<para>
 			It specifies the maximum length of the buffer used
 			to write in the RPC reply information in order to
-			build the html response.
+			build the HTML response.
 		</para>
 		<para>
 		<emphasis>
@@ -131,7 +131,7 @@ modparam("xhttp", "xhttp_rpc_buf_size", )
 		<function moreinfo="none">dispatch_xhttp_rpc()</function>
 	    </title>
 	    <para>
-		Handle the HTTP request and generate back a response.
+		Handle the HTTP request and generate a response.
 	    </para>
 		<example>
 		<title><function>dispatch_xhttp_rpc</function> usage</title>