Merge pull request #301552 from beharris/bh-mpc-edits

Bh mpc edits

Author: prmerger-automator[bot]

articles/planetary-computer/stac-overview.md

@@ -96,6 +96,19 @@ Collections in GeoCatalog are defined in JSON format and include the following f
 | Keywords | List of keywords describing the collection. |
 | STAC Version | Required - STAC version used by the collection. |
 
+### Item assets
+
+The `item_assets` field, at the collection level, provides a way to determine what assets (data files) are available in any child Item. The listed assets in this field don't imply that all assets are available for all Items (it should be the union of the available assets, not the intersection of the available assets). This field is enabled in a GeoCatalog via the [item_assets extension](https://github.com/stac-extensions/item-assets) of the STAC specification. The items assets extension is required if you want to visualize Items in the GeoCatalog Explorer.
+
+The `item_assets` field is itself an object, with at least two of the following fields:
+
+| Field | Type | Description |
+| ------------- | ------------- | ----------- |
+| title | string | The displayed title for clients and users. |
+| description | string | A description of the Asset providing more details, such as how it was processed or created. |
+| type | string | [Media type](https://github.com/radiantearth/stac-spec/tree/v1.0.0-rc.1/catalog-spec/catalog-spec.md#media-types) of the asset. |
+| roles | list of strings | The semantic roles of the asset, similar to the use of rel in links. |
+
 ### Collection JSON examples
 
 The following example shows a minimal collection JSON. For more fields, refer to the [STAC collection specification](https://github.com/radiantearth/stac-spec/blob/master/collection-spec/collection-spec.md).
@@ -143,19 +156,6 @@ In order to visualize collections in the GeoCatalog Explorer, there are several
 - [Tile settings](./tile-settings.md)
 - [Queryable fields](./queryables-for-explorer-custom-search-filter.md)
 
-### Item assets
-
-The `item_assets` field, at the collection level, provides a way to determine what assets (datafiles) are available in any child Item. Otherwise a random Item would need to be examined to determine assets available, but that random Item might not be representative of the rest. Assets included at the collection level doesn't imply that all assets are available for all Items (it should be the union of the available assets, not the intersection of the available assets). This field is enabled in a GeoCatalog via the [item_assets extension](https://github.com/stac-extensions/item-assets) of the STAC specification. The items assets extension is required if you want to visualize Items in the GeoCatalog Explorer.
-
-The `item_assets` field is itself an object, with at least two of the following fields:
-
-| Field | Type | Description |
-| ------------- | ------------- | ----------- |
-| title | string | The displayed title for clients and users. |
-| description | string | A description of the Asset providing more details, such as how it was processed or created. |
-| type | string | [Media type](https://github.com/radiantearth/stac-spec/tree/v1.0.0-rc.1/catalog-spec/catalog-spec.md#media-types) of the asset. |
-| roles | list of strings | The semantic roles of the asset, similar to the use of rel in links. |
-
 ## STAC items
 
 ### Introduction to STAC items