fix a few typos (again)

5 files changed, 17 insertions, 17 deletions

diff --git a/docs/source/usage/apps/cct.rst b/docs/source/usage/apps/cct.rst
index e6f94526..014e7732 100644
--- a/docs/source/usage/apps/cct.rst
+++ b/docs/source/usage/apps/cct.rst
@@ -15,7 +15,7 @@ program, performs transformation coordinate systems on a set of input points.
 The coordinate system transformation can include  translation  between
 projected  and geographic coordinates as well as the application of datum shifts.
 
-cct is an acromyn meaning *Coordinate Conversion and Transformation*.
+cct is an acronym meaning *Coordinate Conversion and Transformation*.
 
 The acronym refers to definitions given in the OGC 08-015r2/ISO-19111
 standard "Geographical Information -- Spatial Referencing by Coordinates",
@@ -33,7 +33,7 @@ professor of Geodesy at the University of Copenhagen, mentor and advisor
 for a generation of Danish geodesists, colleague and collaborator for
 two generations of global geodesists, Secretary General for the
 International Association of Geodesy, IAG (1995--2007), fellow of the
-Amercan Geophysical Union (1991), recipient of the IAG Levallois Medal
+American Geophysical Union (1991), recipient of the IAG Levallois Medal
 (2007), the European Geosciences Union Vening Meinesz Medal (2008), and
 of numerous other honours.
 
@@ -43,7 +43,7 @@ the development of geodesy -- both through his scientific contributions,
 comprising more than 250 publications, and by his mentoring and teaching
 of the next generations of geodesists.
 
-As Christian was an avid Fortran programmer, and a keen Unix connoiseur,
+As Christian was an avid Fortran programmer, and a keen Unix connoisseur,
 he would have enjoyed to know that his initials would be used to name a
 modest Unix style transformation filter, hinting at the tireless aspect
 of his personality, which was certainly one of the reasons he accomplished
diff --git a/docs/source/usage/environmentvars.rst b/docs/source/usage/environmentvars.rst
index e1d63543..24954158 100644
--- a/docs/source/usage/environmentvars.rst
+++ b/docs/source/usage/environmentvars.rst
@@ -4,7 +4,7 @@
 Environment variables
 ================================================================================
 
-PROJ can be crontrolled by setting environment variables. Most users will
+PROJ can be controlled by setting environment variables. Most users will
 have a use for the :envvar:`PROJ_LIB`.
 
 On UNIX systems environment variables can be set for a shell-session with::
diff --git a/docs/source/usage/projections.rst b/docs/source/usage/projections.rst
index 871bc161..f5f46f46 100644
--- a/docs/source/usage/projections.rst
+++ b/docs/source/usage/projections.rst
@@ -93,7 +93,7 @@ Prime Meridian
 
 A prime meridian may be declared indicating the offset between the prime
 meridian of the declared coordinate system and that of greenwich.  A prime
-meridian is clared using the "pm" parameter, and may be assigned a symbolic
+meridian is declared using the "pm" parameter, and may be assigned a symbolic
 name, or the longitude of the alternative prime meridian relative to greenwich.
 
 Currently prime meridian declarations are only utilized by the
diff --git a/docs/source/usage/quickstart.rst b/docs/source/usage/quickstart.rst
index 077e970c..89ac2172 100644
--- a/docs/source/usage/quickstart.rst
+++ b/docs/source/usage/quickstart.rst
@@ -33,7 +33,7 @@ utility ``proj`` we can convert the geodetic coordinates to projected space:
     $ proj +proj=merc +lat_ts=56.5 +ellps=GRS80
 
 If called as above ``proj`` will be in interactive mode, letting you type the
-input data manually and getting a responce presented on screen. ``proj``
+input data manually and getting a response presented on screen. ``proj``
 works as any UNIX filter though, which means that you can also pipe data to
 the utility, for instance by using the ``echo`` command:
 
@@ -44,7 +44,7 @@ the utility, for instance by using the ``echo`` command:
 
 
 PROJ also comes bundled with the ``cs2cs`` utility which is used to transform
-from onecoordinate reference system to another. Say we want to convert
+from one coordinate reference system to another. Say we want to convert
 the above Mercator coordinates to UTM, we can do that with ``cs2cs``:
 
 ::
@@ -52,10 +52,10 @@ the above Mercator coordinates to UTM, we can do that with ``cs2cs``:
     $ echo 3399483.80 752085.60 | cs2cs +proj=merc +lat_ts=56.5 +ellps=GRS80 +to +proj=utm +zone=32
     6103992.36      1924052.47 0.00
 
-Notice the ``+to`` parameter that seperates the source and destination
+Notice the ``+to`` parameter that separates the source and destination
 projection definitions.
 
-If you happen to know the EPSG identifiers for the two cordinates reference
+If you happen to know the EPSG identifiers for the two coordinates reference
 systems you are transforming between you can use those with ``cs2cs``:
 
 ::
diff --git a/docs/source/usage/transformation.rst b/docs/source/usage/transformation.rst
index fd1f2f94..bd32bcd9 100644
--- a/docs/source/usage/transformation.rst
+++ b/docs/source/usage/transformation.rst
@@ -6,11 +6,11 @@ Geodetic transformation
 
 PROJ can do everything from the most simple projection to very complex
 transformations across many reference frames. While originally developed as a
-tool for cartographic projections, PROJ has over time evolved into a powerfull
+tool for cartographic projections, PROJ has over time evolved into a powerful
 generic coordinate transformation engine that makes it possible to do both
 large scale cartographic projections as well as coordinate transformation at a
 geodetic high precision level. This chapter delves into the details of how
-geodetec transformations of varying complexity can be performed.
+geodetic transformations of varying complexity can be performed.
 
 In PROJ, two frameworks for geodetic transformations exists, the *cs2cs*
 framework and the *transformation pipelines* framework. The first is the original,
@@ -69,7 +69,7 @@ solutions for a wide spectrum of geodetic tasks.
 
 As a first example, let us take a look at the iconic
 *geodetic → Cartesian → Helmert → geodetic* case (steps 2 to 4 in the example in
-the itroduction). In PROJ it can be implemented as
+the introduction). In PROJ it can be implemented as
 
 ::
 
@@ -161,11 +161,11 @@ specified in the input proj-string. The most common is ``+towgs84``, which is us
 define a 3- or 7-parameter Helmert shift from the input reference frame to WGS84.
 Exactly which realization of WGS84 is not specified, hence a fair amount of
 uncertainty is introduced in this step of the transformation. With the +nadgrids
-parameter a non-lineaer planar correction derived from interpolation in a
+parameter a non-linear planar correction derived from interpolation in a
 correction grid can be applied. Originally this was implemented as a means to
-transform coordinates between the american datums NAD27 and NAD83, but corrections
-can be applied for any datum for which a correction grid exists. The inverse
-transform for the horizontal grid shift is "dumb", in the sense that the
+transform coordinates between the North American datums NAD27 and NAD83, but
+corrections can be applied for any datum for which a correction grid exists. The
+inverse transform for the horizontal grid shift is "dumb", in the sense that the
 correction grid is applied verbatim without taking into account that the inverse
 operation is non-linear. Similar to the horizontal grid correction, ``+geoidgrids``
 can be used to perform grid corrections in the vertical component.
@@ -203,7 +203,7 @@ using an approximated 7 parameter transformation.
 Grid Based Datum Adjustments
 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 
-In many places (notably North America and Austrialia) national geodetic
+In many places (notably North America and Australia) national geodetic
 organizations provide grid shift files for converting between different datums,
 such as NAD27 to NAD83.  These grid shift files include a shift to be applied
 at each grid location. Actually grid shifts are normally computed based on an