Update README.md

README.md

@@ -25,13 +25,13 @@ Responding to requirements phrased in the project the range type in coverages ha
 
 Of particular interest are the components:
 
-- field name: the record component name under which range values are known and can be extracted, such as `$c.red` in WCPS; this must follow the usual syntax conventions of program variable names
-- definition: the technical data type (int, float, etc.), expressed through OGC URIs as OGC requires
-- description: a human-readable text explaining the meaning
-- nil values, as pairs of reason (some text) and a value (taken from the data type definition, see above)
-- unit of measure: OGC has no guidance on this; earlier UCUM was used, but it appears inconvenient. In Fairicube QUDT seems preferred - more to come once agreed, stay tuned.
+- **field name**: the record component name under which range values are known and can be extracted, such as `$c.red` in WCPS; this must follow the usual syntax conventions of program variable names
+- **definition**: the technical data type (int, float, etc.), expressed through OGC URIs as OGC requires
+- **description**: a human-readable text explaining the meaning
+- **nil values**, as pairs of reason (some text) and a value (taken from the data type definition, see above)
+- **unit of measure**: OGC has no guidance on this; earlier UCUM was used, but it appears inconvenient. In Fairicube QUDT seems preferred - more to come once agreed, stay tuned.
 
-Importantly, datacubes (as data in general) fall into one of several different categories, as statistics teaches: numerical, ordinal, and categorial. SWE Common (upon which the coverage range type relies) supports that halfways, therefore an activity is planned to reflect these categories in a statistically correct way in the OGC/ISO coverage standards.
+Importantly, datacubes (as data in general) fall into one of several different categories, as statistics teaches: *numerical*, *ordinal*, and *categorial*. SWE Common (upon which the coverage range type relies) supports that halfways, therefore an activity is planned to reflect these categories in a statistically correct way in the OGC/ISO coverage standards.
 
 In XML, the complete range type structure is as in the following example: