Merge pull request #2505 from visr/typos

fix a few typos in the docs

2 files changed, 3 insertions, 3 deletions

diff --git a/docs/source/development/reference/datatypes.rst b/docs/source/development/reference/datatypes.rst
index ed219daf..cb90e8db 100644
--- a/docs/source/development/reference/datatypes.rst
+++ b/docs/source/development/reference/datatypes.rst
@@ -824,7 +824,7 @@ Errors in class PROJ_ERR_INVALID_OP
 
 .. c:macro:: PROJ_ERR_INVALID_OP
 
-    Class of error codes typically related to coordinate operation initalization,
+    Class of error codes typically related to coordinate operation initialization,
     typically when creating a PJ* object from a PROJ string.
 
     .. note:: some of them can also be emitted during coordinate transformation,
diff --git a/docs/source/development/reference/functions.rst b/docs/source/development/reference/functions.rst
index 34fe59ed..d06179f3 100644
--- a/docs/source/development/reference/functions.rst
+++ b/docs/source/development/reference/functions.rst
@@ -180,7 +180,7 @@ paragraph for more details.
     coordinate reference systems.
 
     This is the same as :c:func:`proj_create_crs_to_crs` except that the source and
-    target CRS are passed as PJ* objects which must of the CRS variety.
+    target CRS are passed as PJ* objects which must be of the CRS variety.
 
     :param `options`: a list of NUL terminated options, or NULL.
 
@@ -285,7 +285,7 @@ Coordinate transformation
         3. of length one, i.e. a constant, which will be treated as a fully
            populated array of that constant value
 
-    .. note:: Even though he coordinate components are named :c:data:`x`, :c:data:`y`,
+    .. note:: Even though the coordinate components are named :c:data:`x`, :c:data:`y`,
               :c:data:`z` and :c:data:`t`, axis ordering of the to and from CRS
               is respected. Transformations exhibit the same behavior
               as if they were gathered in a :c:type:`PJ_COORD` struct.