Added some small improvements to documentation

js/rhino/docs/footprint.html

@@ -32,7 +32,7 @@ classes on the fly. Removing <tt>org.mozilla.javascript.JavaAdapter</tt> will di
 
 <h3>Class generation library</h3>
 <p>
-If you do not include Optimizer or JavaAdapter, then you do not need Rhino library for class file generation and you can remove all the classes from in <tt>org.mozilla.classfile</tt> package.
+If you do not include Optimizer or JavaAdapter, nor do you use PolicySecurityController then you do not need Rhino library for class file generation and you can remove all the classes from in <tt>org.mozilla.classfile</tt> package.
 
 <h3>Regular Expressions</h3>
 <p>

js/rhino/docs/opt.html

@@ -15,19 +15,21 @@ Optimization</H1></CENTER>
 Optimization settings</H2>
 <P>The currently supported optimization settings are:</P>
 
-<P><B>-1</B>
+<P><B>-1</B></P>
 
-<P><B></B>Interpretive mode is always 
-used. The compilation time is minimized at the expense of runtime performance. 
-No class files are generated, which may improve memory usage depending on your 
-system.
+<p>Interpretive mode is always used. The compilation time is minimized at the 
+expense of runtime performance. No class files are generated, which may improve
+memory usage depending on your system. Another benefit of the interpreted mode
+is that the interpreter performs tail-call elimination of recursive functions.
+Also, you must use this optimization level if your code uses Continuation 
+objects.
 <p>
 If the optimization package is not available, then optimization acts as if it is always -1.
-</P>
+</p>
 
 <P><B>0</B>
 
-<P><B></B>No optimizations are 
+<P>No optimizations are 
 performed. The bytecode compiler runs fastest in this mode, but the generated byte code 
 is less efficient.</P>