update spec compliance

docs/OGC-API-Features-CRS.md

@@ -6,7 +6,7 @@
 
 | requirement | applicable | description |
 | --- | --- | --- |
-| /req/crs/crs-uri | :x: | {Authoritie}:{Code} is used in the request and a URN is used in the feature response. No URI is used. |
+| /req/crs/crs-uri | :x: | {Authoritie}:{Code} is used in the request and a URN is used in the feature response. URI is used in the `/crss` responses. |
 | /req/crs/fc-md-crs-list | :x: | We don't have a `collection` object in this API |
 | /req/crs/fc-md-storageCrs | :x: | No spatial feature collection is stored on the server |
 | /req/crs/fc-md-storageCrs-valid-value | :x: | No storageCrs is advertised |
@@ -20,8 +20,8 @@
 | /req/crs/fc-crs-default-value | :x: | No crs on a featues or feature resource is supported |
 | /req/crs/fc-crs-action | :x: | No crs is specified |
 | /req/crs/geojson | :grey_exclamation: | We are subjected to this rfc7946 |
-| /req/crs/ogc-crs-header | :x: | We don't use the CRS query parameter because we need 2 CRS for our API. Using a named one like source-crs and target-crs makes it clear what the purpose is |
-| /req/crs/ogc-crs-header-value | :x: | No `Content-Crs` header is return in the response |
+| /req/crs/ogc-crs-header | :heavy_check_mark: | We use the `Content-Crs` header in our response |
+| /req/crs/ogc-crs-header-value | :x: | The `Content-Crs` header returns a {AUTH}:{CODE} value for the CRS |
 
 ## Recommendations