Fix variables in The rules for choosing a navigable

The chosen variable was incorrectly initialized again in a nested set
of steps, making it seem as if the outer chosen variable was not
overwritten. And it was referred to incorrectly as part of whatwg#11208.

Fixes whatwg#11282.

Co-authored-by: Anne van Kesteren <[email protected]>

Author: vinhill

source

@@ -99599,8 +99599,6 @@ interface <dfn interface>NotRestoredReasons</dfn> {
         <var>noopener</var> to true.</p>
        </li>
 
-       <li><p>Let <var>chosen</var> be null.</p></li>
-
        <li><p>Let <var>targetName</var> be the empty string.</p></li>
 
        <li><p>If <var>name</var> is not an <span>ASCII case-insensitive</span> match for "<code
@@ -99631,8 +99629,7 @@ interface <dfn interface>NotRestoredReasons</dfn> {
        must be set in <var>chosen</var>'s <span data-x="nav-bc">active browsing context</span>'s
        <span>popup sandboxing flag set</span>.</p></li>
 
-       <li><p>Set <var>targetNavigable</var>'s <span>is created by web content</span> to
-       true.</p></li>
+       <li><p>Set <var>chosen</var>'s <span>is created by web content</span> to true.</p></li>
       </ol>
 
       <p class="note">If the newly created <span>navigable</span> <var>chosen</var> is immediately