Merge pull request #857 from radiantearth/typos-and-api

Minor fixes

Author: matthewhanson

catalog-spec/catalog-spec.md

@@ -36,7 +36,7 @@ also a valid STAC Catalog.
 | description     | string        | **REQUIRED.** Detailed multi-line description to fully explain the catalog. [CommonMark 0.29](http://commonmark.org/) syntax MAY be used for rich text representation. |
 | links           | [[Link Object](#link-object)] | **REQUIRED.** A list of references to other documents.       |
 
-**stac_extensions**: A list of extensions the Catalog implements. This does NOT declare the extensions of children or Items. The list contains URLs to the JSON Schema files it can be validated against. For official [content extensions](../extensions/README.md#list-of-content-extensions), a "shortcut" can be used. This means you can specify the folder name of the extension, for example `pointcloud` for the Point Cloud extension. This does *not* apply for API extensions. If the versions of the extension and the catalog diverge, you can specify the URL of the JSON schema file.
+**stac_extensions**: A list of extensions the Catalog implements. This does NOT declare the extensions of children or Items. The list contains URLs to the JSON Schema files it can be validated against. For official [content extensions](../extensions/README.md#list-of-content-extensions), a "shortcut" can be used. This means you can specify the folder name of the extension, for example `single-file-stac` for the Point Cloud extension. If the versions of the extension and the catalog diverge, you can specify the URL of the JSON schema file.
 This list must only contain extensions that extend the Catalog itself, see the the 'Scope' column in the list of extensions.
 
 ### Link Object

collection-spec/collection-spec.md

@@ -29,7 +29,7 @@ STAC Collections are meant to be compatible with *OGC API - Features* Collection
 | summaries       | Map<string, \[*]\|[Stats Object](#stats-object)> | A map of property summaries, either a set of values or statistics such as a range. |
 | links           | \[[Link Object](#link-object)]                   | **REQUIRED.** A list of references to other documents.       |
 
-**stac_extensions**: A list of extensions the Collection implements. This does NOT declare the extensions of child Catalogs or Items. The list contains URLs to the JSON Schema files it can be validated against. For official [content extensions](../extensions/README.md#list-of-content-extensions), a "shortcut" can be used. This means you can specify the folder name of the extension, for example `version` for the Versioning Indicators extension. This does *not* apply for API extensions. If the versions of the extension and the collection diverge, you can specify the URL of the JSON schema file.
+**stac_extensions**: A list of extensions the Collection implements. This does NOT declare the extensions of child Catalogs or Items. The list contains URLs to the JSON Schema files it can be validated against. For official [content extensions](../extensions/README.md#list-of-content-extensions), a "shortcut" can be used. This means you can specify the folder name of the extension, for example `version` for the Versioning Indicators extension. If the versions of the extension and the collection diverge, you can specify the URL of the JSON schema file.
 This list must only contain extensions that extend the Collection itself, see the the 'Scope' column in the list of extensions. If an extension as the  extension has influence on multiple parts of the whole catalog structure, it must be listed in all affected parts (e.g. Collection and Item for the `datacube` extension). If a structure such as the summaries extension provide fields in their JSON structure, these extensions must not be listed here as they don't extend the Collection itself. For example, if a Collection includes the field `sat:platform` in the summaries, the Collection still does not list the `sat` extension in the `stac_extensions` field.
 
 **license**: Collection's license(s) as a SPDX [License identifier](https://spdx.org/licenses/). Alternatively, use `proprietary` (see below) if the license is not on the SPDX license list or `various` if multiple licenses apply. In all cases links to the license texts SHOULD be added, see the `license` link relation type. If no link to a license is included and the `license` field is set to `proprietary`, the collection is private, and consumers have not been granted any explicit right to use the data.
@@ -144,7 +144,7 @@ Implementors are free to add other derived statistical values to the object, for
 STAC Collections which don't link to any Item are called **standalone Collections**.
 To describe them with more fields than the Collection fields has to offer, it is allowed to re-use the metadata fields defined by content extensions for Items in the `summaries` field.
 This makes much sense for fields such as `platform` or `proj:epsg`, which are often the same for a whole collection, but doesn't make much sense for `eo:cloud_cover`, which usually varies heavily across a Collection.
-The data provider is free to decide, which fields are reasoable to be used.
+The data provider is free to decide, which fields are reasonable to be used.
 
 ## Extensions
 

item-spec/README.md

@@ -3,9 +3,8 @@
 The core of a SpatioTemporal Asset Catalog (STAC) is a set of JSON fields defined by the 
 [STAC Item spec](item-spec.md). These fields define an Item - the atomic units that contain 
 metadata for search as plus links to the actual assets that they represent. Their main function 
-is as the leaf nodes of a [Catalog](../catalog-spec/README.md), and are also returned from the search
-endpoints of a `/search` endpoint. See the [overview](../overview.md) document for more information on how all the
-pieces fit together.
+is as the leaf nodes of a [Catalog](../catalog-spec/README.md).
+See the [overview](../overview.md) document for more information on how all the pieces fit together.
 
 ## In this directory
 

item-spec/common-metadata.md

@@ -57,7 +57,7 @@ There are more date and time related fields available in the [Timestamps extensi
 ### Date and Time Range
 
 While a STAC item can have a nominal datetime describing the capture, these properties allow an item to have a range
-of capture datetimes. An example of this is the [MODIS 16 day vegetation index product.](https://lpdaac.usgs.gov/products/mod13q1v006/).
+of capture dates and times. An example of this is the [MODIS 16 day vegetation index product.](https://lpdaac.usgs.gov/products/mod13q1v006/).
 The datetime property in a STAC item and these fields are not mutually exclusive.
 
 **Important:** Using one of the fields REQUIRES to include the other field as well to enable a user to search STAC records by the provided times. So if you use `start_datetime` you need to add `end_datetime` and vice-versa. Both fields are also REQUIRED if the `datetime` field is set to `null`.

item-spec/item-spec.md

@@ -229,7 +229,7 @@ extensions can add further property fields as well. Any property that can be spe
 a specific asset. This can be used to override a property defined in the Item, or to specify fields for which there is no 
 single value for all assets.
 
-**It is important to note that the STAC API does not faciliate searching across Asset properties in this way, and this 
+**It is important to note that the STAC API does not facilitate searching across Asset properties in this way, and this 
 should be used sparingly.** It is primarily used to define properties at the Asset level that may be used during use of 
 the data instead of for searching.