RFC2119 changes

index.html

@@ -1183,7 +1183,7 @@
 should restrict the [=data=] they transfer to what's either necessary to achieve their users'
 goals or aligns with their users' wishes and interests.</span></div>
 
-<div class="practice" data-audiences="api-designers"><span class="practicelab">Web APIs should be designed to minimize the amount of data that sites need
+<div class="practice" data-audiences="api-designers"><span class="practicelab">Web APIs must be designed to minimize the amount of data that sites need
 to request to carry out their users' goals.
 Web APIs should also provide granularity and user controls over <a>personal
 data</a> that is communicated to sites.</span></div>
@@ -1353,7 +1353,7 @@
 ## Information access {#information}
 
 <div class="practice" data-audiences="api-designers user-agents">
-  <span class="practicelab">New web APIs must guard users' information at least
+  <span class="practicelab">New web APIs should guard users' information at least
   as well as existing APIs that are expected to stay in the web platform.</span>
 </div>
 
@@ -1883,7 +1883,7 @@
 <div class="practice" data-audiences="websites api-designers">
   <span class="practicelab" id="transparency-distinguishable">
     Mechanisms that can be used for [=recognize|recognizing=] [=people=] should be designed so that
-    their operation is visible and distinguishable, to [=user agents=], researchers and regulators.
+    their operation is visible and distinguishable, to [=user agents=], researchers, and regulators.
   </span>
 </div>
 
@@ -1919,7 +1919,7 @@
 <p>
   <span class="practicelab" id="principle-minimize-consent-requests">
     An [=actor=] should avoid interrupting a [=person=]'s use of a site for
-	consent requests when an alternative is available.
+	  consent requests when an alternative is available.
   </span>
 </p>
 </div>
@@ -1941,8 +1941,8 @@
 <div class="practice" data-audiences="websites">
 <p>
   <span class="practicelab" id="principle-consent-withdraw">
-  It should be as easy for a [=person=] to check what consent they have given, to withdraw consent,
-  or to opt out or object, as to give consent.
+    It should be as easy for a [=person=] to check what consent they have given, to withdraw consent,
+    or to opt out or object, as to give consent.
   </span>
 </p>
 </div>
@@ -2389,6 +2389,20 @@
 
 <section class="appendix" id="bp-summary"></section>
 
+<section class="appendix">
+
+# Conformance
+
+This document does not adhere to strict [[?RFC2129]] terminology because it is primarily of
+an informative nature and does not easily lend itself to constraining a conformance class.
+However, within the formulation of its principles, we have taken care to use "should" to indicate 
+that a principle can be ignored in some rare cases given that there are valid reasons for doing so and 
+"must" to indicate that we can see no situation in which deviating from the principle could 
+be justified.
+
+</section>
+
+
 <section class="appendix">
 
 # Acknowledgements {#acknowledgements}