child context

Author: OrKoN

index.bs

@@ -2457,10 +2457,10 @@ To <dfn>get the navigable info</dfn> given |navigable|,
 
   1. Set |child infos| to an empty [=/list=].
 
-  1. For each |child context| of |child navigables|:
+  1. For each |child navigable| of |child navigables|:
 
     1. Let |info| be the result of [=get the navigable info=] given
-       |child context|, |child depth|, and false.
+       |child navigable|, |child depth|, and false.
 
     1. Append |info| to |child infos|
 
@@ -3164,26 +3164,26 @@ The [=remote end steps=] with |command parameters| are:
 
   <!-- This is based on step 5 of https://w3c.github.io/webdriver/#new-window,
        but without using the "current browsing context" concept. -->
-  1. Let |navigable| be the result of trying to [=/create a new top-level traversable=] steps with null and empty string,
+  1. Let |traversable| be the result of trying to [=/create a new top-level traversable=] steps with null and empty string,
      and setting the [=associated user context=] for the newly created [=/top-level traversable=] to |user context|.
-     Which OS window the new [=/navigable=] is created in depends on |type| and |reference navigable|:
+     Which OS window the new [=/top-level traversable=] is created in depends on |type| and |reference navigable|:
 
      * If |type| is "<code>tab</code>" and the implementation supports
-       multiple navigables in the same OS window:
+       multiple [=/top-level traversable=]s in the same OS window:
 
-       * The new navigable should reuse an existing OS window, if any.
+       * The new [=/top-level traversable=] should reuse an existing OS window, if any.
 
-       * If |reference navigable| is not null, the new navigable should
+       * If |reference navigable| is not null, the new [=/top-level traversable=] should
          reuse the window containing |reference navigable|, if any. If the
          top-level traversables inside an OS window have a definite ordering,
-         the new navigable should be immediately after
+         the new [=/top-level traversable=] should be immediately after
          |reference navigable|'s [=navigable/top-level traversable=] in that ordering.
 
      * If |type| is "<code>window</code>", and the implementation supports
-       multiple navigables in separate OS windows, the created browsing
-       context should be in a new OS window.
+       multiple [=/top-level traversable=] in separate OS windows, the created
+       [=/top-level traversable=] should be in a new OS window.
 
-     * Otherwise, the details of how the navigable is presented to the
+     * Otherwise, the details of how the [=/top-level traversable=] is presented to the
        user are implementation defined.
 
   1. If the value of the |command parameters|' <code>background</code> field is false:
@@ -3195,7 +3195,7 @@ The [=remote end steps=] with |command parameters| are:
     Note: Do not invoke the [=/focusing steps=] for the created navigable if <code>background</code> is true.
 
   1. Let |body| be a [=/map=] matching the <code>browsingContext.CreateResult</code>
-     production, with the <code>context</code> field set to |navigable|'s [=navigable id=].
+     production, with the <code>context</code> field set to |traversable|'s [=navigable id=].
 
   1. Return [=success=] with data |body|.