MIX: Changing wording around example 6's data: url.

w3c · Jan 15, 2015 · 537aa36 · 537aa36
1 parent 1f67394
commit 537aa36
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/specs/mixedcontent/index.html b/specs/mixedcontent/index.html
@@ -1045,7 +1045,8 @@ <h3 class="heading settled" data-level="5.1" id="categorize-settings-object"><sp
         <code>https://a.com</code> frames a <code>data:</code> URL, which loads
         <code>http://evil.com</code>. In this case, the insecure request to
         <code>evil.com</code> will be blocked, as <code>a.com</code> was loaded
-        over a secure connection, even though the framed data URL was not.
+        over a secure connection, even though the framed <code>data:</code> URL
+        is <a data-link-type="dfn" href="#a-priori-insecure-origin"><em>a priori</em> insecure</a>.
       </div>
 
 

diff --git a/specs/mixedcontent/index.src.html b/specs/mixedcontent/index.src.html
@@ -667,7 +667,8 @@ <h3 id="categorize-settings-object">
         <code>https://a.com</code> frames a <code>data:</code> URL, which loads
         <code>http://evil.com</code>. In this case, the insecure request to
         <code>evil.com</code> will be blocked, as <code>a.com</code> was loaded
-        over a secure connection, even though the framed data URL was not.
+        over a secure connection, even though the framed <code>data:</code> URL
+        is <a><em>a priori</em> insecure</a>.
       </div>
     </div>
   </section>