Fixed another of Karens nits
author"arangana <arun@mozilla.com>"
Fri, 12 Jul 2013 15:38:58 -0400
changeset 35 6058d05f659f
parent 34 ebe63375c830
child 36 02b1cd05d07d
Fixed another of Karens nits
Overview.html
--- a/Overview.html	Fri Jul 12 15:13:11 2013 -0400
+++ b/Overview.html	Fri Jul 12 15:38:58 2013 -0400
@@ -380,7 +380,7 @@
 <p>Karen now has at least one identity, namely her email of choice, verified on Persona.org, along with a certificate issued by Persona.org.  She then decides to log in to the PSS website using that identity.  The following sequence then takes place:</p>
 <ol>
 <li><p>Karen accesses the website of the PSS, and then clicks on the "Log in with Persona" link.  The log-in link loads script from Persona.org in an <code>iframe</code>, which creates an assertion structure as a JWT [[JWT]].  The assertion consists of the name of the Relying Party, also referred to as an <em>audience</em>, and a validity period.  This assertion is signed using the private key that was created previously. [<a title="keycall">KEYCALL</a> | <a title="sign">SIGN</a>]</p></li>
-<li>The signed assertion is then combined with the certificate created previously into a new [[JWT]] structure, which might look like this:
+<li>Within script loaded by Persona.org, the signed assertion is then combined with the certificate created previously into a new [[JWT]] structure, which might look like this:
   <pre class="example highlight prettyprint">
   // This is for illustrative purposes only
   // Proper use of JWT uses Base64