MIX: Fixing typos.

Fixes #434. Thanks, @tyoshino

Author: mikewest

specs/mixedcontent/index.src.html

@@ -708,8 +708,8 @@ <h3 id="should-block-fetch">
               </li>
             </ol> 
           <li>
-            Otherwise, if <var>context</var> is an <a>optionally-blockable
-            request context</a>, return <strong>blocked</strong>.
+            Otherwise, if <var>context</var> is a <a>blockable request
+            context</a>, return <strong>blocked</strong>.
           </li>
           <li>
             If the user agent is configured to block <a>optionally-blockable</a>
@@ -723,8 +723,7 @@ <h3 id="should-block-fetch">
         </ol>
       </li>
       <li>
-        Otherwise, <var>origin</var> is <a>potentially secure</a>, so
-        return <strong>allowed</strong>.
+        Return <strong>allowed</strong>.
       </li>
     </ol>
 
@@ -745,9 +744,9 @@ <h3 id="should-block-response">
 
     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>blockable</a>
-    <a>request</a>, but the connection is <a>insecure</a>). This algorithm is
-    used to make that determination.
+    that generated the response (e.g. because the request is <a>blockable</a>,
+    but the connection is <a>insecure</a>). This algorithm is used to make
+    that determination.
 
     Given a <a>request</a> <var>request</var> and <a>response</a>
     <var>response</var>, the user agent determines what response should be
@@ -969,8 +968,9 @@ <h3 id="service-workers">Service Workers</h3>
     those requests were triggered from a document (which, presumably, ensures
     that they'll be used in an <a>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>optionally-blockable</a>
-    requests into <a>blockable</a> responses.
+    should the Service Worker be allowed to launder responses to
+    <a>optionally-blockable</a> requests into responses to <a>blockable</a>
+    requests.
 
     To that end: