aboutsummaryrefslogtreecommitdiff
path: root/docs/source/community
diff options
context:
space:
mode:
authorEven Rouault <even.rouault@spatialys.com>2020-03-06 18:33:44 +0100
committerEven Rouault <even.rouault@spatialys.com>2020-03-06 18:33:44 +0100
commit5fff613d07c697040f67f97e40eddd995ec43958 (patch)
treec854c55811466a608bd96b472d32bb6a62b3f2eb /docs/source/community
parent93da0bcaa0880b183b312e1ce7834c74357e5b0e (diff)
downloadPROJ-5fff613d07c697040f67f97e40eddd995ec43958.tar.gz
PROJ-5fff613d07c697040f67f97e40eddd995ec43958.zip
Typo fixes identified by scripts/fix_typos.sh
Diffstat (limited to 'docs/source/community')
-rw-r--r--docs/source/community/rfc/rfc-4.rst6
-rw-r--r--docs/source/community/rfc/rfc-5.rst2
2 files changed, 4 insertions, 4 deletions
diff --git a/docs/source/community/rfc/rfc-4.rst b/docs/source/community/rfc/rfc-4.rst
index 5019a5f6..88abbe9e 100644
--- a/docs/source/community/rfc/rfc-4.rst
+++ b/docs/source/community/rfc/rfc-4.rst
@@ -103,7 +103,7 @@ environment variable.
The rationale for putting proj.ini in that location is
that it is a well-known place by PROJ users, with the existing PROJ_LIB mechanics
-for systems like Windows where hardcoded paths at runtime aren't generaly usable.
+for systems like Windows where hardcoded paths at runtime aren't generally usable.
C API
+++++
@@ -492,7 +492,7 @@ Limitations of current formats
++++++++++++++++++++++++++++++
Several formats exist depending on the ad-hoc needs and ideas of the original
-data producer. It would be apropriate to converge on a common format able to
+data producer. It would be appropriate to converge on a common format able to
address the different use cases.
- Not tiled. Tiling is a nice to have propery for cloud-friendly access to
@@ -538,7 +538,7 @@ Strong points:
geospatial field to store multi-resolution/pyramid rasters. So it can be
used with sub-grids as in the NTv2 format.
-* Extensive experience with the TIFF format, and its appropriatness for network
+* Extensive experience with the TIFF format, and its appropriateness for network
access, in particular through the `Cloud Optimized GeoTIFF initiative <https://www.cogeo.org/>`_
whose layout can make use of sub-grids efficient from a network access
perspective, because grid headers can be put at the beginning of the file, and
diff --git a/docs/source/community/rfc/rfc-5.rst b/docs/source/community/rfc/rfc-5.rst
index cab4687f..99fec5f7 100644
--- a/docs/source/community/rfc/rfc-5.rst
+++ b/docs/source/community/rfc/rfc-5.rst
@@ -86,7 +86,7 @@ Summary of work planned by this RFC and related decisions
- Obviously, all the above assumes PROJ builds to have libtiff enabled.
Non-libtiff builds are not considered as nominal PROJ builds (if a PROJ master
build is attempted and libtiff is not detected, it fails. The user has to
- explictly ask to disable TIFF support), and users deciding to go through that
+ explicitly ask to disable TIFF support), and users deciding to go through that
route will have to deal with the consequences (that is that
grid-based transformations generated by PROJ will likely be non working)