[sr-dev] git:master:eaded8a4: modules/[tm|db2_ops]: use consistent naming for route names in documentation

[Mikko Lehto]

Module: kamailio
Branch: master
Commit: eaded8a4c90e7d35c91a9101190ff79f161bea51
URL: https://github.com/kamailio/kamailio/commit/eaded8a4c90e7d35c91a9101190ff79f161bea51

Author: Mikko Lehto <mslehto at iki.fi>
Committer: Mikko Lehto <mslehto at iki.fi>
Date: 2016-11-15T00:01:30+02:00

modules/[tm|db2_ops]: use consistent naming for route names in documentation

---

Modified: modules/db2_ops/doc/db2_ops.xml
Modified: modules/tm/doc/functions.xml

---

Diff:  https://github.com/kamailio/kamailio/commit/eaded8a4c90e7d35c91a9101190ff79f161bea51.diff
Patch: https://github.com/kamailio/kamailio/commit/eaded8a4c90e7d35c91a9101190ff79f161bea51.patch

---

diff --git a/modules/db2_ops/doc/db2_ops.xml b/modules/db2_ops/doc/db2_ops.xml
index 95a1156..9e979f2 100644
--- a/modules/db2_ops/doc/db2_ops.xml
+++ b/modules/db2_ops/doc/db2_ops.xml
@@ -277,7 +277,7 @@
 			</title>
 			<para>
 				Hack which enables using db_ops queries in failure route.
-				Call it at the beginning of <emphasis>failure_route</emphasis> block.
+				Call it at the beginning of FAILURE_ROUTE block.
 			</para>
 			<example>
 				<title><function>db_proper</function> usage</title>
diff --git a/modules/tm/doc/functions.xml b/modules/tm/doc/functions.xml
index 4ad34fc..ddc7dd9 100644
--- a/modules/tm/doc/functions.xml
+++ b/modules/tm/doc/functions.xml
@@ -787,8 +787,7 @@ route {
 	<para>
 		Returns true if the failure route is executed for a branch that did
 		timeout. It can be used from 
-		<emphasis>failure_route</emphasis> and
-		<emphasis>branch-failure</emphasis> event route.
+		FAILURE_ROUTE and BRANCH_FAILURE_ROUTE event route.
 	</para>
 	<example>
 	    <title><function>t_branch_timeout</function> usage</title>
@@ -1289,7 +1288,7 @@ if (!t_next_contacts()) {
 		was empty and thus there was
 		nothing to do, and returns -1 in case of an error (see
 		syslog).
-		This function can be used from a BRANCH_FAILURE event route.
+		This function can be used from a BRANCH_FAILURE_ROUTE event route.
 		</para>
 		<example>
 		<title><function>t_next_contact_flow</function> usage</title>