carrierroute: typos a/an

src/modules/carrierroute/carrierroute.c

@@ -29,7 +29,7 @@
  * \defgroup carrierroute CARRIERROUTE :: The Kamailio carrierroute Module
  * The module provides routing, balancing and blocklisting capabilities.
  * It reads routing entries from a database source or from a config file
- * at Kamailio startup. It can uses one routing tree (for one carrier),
+ * at Kamailio startup. It can use one routing tree (for one carrier),
  * or if needed for every user a different routing tree (unique for each carrier)
  * for number prefix based routing. It supports several routing domains, e.g.
  * for failback routes or different routing rules for VoIP and PSTN targets.

src/modules/carrierroute/cr_fixup.c

@@ -126,7 +126,7 @@ static int carrier_fixup(void ** param) {
 	}
 
 	if (((gparam_p)(*param))->type == GPARAM_TYPE_STR) {
-		/* This is a name string, convert to a int */
+		/* This is a name string, convert to an int */
 		((gparam_p)(*param))->type=GPARAM_TYPE_INT;
 		/* get carrier id */
 		if ((id = carrier_name_2_id(&((gparam_p)(*param))->v.str)) < 0) {
@@ -157,7 +157,7 @@ static int domain_fixup(void ** param) {
 	}
 
 	if (((gparam_p)(*param))->type == GPARAM_TYPE_STR) {
-		/* This is a name string, convert to a int */
+		/* This is a name string, convert to an int */
 		((gparam_p)(*param))->type=GPARAM_TYPE_INT;
 		/* get domain id */
 		if ((id = domain_name_2_id(&(((gparam_p)(*param))->v.str))) < 0) {

src/modules/carrierroute/cr_rule.c

@@ -46,7 +46,7 @@
  * @param backup indicates if the route is backed up by another. only
                  useful if status==0, if set, it is the hash value
                  of another rule
- * @param backed_up an NULL-termintated array of hash indices of the route
+ * @param backed_up a NULL-termintated array of hash indices of the route
                     for which this route is backup
  * @param comment a comment for the route rule
  *

src/modules/carrierroute/cr_rule.h

@@ -111,7 +111,7 @@ struct failure_route_rule {
  * @param backup indicates if the route is backed up by another. only
                  useful if status==0, if set, it is the hash value
                  of another rule
- * @param backed_up an NULL-termintated array of hash indices of the route
+ * @param backed_up a NULL-termintated array of hash indices of the route
                     for which this route is backup
  * @param comment a comment for the route rule
  *

src/modules/carrierroute/doc/carrierroute_admin.xml

@@ -17,7 +17,7 @@
 	<para>
 		The module provides routing, balancing and blocklisting capabilities.
 		It reads routing entries from a database source or from a config file at &kamailio;
-		startup. It can uses one routing tree (for one carrier), or if needed for every user
+		startup. It can use one routing tree (for one carrier), or if needed for every user
 		a different routing tree (unique for each carrier) for number prefix based routing.
 		It supports several route tree domains,	e.g. for fallback routes or different routing
 		rules for VoIP and PSTN targets.
@@ -41,7 +41,7 @@
 		Routing tables can be reloaded and edited (in config file mode) with the RPC
 		interface, the config file is updated according the changes. This is not
 		implemented for the db interface, because its easier to do the changes
-		directly on the db. But the reload and dump functions works of course here
+		directly on the db. But the reload and dump functions work of course here
 		too.
 	</para>
 	<para>
@@ -61,7 +61,7 @@
 		AVPs to the routing functions.
 	</para>
 	<para>
-		Basically this module could be used as an replacement for the lcr and the
+		Basically this module could be used as a replacement for the lcr and the
 		dispatcher module, if you have certain flexibility, integration and/or performance
 		requirements that can't be satisfied with these modules. But for smaller
 		installations it probably make more sense to use the lcr and dispatcher module.
@@ -745,15 +745,15 @@ failure_route[1] {
 		<title>Configuration example - module configuration</title>
 		<para>
 			The following config file specifies within the default carrier two
-			domains, each with an prefix that contains two hosts. It is not possible
+			domains, each with a prefix that contains two hosts. It is not possible
 			to specify another carrier if you use the config file as data source.
 		</para>
 		<para>
 			All traffic will be equally distributed between the hosts, both are
 			active. The hash algorithm will working over the [1,2] set, messages
 			hashed to one will go to the first host, the other to the second one.
 			Don't use a hash index value of zero. If you omit the hash completely,
-			the module gives them a autogenerated value, starting from one.
+			the module gives them an autogenerated value, starting from one.
 		</para>
 		<para>
 			Use the <quote>NULL</quote> prefix to specify an empty prefix in the config file.
@@ -861,7 +861,7 @@ domain register {
 			and a default route for other prefixes over carrier 2 and carrier 1. The
 			gateways for the default carrier will be used for functions that don't
 			support the user specific carrier lookup. The routing rules for carrier 1
-			and carrier 2 for the <quote>49</quote> prefix contains a additional rule
+			and carrier 2 for the <quote>49</quote> prefix contains an additional rule
 			with the domain 2, that can be used for example as fallback if the gateways
 			in domain 1 are not reachable. Two more fallback rules (domain 3 and 4) for 
 			carrier 1 are also supplied to support the functionality of the carrierfailureroute