touch up

CHANGELOG.md

@@ -10,7 +10,7 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 - [Basics](item-spec/common-metadata.md#basics) added to Common Metadata definitions with new `description` field for
 Item properties.
 - Clarification text on HTTP verbs in STAC API
-- [Overhead Sensor Extension](extensions/view/README.md)
+- [View Geometry Extension](extensions/view/README.md)
 
 ### Changed
 - Item `title` definition moved from core Item fields to [Common Metadata Basics](item-spec/common-metadata.md#basics) 
@@ -174,7 +174,7 @@ fields. No change is required for STAC Items.
 - `page` parameter for STAC API
 - Optional `collection` property field in Items (previously part of the Commons extension)
 - It is now required to link to `/stac/search/` from `/stac/`
-- Added new fields to SAR extension: `sat:incidence_angle`, `sat:relative_orbit`, `sat:observation_direction`
+- Added new fields to SAR extension: `sar:incidence_angle`, `sar:relative_orbit`, `sar:observation_direction`
 - Added new filter parameters `ids` and `collections` to `/stac/search/`
 
 ### Removed

extensions/eo/json-schema/schema.json

@@ -59,7 +59,7 @@
               "type": "number",
               "minimum": 0,
               "maximum": 100
-            },
+            }
           }
         },
         "assets": {

extensions/sat/README.md

@@ -13,8 +13,8 @@ The Satellite extension requires the [Instrument Fields](../../item-spec/common-
 
 | Field Name       | Type                     | Description |
 | ---------------- | ------------------------ | ----------- |
-| sat:orbit_state        | string  | The state of the orbit. Either `ascending` or `descending` for polar orbiting satellites, or `geostationary` for geosynchronous satellites |
-| sat:relative_orbit        | integer       | The relative orbit number at the time of acquisition. |
+| sat:orbit_state        | string        | The state of the orbit. Either `ascending` or `descending` for polar orbiting satellites, or `geostationary` for geosynchronous satellites |
+| sat:relative_orbit     | integer       | The relative orbit number at the time of acquisition. |
 
 **sat:orbit_state** indicates the type and current state of orbit. Satellites are either geosynchronous in which case they have one state: `geostationary`, or they are sun synchronous (i.e., polar orbiting satellites) in which case they are either `ascending` or `descending`. For sun synchronous satellites it is daytime during one of these states, and nighttime during the other.
 

item-spec/item-spec.md

@@ -88,7 +88,7 @@ throughout all domains. These optional fields are included for STAC Items by def
 such as EO, SAR and point clouds.
 * [Custom Extensions](../extensions/README.md#extending-stac) - It is generally allowed to add custom 
 fields but it is recommended to add multiple attributes for related values instead of a nested object, 
-e.g., two fields `eo:cloud_cover` and `view:sun_azimuth` instead of a field `eo` with an object 
+e.g., two fields `eo:cloud_cover` and `eo:gsd` instead of a field `eo` with an object 
 value containing the two fields. The convention (as used within Extensions) is for related attributes 
 to use a common prefix on the attribute names to group them, e.g. `eo`. A nested data structure should 
 only be used when the data itself is nested, as with `eo:bands`.