.

index.bs

@@ -7678,19 +7678,19 @@ This extension allows for a simple form of transaction authorization. A
        1. use a dialog to the user that makes sense in the context of approving a transaction (as opposed to sign in).
        1. display the transaction text to the user. The client SHOULD
              indicate that the transaction text originates from a specific relying party
-	     (as opposed to the platform itself).
-	     
+             (as opposed to the platform itself).
+
        1. use the {{CollectedClientTxAuthSimple2Data}} structure containing the transaction text instead of using
              the {{CollectedClientData}} structure.
-	     
+
        1. pass-through the extension to the authenticator (see "client extension output" below)
        1. pass-through the "authenticator extension output" to the caller as part of the assertion
 
 
     <div class="issue">
       Should we keep the "type" on "authenticate" or change to something closer to transaction (SPC uses 'payment.get')?
 
-      Should we change the name back to txAuthSimple - cannot really hurt - but makes it easier for authenticators already implementing it.
+      Should we change the name back to txAuthSimple - cannot really hurt as no platform supports it today and authenticator implementations don't have to change.
     </div>
 
     <xmp class="idl">