From 6a69220ec8f46528d1c02295452e59462d02d0f5 Mon Sep 17 00:00:00 2001
From: Kamailio Dev <kamailio.dev@kamailio.org>
Date: Tue, 22 Aug 2017 12:31:44 +0200
Subject: [PATCH] modules: readme files regenerated - statsc ... [skip ci]

---
 src/modules/statsc/README |  8 ++++----
 src/modules/statsd/README | 13 +++++++------
 src/modules/usrloc/README |  2 +-
 3 files changed, 12 insertions(+), 11 deletions(-)

diff --git a/src/modules/statsc/README b/src/modules/statsc/README
index a546b56db5a..a753399731f 100644
--- a/src/modules/statsc/README
+++ b/src/modules/statsc/README
@@ -31,7 +31,7 @@ Daniel-Constantin Mierla
 
         4. RPC Commands
 
-              4.1. statsc.exec
+              4.1. statsc.report
 
    List of Examples
 
@@ -57,7 +57,7 @@ Chapter 1. Admin Guide
 
    4. RPC Commands
 
-        4.1. statsc.exec
+        4.1. statsc.report
 
 1. Overview
 
@@ -135,9 +135,9 @@ modparam("statsc", "track", "req.received=rcv_requests;rpl.received=rcv_replies"
 
 4. RPC Commands
 
-   4.1. statsc.exec
+   4.1. statsc.report
 
-4.1.  statsc.exec
+4.1.  statsc.report
 
    Get the report of recorded statistics.
 
diff --git a/src/modules/statsd/README b/src/modules/statsd/README
index 58b3fd8ae1c..5a414b77448 100644
--- a/src/modules/statsd/README
+++ b/src/modules/statsd/README
@@ -129,11 +129,10 @@ failure_route[tryagain] {
 3.2.  statsd_gauge(key, value)
 
    Gauges are a constant data type. They are not subject to averaging and
-   they don’t change unless you change them. That is, once you set a
-   gauge value, it will be a flat line on the graph until you change it
-   again.
+   they don't change unless you change them. That is, once you set a gauge
+   value, it will be a flat line on the graph until you change it again.
 
-   Gauges are useful for things that are already averaged, or don’t need
+   Gauges are useful for things that are already averaged, or don't need
    to reset periodically
 
    This function can be used in ALL ROUTES.
@@ -141,10 +140,12 @@ failure_route[tryagain] {
    The statsd server collects gauges under the stats.gauges prefix.
 
    Example 1.4. statsd_set usage
+...
 route [gauge_method]{
     statsd_gauge("method"+$rm, "+1");
     statsd_gauge("customer_credit"+$var(customer),"$var(customer_credit)");
 }
+...
 
 3.3.  statsd_start(key)
 
@@ -158,7 +159,7 @@ route [gauge_method]{
    The statsd server collects all timers under the stats.timers prefix and
    will calculate the lower bound, mean, 90th percentile, upper bound, and
    count of each timer for each period (by the time it can be seen in
-   graphite, that’s usually per minute).
+   graphite, that's usually per minute).
 
    Example 1.5. statsd_start usage
 ...
@@ -205,6 +206,6 @@ if(geoip_match("$si", "src")){
 ...
 if (t_check_status("408")) {
     statsd_decr("kamailio.successfulCalls");
-    statsd_incr("kamailio.reply.busy");
+    statsd_incr("kamailio.reply.timeout");
 }
 ...
diff --git a/src/modules/usrloc/README b/src/modules/usrloc/README
index fbddff49a1d..131baca9c5d 100644
--- a/src/modules/usrloc/README
+++ b/src/modules/usrloc/README
@@ -895,7 +895,7 @@ modparam("usrloc", "close_expired_tcp", 1)
 
    If set to 1, Kamailio expects to deal with BIGINT type on database
    columns for expires and last modified values. It allows to handle
-   better the daylight time adjustmens. If set to 0, those columns are
+   better the daylight time adjustments. If set to 0, those columns are
    expected to be on default type 'DATETIME'. When it is 1, the database
    columns types have to be changed manually to 'BIGINT'.