Modify some terminologies

index.bs

@@ -21,7 +21,7 @@ As a general principle,
 keyboard navigation,
 and spatial navigation in particular,
 should be possible to control without JavaScript;
-declarative solutions are prefered,
+declarative solutions are preferred,
 and since spatial navigation depends on layout,
 that means CSS is typically the right place to define
 spatial navigation related features.
@@ -48,13 +48,13 @@ such as scrolling.
 
 The 'arrow-key-behavior' property enables an author to declare
 that their document, or part of their document,
-has been authored with spatinal navigation in mind,
+has been authored with spatial navigation in mind,
 and the UA can bind the arrow keys to spatial navigation
-without risk of interering with other behavior.
+without risk of interfering with other behavior.
 
 <pre class='propdef'>
 Name: arrow-key-behavior
-Value: auto | mixed | spat-nav
+Value: auto | mixed | focus-nav
 Initial: auto
 Inherited: yes
 </pre>
@@ -87,7 +87,7 @@ Does that depend on whether the selection is collapsed or not?
 	<strong>in <a>mixed mode</a></strong>
 	when the user presses arrow keys.
 
-	Additionally, User Agents which allow spatial navigation to be controled
+	Additionally, User Agents which allow spatial navigation to be controlled
 	by keys other than arrow keys without a modifier key
 	when the value of 'arrow-key-behavior' is auto
 	must continue to do so.
@@ -96,7 +96,7 @@ Does that depend on whether the selection is collapsed or not?
 	<strong>in <a>strict mode</a></strong>
 	when the user presses arrow keys.
 
-	Additionally, User Agents which allow spatial navigation to be controled
+	Additionally, User Agents which allow spatial navigation to be controlled
 	by keys other than arrow keys without a modifier key
 	when the value of 'arrow-key-behavior' is auto
 	must continue to do so.
@@ -169,12 +169,12 @@ Processing Model</h2>
 <h3 id=events>
 Event Sequence</h3>
 
-When the user performs performs an action that triggers spatial nagivation
+When the user performs an action that triggers spatial navigation
 (typically pressing an arrow key),
 the sequence is as follows:
 
 * The corresponding UI event is fired
-* If `preventDefault()` is not called during that event's handler, then
+* If `preventDefault()` is not called during that event handler, then
 
     * Find where the focus should go, based on the <a>focus navigation heuristic</a>
     * `FocusNavigationEvent` event is fired
@@ -188,7 +188,7 @@ when the user invokes either spatial or sequential navigation.
 
 Issue: Add the details. Link to HTML for the logic on sequential navigation.
 Include <dfn>strict mode</dfn> and <dfn>mixed mode</dfn> giving different results when
-there is no appropirate target without scrolling.
+there is no appropriate target without scrolling.
 
 </div>