Merge pull request #11 from ljharb/when-possible

spec: add "when possible" to recommendation

Author: Daniel Ehrenberg

spec.html

@@ -47,7 +47,7 @@ <h1>Runtime Semantics: HostResolveImportedModule ( _referencingScriptOrModule_,
         Each time this operation is called with a specific _referencingScriptOrModule_, _moduleRequest_.[[Specifier]], _moduleRequest_.[[Assertions]] triple as arguments it must return the same Module Record instance if it completes normally.
         <ul>
           <li>
-            It is recommended but not required that implementations additionally conform to the following stronger constraint: each time this operation is called with a specific _referencingScriptOrModule_, _moduleRequest_.[[Specifier]] pair as arguments it must return the same Module Record instance if it completes normally.
+            It is recommended but not required that when possible, implementations additionally conform to the following stronger constraint: each time this operation is called with a specific _referencingScriptOrModule_, _moduleRequest_.[[Specifier]] pair as arguments it must return the same Module Record instance if it completes normally.
           </li>
         </ul>
       </li>
@@ -76,7 +76,7 @@ <h1>Runtime Semantics: HostResolveImportedModule ( _referencingScriptOrModule_,
       <p>It's possible that one of these three options may make sense for a module load, on a case-by-case basis by attribute, but it's worth careful thought before making this choice.</p>
     </emu-note>
 
-    
+
     <emu-note type=editor>
       <p><ins>The above text implies that hosts *must* support JSON modules imported with `type: "json"` (if it completes normally), but it doesn't prohibit hosts from supporting JSON modules imported with no type specified. Some environments (for example, web browsers) are expected to require `assert { type: "json" }`, and environments which want to restrict themselves to a compatible subset would do so as well.</ins></p>
     </emu-note>