[css-nav-1] Fix the typo error

Author: Jihye Hong

css-nav-1/Overview.bs

@@ -109,7 +109,7 @@ Historically, most browsers have not offered features to let the user move the f
 Some, such as TV browsers, have enabled the user to move the focus using the arrow keys out of necessity,
 since no other input mechanism is available on a typical TV remote control.
 
-Others, have enabled different key combinations to control spatial navigation,
+Others have enabled different key combinations to control spatial navigation,
 such as pressing the <code class=key>Shift</code> key together with arrow keys.
 
 This ability to move around the page directionally is called <dfn lt="spatial navigation | spatialNavigation" export>spatial navigation</dfn>.
@@ -139,8 +139,7 @@ enabling the author to control and override how spatial navigation works.</span>
 
 Note: Some aspects of this specification, such as the JavaScript Events and APIs
 could also be extended to sequential navigation,
-in order to make sure that keyboard navigation in general
-has a consistent and well defined model.
+in order to make sure that keyboard navigation has a consistent and well defined model in general.
 
 Note: As a general principle,
 keyboard navigation,
@@ -193,7 +192,7 @@ More specifically,
 the User Agent will first search for visible and focusable items
 in the direction indicated
 within the current <a>spatial navigation container</a>
-(<span class=cssapi>by default </span>the root element, scrollable elements, and iframes<span class=cssapi>,
+(<span class=cssapi>by default, </span>the root element, scrollable elements, and iframes<span class=cssapi>,
 but other elements can be made into <a>spatial navigation containers</a>
 using the 'spatial-navigation-contain' property</span>).
 
@@ -366,8 +365,8 @@ the following requirements apply:
         the text insertion caret when an editable element is focused,
         the arrow keys should by default to moving the caret.
         Spatial navigation would only be triggered by the arrow keys
-        when the focused element is not editable,
-        or when it is editable but the caret cannot move any further in the requested direction.
+        when the focused element is not editable
+        or when it is editable, but the caret cannot move any further in the requested direction.
     </div>
 
     An exception is made for scrolling:
@@ -401,7 +400,7 @@ The {{Window/navigate()}} method enables the author to trigger spatial navigatio
 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).
 
-Note: As this triggers the same processing model as a manual navigation,
+Note: As this triggers the same processing model as manual navigation,
 all the same results should be expected:
 the same chain of events will be fired and
 the same element will be scrolled or focused.
@@ -412,7 +411,7 @@ such as mapping to different keys,
 or triggering spatial navigation from a clickable on-screen directional pad,
 or in reaction to other events than UI ones.
 It could also be used when an author wants to interrupt navigation to do some asynchronous operation
-(e.g. load more content in an infinite scroller) then resume the navigation where they cancelled.
+(e.g. load more content in an infinite scroller) then resume the navigation where they canceled.
 
 Note: This API is also useful for testing purposes,
 as there it is difficult to trigger spatial navigation
@@ -536,7 +535,7 @@ the User Agent must run the steps described below:
     1. Let <var>direction</var> be the value of <var>dir</var>.
     2. Let <var>container</var> be
         * if the value of {{SpatialNavigationSearchOptions/container}} attribute of <var>options</var> is not null,
-            * itself, if it is <a>sptial navigation container</a>.
+            * itself, if it is <a>spatial navigation container</a>.
             * its nearest <a>spatial navigation container</a> ancestor, otherwise.
         * else the element's nearest <a>spatial navigation container</a> ancestor.
     3. Let <var>areas</var> be
@@ -1114,6 +1113,8 @@ If the status of <var>focus target</var> changed not by moving the focus,
 3. If <var>focus target</var> is completely off-screen,
     then let <var>searchOrigin</var> be the viewport of <var>focus target</var>'s nearest visible <a>spatial navigation container</a>.
 
+NOTE: The User Agent should <a>update the search origin</a>, for example,
+when the focused element was scrolled out by mouse scrolling or vanished from the viewport.
 </div>
 
 <div algorithm="to find focusable areas">
@@ -1140,7 +1141,7 @@ run the following steps:
     Except for elements that are in the currently non visible part of a scroller,
     spatial navigation does not automatically exclude
     elements which cannot be clicked on,
-    for example due to being obscured by some other element.
+    for example, due to being obscured by some other element.
     To avoid breaking assumptions in
     the application logic if a user actually focuses and activates such an element,
     and to avoid confusing users by focusing invisible or apparently unreachable elements,
@@ -1292,14 +1293,14 @@ The meaning of each term is as follows:
 </dl>
 
 Note: This general formula was picked from several plausible alternatives,
-based on which one most often match intuition
+based on which one most often matches intuition
 when used to select the best candidate
 in a series of <a href="https://wicg.github.io/spatial-navigation/tests/ux/list.html">UX test cases</a>.
 Similarly, the values of <var>alignWeight</var> and <var>orthogonalWeight</var>
 were also determined experimentally based on the same test cases.
 The resulting formula is somewhat complicated,
 but seems to give good answers.
-Suggestions on improvements or simplifications are welcome.
+Suggestions for improvements or simplifications are welcome.
 
 </div>
 
@@ -1713,6 +1714,7 @@ The editors of this specification would like to thank the following individuals
 * Alice Boxhall
 * Brian Kardell
 * Elika Etemad
+* Eric Seong
 * Hugo Holgersson
 * Hyojin Song
 * Jeonghee Ahn