cziegeler    2003/09/04 23:37:35

  Modified:    src/documentation/xdocs/tracks first-steps-track.xml
               src/documentation/xdocs/howto howto-explore-samples.xml
  Log:
  Make docs valid
  
  Revision  Changes    Path
  1.2       +1 -1      
cocoon-2.1/src/documentation/xdocs/tracks/first-steps-track.xml
  
  Index: first-steps-track.xml
  ===================================================================
  RCS file: 
/home/cvs/cocoon-2.1/src/documentation/xdocs/tracks/first-steps-track.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- first-steps-track.xml     4 Sep 2003 14:08:32 -0000       1.1
  +++ first-steps-track.xml     5 Sep 2003 06:37:35 -0000       1.2
  @@ -52,11 +52,11 @@
                 use a wide variety of tools and
                 technologies, and attempting to understand everything will 
most probably leave you frustrated, so
                 it is better to limit yourself to a subset of the samples.
  +          </p>
                 <note>
                     <em>Blocks</em> are components which are largely 
independent of each other, and which are
                     optional when installing Cocoon.
                 </note>
  -          </p>
          </s1>
         <s1 title="Comments">
           <p>
  
  
  
  1.2       +1 -1      
cocoon-2.1/src/documentation/xdocs/howto/howto-explore-samples.xml
  
  Index: howto-explore-samples.xml
  ===================================================================
  RCS file: 
/home/cvs/cocoon-2.1/src/documentation/xdocs/howto/howto-explore-samples.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- howto-explore-samples.xml 4 Sep 2003 14:08:32 -0000       1.1
  +++ howto-explore-samples.xml 5 Sep 2003 06:37:35 -0000       1.2
  @@ -106,6 +106,7 @@
                       This is fairly simple as the directory structure of the 
samples is similar to the URLs
                       used to access the samples. These simple rules should 
help you find out much more about
                       the samples:
  +                </p>
                       <ul>
                           <li>If using the standard build configuration, 
samples are found under the
                               <em>build/webapp/samples</em> directory. That's 
where you want to look
  @@ -123,7 +124,6 @@
                               files, which map incoming requests to pipelines.
                           </li>
                       </ul>
  -                </p>
               </s2>
           </s1>
   
  
  
  

Reply via email to