--- a/latest/use-cases/index.html	Thu Jun 25 01:05:43 2015 -0400
+++ b/latest/use-cases/index.html	Thu Jun 25 01:10:05 2015 -0400
@@ -268,9 +268,8 @@
 A title and short description.
         </li>
         <li>
-Goals. How the use case advances one or more of the
-<a href="https://www.w3.org/Payments/IG/wiki/ExecSummary#Goals">goals
-for an interoperable Web payments framework</a>.
+A <em>Target version</em> which specifies the intended version of the Web
+Payments Architecture that will enable the use case.
         </li>
         <li>
 Motivation. This is commentary to help explain why the use
@@ -288,15 +287,19 @@
 case.
         </li>
         <li>
+Accessibility. Accessibility considerations (e.g., in multi-factor
+authentication, management of biometrics in the case of users with some
+disabilities).
+        </li>
+        <li>
+Regulatory. Regulatory considerations (e.g., anti-money laundering
+clearing, suspicious activity reporting, tax collection, trade compliance).
+        </li>
+        <li>
 Exceptions. Considerations in the case of specific exceptions (e.g., if a
 user pays with a voucher and the <a>transaction</a> fails, the user's voucher
 should be restored).
         </li>
-        <li>
-Accessibility. Accessibility considerations (e.g., in multi-factor
-authentication, management of biometrics in the case of users with some
-disabilities).
-        </li>
       </ul>
 
       <p class="issue">