[mediaqueries-4] Spell check. Fixes w3c#5288.

Author: dbaron

mediaqueries-4/Overview.bs

@@ -961,7 +961,7 @@ Evaluating Media Queries {#evaluating}
 		In standard boolean logic, the only reasonable value is “false”,
 		but this means that ''not unknown(function)'' is true,
 		which can be confusing and unwanted.
-		Kleen's 3-valued logic ensures that unknown things will prevent a <a>media query</a> from matching,
+		Kleene's 3-valued logic ensures that unknown things will prevent a <a>media query</a> from matching,
 		unless their value is irrelevant to the final result.
 	</div>
 
@@ -1242,7 +1242,7 @@ Display Resolution: the 'resolution' feature</h3>
 		along each axis, and the would therefore be no difference between the vertical
 		and horizontal resolution.
 
-		Otherwise, if the UA choses to map a different number along each axis,
+		Otherwise, if the UA chooses to map a different number along each axis,
 		this would be to respond to physical pixels not being square either. How
 		the UA comes to this knowledge is out of scope, but having enough information
 		to take this decision, it can invert the mapping should the device be rotated 90 degrees.
@@ -1339,7 +1339,7 @@ Display Update Frequency: the 'update' feature</h3>
 	</pre>
 
 	The 'update' media feature is used to query the ability of the output device
-	to modify the apearance of content once it has been rendered.
+	to modify the appearance of content once it has been rendered.
 	It accepts the following values:
 
 	<dl dfn-type=value dfn-for="@media/update">
@@ -1806,7 +1806,7 @@ Pointing Device Quality: the 'pointer' feature</h3>
 	In addition, even if the primary pointing device has ''fine'' pointing accuracy,
 	there may be additional ''coarse'' pointing devices available to the user. Authors may
 	wish to query the 'any-pointer' media feature to take these other ''coarse'' potential
-	pointing devicess into account.
+	pointing devices into account.
 
 	<div class="example">
 		<pre>
@@ -2152,7 +2152,7 @@ device-aspect-ratio</h3>
 Changes</h2>
 
 <h3 id="changes-2017-9">
-Changes since the 5 Septemper 2017 Candidate Recommendation</h3>
+Changes since the 5 September 2017 Candidate Recommendation</h3>
 The following changes were made to this specification since the
 <a href="https://www.w3.org/TR/2017/CR-mediaqueries-4-20170905/">5 September 2017 Candidate Recommendation</a>:
 
@@ -2200,11 +2200,11 @@ The following changes were made to this specification since the
 Changes Since Media Queries Level 3</h3>
 
 The following changes were made to this specification since the
-<a href="https://www.w3.org/TR/css3-mediaqueries/">19 June 2012 Recomendation of Media Queries Level 3</a>:
+<a href="https://www.w3.org/TR/css3-mediaqueries/">19 June 2012 Recommendation of Media Queries Level 3</a>:
 
 <ul>
 	<li>
-		Large editorial rewrite and reorgization of the document.
+		Large editorial rewrite and reorganization of the document.
 
 	<li>
 		<a href="#mq-boolean-context">Boolean-context</a> <a>media features</a> are now additionally false
@@ -2291,9 +2291,9 @@ expose information about the environment in which the UA is running
 without any clear benefit to doing so.
 They are retained for compatibility reasons,
 but for the sake of privacy and security,
-UAs have been allowed to report inacurate information.
+UAs have been allowed to report inaccurate information.
 
-The <a href="http://www.w3.org/2001/tag/">TAG</a> has developed a <a href="https://www.w3.org/TR/security-privacy-questionnaire/">self-review questionaire</a>
+The <a href="http://www.w3.org/2001/tag/">TAG</a> has developed a <a href="https://www.w3.org/TR/security-privacy-questionnaire/">self-review questionnaire</a>
 to help editors and Working Groups evaluate the risks introduced by their specifications.
 Answers are provided below.
 
@@ -2325,7 +2325,7 @@ Answers are provided below.
 
 <dt>Does this specification allow an origin access to aspects of a user’s local computing environment?
 <dd>
-Yes, as described in the prose above this questionaire.
+Yes, as described in the prose above this questionnaire.
 
 <dt>Does this specification allow an origin access to other devices?
 <dd>No.