Reword the note about pointer/hover vs any-*

Change the emphasis of the note, away from making the `any-*` features
sound like a nice-to-have, and more towards aknowledging that these can
be useful in making a page/app adapt better/preemptively to all
available input methods.

Author: patrickhlauke

mediaqueries/Overview.bs

@@ -1747,17 +1747,17 @@ All Available Interaction Capabilities: the 'any-pointer' and 'any-hover' featur
 	or there are no pointing devices at all.
 
 	<div class="note">
-	These two media features are best suited to provide refinements over 'hover' and 'pointer',
-	and it is rarely appropriate to use them
-	without having first designed the main style and interaction mode of the page
-	to suit the primary input mechanism.
-	Once that has been taken into account, 'any-hover' and 'any-pointer' can be used
-	to see if some extra conveniences or non essential controls
-	can be offered to users who have additional ways to interact.
+	While 'pointer' and 'hover' can be used to design the main style and interaction
+	mode of the page to suit the primary input mechanism, 'any-pointer' and 'any-hover'
+	can be used to potentially take into account all possible types of pointers
+	that have been detected.
 
 	Designing a page that relies on hovering or accurate pointing
-	only because 'any-hover' or 'any-pointer' indicate that an input mechanism with these capabilities is available,
-	is likely to result in a poor experience.
+	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.
+	However, authors may use this information to inform their decision about the style and
+	functionality they wish to provide based on additional input mechanisms that
+	are available to the user.
 	</div>
 
 	<div class="example">