Rework retaliation text

index.html

@@ -1989,7 +1989,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>
@@ -2080,11 +2080,24 @@
   </span>
 </div>
 
-Whenever people have the ability to cause an [=actor=] to process less of their [=data=] or to stop
-carrying out some given set of data processing that is not essential to the service, they must be
-allowed to do so without the [=actor=] retaliating, for instance by artificially removing an
-unrelated feature, by decreasing the quality of the service, or by trying to cajole, badger, or
-trick the [=person=] into opting back into the [=processing=].
+People should be free to limit the amount of private information they share,
+to request that an actor limit the uses of data already shared,
+or that data be deleted.
+When a person chooses to deny or withdraw their permission to use their data,
+retaliation is inappropriate.
+
+It is not retaliation to terminate a service
+when data that is essential to the operation of a service is withheld.
+However, it might be retaliation if withholding data
+results in actions unrelated to the use of that data.
+Examples of retaliatory behavior include:
+
+* making the process of withdrawing consent more onerous than granting it;
+
+* using threats, badgering, or trickery ([[?dark-patterns]])
+  to encourage people to reconsider their choice; and,
+
+* denying access to services that do not depend on use of the data.
 
 ## Support Choosing Which Information to Present {#support-choosing-info}