diff --git a/css-images-3/Overview.bs b/css-images-3/Overview.bs
index d1d93fffb65..3a0ce566ff0 100644
--- a/css-images-3/Overview.bs
+++ b/css-images-3/Overview.bs
@@ -216,7 +216,7 @@ Image References: the ''url()'' notation {#url-notation}
 ### Image Metadata ### {#url-metadata}
 
 Images can contain metadata
-such as resolution and orientation
+such as color space, resolution and orientation
 which specifies how to render the image.
 Some image formats are flexible in where this metadata can be placed in the file;
 however, if the metadata occurs <em>after</em> the actual image data,
@@ -226,21 +226,19 @@ and display it as the image's data streams in.
 To reduce the impact of this issue:
 
 * If the choice exists for a given image format, 
-	authors <em>must</em> produce their image files
-	so that such metadata occurs before the image data in the image file.
+	authors <em>must</em> produce their images
+	so that such metadata occurs before the image data in the image.
 	(Note: This is the default for most images already.)
 * User agents <em>should</em> ignore any layout-impacting metadata (such as orientation or resolution)
-	that occurs after the image data begins in the file.
-	(Note: This rule does not impact metadata that does not affect layout,
-	such as color space information.)
+	that occurs after the image data begins.
 
-	If a user agent cannot ignore the metadata based its location in the file
+	If a user agent cannot ignore the metadata based its location in the image
 	(for example, if the decoder being used
-	does not report where in the file the metadata was located),
+	does not report where in the image the metadata was located),
 	it <em>must</em> use the metadata in all cases.
 	(In particular, it is not valid
 	to use the metadata only when the image is "small"
-	and the entire file is downloaded quickly,
+	and the entire image is downloaded quickly,
 	but to ignore it if the image is large
 	and the metadata isn't downloaded until well after the image starts being displayed.)