Fix typos (#1701)

docs/source/admin-api.rst

@@ -18,7 +18,7 @@ Access control
 --------------
 
 It should be made clear that authentication and authorization is beyond the responsibility of pygeoapi.  This means that
-if a pygeoapi user enables the Admin API, they must provide access control explicity via another service.
+if a pygeoapi user enables the Admin API, they must provide access control explicitly via another service.
 
 pygeoapi hot reloading in gunicorn
 ----------------------------------

docs/source/configuration.rst

@@ -83,8 +83,8 @@ The ``logging`` section provides directives for logging messages which are usefu
   logging:
       level: ERROR  # the logging level (see https://docs.python.org/3/library/logging.html#logging-levels)
       logfile: /path/to/pygeoapi.log  # the full file path to the logfile
-      logformat: # example for miliseconds:'[%(asctime)s.%(msecs)03d] {%(pathname)s:%(lineno)d} %(levelname)s - %(message)s'
-      dateformat: # example for miliseconds:'%Y-%m-%dT%H:%M:%S'
+      logformat: # example for milliseconds:'[%(asctime)s.%(msecs)03d] {%(pathname)s:%(lineno)d} %(levelname)s - %(message)s'
+      dateformat: # example for milliseconds:'%Y-%m-%dT%H:%M:%S'
 
 .. note::
    If ``level`` is defined and ``logfile`` is undefined, logging messages are output to the server's ``stdout``.

docs/source/data-publishing/ogcapi-features.rst

@@ -361,7 +361,7 @@ Mandatory properties
         - example_group_id
 
 On large tables it could be useful to disallow a query on the complete dataset. For this reason it is possible to 
-configure mandatory properties. When this is activated, the provoder throws an exception when the parameter
+configure mandatory properties. When this is activated, the provider throws an exception when the parameter
 is not in the query uri.
 
 Extra properties
@@ -408,7 +408,7 @@ Custom SQL Manipulator Plugin
 The provider supports a SQL-Manipulator-Plugin class. With this, the SQL statement could be manipulated. This is
 useful e.g. for authorization at row level or manipulation of the explain plan with hints. 
 
-An example an more informations about that feature you can find in the test class in tests/test_oracle_provider.py.
+An example an more information about that feature you can find in the test class in tests/test_oracle_provider.py.
 
 .. _PostgreSQL:
 
@@ -503,7 +503,7 @@ SQLiteGPKG
 ^^^^^^^^^^
 
 .. note::
-   Requries Spatialite installation
+   Requires Spatialite installation
 
 SQLite file:
 

docs/source/data-publishing/stac.rst

@@ -49,7 +49,7 @@ Connection examples
 pygeometa metadata control files
 --------------------------------
 
-pygeoapi's STAC filesystem fuctionality supports `pygeometa`_ MCF files residing
+pygeoapi's STAC filesystem functionality supports `pygeometa`_ MCF files residing
 in the same directory as data files.  If an MCF file is found, it will be used
 as part of generating the STAC item metadata (e.g. a file named ``birds.csv``
 having an associated ``birds.yml`` file).  If no MCF file is found, then

docs/source/language.rst

@@ -176,7 +176,7 @@ Translator guide
 Hardcoded strings in pygeoapi templates are translated using the Babel translation system.
 
 By default, pygeoapi stores translation files in the `locale` directory at the root of the
-source code repository. This value can be overriden in the pygeoapi configuration with
+source code repository. This value can be overridden in the pygeoapi configuration with
 the `server.locale_dir` directive.
 
 Translators can follow these steps to prepare their environment for translations.

docs/source/running.rst

@@ -159,7 +159,7 @@ main Django application urls:
 
 
 This integration can be seen in the provided example Django project. Refer to the `Django example in the pygeoapi-examples repository`_
-for the integration of pygeoapi with an already exising Django application.
+for the integration of pygeoapi with an already existing Django application.
 
 
 .. note::

docs/source/transactions.rst

@@ -14,6 +14,6 @@ Access control
 ^^^^^^^^^^^^^^
 
 It should be made clear that authentication and authorization is beyond the responsibility of pygeoapi.  This means that
-if a pygeoapi user enables transactions, they must provide access control explicity via another service.
+if a pygeoapi user enables transactions, they must provide access control explicitly via another service.
 
 .. _`OGC API - Features - Part 4: Create, Replace, Update and Delete`: https://docs.ogc.org/DRAFTS/20-002.html