From b2ee530a405afeeacd4108e7aaeba93da7a9e6ee Mon Sep 17 00:00:00 2001
From: Francois Marier <francois@mozilla.com>
Date: Thu, 29 Oct 2015 10:21:18 +0900
Subject: [PATCH] Replace "potentially secure origins" with "secure contexts"

This term has been removed from the mixed content specification
so we should avoid using it anywhere in the SRI spec.
---
 spec.markdown | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/spec.markdown b/spec.markdown
index 135cf9b..ef33890 100755
--- a/spec.markdown
+++ b/spec.markdown
@@ -136,13 +136,6 @@ document loaded over HTTPS. A counterexample is a document loaded over HTTP.
 [secure context]: #dfn-secure-context
 [secure document]: #dfn-secure-document
 
-A <dfn>potentially secure origin</dfn> is defined in [section 2 of the Mixed
-Content][mixedcontent] specification. An example of a potentially secure origin
-is an origin whose scheme component is <code>HTTPS</code>.
-
-[potentially secure origin]: #dfn-potentially-secure-origin
-[mixedcontent]: https://www.w3.org/TR/mixed-content/#potentially-secure-origin
-
 The <dfn>representation data</dfn> and <dfn>content encoding</dfn> of a resource
 are defined by [RFC7231, section 3][representationdata]. [[!RFC7231]]
 
@@ -338,7 +331,7 @@ change the security state of the user agent, a [secure document] is
 unnecessary. However, if integrity is used in something other than a [secure document][]
 (e.g., a document delivered over HTTP), authors should be aware that the integrity
 provides <em>no security guarantees at all</em>. For this reason, authors should
-only deliver integrity metadata on a [potentially secure origin][].  See
+only deliver integrity metadata in a [secure context][].  See
 [Non-secure contexts remain non-secure][] for more discussion.
 
 {:.note}