[css-color-hdr] consistent "color space" w3c#6217

Author: svgeesus

css-color-hdr/Overview.bs

@@ -71,8 +71,8 @@ Introduction {#intro}
 
 	<em>This section is not normative.</em>
 
-	CSS Color 4 adds Wide Color Gamut (WCG) colorspaces to the Open Web Platform.
-	By design, these are all Standard Dynamic Range (SDR) colorspaces.
+	CSS Color 4 adds Wide Color Gamut (WCG) color spaces to the Open Web Platform.
+	By design, these are all Standard Dynamic Range (SDR) color spaces.
 	This specification explores what additions might be suitable
 	to also add High Dynamic Range (HDR).
 
@@ -97,19 +97,19 @@ Value Definitions {#values}
 	also accept the <a>CSS-wide keywords</a> as their property value.
 	For readability they have not been repeated explicitly.
 
-Predefined colorspaces for HDR: {#predefined-HDR}
+Predefined color spaces for HDR: {#predefined-HDR}
 =====================
 
 	In addition to the <a href="https://drafts.csswg.org/css-color-4/#predefined">SDR
-	colorspaces</a> defined by CSS Color 4, the following HDR colorspaces are defined
+	color spaces</a> defined by CSS Color 4, the following HDR color spaces are defined
 	for use in the color function [[css-color-4#color-function]].
 
-	Serialization of values in these new colorspaces is identical to the description in [[css-color-4#serializing-color-values]].
+	Serialization of values in these new color spaces is identical to the description in [[css-color-4#serializing-color-values]].
 
 <dfn export>rec2100-pq</dfn> {#valdef-color-rec2100-pq}
 ---------------------------
 
-	The ''rec2100-pq'' [[!Rec_BT.2100]] colorspace accepts three numeric parameters,
+	The ''rec2100-pq'' [[!Rec_BT.2100]] color space accepts three numeric parameters,
 	representing the red, green, and blue channels of the color,
 	with each having a valid range of [0, 1]
 	regardless of the actual bit depth (10 or 12 bits per component).
@@ -134,7 +134,7 @@ Predefined colorspaces for HDR: {#predefined-HDR}
 
 	ITU Reference 2100 is used for HDR 4k and 8k television.
 
-	In contrast to SDR colorspaces and some HDR colorspaces,
+	In contrast to SDR color spaces and some HDR color spaces,
 	the PQ values are <em>absolute</em> rather than relative.
 
 	Issue: add a diagram showing SDR and HDR dynamic ranges on a log scale
@@ -230,7 +230,7 @@ Predefined colorspaces for HDR: {#predefined-HDR}
 <dfn export>rec2100-hlg</dfn> {#valdef-color-rec2100-hlg}
 ---------------------------
 
-	The ''rec2100-hlg'' [[Rec_BT.2100]] colorspace accepts three numeric parameters,
+	The ''rec2100-hlg'' [[Rec_BT.2100]] color space accepts three numeric parameters,
 	representing the red, green, and blue channels of the color,
 	with each having a valid range of [0, 1]
 	regardless of the actual bit depth (10 or 12 bits per component).
@@ -323,7 +323,7 @@ Predefined colorspaces for HDR: {#predefined-HDR}
 <dfn export>Jzazbz</dfn> {#Jzazbz}
 -----------------
 
-	The ''Jzazbz'' colorspace [[!Safdar-PUCS]] accepts three numeric parameters,
+	The ''Jzazbz'' color space [[!Safdar-PUCS]] accepts three numeric parameters,
 	with J<sub>z</sub> representing the Lightness (similar to L in Lab)
 	while a<sub>z</sub> and b<sub>z</sub> represent the
 	redness-greenness and yellowness-blueness
@@ -399,7 +399,7 @@ Converting JzCzHz colors to Jzazbz  colors</h4>
 <dfn export>ICtCp</dfn> {#ICtCp}
 -----------------
 
-	The ''ICtCp'' colorspace
+	The ''ICtCp'' color space
 	is defined as Constant Intensity IC<sub>T</sub>C<sub>P</sub> signal format
 	in [[!Rec_BT.2100]] and accepts three numeric parameters,
 	with I representing the Intensity
@@ -466,7 +466,7 @@ which will give the same result
 provided out-of-gamut values (negative, or greater than 100%)
 are correctly handled
 and not clipped or gamut mapped until
-the final transfer to the device colorspace.
+the final transfer to the device color space.
 
 Relative HDR, using the HLG transfer function,
 must map SDR media white
@@ -663,7 +663,7 @@ For: @some-at-rule
 
 (A required descriptor can use `Initial: n/a</code>.) -->
 
-Issue: Do the PQ-based colorspaces require tone-mapping (OOTF) for display in different viewing environments?
+Issue: Do the PQ-based color spaces require tone-mapping (OOTF) for display in different viewing environments?
 
 <h2 class=no-num id=priv-sec>Privacy and Security Considerations</h2>