Fix typos (#1701)

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