Editorial: Fix spelling mistakes

Author: Jihye Hong

index.bs

@@ -79,13 +79,13 @@ depending on their position
 allowing it to address problems encountered with sequential navigation.
 
 <figure>
-    <img alt="When elements are layed out in a grid pattern, spatial navigation makes it much easier to predict and control where focus should move to." src="images/spatnav-enable.png" style="width: 500px;"/>
+    <img alt="When elements are laid out in a grid pattern, spatial navigation makes it much easier to predict and control where focus should move to." src="images/spatnav-enable.png" style="width: 500px;"/>
     <figcaption>Application using a grid-like layout.</figcaption>
 </figure>
 
 While arrow keys are naturally suited to control spatial navigation,
 no previous specification describes how that should work,
-or how it may be controled.
+or how it may be controlled.
 This specification introduces a processing model for spatial navigation,
 as well as APIs
 enabling authors to control and override how spatial navigation works.
@@ -115,7 +115,7 @@ they represent an important part of the user or author experience
 of the features defined in specification.
 At the same time, the core functionality of this specification
 can be implemented without implementing these
-so it seems possible that implementors may chose to down-prioritize them
+so it seems possible that implementors may choose to down-prioritize them
 to reduce the scope of a first implementation.
 While it is hoped that these features will be implemented as well,
 they are marked at-risk in recognition that they might not be at first.
@@ -276,7 +276,7 @@ When the user triggers spatial navigation in a given direction,
 the User Agent must run the <a>spatial navigation steps</a> in that direction.
 
 This specification does not define what UI mechanism User Agents should offer to users to trigger spatial navigation.
-This intentionaly left for User Agents to decide.
+This intentionally left for User Agents to decide.
 
 <div class=note>Note:
     It is expected that User Agents on devices with limited input capabilities,
@@ -287,7 +287,7 @@ This intentionaly left for User Agents to decide.
 
 Although it is possible for User Agents
 to implement the processing model and APIs defined by the specification
-without giving any direct means to the user to trigger spatial navigation themself,
+without giving any direct means to the user to trigger spatial navigation themselves,
 this specification recommends not to do so:
 User Agents should offer a means for users to trigger spatial navigation directly,
 without having to use the APIs.
@@ -297,7 +297,7 @@ by the UA in response to user actions
 even if the author has not invoked any of the APIs.
 
 Regardless of the actual mechanism chosen to trigger spatial navigation,
-the following requiremnts apply:
+the following requirements apply:
 * If the mechanism the user must use to trigger spatial navigation
     would normally fire a {{UIEvent}},
     then that event must be fired prior to running the <a>spatial navigation steps</a>
@@ -429,7 +429,7 @@ The {{Element/focusableAreas()}} method must follow these steps:
 The {{Element/spatNavSearch()}} method must follow these steps:
 1. Let <var>d</var> be the argument's {{SpatNavSearchOptions/dir}} attribute
 2. If the argument's {{SpatNavSearchOptions/candidates}} attribute is not <code>null</code>,
-    then let <var>areas</var> be that atribute,
+    then let <var>areas</var> be that attribute,
     else, let <var>areas</var> be the result of <a>finding focusable areas</a>
     within the argument's {{SpatNavSearchOptions/container}} attribute is not <code>null</code>,
     or the element's nearest <a>spatnav container</a> ancestor

index.html

@@ -1546,12 +1546,12 @@ <h2 class="non-normative heading settled" data-level="1" id="intro"><span class=
 depending on their position
 allowing it to address problems encountered with sequential navigation.</p>
    <figure>
-     <img alt="When elements are layed out in a grid pattern, spatial navigation makes it much easier to predict and control where focus should move to." src="images/spatnav-enable.png" style="width: 500px;"> 
+     <img alt="When elements are laid out in a grid pattern, spatial navigation makes it much easier to predict and control where focus should move to." src="images/spatnav-enable.png" style="width: 500px;"> 
     <figcaption>Application using a grid-like layout.</figcaption>
    </figure>
    <p>While arrow keys are naturally suited to control spatial navigation,
 no previous specification describes how that should work,
-or how it may be controled.
+or how it may be controlled.
 This specification introduces a processing model for spatial navigation,
 as well as APIs
 enabling authors to control and override how spatial navigation works.</p>
@@ -1578,7 +1578,7 @@ <h2 class="non-normative heading settled" data-level="1" id="intro"><span class=
 of the features defined in specification.
 At the same time, the core functionality of this specification
 can be implemented without implementing these
-so it seems possible that implementors may chose to down-prioritize them
+so it seems possible that implementors may choose to down-prioritize them
 to reduce the scope of a first implementation.
 While it is hoped that these features will be implemented as well,
 they are marked at-risk in recognition that they might not be at first.</p>
@@ -1699,23 +1699,23 @@ <h2 class="heading settled" data-level="4" id="triggering"><span class="secno">4
    <p>When the user triggers spatial navigation in a given direction,
 the User Agent must run the <a data-link-type="dfn" href="#spatial-navigation-steps" id="ref-for-spatial-navigation-steps">spatial navigation steps</a> in that direction.</p>
    <p>This specification does not define what UI mechanism User Agents should offer to users to trigger spatial navigation.
-This intentionaly left for User Agents to decide.</p>
+This intentionally left for User Agents to decide.</p>
    <div class="note" role="note">Note:
     It is expected that User Agents on devices with limited input capabilities,
     such as TVs operated with a remote control,
     or devices operated with a game controller,
     will use spatial navigation as their primary or exclusive navigation mechanism. </div>
    <p>Although it is possible for User Agents
 to implement the processing model and APIs defined by the specification
-without giving any direct means to the user to trigger spatial navigation themself,
+without giving any direct means to the user to trigger spatial navigation themselves,
 this specification recommends not to do so:
 User Agents should offer a means for users to trigger spatial navigation directly,
 without having to use the APIs.</p>
    <p class="note" role="note"><span>Note:</span> Conversely, authors should assume that spatial navigation may be triggered
 by the UA in response to user actions
 even if the author has not invoked any of the APIs.</p>
    <p>Regardless of the actual mechanism chosen to trigger spatial navigation,
-the following requiremnts apply:</p>
+the following requirements apply:</p>
    <ul>
     <li data-md="">
      <p>If the mechanism the user must use to trigger spatial navigation
@@ -1835,7 +1835,7 @@ <h2 class="heading settled" data-level="5" id="js-api"><span class="secno">5. </
       <p>Let <var>d</var> be the argument’s <code class="idl"><a data-link-type="idl" href="#dom-spatnavsearchoptions-dir" id="ref-for-dom-spatnavsearchoptions-dir">dir</a></code> attribute</p>
      <li data-md="">
       <p>If the argument’s <code class="idl"><a data-link-type="idl" href="#dom-spatnavsearchoptions-candidates" id="ref-for-dom-spatnavsearchoptions-candidates">candidates</a></code> attribute is not <code>null</code>,
-then let <var>areas</var> be that atribute,
+then let <var>areas</var> be that attribute,
 else, let <var>areas</var> be the result of <a data-link-type="dfn" href="#find-focusable-areas" id="ref-for-find-focusable-areas①">finding focusable areas</a> within the argument’s <code class="idl"><a data-link-type="idl" href="#dom-spatnavsearchoptions-container" id="ref-for-dom-spatnavsearchoptions-container">container</a></code> attribute is not <code>null</code>,
 or the element’s nearest <a data-link-type="dfn" href="#spatial-navigation-focus-container" id="ref-for-spatial-navigation-focus-container⑨">spatnav container</a> ancestor</p>
      <li data-md="">