Reformat status spec requirements in Status section.

index.html

@@ -2172,24 +2172,16 @@ <h3>Status</h3>
         </p>
 
         <p>
-Specification authors that create status schemes are provided the following
-guideline:
+Credential status specifications MUST NOT enable tracking of individuals, such
+as an [=issuer=] being notified (either directly or indirectly) when a
+[=verifier=] is interested in a specific [=holder=] or [=subject=]. Unacceptable
+approaches include "phoning home," such that every use of a credential contacts
+the [=issuer=] of the credential to check the status for a specific individual,
+or "pseudonymity reduction", such that every use of the credential causes a
+request for information from the [=issuer=] that can be used by the [=issuer=]
+to deduce [=verifier=] interest in a specific individual.
         </p>
 
-        <ul>
-          <li>
-Status schemes MUST NOT be implemented in ways that enable tracking of
-individuals, such as an [=issuer=] being notified (either directly or
-indirectly) when a [=verifier=] is interested in a particular [=holder=]
-or [=subject=]. Unacceptable approaches include "phoning home," such that
-every use of a credential contacts the [=issuer=] of the credential to
-check the status for a specific individual, or "pseudonymity reduction,"
-such that every use of the credential causes a request for information
-from the [=issuer=] that can be used by the [=issuer=] to deduce
-[=verifier=] interest in a specific individual.
-          </li>
-        </ul>
-
       </section>
 
       <section>