Tweaks to privacy considerations section about decoy values.

Follows on #155

Author: TallTed

index.html

@@ -1407,22 +1407,22 @@ <h3>Decoy Values</h3>
 [=Issuer=] use of decoy values in status lists has been explored as a mechanism
 to increase the privacy of [=subjects=]. While algorithms for employing decoy
 values are out of scope for this specification, implementers are advised that
-the use of decoy values do not provide privacy gains and can harm privacy in
+the use of decoy values does not improve privacy and can harm privacy in
 most cases.
       </p>
       <p>
-When status list entry indexes are allocated in a random fashion, which is the
-suggested mode of operation for this specification, adding decoys harms privacy
-because it reduces the group privacy size by the number of decoys added to the
-group. A random allocation of indexes inherently hides the true group size,
-ensuring that decoys are not necessary.
+When indexes of status list entries are allocated in a random fashion, which is
+the suggested mode of operation for this specification, adding decoys harms
+privacy because it reduces the group privacy size by the number of decoys added
+to the group. A random allocation of indexes inherently hides the true size of
+the group, ensuring that decoys are not necessary.
       </p>
       <p>
 There might be use cases where decoy values provide benefits. Implementers are
-cautioned that no such use cases were clearly identified by the group that
-created this specification. As a result, the use of decoys is discouraged for
-most use cases, as random allocation of status list entry indexes provides
-adequate protection.
+cautioned that no such use cases were clearly identifiable by the group that
+created this specification. Therefore, the use of decoys is discouraged for
+most if not all use cases, as random allocation of status list entry indexes
+provides adequate protection.
       </p>
     </section>