Renaming 'powerful features' to 'privileged contexts'.

Author: mikewest

admin/webappsec-charter-2015.html

@@ -209,14 +209,14 @@ <h2 id="deliverables">Deliverables</h2>
         </dd>
 
 	<dt>
-          <b><a href="http://www.w3.org/TR/powerful-features/">Sufficiently Secure Contexts</a> (FPWD)</a></b>
+          <b><a href="http://www.w3.org/TR/powerful-features/">Privileged Contexts</a> (FPWD)</a></b>
         </dt>
 
         <dd> <p>A recommendation for dealing with features which self-designate as requiring
-		a sufficiently secure context to be enabled, e.g. because such features provide
+		a privileged context to be enabled, e.g. because such features provide
 		access to sensitive personal information.  The recommendation will include non-normative
 		advice on when a feature might designate itself as requiring a secure context and provide
-		a normative algorithm for determining if a given context is sufficiently secure.
+		a normative algorithm for determining if a given context is privileged.
 		This work will be a joint deliverable with the W3C Technical Architecture Group.
 	    </p>
         </dd>