[css-nav-1] Fix the spelling mistakes

Author: Jihye Hong

css-nav-1/Overview.bs

@@ -88,7 +88,7 @@ the specification remains the full document.
 
 <input type=checkbox id=api-check> <label for=api-check>Hide JavaScript APIs, including events</label><br>
 <input type=checkbox id=cssapi-check> <label for=cssapi-check>Hide CSS properties that enable selecting behavior variants, and related information</label><br>
-<input type=checkbox id=verbose-check> <label for=verbose-check>Hide informative sections that explain and summarise normative sections without adding more information</label><br>
+<input type=checkbox id=verbose-check> <label for=verbose-check>Hide informative sections that explain and summarize normative sections without adding more information</label><br>
 
 <h2 id="intro" class=non-normative>
 Introduction</h2>
@@ -209,7 +209,7 @@ until it has either moved focus,
 scrolled,
 or reached the root.
 
-Note: As a consequnce of this processing model,
+Note: As a consequence of this processing model,
 the elements that are reachable by sequential navigation
 and by spatial navigation are almost the same:
 elements that are currently outside of the viewport of a scrollable element
@@ -394,7 +394,7 @@ JavaScript API</h2>
 <h3 id=high-level-api>
 Triggering Navigation Programmatically</h3>
 
-The {{Window/navigate()}} method enables the author to trigger spatial navigation programatically,
+The {{Window/navigate()}} method enables the author to trigger spatial navigation programmatically,
 as if the user had done so manually
 (for instance, by pressing the arrow keys in a browser where that is the way to trigger spatial navigation).
 
@@ -537,7 +537,7 @@ and the result will be <code>null</code>.</strong>
     The following code changes the behavior of spatial navigation
     so that when a scroll container would get focused,
     if it has at least one visible focusable descendant,
-    the focus is automatically transfered to it.
+    the focus is automatically transferred to it.
 
     <pre><code highlight=javascript>
     document.addEventListener("navbeforefocus", function(e) {
@@ -566,14 +566,14 @@ and the result will be <code>null</code>.</strong>
 <div class=example id=loop>
     The following code changes the behavior of spatial navigation
     to trap the focus within a spatial navigation container:
-    when no further focusable elements can be found in the requested direcition
+    when no further focusable elements can be found in the requested direction
     and the spatial navigation container cannot be scrolled any futher,
     we loop back to the other side instead of searching outside of it,
     either by focusing or scrolling depending on what is available.
 
     The focus can still be moved outside by sequential navigation,
     mouse interaction,
-    programatic calls to {{focus()}}…
+    programmatic calls to {{focus()}}…
 
     <pre><code highlight=javascript>
     document.addEventListener("navnotarget", function(e) {
@@ -983,15 +983,14 @@ The <a>navigation-override</a> [=policy-controlled feature=]</h2>
 	We recognize that there exists other mechanisms predating spatial navigation
 	that malicious authors could use
 	to interfere with the user's ability to control where the focus goes.
-	Despite that, it seems worthwile to attempt not to increase this attack surface,
+	Despite that, it seems worthwhile to attempt not to increase this attack surface,
 	although it is possible that such attacks are already sufficiently easy to perform
 	that this is a lost cause.
 	Further feedback on this topic,
 	based on experience with implementation or with mitigating such attacks,
 	is very welcome.
 
 
-
 <h2 id=processing-model>
 Processing Model</h2>