add migration for upcoming change to tiger tables

[nominatim.git] / docs / api / Reverse.md

diff --git a/docs/api/Reverse.md b/docs/api/Reverse.md
index 664593d8c26d6cb45687919459c399cdcc141c40..06d7cdea6cf138428b13e395c7ff79483ec9738d 100644 (file)
--- a/docs/api/Reverse.md
+++ b/docs/api/Reverse.md
@@ -4,7 +4,7 @@ Reverse geocoding generates an address from a latitude and longitude.
 
 ## How it works
 
-The reveser geocoding API does not exactly compute the address for the
+The reverse geocoding API does not exactly compute the address for the
 coordinate it receives. It works by finding the closest suitable OSM object
 and returning its address information. This may occasionally lead to
 unexpected results.
@@ -27,7 +27,7 @@ The main format of the reverse API is
 https://nominatim.openstreetmap.org/reverse?lat=<value>&lon=<value>&<params>
 ```
 
-where `lat` and `lon` are latitude and longitutde of a coordinare in WGS84
+where `lat` and `lon` are latitude and longitutde of a coordinate in WGS84
 projection. The API returns exactly one result or an error when the coordinate
 is in an area with no OSM data coverage.
 
@@ -162,7 +162,7 @@ This overrides the specified machine readable format. (Default: 0)
   "licence":"Data © OpenStreetMap contributors, ODbL 1.0. https:\/\/www.openstreetmap.org\/copyright",
   "osm_type":"way",
   "osm_id":"280940520",
-"lat":"-34.4391708",
+  "lat":"-34.4391708",
   "lon":"-58.7064573",
   "place_rank":"26",
   "category":"highway",