Index: docs/site/code-standards.html
===================================================================
RCS file: /home/cvspublic/jakarta-jetspeed/docs/site/code-standards.html,v
retrieving revision 1.35
diff -u -r1.35 code-standards.html
--- code-standards.html	1 Aug 2003 20:58:10 -0000	1.35
+++ code-standards.html	25 Aug 2003 08:19:27 -0000
@@ -130,7 +130,7 @@
         </font>
       </td></tr>
       <tr><td>
-        <blockquote>
+        <blockquote style="width:450px;">
                                     <ul>
             <li>
             Use javadoc on all methods.
@@ -179,7 +179,7 @@
         </font>
       </td></tr>
       <tr><td>
-        <blockquote>
+        <blockquote style="width:450px;">
                                     <p>
 A Java style checker, checkStyle, is part of the build process.  This should aid
 in the development of readable code.  Jetspeed currently works with version 2.4 of 
@@ -244,7 +244,7 @@
     </tr>
     </table>
     </div>
-                                                <p>
+                                                <p style="width:450px;">
 Use of brackets.  Some developers have personal a preference to
 how they place brackets within their source code:
 </p>
@@ -281,11 +281,11 @@
     </tr>
     </table>
     </div>
-                                                <p>
+                                                <p style="width:450px;">
 Please choose whatever style you want for new files but you should
 maintain the existing style of source you wish to modify.
 </p>
-                                                <p>
+                                                <p style="width:450px;">
 If you have a method with multiple parameters, separate them across
 multiple lines.
 </p>
@@ -339,8 +339,8 @@
       </td></tr>
       <tr><td>
         <blockquote>
-                                    <p>
-          Testing is a great way to detect and prevent bug.  By automating the
+                                    <p style="width:450px;">
+          Testing is a great way to detect and prevent bugs.  By automating the
           testing process, the test are easy to run and identify failures.  
           Jetspeed uses the testing facilities built into Ant, primarily Cactus
           and JUnit. 
@@ -352,7 +352,7 @@
         </font>
       </td></tr>
       <tr><td>
-        <blockquote>
+        <blockquote style="width:450px;">
                                     <ul>
             <li>
               The name of test class should start with <code>Test</code> and be
@@ -389,7 +389,7 @@
         <blockquote>
                                     <br />
                                                 <strong>Required Tests</strong>
-                                                <p>
+                                                <p style="width:450px;">
             The required tests are made up of Cactus and JUnit test used to 
             insure working, and hopefully bug free, code.  
           </p>
@@ -445,7 +445,7 @@
             </table>
                                                 <br />
                                                 <strong>Unit Test Groups</strong>
-                                                <p>
+                                                <p style="width:450px;">
             These are unit tests grouped logically.  In some case their is a
             testing hierarchy.  In the case of unittest-security.  It is composed
             of the security implementation test, i.e. unittest-security-registry
@@ -515,7 +515,7 @@
         </font>
       </td></tr>
       <tr><td>
-        <blockquote>
+        <blockquote style="width:450px;">
                                     <p>
             Cactus testing is used when rundata is required.  The test usually
             involve generating a URL in begin<i>TestName</i>(). The URL is 
@@ -546,7 +546,7 @@
         </font>
       </td></tr>
       <tr><td>
-        <blockquote>
+        <blockquote style="width:450px;">
                                     <p>
             JUnit testing is simpler the Cactus testing, in part because the do
             not require a web server.  These test generally test small functional
@@ -585,7 +585,7 @@
         </font>
       </td></tr>
       <tr><td>
-        <blockquote>
+        <blockquote style="width:450px;">
                                     <p>
             Enter the property in the language propery file, 
             <code>org.apache.jetspeed.modules.localization.JetspeedProperty_</code>
@@ -629,7 +629,7 @@
         </font>
       </td></tr>
       <tr><td>
-        <blockquote>
+        <blockquote style="width:450px;">
                                     <p>
           The following code will place the localized, based on the user's 
           language, value into the variable <code>title</code>.
@@ -669,7 +669,7 @@
       </td></tr>
       <tr><td>
         <blockquote>
-                                    <p>
+                                    <p style="width:450px;">
           The following code will center the localized, based on the user's 
           language, value on the resulting portlet.
         </p>
@@ -710,7 +710,7 @@
         </font>
       </td></tr>
       <tr><td>
-        <blockquote>
+        <blockquote style="width:450px;">
                                     <p>
       Logging is very useful for diagnosing and resolving problems. As a general rule, all exceptions should be logged, 
       and done so in the following fashion: <br />
@@ -762,7 +762,7 @@
     </tr>
     </table>
     </div>
-                                                <p>
+                                                <p style="width:450px;">
       The following code snippet shows how to use the new logging features.
     </p>
                                                     <div align="left">
@@ -822,7 +822,7 @@
         </font>
       </td></tr>
       <tr><td>
-        <blockquote>
+        <blockquote style="width:450px;">
                                     <ul>
             <li>
             File structuring.  Try to keep everything organized according to the 
@@ -849,7 +849,7 @@
         </font>
       </td></tr>
       <tr><td>
-        <blockquote>
+        <blockquote style="width:450px;">
                                     <p>
       All changes posted by non-committers should be submitted (and accepted) in form
       of patches. Patches can be created from root of the project using the this command: