summaryrefslogtreecommitdiff
path: root/CONTRIBUTING.md
diff options
context:
space:
mode:
authorJavier Jimenez Shaw <j1@jimenezshaw.com>2020-04-10 20:41:29 +0200
committerJavier Jimenez Shaw <j1@jimenezshaw.com>2020-04-10 20:41:29 +0200
commit33204f7fcbf2d50c140a1985b9272cfca1dd56a7 (patch)
tree6248a40b6a15c72a1778eb5541dc7a9342fc54d1 /CONTRIBUTING.md
parentcf29b837994ab52a576f6c3556f6b0657f353ab8 (diff)
downloadPROJ-data-33204f7fcbf2d50c140a1985b9272cfca1dd56a7.tar.gz
PROJ-data-33204f7fcbf2d50c140a1985b9272cfca1dd56a7.zip
fix two typos
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r--CONTRIBUTING.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 246fa88..a07bb2b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -49,7 +49,7 @@ the PROJ database (typically they have a EPSG code), a transformation for them u
the grid must be referenced in the PROJ database. Generally, the EPSG database will
already have an entry for the grid, sometimes with a slightly different name.
The relevant file to look into is [grid_transformation.sql](https://github.com/OSGeo/PROJ/blob/master/data/sql/grid_transformation.sql).
-If the gris is not yet registered in the EPSG database, you are *strongly* encouraged to
+If the grid is not yet registered in the EPSG database, you are *strongly* encouraged to
engage with EPSG to register it. This will make its addition to PROJ and its later maintenance
much easier. http://www.epsg.org/EPSGDataset/Makechangerequest.aspx explains the procedure
to follow to submit a change request to EPSG.