MIX: Regenerating HTML.

Author: mikewest

specs/mixedcontent/index.html

@@ -71,7 +71,7 @@
    <h1 class="p-name no-ref" id="title">Mixed Content</h1>
 
    <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft,
-    <time class="dt-updated" datetime="2015-07-20">20 July 2015</time></span></h2>
+    <time class="dt-updated" datetime="2015-07-22">22 July 2015</time></span></h2>
 
    <div data-fill-with="spec-metadata">
     <dl>
@@ -1041,8 +1041,8 @@ <h3 class="heading settled" data-level="5.2" id="should-block-fetch"><span class
 
 
         <li>
-            Otherwise, if <var>context</var> is an <a data-link-type="dfn" href="#optionally_blockable-request-contexts">optionally-blockable
-            request context</a>, return <strong>blocked</strong>.
+            Otherwise, if <var>context</var> is a <a data-link-type="dfn" href="#blockable-request-context">blockable request
+            context</a>, return <strong>blocked</strong>.
 
 
 
@@ -1065,8 +1065,7 @@ <h3 class="heading settled" data-level="5.2" id="should-block-fetch"><span class
 
 
       <li>
-        Otherwise, <var>origin</var> is <a data-link-type="dfn" href="#potentially-secure-origin">potentially secure</a>, so
-        return <strong>allowed</strong>.
+        Return <strong>allowed</strong>.
 
 
 
@@ -1097,9 +1096,9 @@ <h3 class="heading settled" data-level="5.3" id="should-block-response"><span cl
 
      <p class="note" role="note">Note: <a href="#should-block-fetch">If a request proceeds</a>, we still
     might want to block the response based on the state of the connection
-    that generated the response (e.g. because the response is a <a data-link-type="dfn" href="#blockable">blockable</a>
-    <a data-link-type="dfn" href="https://fetch.spec.whatwg.org/#concept-request">request</a>, but the connection is <a data-link-type="dfn" href="#insecure-origin">insecure</a>). This algorithm is
-    used to make that determination.</p>
+    that generated the response (e.g. because the request is <a data-link-type="dfn" href="#blockable">blockable</a>,
+    but the connection is <a data-link-type="dfn" href="#insecure-origin">insecure</a>). This algorithm is used to make
+    that determination.</p>
 
 
 
@@ -1416,8 +1415,9 @@ <h3 class="heading settled" data-level="7.5" id="service-workers"><span class="s
     those requests were triggered from a document (which, presumably, ensures
     that they’ll be used in an <a data-link-type="dfn" href="#optionally_blockable">optionally-blockable</a> context). Those
     insecure results, however, cannot be exposed to the Service Worker, nor
-    should the Service Worker be allowed to launder <a data-link-type="dfn" href="#optionally_blockable">optionally-blockable</a>
-    requests into <a data-link-type="dfn" href="#blockable">blockable</a> responses.</p>
+    should the Service Worker be allowed to launder responses to
+    <a data-link-type="dfn" href="#optionally_blockable">optionally-blockable</a> requests into responses to <a data-link-type="dfn" href="#blockable">blockable</a>
+    requests.</p>