diff --git a/extensions/stac-collection-spec.md b/extensions/stac-collection-spec.md
index be252ed45..99f67f5d6 100644
--- a/extensions/stac-collection-spec.md
+++ b/extensions/stac-collection-spec.md
@@ -7,7 +7,7 @@ A group of STAC `Item` objects from a single source can share a lot of common me
 | element             | type info                 | name                    | description                                                                                 | 
 |----------------------|---------------------------|-------------------------|---------------------------------------------------------------------------------------------| 
 | c:id | string | Collection ID | Machine readable ID for the collection
-| c:name | string | Collection Name (optional) | A name given to the Collection, used for display
+| c:name | string (optional) | Collection Name | A name given to the Collection, used for display
 | c:description | string (optional) | Collection Description | A human readable description of the collection
 
 A `Collection` does not have many specific fields, as it may contain any fields that are in the core spec as well as any other extension. This provides maximum flexibility to data providers, as some the set of common metadata fields can vary between different types of data. For instance, Landsat and Sentinel data always has a eo:off_nadir value of 0, because those satellites are always pointed downward (i.e., nadir), while satellite that can be pointed will have varying eo:off_nadir values.
@@ -61,6 +61,7 @@ The fields from the `Collection` record can be merged with an `Item` record to g
 {
     "id": "SCENE_001",
     "properties": {
+        "c:id": "my_collection",
         "datetime": "2017-01-01T00:00:00Z",
         "geometry": {...}
     },
@@ -188,4 +189,4 @@ This is an example `Collection` for Landsat-8 imagery and uses the [EO extension
         "fwhm": 1.0
       }
     }
-```
\ No newline at end of file
+```