[mediaqueries] Make resolution properly refer to range context, not just min/max prefix.

Author: tabatkins

mediaqueries/Overview.html

@@ -1337,7 +1337,7 @@ <h3 class="heading settled heading" data-level=5.1 id=resolution><span class=sec
 <p>	When querying devices with non-square pixels,
 	in <a class=property data-link-type=propdesc title=min-resolution>min-resolution</a> queries the least-dense dimension must be compared to the specified value
 	and in <a class=property data-link-type=propdesc title=max-resolution>max-resolution</a> queries the most-dense dimensions must be compared instead.
-	A <a class=property data-link-type=propdesc href=#descdef-resolution title=resolution>resolution</a> (without a "min-" or "max-" prefix) query never matches a device with non-square pixels.
+	A <a class=property data-link-type=propdesc href=#descdef-resolution title=resolution>resolution</a> query that’s not evaluated in a <a data-link-type=dfn href=#range-context title="range context">range context</a> never matches a device with non-square pixels.
 
 <p>	For printers, this corresponds to the screening resolution
 	(the resolution for printing dots of arbitrary color).

mediaqueries/Overview.src.html

@@ -943,7 +943,7 @@ <h3 id="resolution">
 	When querying devices with non-square pixels,
 	in 'min-resolution' queries the least-dense dimension must be compared to the specified value
 	and in 'max-resolution' queries the most-dense dimensions must be compared instead.
-	A 'resolution' (without a "min-" or "max-" prefix) query never matches a device with non-square pixels.
+	A 'resolution' query that's not evaluated in a <a>range context</a> never matches a device with non-square pixels.
 
 	For printers, this corresponds to the screening resolution
 	(the resolution for printing dots of arbitrary color).