DOC: configure and add spelling wordlist; fix typos, apply Sphinx syntax (#2705)

13 files changed, 30 insertions, 30 deletions

diff --git a/docs/source/operations/conversions/geoc.rst b/docs/source/operations/conversions/geoc.rst
index a9be2dfb..6ee32ea6 100644
--- a/docs/source/operations/conversions/geoc.rst
+++ b/docs/source/operations/conversions/geoc.rst
@@ -36,7 +36,7 @@ the body centre to the considered point.
 
 .. note::
 
-    This conversion must be distinguished fom the :ref:`cart`
+    This conversion must be distinguished from the :ref:`cart`
     which converts geodetic coordinates to geocentric coordinates in the cartesian
     domain.
 
diff --git a/docs/source/operations/operations_computation.rst b/docs/source/operations/operations_computation.rst
index 0d78feae..0bc57ff0 100644
--- a/docs/source/operations/operations_computation.rst
+++ b/docs/source/operations/operations_computation.rst
@@ -69,7 +69,7 @@ Geographic CRS to Geographic CRS, with known identifiers
 With the above example of two geographic CRS, that have an identified identifier,
 (:program:`projinfo` internally resolves NAD27 to EPSG:4267 and NAD83 to EPSG:4269)
 the algorithm will first search
-in the coordinate operation related tables of the ``proj.db`` if there are records
+in the coordinate operation related tables of the :file:`proj.db` if there are records
 that list direct transformations between the source and the target CRS. The
 transformations typically involve :ref:`Helmert <helmert>`-style operations or datum shift based on
 grids (more esoteric operations are possible).
@@ -161,7 +161,7 @@ Geodetic/geographic CRS to Geodetic/geographic CRS, without known identifiers
 
 In a number of situations, the source and/or target CRS do not have an identifier
 (WKT without identifier, PROJ string, ..)
-The first step is to try to find in the ``proj.db`` a CRS of the same nature of
+The first step is to try to find in the :file:`proj.db` a CRS of the same nature of
 the CRS to identify and whose name exactly matches the one provided to the
 :c:func:`createOperations` method. If there is exactly one match and that the CRS are
 "computationally" equivalent, then use the code of the CRS for further computations.
@@ -238,7 +238,7 @@ are equivalent for most purposes.
 
     Candidate operations found: 1
     -------------------------------------
-    Operation n°1:
+    Operation No. 1:
 
     unknown id, axis order change (geographic3D horizontal) + RGF93 to ETRS89 (1) + Conversion from ETRS89 (geog2D) to ETRS89 (geocentric), 0 m, France
 
@@ -338,7 +338,7 @@ following results for the AGD84 to GDA2020 coordinate operations lookup:
 
     Candidate operations found: 4
     -------------------------------------
-    Operation n°1:
+    Operation No. 1:
 
     unknown id, AGD84 to GDA94 (5) + GDA94 to GDA2020 (1), 0.11 m, Australia - AGD84
 
@@ -357,7 +357,7 @@ following results for the AGD84 to GDA2020 coordinate operations lookup:
                    +step +proj=axisswap +order=2,1
 
     -------------------------------------
-    Operation n°2:
+    Operation No. 2:
 
     unknown id, AGD84 to GDA94 (2) + GDA94 to GDA2020 (1), 1.01 m, Australia - AGD84
 
@@ -378,7 +378,7 @@ following results for the AGD84 to GDA2020 coordinate operations lookup:
                    +step +proj=axisswap +order=2,1
 
     -------------------------------------
-    Operation n°3:
+    Operation No. 3:
 
     unknown id, AGD84 to GDA94 (5) + GDA94 to GDA2020 (2), 0.15 m, unknown domain of validity
 
@@ -391,7 +391,7 @@ following results for the AGD84 to GDA2020 coordinate operations lookup:
                    +step +proj=axisswap +order=2,1
 
     -------------------------------------
-    Operation n°4:
+    Operation No. 4:
 
     unknown id, AGD84 to GDA94 (5) + GDA94 to GDA2020 (3), 0.15 m, unknown domain of validity
 
@@ -424,7 +424,7 @@ If one forces the datum hub to be considered to be EPSG:4326, ones gets:
 
     Candidate operations found: 2
     -------------------------------------
-    Operation n°1:
+    Operation No. 1:
 
     unknown id, AGD84 to WGS 84 (7) + Inverse of GDA2020 to WGS 84 (2), 4 m, Australia - AGD84
 
@@ -442,7 +442,7 @@ If one forces the datum hub to be considered to be EPSG:4326, ones gets:
                    +step +proj=axisswap +order=2,1
 
     -------------------------------------
-    Operation n°2:
+    Operation No. 2:
 
     unknown id, AGD84 to WGS 84 (9) + Inverse of GDA2020 to WGS 84 (2), 4 m, Australia - AGD84
 
@@ -500,7 +500,7 @@ particular case. Such transformations are done in 2 steps:
 
     Candidate operations found: 1
     -------------------------------------
-    Operation n°1:
+    Operation No. 1:
 
     unknown id, Inverse of UTM zone 31N + Inverse of RGF93 to WGS 84 (1), 1 m, France
 
@@ -531,7 +531,7 @@ between those:
     $ projinfo -s "NAVD88 height" -t "NAD83(2011)" -o PROJ --spatial-test intersects
     Candidate operations found: 11
     -------------------------------------
-    Operation n°1:
+    Operation No. 1:
 
     INVERSE(DERIVED_FROM(EPSG)):9229, Inverse of NAD83(2011) to NAVD88 height (3), 0.015 m, USA - CONUS - onshore
 
@@ -560,7 +560,7 @@ This is implemented by the ``createOperationsVertToVert`` method
 
     Candidate operations found: 3
     -------------------------------------
-    Operation n°1:
+    Operation No. 1:
 
     unknown id, Inverse of NGVD29 height (ftUS) to NGVD29 depth (ftUS) + NGVD29 height (ftUS) to NGVD29 height (m) + NGVD29 height (m) to NAVD88 height (3), 0.02 m, USA - CONUS east of 89°W - onshore
 
@@ -568,7 +568,7 @@ This is implemented by the ``createOperationsVertToVert`` method
     +proj=pipeline +step +proj=axisswap +order=1,2,-3 +step +proj=unitconvert +z_in=us-ft +z_out=m +step +proj=vgridshift +grids=vertcone.gtx +multiplier=0.001
 
     -------------------------------------
-    Operation n°2:
+    Operation No. 2:
 
     unknown id, Inverse of NGVD29 height (ftUS) to NGVD29 depth (ftUS) + NGVD29 height (ftUS) to NGVD29 height (m) + NGVD29 height (m) to NAVD88 height (2), 0.02 m, USA - CONUS 89°W-107°W - onshore
 
@@ -576,7 +576,7 @@ This is implemented by the ``createOperationsVertToVert`` method
     +proj=pipeline +step +proj=axisswap +order=1,2,-3 +step +proj=unitconvert +z_in=us-ft +z_out=m +step +proj=vgridshift +grids=vertconc.gtx +multiplier=0.001
 
     -------------------------------------
-    Operation n°3:
+    Operation No. 3:
 
     unknown id, Inverse of NGVD29 height (ftUS) to NGVD29 depth (ftUS) + NGVD29 height (ftUS) to NGVD29 height (m) + NGVD29 height (m) to NAVD88 height (1), 0.02 m, USA - CONUS west of 107°W - onshore
 
@@ -761,7 +761,7 @@ Example:
 
     Candidate operations found: 1
     -------------------------------------
-    Operation n°1:
+    Operation No. 1:
 
     unknown id, Inverse of unknown + Transformation from unknown to WGS84 + Inverse of ETRS89 to WGS 84 (1), unknown accuracy, Europe - ETRS89
 
diff --git a/docs/source/operations/pipeline.rst b/docs/source/operations/pipeline.rst
index 90112c05..97b58e3e 100644
--- a/docs/source/operations/pipeline.rst
+++ b/docs/source/operations/pipeline.rst
@@ -57,7 +57,7 @@ Rules for pipelines
 
 Will result in an error.
 
-**2. Pipelines can only be nested if the nested pipeline is defined in an init-file.**
+**2. Pipelines can only be nested if the nested pipeline is defined in an init file.**
 
 ::
 
diff --git a/docs/source/operations/projections/cass.rst b/docs/source/operations/projections/cass.rst
index 5428260a..073fe6cc 100644
--- a/docs/source/operations/projections/cass.rst
+++ b/docs/source/operations/projections/cass.rst
@@ -68,7 +68,7 @@ Options
 .. option:: +hyperbolic
 
     Use modified form of the standard Cassini-Soldner projection known as the Hyperbolic Cassini-Soldner.
-    This is used in particular for the "Vanua Levu Grid" of the the island of Vanua Levu, Fiji (EPSG:3139)
+    This is used in particular for the "Vanua Levu Grid" of the island of Vanua Levu, Fiji (EPSG:3139)
 
 
 Mathematical definition
diff --git a/docs/source/operations/projections/cc.rst b/docs/source/operations/projections/cc.rst
index 81ea17db..c6f3927a 100644
--- a/docs/source/operations/projections/cc.rst
+++ b/docs/source/operations/projections/cc.rst
@@ -31,7 +31,7 @@ Central Cylindrical
 Parameters
 ################################################################################
 
-.. note:: All parameters are optional for the Central Cylindricla projection.
+.. note:: All parameters are optional for the Central Cylindrical projection.
 
 .. include:: ../options/lon_0.rst
 
diff --git a/docs/source/operations/projections/gall.rst b/docs/source/operations/projections/gall.rst
index c5f05478..8114815a 100644
--- a/docs/source/operations/projections/gall.rst
+++ b/docs/source/operations/projections/gall.rst
@@ -43,12 +43,12 @@ The Gall projection is neither conformal nor equal-area, but has a blend of vari
 Unlike the Mercator, the Gall shows the poles as lines running across the top and bottom of the map.
 
 
-Example using Gall Stereographical  ::
+Example using Gall Stereographic  ::
 
     $ echo 9 51 | proj +proj=gall +lon_0=0 +x_0=0 +y_0=0 +ellps=WGS84 +units=m
     708432.90   5193386.36
 
-Example using Gall Stereographical (Central meridian 90°W) ::
+Example using Gall Stereographic (Central meridian 90°W) ::
 
     $ echo 9 51 | proj +proj=gall +lon_0=90w +x_0=0 +y_0=0 +ellps=WGS84 +units=m
     7792761.91  5193386.36
@@ -72,7 +72,7 @@ Parameters
 Mathematical definition
 #######################
 
-The formulas describing the Gall Stereographical are all taken from :cite:`Snyder1993`.
+The formulas describing the Gall Stereographic are all taken from :cite:`Snyder1993`.
 
 Spherical form
 **************
diff --git a/docs/source/operations/projections/gnom.rst b/docs/source/operations/projections/gnom.rst
index c9fc4bcf..c18ab4e7 100644
--- a/docs/source/operations/projections/gnom.rst
+++ b/docs/source/operations/projections/gnom.rst
@@ -31,7 +31,7 @@ Gnomonic
 Parameters
 ################################################################################
 
-.. note:: All parameters are optional for the Gnomomic projection.
+.. note:: All parameters are optional for the Gnomonic projection.
 
 .. include:: ../options/lon_0.rst
 
diff --git a/docs/source/operations/projections/lcc.rst b/docs/source/operations/projections/lcc.rst
index 8002fa31..bf15d76a 100644
--- a/docs/source/operations/projections/lcc.rst
+++ b/docs/source/operations/projections/lcc.rst
@@ -23,7 +23,7 @@ justifies adding this otherwise non-standard projection.
 | **Available forms** | Forward and inverse, spherical and ellipsoidal          .|
 |                     | One or two standard parallels (1SP and 2SP).             |
 |                     | "LCC 2SP Michigan" form can be used by setting           |
-|                     | `+k_0` parameter to specify elliposid scale.             |
+|                     | ``+k_0`` parameter to specify ellipsoid scale.           |
 +---------------------+----------------------------------------------------------+
 | **Defined area**    | Best for regions predominantly east–west in extent and   |
 |                     | located in the middle north or south latitudes.          |
diff --git a/docs/source/operations/projections/merc.rst b/docs/source/operations/projections/merc.rst
index 2107b7b2..6eae9d36 100644
--- a/docs/source/operations/projections/merc.rst
+++ b/docs/source/operations/projections/merc.rst
@@ -181,7 +181,7 @@ This is obtained by taking the :math:`\sinh` of the equation for
 using :math:`\tau = \tau'/(1 - e^2)` as an initial guess and with the
 needed derivative given by
 
-..math::
+.. math::
     \frac{d\tau'}{d\tau} = \frac{1 - e^2}{1 + (1 - e^2)\tau^2}
     \sqrt{1 + \tau'^2} \sqrt{1 + \tau^2}
 
diff --git a/docs/source/operations/projections/tmerc.rst b/docs/source/operations/projections/tmerc.rst
index 3a18904f..576ad327 100644
--- a/docs/source/operations/projections/tmerc.rst
+++ b/docs/source/operations/projections/tmerc.rst
@@ -156,7 +156,7 @@ Spherical form
 **************
 
 Because the full (ellipsoidal) projection includes the spherical
-projection as one of the components, we present the spherial form first
+projection as one of the components, we present the spherical form first
 with the coordinates tagged with primes, :math:`\phi'`,
 :math:`\lambda'`, :math:`\zeta' = \xi' + i\eta'`, :math:`x'`,
 :math:`y'`, so that they can be distinguished from the corresponding
diff --git a/docs/source/operations/projections/tobmerc.rst b/docs/source/operations/projections/tobmerc.rst
index 69a4855d..7bc5cb95 100644
--- a/docs/source/operations/projections/tobmerc.rst
+++ b/docs/source/operations/projections/tobmerc.rst
@@ -40,7 +40,7 @@ The inappropriate use of the Mercator projection has declined but still
 occasionally occurs. One method of contrasting the Mercator projection is to
 present an alternative in the form of an equal area projection. The map
 projection derived here is thus not simply a pretty Christmas tree ornament:
-it is instead a complement to Mercator's conformal navigation anamorphose
+it is instead a complement to Mercator's conformal navigation anamorphosis
 and can be displayed as an alternative. The equations for the new map
 projection preserve the latitudinal stretching of the Mercator while
 adjusting the longitudinal spacing. This allows placement of the new map
diff --git a/docs/source/operations/projections/utm.rst b/docs/source/operations/projections/utm.rst
index 6b957472..2367cbad 100644
--- a/docs/source/operations/projections/utm.rst
+++ b/docs/source/operations/projections/utm.rst
@@ -47,7 +47,7 @@ Convert geodetic coordinate to UTM Zone 32 on the northern hemisphere::
     $ echo 12 56 | proj +proj=utm +zone=32
     687071.44       6210141.33
 
-Convert geodetic coordinate to UTM Zone 59 on the souther hemisphere::
+Convert geodetic coordinate to UTM Zone 59 on the southern hemisphere::
 
     $ echo 174 -44 | proj +proj=utm +zone=59 +south
     740526.32       5123750.87
diff --git a/docs/source/operations/transformations/xyzgridshift.rst b/docs/source/operations/transformations/xyzgridshift.rst
index 6a3a40f0..e76b3a63 100644
--- a/docs/source/operations/transformations/xyzgridshift.rst
+++ b/docs/source/operations/transformations/xyzgridshift.rst
@@ -38,7 +38,7 @@ method in the forward direction, and direct read in the reverse direction.
 Example
 -------------------------------------------------------------------------------
 
-NTF to RGF93 transformation using gr3df97a.tif grid
+NTF to RGF93 transformation using :file:`gr3df97a.tif` grid
 
 ::
 
@@ -83,7 +83,7 @@ Optional
 
     If output_crs is specified, the grid is referenced in the geographic CRS corresponding
     to the output geocentric CRS. This is for example the case for the French
-    gr3df97a.tif grid converting from NTF to RGF93, but referenced against RGF93.
+    :file:`gr3df97a.tif` grid converting from NTF to RGF93, but referenced against RGF93.
     Thus in the forward direction (NTF->RGF93), an iterative method is used to find
     the appropriate shift.