avalon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ne...@apache.org
Subject cvs commit: avalon-excalibur/event/src/xdocs cpuparser-howto.xml event-howto.xml mpool-howto.xml mpool.xml
Date Sun, 26 Oct 2003 12:33:25 GMT
neeme       2003/10/26 04:33:25

  Modified:    event/src/xdocs cpuparser-howto.xml event-howto.xml
                        mpool-howto.xml mpool.xml
  Log:
  fixed some spelling and other mistakes
  
  Revision  Changes    Path
  1.4       +3 -3      avalon-excalibur/event/src/xdocs/cpuparser-howto.xml
  
  Index: cpuparser-howto.xml
  ===================================================================
  RCS file: /home/cvs/avalon-excalibur/event/src/xdocs/cpuparser-howto.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- cpuparser-howto.xml	20 Feb 2003 14:25:21 -0000	1.3
  +++ cpuparser-howto.xml	26 Oct 2003 12:33:25 -0000	1.4
  @@ -10,7 +10,7 @@
     <body>
       <section><title>System Util Design</title>
         <p>
  -        SystemUtil determins which CPUParser it needs by examining
  +        SystemUtil determines which CPUParser it needs by examining
           the results from <code>System.getProperty( "os.name" )</code>.
           It strips all the whitespace from the name, and appends it
           to the <code>org.apache.excalibur.util.system</code> package.
  
  
  
  1.6       +2 -2      avalon-excalibur/event/src/xdocs/event-howto.xml
  
  Index: event-howto.xml
  ===================================================================
  RCS file: /home/cvs/avalon-excalibur/event/src/xdocs/event-howto.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- event-howto.xml	20 Feb 2003 14:25:22 -0000	1.5
  +++ event-howto.xml	26 Oct 2003 12:33:25 -0000	1.6
  @@ -159,7 +159,7 @@
           There are some other methods that are utility methods:
           <code>maxSize()</code>, <code>isFull()</code>,
           <code>canAccept()</code>, <code>size()</code>.  They help
  -        yoy in your planning.  Use <code>maxSize()</code> to determine
  +        you in your planning.  Use <code>maxSize()</code> to determine
           the bounds of the Sink.  If the value returned is -1, then
           there are no bounds.  If the value is positive, then that
           is the limit of the number of events the Sink can have at
  
  
  
  1.4       +4 -4      avalon-excalibur/event/src/xdocs/mpool-howto.xml
  
  Index: mpool-howto.xml
  ===================================================================
  RCS file: /home/cvs/avalon-excalibur/event/src/xdocs/mpool-howto.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- mpool-howto.xml	20 Feb 2003 14:25:22 -0000	1.3
  +++ mpool-howto.xml	26 Oct 2003 12:33:25 -0000	1.4
  @@ -111,7 +111,7 @@
       </section>
       <section><title>Using the Pool</title>
         <p>
  -        Using the pools are quite simple:
  +        Using the pools is quite simple:
         </p>
         <source>
           <![CDATA[
  @@ -124,9 +124,9 @@
         </source>
         <p>
           What if we have an object that needs to perform some simple
  -        clieanup?  Have your Object implement the <code>Resettable</code>
  +        cleanup?  Have your Object implement the <code>Resettable</code>
           interface.  What if we are migrating from the old Pool package?
  -        you don't have to do anything.  MPool knows about the old Pool
  +        You don't have to do anything.  MPool knows about the old Pool
           package, and will check for its recyclable method.  It will only
           call the Resettable.reset() method if your object implements both
           interfaces.  Both of these will work:
  
  
  
  1.4       +2 -2      avalon-excalibur/event/src/xdocs/mpool.xml
  
  Index: mpool.xml
  ===================================================================
  RCS file: /home/cvs/avalon-excalibur/event/src/xdocs/mpool.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- mpool.xml	20 Feb 2003 14:25:22 -0000	1.3
  +++ mpool.xml	26 Oct 2003 12:33:25 -0000	1.4
  @@ -51,7 +51,7 @@
             An Object Factory is what the pools use to create new objects
             or destroy old ones.  They are particularly helpful when there
             is a complex creation/destruction policy.  They are also essential
  -          for ManagablePools.
  +          for ManageablePools.
           </p>
         </section>
         <section><title>Pool</title>
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org


Mime
View raw message