Doc: fix typos

rouault · Sep 15, 2024 · f9896d0 · f9896d0
1 parent 49ebcf5
commit f9896d0
Show file tree

Hide file tree

Showing 9 changed files with 18 additions and 18 deletions.
diff --git a/docs/source/community/rfc/rfc-3.rst b/docs/source/community/rfc/rfc-3.rst
@@ -132,7 +132,7 @@ This RFC comes with a set of guidelines for handling dependencies for PROJ in
 the future. Up until now dependencies hasn't been handled consistently,  with
 some dependencies not being approved formally by the projects governing body.
 Therefore minimum versions of PROJ dependencies is proposed so that at the
-acception of this RFC PROJ will have the following external requirements:
+approval of this RFC PROJ will have the following external requirements:
 
 * C99 (was C89)
 * C++11 (already approved in :ref:`RFC2 <rfc2>`)

diff --git a/docs/source/news.rst b/docs/source/news.rst
@@ -12,7 +12,7 @@ Updates
 
   * Database: add constraint for unicity of CRS and operation names (`#4071 <https://github.com/OSGeo/PROJ/issues/4071>`_)
 
-  * Make a few more functions that accept a ``PJ*`` to actually acccept a ``const PJ*`` (`#4074 <https://github.com/OSGeo/PROJ/issues/4074>`_)
+  * Make a few more functions that accept a ``PJ*`` to actually accept a ``const PJ*`` (`#4074 <https://github.com/OSGeo/PROJ/issues/4074>`_)
 
   * Database: Increase consistency in trigger checks (`#4080 <https://github.com/OSGeo/PROJ/issues/4080>`_)
 
@@ -329,14 +329,14 @@ Updates
   * Added option ``ONLY_BEST=YES`` (`#3535 <https://github.com/OSGeo/PROJ/issues/3535>`_)
 
     When enabled only use the best possible transformation between two CRS's can be
-    instantiated. If the best possible transfomations can't be instantiated it will
+    instantiated. If the best possible transformations can't be instantiated it will
     fail instead of opting for the next best transformation.
 
     With ``ONLY_BEST=YES`` a transformation will fail if a needed grid is unavailable.
 
     The option can be toggled in ``proj.ini`` and with ``--only-best`` in :program:`cs2cs`.
 
-  * Implement 'Similarity transformation' (EPSG:9621) and import related tranformations from EPSG (`#3578 <https://github.com/OSGeo/PROJ/issues/3578>`_)
+  * Implement 'Similarity transformation' (EPSG:9621) and import related transformations from EPSG (`#3578 <https://github.com/OSGeo/PROJ/issues/3578>`_)
 
   * Optimise transformations between GDA94, GDA2020 and WGS84 (`#3621 <https://github.com/OSGeo/PROJ/issues/3621>`_)
 
@@ -578,7 +578,7 @@ Updates
 
   * Make it possible to determine which grid files were actually used during a transformation (`#3180 <https://github.com/OSGeo/PROJ/issues/3180>`_)
 
-  * Transformation: no longer do vertical trasnformation when doing compound CRS to 2D CRS / add --3d to cs2cs (`#3119 <https://github.com/OSGeo/PROJ/issues/3119>`_)
+  * Transformation: no longer do vertical transformation when doing compound CRS to 2D CRS / add --3d to cs2cs (`#3119 <https://github.com/OSGeo/PROJ/issues/3119>`_)
 
   * Deprecate PROJ4 CMake name (`#3094 <https://github.com/OSGeo/PROJ/issues/3094>`_)
 
@@ -922,7 +922,7 @@ Bug Fixes
 * ortho: remove useless and invalid log trace (`#2777 <https://github.com/OSGeo/PROJ/issues/2777>`_)
 
 * CMake: remove external nlohmann_json from INTERFACE_LINK_LIBRARIES target (`#2781 <https://github.com/OSGeo/PROJ/issues/2781>`_)
-* reateOperations(): fix SourceTargetCRSExtentUse::NONE mode (`#2783 <https://github.com/OSGeo/PROJ/issues/2783>`_)
+* createOperations(): fix SourceTargetCRSExtentUse::NONE mode (`#2783 <https://github.com/OSGeo/PROJ/issues/2783>`_)
 
 * GeoTIFF grid reading: perf improvements (`#2788 <https://github.com/OSGeo/PROJ/issues/2788>`_)
 
@@ -1318,7 +1318,7 @@ Bug fixes
 
 * Helmert 2D: do not require a useless +convention= parameter (`#2305 <https://github.com/OSGeo/PROJ/issues/2305>`_)
 
-* Fix a few spelling errors ("vgridshit" vs. "vgridshift") (`#2307 <https://github.com/OSGeo/PROJ/issues/2307>`_)
+* Fix a few spelling errors related to "vgridshift" (`#2307 <https://github.com/OSGeo/PROJ/issues/2307>`_)
 
 * Fix ability to identify EPSG:2154 as a candidate for 'RGF93_Lambert_93' (`#2316 <https://github.com/OSGeo/PROJ/issues/2316>`_)
 
@@ -1668,7 +1668,7 @@ Updates
   WKT2_2018 to WKT2_2019 to reflect the proper name of the standard (`#1585 <https://github.com/OSGeo/PROJ/issues/1585>`_)
 
 * Improvements in transformations from/to WGS 84 (Gxxxx) realizations and
-  vertical <--> geog transormations (`#1608 <https://github.com/OSGeo/PROJ/issues/1608>`_)
+  vertical <--> geog transformations (`#1608 <https://github.com/OSGeo/PROJ/issues/1608>`_)
 
 * Update to version 1.50 of the geodesic library (`#1629 <https://github.com/OSGeo/PROJ/issues/1629>`_)
 
@@ -2085,7 +2085,7 @@ transformation capabilities to a more complete library supporting coordinate
 transformations and coordinate reference systems.
 
 As a foundation for other enhancements, PROJ now includes a C++ implementation
-of the modelisation propopsed by the ISO-19111:2019 standard / OGC Abstract
+of the modelisation proposed by the ISO-19111:2019 standard / OGC Abstract
 Specification Topic 2: "Referencing By Coordinates", for geodetic reference
 frames (datums), coordinate reference systems and coordinate operations.
 Construction and query of those geodetic objects is available through a new C++
@@ -2105,7 +2105,7 @@ IOGP EPSG dataset (v9.6.0 release), the IGNF (French national mapping agency)
 geodetic registry and the ESRI projection engine database. PROJ is now the
 reference software in the "OSGeo C stack" for this CRS and coordinate operation
 database, whereas previously this functionality was spread over PROJ, GDAL and
-libgeotiff, and used CSV or other adhoc text-based formats.
+libgeotiff, and used CSV or other ad hoc text-based formats.
 
 Late-binding coordinate operation capabilities, that takes  metadata such as
 area of use and accuracy into account, has been added. This can avoid in a

diff --git a/docs/source/operations/projections/mod_krovak.rst b/docs/source/operations/projections/mod_krovak.rst
@@ -30,7 +30,7 @@ Modified Krovak
 
    proj-string: ``+proj=mod_krovak``
 
-Modified Krovak builts upon traditional :ref:`krovak`, with corrective terms that
+Modified Krovak builds upon traditional :ref:`krovak`, with corrective terms that
 are better suited when using it with the S-JTSK/05 datum. This method is specific
 to the Czech Republic. Due to the corrective terms, this projection method is
 no longer strictly conformal.

diff --git a/docs/source/tutorials/EUREF2019/exercises/projections2.gie b/docs/source/tutorials/EUREF2019/exercises/projections2.gie
@@ -77,7 +77,7 @@ expect      1371811.19          218598.22
    By reducing the scale factor, the line of zero distance distortion degenerates
    into two lines, north and south of the standard parallel.
 
-   For the abovementioned point in Tallinn, the distance error is around 0.002%,
+   For the above-mentioned point in Tallinn, the distance error is around 0.002%,
    but this can be reduced to zero by varying the scaling factor.
 
    Even by trial and error it is not hard to reduce it to a few millionths of a

diff --git a/docs/source/tutorials/EUREF2019/exercises/projections2.rst b/docs/source/tutorials/EUREF2019/exercises/projections2.rst
@@ -72,7 +72,7 @@ line segments at the latitude of the standard parallel.
 By reducing the scale factor, the line of zero distance distortion degenerates
 into two lines, north and south of the standard parallel.
 
-For the abovementioned point in Tallinn, the distance error is around 0.002%,
+For the above-mentioned point in Tallinn, the distance error is around 0.002%,
 but this can be reduced to zero by varying the scaling factor.
 
 Even by trial and error it is not hard to reduce it to a few millionths of a

diff --git a/docs/source/tutorials/EUREF2019/exercises/projections3.gie b/docs/source/tutorials/EUREF2019/exercises/projections3.gie
@@ -105,7 +105,7 @@ Hints:
 
 -------------------------------------------------------------------------------
 
-* 3a. As a baseline, determine the roundtrip accuracy of the default algorirthm
+* 3a. As a baseline, determine the roundtrip accuracy of the default algorithm
       using UTM zone 22:
 
 -------------------------------------------------------------------------------

diff --git a/docs/source/tutorials/EUREF2019/exercises/projections3.rst b/docs/source/tutorials/EUREF2019/exercises/projections3.rst
@@ -84,7 +84,7 @@ consider in which situation use of each of the algorithms is  appropriate.
 Exercise 3a
 ===========
 
-As a baseline, determine the roundtrip accuracy of the default algorirthm
+As a baseline, determine the roundtrip accuracy of the default algorithm
 using UTM zone 22.
 
 .. literalinclude:: projections3.gie

diff --git a/docs/source/usage/network.rst b/docs/source/usage/network.rst
@@ -98,8 +98,8 @@ data:
 
     wget --mirror https://cdn.proj.org/
 
-Acknowledgments
----------------
+Acknowledgements
+----------------
 
 The s3://cdn.proj.org bucket is hosted by the
 `Amazon Public Datasets program <https://aws.amazon.com/opendata/public-datasets/>`_.

diff --git a/src/iso19111/c_api.cpp b/src/iso19111/c_api.cpp
@@ -9667,7 +9667,7 @@ proj_get_geoid_models_from_database(PJ_CONTEXT *ctx, const char *auth_name,
 
 // ---------------------------------------------------------------------------
 
-/** \brief Instanciate a CoordinateMetadata object
+/** \brief Instantiate a CoordinateMetadata object
  *
  * @since 9.4
  */