Typo fixes identified by scripts/fix_typos.sh

6 files changed, 11 insertions, 11 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)
 
diff --git a/docs/source/faq.rst b/docs/source/faq.rst
index d3cdb50f..cd545036 100644
--- a/docs/source/faq.rst
+++ b/docs/source/faq.rst
@@ -173,7 +173,7 @@ Note that if you're using conda, activating an environment sets
 :envvar:`PROJ_LIB` to a resource directory located in that environment.
 
 
-What happend to PROJ.4?
+What happened to PROJ.4?
 --------------------------------------------------------------------------------
 
 The first incarnation of PROJ saw the light of day in 1983. Back then it
diff --git a/docs/source/resource_files.rst b/docs/source/resource_files.rst
index 48120982..39de6057 100644
--- a/docs/source/resource_files.rst
+++ b/docs/source/resource_files.rst
@@ -95,10 +95,10 @@ Its default content is:
     ;
 
     ; Network capabilities disabled by default.
-    ; Can be overriden with the PROJ_NETWORK=ON environment variable.
+    ; Can be overridden with the PROJ_NETWORK=ON environment variable.
     ; network = on
 
-    ; Can be overriden with the PROJ_NETWORK_ENDPOINT environment variable.
+    ; Can be overridden with the PROJ_NETWORK_ENDPOINT environment variable.
     cdn_endpoint = https://cdn.proj.org
 
     cache_enabled = on
diff --git a/docs/source/specifications/geodetictiffgrids.rst b/docs/source/specifications/geodetictiffgrids.rst
index 9e849074..479d6ca9 100644
--- a/docs/source/specifications/geodetictiffgrids.rst
+++ b/docs/source/specifications/geodetictiffgrids.rst
@@ -37,7 +37,7 @@ is an easy way to inspect such grid files:
 - Files hosted on the CDN will use a Geographic 2D CRS for the GeoTIFF GeoKeys.
   That CRS is intended to be the interpolation CRS as defined in
   `OGC Abstract Specification Topic 2 <http://docs.opengeospatial.org/as/18-005r4/18-005r4.html>`_,
-  that is the CRS to which grid values are refered to.
+  that is the CRS to which grid values are referred to.
 
   Given that they will nominally be related to the EPSG dataset, the `GeodeticCRSGeoKey
   <http://docs.opengeospatial.org/is/19-008r4/19-008r4.html#_requirements_class_geodeticcrsgeokey>`_
@@ -137,7 +137,7 @@ is an easy way to inspect such grid files:
 
     * SamplesPerPixel = 1 for vertical shift grids.
 
-   In the future, different values of SamplesPerPixel may be used to accomodate
+   In the future, different values of SamplesPerPixel may be used to accommodate
    for other needs. For example for deformation models, SamplesPerPixel = 3 to combine
    horizontal and vertical adjustments.
    And even for the current identified needs of horizontal or vertical shifts,
diff --git a/docs/source/usage/differences.rst b/docs/source/usage/differences.rst
index be163176..2a262232 100644
--- a/docs/source/usage/differences.rst
+++ b/docs/source/usage/differences.rst
@@ -132,13 +132,13 @@ proj
 --------
 
 Removed ``-ld`` option from application, since it promoted use of deprecated
-paramters like ``+towgs`` and ``+datum``.
+parameters like ``+towgs`` and ``+datum``.
 
 cs2cs
 --------
 
 Removed ``-ld`` option from application, since it promoted use of deprecated
-paramters like ``+towgs`` and ``+datum``.
+parameters like ``+towgs`` and ``+datum``.
 
 UTF-8 adoption
 --------------