diff --git a/src/modules/lost/README b/src/modules/lost/README
index 357c41d3883..d1940ce7e1e 100644
--- a/src/modules/lost/README
+++ b/src/modules/lost/README
@@ -9,7 +9,7 @@ Edited by
 
 Wolfgang Kampichler
 
-   Copyright © 20018-2019 Wolfgang Kampichler
+   Copyright © 20018-2020 Wolfgang Kampichler
      __________________________________________________________________
 
    Table of Contents
@@ -60,9 +60,9 @@ Chapter 1. Admin Guide
    SIP requests may be forwarded based on a location provided with the
    request or retrieved from a specific location server using an identity
    (HELD). This module implements the basic functionality to get or parse
-   location information and to query a mapping service (LOST) in order to
-   get next hop based on location and service urn either specified or
-   provided with the request.
+   location information (civic and geodetic) and to query a mapping
+   service (LOST) in order to get next hop based on location and service
+   urn either specified or provided with the request.
 
    This module implements protocol functions that use the http_client api
    to fetch data from external LOST and HELD servers. The module is using
@@ -81,11 +81,11 @@ Chapter 1. Admin Guide
 
    The function lost_query allows Kamailio to assemble a LOST findService
    request as defined in RFC5222 (https://tools.ietf.org/html/rfc5255) to
-   query routing information for a given (geodetic) location and a service
-   URN. Both, PIDF-LO and service URN may be provided as function
-   parameter, or are taken from the request message if applicable. The
-   findServiceResponse is parsed and represented asdisplay name and SIP
-   URI typically used as next hop in a Route header.
+   query routing information for a given (geodetic or civic) location and
+   a service URN. Both, PIDF-LO and service URN may be provided as
+   function parameter, or are taken from the request message if
+   applicable. The findServiceResponse is parsed and represented asdisplay
+   name and SIP URI typically used as next hop in a Route header.
 
    The http_client module use the CURL library setting up connections. The
    CURL library by default use the system configured DNS resolvers, not
@@ -196,24 +196,24 @@ $var(id) = "urn:service:sos";
 $var(res) = lost_query("lostsrv", "$var(pidf)", "$var(urn)", "$var(uri)", "$var(
 name)", "$var(err)");
 xlog("L_INFO", "LOST findService: Result code $var(res)\nUri: $var(uri)\nName: $
-var(uri)\n");
+var(name)\n");
 ...
 # LOST findService request - pidf-lo as parameter, urn taken from request line
 $var(res) = lost_query("lostsrv", "$var(pidf)", "", "$var(uri)", "$var(name)", "
 $var(err)");
 xlog("L_INFO", "LOST findService: Result code $var(res)\nUri: $var(uri)\nName: $
-var(uri)\n");
+var(name)\n");
 ...
 # LOST findService request - urn as parameter, pidf-lo taken from message body
 $var(res) = lost_query("lostsrv", "", "$var(urn)", "$var(uri)", "$var(name)", "$
 var(err)");
 xlog("L_INFO", "LOST findService: Result code $var(res)\nUri: $var(uri)\nName: $
-var(uri)\n");
+var(name\n");
 ...
 # LOST findService request - pidf-lo and urn taken from message
 $var(res) = lost_query("lostsrv", "$var(uri)", "$var(name)", "$var(err)");
 xlog("L_INFO", "LOST findService: Result code $var(res)\nUri: $var(uri)\nName: $
-var(uri)\n");
+var(name)\n");
 ...
 
 5. Counters
@@ -236,5 +236,5 @@ var(uri)\n");
    requires query_params.oneline set to 0. In the case lost_query is used
    with the default http_client API, dereferencing location via HTTP
    provided with the Geolocation header causes an error. Therefore, to
-   work properlu=y, it requires to set http_client module parameter
+   work properly, it requires to set http_client module parameter
    query_result to 0.