Merge pull request #108296 from hyoshioka0128/patch-647

Typo "PostgresSQL"→"PostgreSQL"

Author: Court72

articles/orbital/organize-stac-data.md

@@ -88,7 +88,7 @@ The following sections describe the four stages in the architecture.
 
 - STAC API is based on open source STAC FastAPI. 
 - STAC API layer is implemented on Azure Kubernetes Service and the APIs are exposed using [API Management Service](https://azure.microsoft.com/products/api-management/).
-- STAC APIs are used to discover the geospatial data in your Catalog. These APIs are based on STAC specifications and understand the STAC metadata defined and indexed in the STAC Catalog database (PostgresSQL server).
+- STAC APIs are used to discover the geospatial data in your Catalog. These APIs are based on STAC specifications and understand the STAC metadata defined and indexed in the STAC Catalog database (PostgreSQL server).
 - Based on the search criteria, you can quickly locate your data from a large dataset.
   - Querying the STAC Collection, Items & Assets:
     - A query is submitted by a user to look up one or more STAC Collection, Items & Assets through the STAC FastAPI.
@@ -201,4 +201,4 @@ If you want to start building this, we have put together a [sample solution](htt
 |STAC Item|The core atomic unit, representing a single spatiotemporal asset as a GeoJSON feature plus metadata like datetime and reference links.|
 |STAC Catalog|A simple, flexible JSON that provides a structure and organized the metadata like STAC items, collections and other catalogs.|
 |STAC Collection|Provides additional information such as the extents, license, keywords, providers, and so forth, that describe STAC Items within the Collection.|
-|STAC API|Provides a RESTful endpoint that enables search of STAC Items, specified in OpenAPI.|
+|STAC API|Provides a RESTful endpoint that enables search of STAC Items, specified in OpenAPI.|