Apply suggestions from @chaals.

Author: msporny

common.js

@@ -66,6 +66,16 @@ var vcwg = {
       status: "CG-DRAFT",
       publisher: "Digital Verification Community Group"
     },
+    "CL-SIGNATURES": {
+      title: "A Signature Scheme with Efficient Protocols",
+      href: "http://groups.csail.mit.edu/cis/pubs/lysyanskaya/cl02b.pdf",
+      authors: [
+        "Jan Camenisch",
+        "Anna Lysyanskaya"
+      ],
+      status: "Peer Reviewed Paper",
+      publisher: "IBM Research"
+    },
     // aliases to known references
     "HTTP-SIGNATURES": {
       aliasOf: "http-signatures"

index.html

@@ -564,16 +564,16 @@ <h3>Use Cases and Requirements</h3>
 While digital proofs, a subset of which are digital signatures, are required
 to ensure the protection of a <a>verifiable credential</a>, this specification
 does not standarize on any single digital signature format. At the time of
-publication, the Working Group included members that had implemented using
-at least three proof mechanisms. These implementations utilized
-JSON Web Tokens, Linked Data Signatures, and Camenisch-Lysyanskaya
-Zero-Knowledge Proofs. It is expected that each of these mechanisms will mature
-independently and additional mechanisms will also become standardized. One
-of the goals of this specification is to provide a data model that can be
-protected by a variety of current and future digital proof approaches.
-Conformance with respect to digital proofs in this specification is focused
-on the clear identification of each digital proof mechanism and not the details
-of any particular proof mechanism.
+publication, Working Group members had implemented
+<a>verifiable credentials</a> using at least three proof mechanisms:
+JSON Web Tokens [[JWT]], Linked Data Signatures [[?LD-SIGNATURES]], and
+Camenisch-Lysyanskaya Zero-Knowledge Proofs [[?CL-SIGNATURES]]. The group
+expects some of these mechanisms, as well as new ones, to mature independently
+and become standardized in time. One of the goals of this specification is to
+provide a data model that can be protected by a variety of current and future
+digital proof mechanisms. Conformance to this specification does not
+depend on the details of a particular proof mechanism; it requires clearly
+identifying the mechanism a <a>verifiable credential</a> uses.
         </p>
       </section>