[SR-Dev] git:master: port doc changes from kamailio 1.5 branch, r5794

Module: sip-router Branch: master Commit: 5bad9d33802f87be1fbce04b0f24b4aedf6c606c URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=5bad9d3… Author: Henning Westerholt &lt;henning.westerholt(a)1und1.de&gt; Committer: Henning Westerholt &lt;henning.westerholt(a)1und1.de&gt; Date: Thu Apr 16 12:51:18 2009 +0200 port doc changes from kamailio 1.5 branch, r5794 --- modules/carrierroute/README | 8 ++++---- modules/carrierroute/doc/carrierroute_admin.xml | 9 ++++----- 2 files changed, 8 insertions(+), 9 deletions(-) diff --git a/modules/carrierroute/README b/modules/carrierroute/README index 67fbb2b..475138a 100644 --- a/modules/carrierroute/README +++ b/modules/carrierroute/README @@ -227,10 +227,10 @@ Chapter 1. Admin Guide is better to pass only IDs in AVPs to the routing functions. Basically this module could be used as an replacement for the - lcr and the dispatcher module, if you have certain performance, - flexibility and/or integration requirements that these modules - don't handle properly. But for small installations it probably - make more sense to use the lcr and dispatcher module. + 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. If you want to use this module in failure routes, then you need to call "append_branch()" after rewriting the request URI in diff --git a/modules/carrierroute/doc/carrierroute_admin.xml b/modules/carrierroute/doc/carrierroute_admin.xml index d115478..317a54e 100644 --- a/modules/carrierroute/doc/carrierroute_admin.xml +++ b/modules/carrierroute/doc/carrierroute_admin.xml @@ -53,11 +53,10 @@ AVPs to the routing functions. </para> <para> - Basically this module could be used as an replacement for the lcr and the - dispatcher module, if you have certain performance, flexibility and/or - integration requirements that these modules don't handle properly. But for - small installations it probably make more sense to use the lcr and dispatcher - module. + Basically this module could be used as an 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. </para> <para> If you want to use this module in failure routes, then you need to call