Editorial: improve links to "resolve a module specifier" assertions

The explanatory text of the assertion in HostResolveImportedModule
stating that "resolve a module specifier" must have been previously
successful lists HostImportModuleDynamically as one of the places where
"resolve a module specifier" would previously have succeeded. However,
it's "fetch() an import() module script graph", called by
HostImportModuleDynamically, where "resolve a module specifier" is
actually called. Update the assertion text to reference "fetch() an
import() module script graph" directly.

The corresponding assertion in "find the first parse error" didn't have
a link to where the prior "resolve a module specifier" call would occur,
so add one.

Author: dandclark

source

@@ -90183,8 +90183,8 @@ document.querySelector("button").addEventListener("click", bound);
    <li><p>Let <var>childURLs</var> be the <span>list</span> obtained by calling
    <span>resolve a module specifier</span> once for each item of <var>childSpecifiers</var>, given
    <var>moduleScript</var>'s <span data-x="concept-script-base-url">base URL</span> and that item.
-   (None of these will ever fail, as otherwise <var>moduleScript</var> would have been marked as
-   itself having a parse error.)</p></li>
+   (None of these will ever fail, as otherwise <var>moduleScript</var> would have been <a
+   href="#validate-requested-module-specifiers">marked as itself having a parse error</a>.)</p></li>
 
    <li><p>Let <var>childModules</var> be the <span>list</span> obtained by <span
    data-x="map get">getting each value</span> in <var>moduleMap</var> whose key is given by an
@@ -91327,7 +91327,7 @@ import "https://example.com/foo/../module2.mjs";</code></pre>
    <li><p>Assert: <var>url</var> is never failure, because <span data-x="resolve a module
    specifier">resolving a module specifier</span> must have been previously successful with these
    same two arguments (either <a href="#validate-requested-module-specifiers">while creating the
-   corresponding module script</a>, or in <span>HostImportModuleDynamically</span>).</p></li>
+   corresponding module script</a>, or in <span>fetch an import() module script graph</span>).</p></li>
 
    <li><p>Let <var>resolved module script</var> be <var>moduleMap</var>[<var>url</var>]. (This entry
    must <span data-x="map exists">exist</span> for us to have gotten to this point.)</p></li>