Merge pull request #2470 from patrickhlauke/patrickhlauke-patch1

[mediaqueries-4] Move 'pointer'/'hover' note, reword "can potentially" to "should strongly consider"

Author: frivoal

mediaqueries-4/Overview.bs

@@ -1752,7 +1752,14 @@ Note: the '@media/hover', '@media/any-hover', '@media/pointer', and '@media/any-
 	or the complete absence, of pointing devices,
 	and can not be used to detect the presence of non-pointing device input mechanisms such as keyboards.
 	Authors should take into account the potential presence of non-pointing device inputs,
-	regardless of which values are matched when querying these features. 
+	regardless of which values are matched when querying these features.
+
+	<div class="note">
+		While 'pointer' and 'hover' can be used to design the main style and interaction
+		mode of the page to suit the primary input mechanism (based on the characteristics, or complete absence,
+		of the primary pointing device), authors should strongly consider using 'any-pointer' and 'any-hover'
+		to take into account all possible types of pointing devices	that have been detected.
+	</div>
 
 <h3 id="pointer">
 Pointing Device Quality: the 'pointer' feature</h3>
@@ -1952,12 +1959,6 @@ Note: This feature is at risk.
 	</div>
 
 	<div class="note">
-	While 'pointer' and 'hover' can be used to design the main style and interaction
-	mode of the page to suit the primary input mechanism (based on the characteristics, or complete absence,
-	of the primary pointing device), 'any-pointer' and 'any-hover'
-	can be used to potentially take into account all possible types of pointing devices
-	that have been detected.
-
 	Designing a page that relies on hovering or accurate pointing
 	only because 'any-hover' or 'any-pointer' indicate that at least one of the available
 	input mechanisms has these capabilities	is likely to result in a poor experience.