MIX: Drop the obsolete references to Fetch's 'frame type' and 'context'

Closes #465.

Author: mikewest

specs/mixedcontent/index.src.html

@@ -45,6 +45,7 @@ <h1>Mixed Content</h1>
       text: creating a new Document object; url: create-a-document-object
       text: navigated; url: navigate
       text: nested browsing context
+      text: parent browsing context
       text: nested through; url: browsing-context-nested-through
       text: plugin document
       text: sandboxed origin browsing context flag
@@ -79,12 +80,6 @@ <h1>Mixed Content</h1>
     url: concept-request-client
       text: request client
       text: client
-    url: concept-request-context
-      text: request context
-      text: context
-    url: concept-request-context-frame-type
-      text: request context frame type
-      text: frame type
     url: concept-response-https-state
       text: response https state;
       text: https state
@@ -795,8 +790,6 @@ <h3 id="should-block-response">
       content?
     </h3>
 
-    ISSUE(w3c/webappsec#465): This still uses "context" and "frame type". Fix.
-
     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 request is <a>blockable</a>,
@@ -1064,14 +1057,14 @@ <h3 id="service-workers">Service Workers</h3>
     To that end:
 
     1.  [[#should-block-fetch]] has some carve-outs for the <code>fetch</code>
-        request context, with the intent of allowing a Service Worker to copy
-        a request as part of its response to a Fetch event (e.g.
+        request <a>initiator</a>, with the intent of allowing a Service Worker
+        to copy a request as part of its response to a Fetch event (e.g.
         <code>fetch(event.response)</code> should be executable inside the
         event handler.
 
-        The <code>fetch</code> request context will continue to be treated as
-        <a>blockable</a> when executed outside the context of a Fetch event,
-        which of course includes document contexts.
+        <code>fetch</code> will continue to be treated as <a>blockable</a> when
+        executed outside the context of a Fetch event, which of course includes
+        document contexts.
 
     2.  [[#should-block-response]] verifies that the incoming response has the
         same security characteristics that were allowed for the request. That