Changed resolution to refinement level where applicable

- In 4-terms, 9-custom-depths and 16-JSON zone-list

core/requirements/requirements_class_data-custom-depths.adoc

@@ -16,7 +16,7 @@ requirement:: /req/data-custom-depths/zone-depth-parameter
 [%metadata]
 identifier:: /req/data-custom-depths/zone-depth-parameter
 
-description:: Parameter to specify the DGGS resolution levels beyond the specified DGGS zone's hierarchy level to include in the response, when retrieving data for that zone
+description:: Parameter to specify the DGGS refinement levels beyond the specified DGGS zone's refinement level to include in the response, when retrieving data for that zone
 
 part:: The Implementation SHALL support a `zone-depth` parameter for the HTTP GET operation on a resource path ending with `.../dggs/{dggrsId}/zones/{zoneId}/data`.
 
@@ -36,7 +36,7 @@ part:: For each zone depth to be included in the response, the interpretation of
 part:: The association of zones of deeper hierarchy levels with the requested zone SHALL be based on the DGGS reference system,
 which takes into consideration both the grid definition as well as the indexing system in use for the DGGS resource.
 
-part:: If a `zone-depth` is specified, the operation SHALL return the data at the resolution(s) / scale(s) specified.
+part:: If a `zone-depth` is specified, the operation SHALL return the data at the refinement level(s) specified.
 ====
 
 NOTE: A use case for a `zone-depth` of 0 would be to query the single set of values for a specific DGGS zone.

core/requirements/requirements_class_zone_list_json.adoc

@@ -57,7 +57,7 @@ part:: The `links` property SHOULD include an `[ogc-rel:geodata]` link for zone
 ====
 [%metadata]
 identifier:: /rec/zone-json/zone-order
-part:: For responses where zones of multiple hierarchy levels are returned when `compact-zones` is true, the zones SHOULD be listed with the coarser resolution level first (larger zones).
+part:: For responses where zones of multiple hierarchy levels are returned when `compact-zones` is true, the zones SHOULD be listed with coarser refinement levels first (larger zones).
 ====
 
 [recommendation]

core/sections/clause_4_terms_and_definitions.adoc

@@ -79,14 +79,14 @@ region of space-time enclosing a celestial body
 [[term-parent-zone]]
 === parent zone
 
-<<term-zone,zone>> in a lower <<term-refinement-level,refinement level>> of a <<term-dgg,discrete global grid>> with immediate descendants
+<<term-zone,zone>> in a coarser <<term-refinement-level,refinement level>> of a <<term-dgg,discrete global grid>> with immediate descendants
 
 [.source]
 <<OGC20-040r3>>
 
 NOTE: adapted from _parent cell_ in OGC Abstract Specification Topic 21
 
-NOTE: Adapted to say _lower_ rather than _higher_, where _lower_ refers to a zone covering a larger area of space-time which would normally correspond to lower resolution data.
+NOTE: Adapted to say _coarser_ rather than _higher_, where _coarser_ refers to a zone covering a larger area of space-time.
 
 [[term-refinement-level]]
 === refinement level