diff --git a/TTPAssistedAssurancePolicy.html b/TTPAssistedAssurancePolicy.html
index 66eb03e..2d87d70 100644
--- a/TTPAssistedAssurancePolicy.html
+++ b/TTPAssistedAssurancePolicy.html
@@ -329,12 +329,14 @@
     <p>
      The paperwork is sent to the Assurer by the TTP.
     </p>
-     <span class="q">
-      <p>Old: sending a Remote Assurance Form and copies of identity documents to the Assurer by mutually agreed medium (eg post, web form or encrypted email).</p>
-      <p>iang:  this clause <B>is similar</B> to the requirement DRC C.9.b:</p>
+     <ul class="q">
+      <li>Old: sending a Remote Assurance Form and copies of identity documents to the Assurer by mutually agreed medium (eg post, web form or encrypted email).</li>
+      <li>iang:  this requirement was informed by DRC C.9.b:</li>
         <blockquote><u>"RAs provide the CA with complete documentation on each verified applicant for a certificate."</u></blockquote>
-      <p>What is different is that the criteria requires the TTP to send the form, not the Member.</p>
-     </span>
+      <li>What is different?  In the old version of TTP, the TTP was the RA.  Thus the criteria would require the TTP to send the form, not the Member.</li>
+      <li> However in the new TTP-assisted version of assurance, the Assurer is the RA, and the existing arrangement of the RA's documentation process (forms provided to Arbitrator) are workable.  Also note responsibility laid out in 3.d, the TTP-assist assurer makes a CARS of the Assurance Statement over the subject member.  Ergo the Assurer is the RA, and is the responsible party.</li>
+      <li> Hence, the above point 5. is likely going to change. </li>
+     </ul>
   </li></ol>
 
  <h3 id="s3.3"> 3.3 Completion of the Assurance  </h3>