1.1 --- a/docs/in-page-updates.html Sat Dec 03 01:52:11 2005 +0000
1.2 +++ b/docs/in-page-updates.html Sat Dec 03 01:53:18 2005 +0000
1.3 @@ -50,7 +50,7 @@
1.4 <ol>
1.5 <li>Inside this new <code>options</code> element, investigate
1.6 the values associated with the <code>type</code> element.</li>
1.7 - <li>If any of the selected type values is "Personal", make a new <code>comment</code>
1.8 + <li>If any of the selected type values represents the "Personal" category, make a new <code>comment</code>
1.9 element, then add any attributes that may be found on
1.10 existing <code>comment</code> elements within the current <code>type</code>
1.11 element.</li>
1.12 @@ -194,7 +194,9 @@
1.13 <p>Instead of just obtaining a stylesheet for the <code>structure</code>
1.14 document, we instead check to see if an in-page update is being
1.15 requested and, if so, prepare the stylesheet representing the fragment
1.16 -of the Web form to be presented. Additionally, we obtain special stylesheet parameters using the raw request parameters; this introduces information that will be used to control the
1.17 +of the Web form to be presented. Additionally, we obtain special
1.18 +stylesheet parameters using the raw request parameters; this introduces
1.19 +information that will be used to control the
1.20 stylesheet when making the final Web page output.</p>
1.21 <p>Finally, we send the output to the user but employing the additional
1.22 stylesheet parameters to configure the result:</p>
1.23 @@ -220,4 +222,4 @@
1.24 script file; otherwise it gets a Web page showing either all of the
1.25 form (if a normal request is received), or a part of the form (if an
1.26 in-page request is received).</p>
1.27 -</body></html>
1.28 +</body></html>
1.29 \ No newline at end of file