--- a/latest/roadmap/index.html	Tue Jun 23 22:56:53 2015 -0400
+++ b/latest/roadmap/index.html	Tue Jun 23 23:07:18 2015 -0400
@@ -348,6 +348,10 @@
 
     <section>
       <h3>Capabilities</h3>
+      <p class="issue">
+This section is out of date and needs to be re-aligned with the latest
+capabilities document.
+      </p>
       <p>
 The following table shows the capabilities for this version, with annotations
 about where those capabilities arise in the payment flow and which groups will

--- a/latest/use-cases/index.html	Tue Jun 23 22:56:53 2015 -0400
+++ b/latest/use-cases/index.html	Tue Jun 23 23:07:18 2015 -0400
@@ -1638,6 +1638,24 @@
         <p>
         </p>
 
+        <dl id="uc-password" class="dl-horizontal">
+          <dt>Password Auth</dt>
+          <dd>
+When Suresh attempts to pay online, he is asked for a username and password
+by his payment service provider before the payment is approved.
+          </dd>
+          <dt>Goals</dt>
+          <dd>
+Minimal standardization,
+and rapid, widespread adoption.
+          </dd>
+          <dt>Motivation</dt>
+          <dd>
+The most common mechanism for protecting access to payment instruments on the
+Web in 2015 is the use of a username and password.
+          </dd>
+        </dl>
+
         <dl id="uc-multifactor" class="dl-horizontal">
           <dt>Multi-Factor</dt>
           <dd>