Correct branching logic in choosing a browsing context

Issue for tests: web-platform-tests/wpt#14256.

Author: annevk

source

@@ -77669,23 +77669,23 @@ console.assert(iframeWindow.frameElement === null);
    <li><p>If <var>name</var> is the empty string or an <span>ASCII case-insensitive</span> match for
    "<code data-x="">_self</code>", then set <var>chosen</var> to <var>current</var>.</p></li>
 
-   <li><p>If <var>name</var> is an <span>ASCII case-insensitive</span> match for "<code
-   data-x="">_parent</code>", then set <var>chosen</var> to <var>current</var>'s <span>parent
-   browsing context</span>, if any, and <var>current</var> otherwise.</p></li>
+   <li><p>Otherwise, if <var>name</var> is an <span>ASCII case-insensitive</span> match for "<code
+   data-x="">_parent</code>", set <var>chosen</var> to <var>current</var>'s <span>parent browsing
+   context</span>, if any, and <var>current</var> otherwise.</p></li>
 
-   <li><p>If <var>name</var> is an <span>ASCII case-insensitive</span> match for "<code
-   data-x="">_top</code>", then set <var>chosen</var> to <var>current</var>'s <span>top-level
-   browsing context</span>, if any, and <var>current</var> otherwise.</p></li>
+   <li><p>Otherwise, if <var>name</var> is an <span>ASCII case-insensitive</span> match for "<code
+   data-x="">_top</code>", set <var>chosen</var> to <var>current</var>'s <span>top-level browsing
+   context</span>, if any, and <var>current</var> otherwise.</p></li>
 
    <li>
-    <p>If <var>name</var> is not an <span>ASCII case-insensitive</span> match for "<code
-    data-x="">_blank</code>" and there exists a browsing context whose <span data-x="browsing
-    context name">name</span> is the same as <var>name</var>, and <var>current</var> is
-    <span>familiar with</span> that browsing context, and the user agent determines that the two
-    browsing contexts are related enough that it is ok if they reach each other, then set
-    <var>chosen</var> to that browsing context. If there are multiple matching browsing contexts,
-    the user agent should set <var>chosen</var> to one in some arbitrary consistent manner, such as
-    the most recently opened, most recently focused, or more closely related.</p>
+    <p>Otherwise, if <var>name</var> is not an <span>ASCII case-insensitive</span> match for "<code
+    data-x="">_blank</code>", there exists a browsing context whose <span data-x="browsing context
+    name">name</span> is the same as <var>name</var>, <var>current</var> is <span>familiar
+    with</span> that browsing context, and the user agent determines that the two browsing contexts
+    are related enough that it is ok if they reach each other, set <var>chosen</var> to that
+    browsing context. If there are multiple matching browsing contexts, the user agent should set
+    <var>chosen</var> to one in some arbitrary consistent manner, such as the most recently opened,
+    most recently focused, or more closely related.</p>
 
     <p class="&#x0058;&#x0058;&#x0058;">This will be made more precise in <a
     href="https://github.com/whatwg/html/issues/1440">issue #1440</a>.</p>
@@ -77705,7 +77705,7 @@ console.assert(iframeWindow.frameElement === null);
 
      <dt id="sandboxWindowOpen">If <var>current</var>'s <span>active document</span>'s <span>active
      sandboxing flag set</span> has the <span>sandboxed auxiliary navigation browsing context
-     flag</span> set.</dt>
+     flag</span> set</dt>
 
      <dd>
       <p>The user agent may offer the user one of:
@@ -77726,7 +77726,7 @@ console.assert(iframeWindow.frameElement === null);
      </dd>
 
      <dt id="noopener">If the user agent has been configured such that in this instance it will
-     create a new browsing context:</dt>
+     create a new browsing context</dt>
 
      <dd>
       <p>Set <var>chosen</var> to a <span data-x="creating a new browsing context">new</span>