cvs: peardoc /en/chapters constitution.xml group.xml standards.xml support.xml /en/chapters/faq devs.xml /en/chapters/installation cvs.xml /en/core/pear/pear loadextension.xml /en/guide/developers documentation.xml packagedef.xml recommendations.xml release.xml /en/guide/developers/package2 tasks.xml /en/guide/migrating customtasks.xml /en/guide/newmaint proposal.xml /en/package/caching/cache-lite intro.xml /en/package/database mdb2-schema.xml /en/package/database/db-table intro-database.xml /en/package/database/db/db-common limitquery.xml /en/package/database/mdb/mdb-common limitquery.xml /en/package/database/mdb2 intro-reverse-module.xml /en/package/database/mdb2-schema intro.xml /en/package/event/event-dispatcher/event-dispatcher post.xml /en/package/filesystem/file-searchreplace getnumoccurences.xml /en/package/html/html-template-sigma/html-template-sigma loadtemplatefile.xml settemplate.xml /en/package/xml/xml-serializer/xml-unserializer unser! ialize.xml

http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/constitution.xml?r1=1.2&r2=1.3&diff_format=u
Index: peardoc/en/chapters/constitution.xml
diff -u peardoc/en/chapters/constitution.xml:1.2 peardoc/en/chapters/constitution.xml:1.3
--- peardoc/en/chapters/constitution.xml:1.2	Sun Dec  2 04:18:11 2007
+++ peardoc/en/chapters/constitution.xml	Wed Jan  9 22:11:56 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8" ?>
-<!-- $Revision: 1.2 $ -->
+<!-- $Revision: 1.3 $ -->
  <chapter id="constitution">
   <chapterinfo>
    <date>2007-03-14</date>
@@ -312,7 +312,7 @@
        <simpara>
         Document all communications and archive them, either through email list or
         some other publicly accessible format like a forum or wiki - the first elected
-        PEAR Group should decide how to do this and amend the consitution.  The PEAR
+        PEAR Group should decide how to do this and amend the constitution.  The PEAR
         Group may occasionally choose to hold secret communications until a bill is
         voted on, and then the communications must be made public.  A summary of
         communications is acceptable, and should at the least document topics debated
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/support.xml?r1=1.10&r2=1.11&diff_format=u
Index: peardoc/en/chapters/support.xml
diff -u peardoc/en/chapters/support.xml:1.10 peardoc/en/chapters/support.xml:1.11
--- peardoc/en/chapters/support.xml:1.10	Sat Nov 25 17:45:59 2006
+++ peardoc/en/chapters/support.xml	Wed Jan  9 22:11:56 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.10 $ -->
+<!-- $Revision: 1.11 $ -->
  <chapter id="support">
   <title>Support</title>
   <simpara>
@@ -59,7 +59,7 @@
      questions. Please read below to get to know, what list
      fits to your needs. The CVS commit list is intended for people
      that are contributing to PEAR: All commits to our revision
-     control system (CVS) are send to this list. The core and QA lists
+     control system (CVS) are sent to this list. The core and QA lists
      are intended for people that want to take part in the development
      of PEAR.
     </para>
@@ -80,7 +80,7 @@
      package etc.
     </para>
     <para>
-     The list is no support forum for question concerning the usage
+     The list is not a support forum for questions concerning the usage
      of PHP. Please use 
      <ulink url="mailto:&email.php.general;">
      &email.php.general;</ulink> instead.
@@ -91,14 +91,14 @@
     <title>The Developers mailing list</title>
 
     <para>
-     As the name already tells you, this list is the place where the
-     developers of PEAR come together to make decisions, to discuss
-     about code and to handle things that are related to this.
+     As the name implies, this list is where the developers of PEAR 
+     come together to make decisions, to discuss code and to handle 
+     things that are related to PEAR.
     </para>
 
     <para>
-     If you are no developer of PEAR itself, this list is of no real
-     interest for you, unless
+     If you are not a developer of PEAR itself, this list is of no real
+     interest to you, unless
      <itemizedlist>
       <listitem>
        <simpara>
@@ -120,7 +120,7 @@
     </para>
 
     <para>
-     The adress for this list is <ulink url="mailto:&email.pear.dev;">
+     The address for this list is <ulink url="mailto:&email.pear.dev;">
      &email.pear.dev;</ulink>.
     </para>
    </sect2>
@@ -130,11 +130,11 @@
 
     <para>
      <ulink url="mailto:&email.pear.doc;">This list</ulink> is the
-     place, where all the things concerning the PEAR documentation,
+     place where all the things concerning the PEAR documentation,
      the manual etc. are discussed.
     </para>
     <para>
-     If you want to help out documenting PEAR packages, don't hesitate
+     If you want to help out documenting PEAR packages don't hesitate
      to drop a mail there.
     </para>
    </sect2>
@@ -143,7 +143,7 @@
     <title>The QA mailing list</title>
 
     <para>
-     People being interested in improving the overall quality of PEAR
+     People interested in improving the overall quality of PEAR
      come together on the <ulink url="mailto:&email.pear.qa;">QA list</ulink>.
     </para>
     <para>
@@ -178,7 +178,7 @@
      <itemizedlist>
       <listitem>
        <simpara>
-        New main features for the PEAR website
+        New features for the PEAR website
        </simpara>
       </listitem>
       <listitem>
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/standards.xml?r1=1.59&r2=1.60&diff_format=u
Index: peardoc/en/chapters/standards.xml
diff -u peardoc/en/chapters/standards.xml:1.59 peardoc/en/chapters/standards.xml:1.60
--- peardoc/en/chapters/standards.xml:1.59	Mon Dec 17 07:16:31 2007
+++ peardoc/en/chapters/standards.xml	Wed Jan  9 22:11:56 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.59 $ -->
+<!-- $Revision: 1.60 $ -->
 
  <chapter id="standards">
   <title>Coding Standards</title>
@@ -1233,7 +1233,7 @@
         section requirements.
       </para>
       <para>
-        Aditionally, each PEAR package must provide a top level
+        Additionally, each PEAR package must provide a top level
         exception, named &lt;Package_Name&gt;_Exception. It is
         considered best practice that the package never throws
         exceptions that aren't descendant from its top level exception.
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/group.xml?r1=1.7&r2=1.8&diff_format=u
Index: peardoc/en/chapters/group.xml
diff -u peardoc/en/chapters/group.xml:1.7 peardoc/en/chapters/group.xml:1.8
--- peardoc/en/chapters/group.xml:1.7	Tue Jan  1 19:25:19 2008
+++ peardoc/en/chapters/group.xml	Wed Jan  9 22:11:56 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.7 $ -->
+<!-- $Revision: 1.8 $ -->
 
  <chapter id="group">
    <title>PEAR Group Administrative Documents</title>
@@ -457,7 +457,7 @@
 
        <para>
          In these two cases PEAR QA should step in and try to get in touch
-         with the specific proposers. If the proposer is no more
+         with the specific proposers. If the proposer is no longer
          interested in the proposal, PEAR QA should search for a new
          maintainer for the package or the proposal should be deleted.
        </para>
@@ -493,8 +493,7 @@
              <listitem>
                <simpara>
                  PEAR QA tries to contact the maintainer 4 weeks after
-                 the proposal is finished and no release has been
-                 throwen.
+                 the proposal is finished and no package has been released.
                </simpara>
              </listitem>
              <listitem>
http://cvs.php.net/viewvc.cgi/peardoc/en/package/filesystem/file-searchreplace/getnumoccurences.xml?r1=1.2&r2=1.3&diff_format=u
Index: peardoc/en/package/filesystem/file-searchreplace/getnumoccurences.xml
diff -u peardoc/en/package/filesystem/file-searchreplace/getnumoccurences.xml:1.2 peardoc/en/package/filesystem/file-searchreplace/getnumoccurences.xml:1.3
--- peardoc/en/package/filesystem/file-searchreplace/getnumoccurences.xml:1.2	Sat Dec 17 23:28:54 2005
+++ peardoc/en/package/filesystem/file-searchreplace/getnumoccurences.xml	Wed Jan  9 22:11:57 2008
@@ -1,4 +1,4 @@
-<!-- $Revision: 1.2 $ -->
+<!-- $Revision: 1.3 $ -->
 <refentry id="package.filesystem.file-searchreplace.getnumoccurences">
    <refnamediv>
     <refname>File_SearchReplace::getNumOccurences()</refname>
@@ -20,7 +20,7 @@
    <refsect1 id="package.filesystem.file-searchreplace.getnumoccurences.desc">
     &title.desc;
     <para>
-     Returns the the number replaced strings after a 
+     Returns the number of replaced strings after a 
      <link linkend="package.filesystem.file-searchreplace.dosearch">
       <function>File_SearchReplace::doSearch</function></link> call.
     </para>
http://cvs.php.net/viewvc.cgi/peardoc/en/guide/migrating/customtasks.xml?r1=1.4&r2=1.5&diff_format=u
Index: peardoc/en/guide/migrating/customtasks.xml
diff -u peardoc/en/guide/migrating/customtasks.xml:1.4 peardoc/en/guide/migrating/customtasks.xml:1.5
--- peardoc/en/guide/migrating/customtasks.xml:1.4	Sun Sep 18 07:11:09 2005
+++ peardoc/en/guide/migrating/customtasks.xml	Wed Jan  9 22:11:57 2008
@@ -1,12 +1,12 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.4 $ -->
+<!-- $Revision: 1.5 $ -->
 <chapter id="guide.migrating.customtasks">
  <chapterinfo>
   <author>
    <firstname>Gregory</firstname>
    <surname>Beaver</surname>
   </author>
-  <date>$Date: 2005/09/18 07:11:09 $</date>
+  <date>$Date: 2008/01/09 22:11:57 $</date>
  </chapterinfo>
  <title>Custom File Tasks</title>
 
@@ -36,8 +36,8 @@
  <simpara>
   This example above would scan the blah.php file at installation, and then use
   <ulink url="&url.php.manual;str_replace"><function>str_replace</function></ulink>
-  to replace all occurences of the string <literal>@token@</literal> with the package's
-  version number.  Then, it would replace all occurences of the string
+  to replace all occurrences of the string <literal>@token@</literal> with the package's
+  version number.  Then, it would replace all occurrences of the string
   <literal>@anothertoken@</literal> with the value of the user's php_dir configuration
   variable.
  </simpara>
@@ -110,7 +110,7 @@
    committed to disk, allowing more complex processing.
   </para>
   <para>
-   All simple tasks must define 3 methods, all multiple task must define 4 methods.
+   All simple tasks must define 3 methods, all multiple tasks must define 4 methods.
    These are:
   </para>
   <para>
http://cvs.php.net/viewvc.cgi/peardoc/en/guide/developers/release.xml?r1=1.18&r2=1.19&diff_format=u
Index: peardoc/en/guide/developers/release.xml
diff -u peardoc/en/guide/developers/release.xml:1.18 peardoc/en/guide/developers/release.xml:1.19
--- peardoc/en/guide/developers/release.xml:1.18	Sun Dec  2 04:18:11 2007
+++ peardoc/en/guide/developers/release.xml	Wed Jan  9 22:11:57 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.18 $ -->
+<!-- $Revision: 1.19 $ -->
 
  <chapter id="developers.release">
   <chapterinfo>
@@ -19,7 +19,7 @@
    <para>
     Rolling a new release requires that the package to which the release
     belongs has been approved by the PEAR developers and that you have a
-    valid PEAR website account. Information about meeting this two
+    valid PEAR website account. Information about meeting these two
     requirements can be found in the chapter <link
     linkend="developers.contributing">Contributing your own code</link>.
    </para>
http://cvs.php.net/viewvc.cgi/peardoc/en/guide/developers/recommendations.xml?r1=1.8&r2=1.9&diff_format=u
Index: peardoc/en/guide/developers/recommendations.xml
diff -u peardoc/en/guide/developers/recommendations.xml:1.8 peardoc/en/guide/developers/recommendations.xml:1.9
--- peardoc/en/guide/developers/recommendations.xml:1.8	Tue Apr 10 19:09:05 2007
+++ peardoc/en/guide/developers/recommendations.xml	Wed Jan  9 22:11:57 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.8 $ -->
+<!-- $Revision: 1.9 $ -->
  <chapter id="developers.recommendations">
   <chapterinfo>
    <author>
@@ -41,7 +41,7 @@
    </para>
       
    <sect2>
-    <title>RGB represesentation</title>
+    <title>RGB representation</title>
     <para>
      The following snippet defines an array that holds the RGB
      definition of the green coloring that is used in the official PEAR
@@ -74,8 +74,8 @@
     <title>RGB representation with alpha-values</title>
     <para>
      Since this an extension of the RGB representation above, it is
-     recommended to use a forth value for alpha-channel-prepresentation. 
-     An example of the <quote>PEAR-green</quote> with aprox. 80% 
+     recommended to use a fourth value for alpha-channel-presentation. 
+     An example of the <quote>PEAR-green</quote> with approximately 80% 
      intensity would be:
 
      <programlisting role="php">
@@ -91,8 +91,8 @@
     <para>
      Please note this is in contrast to the alpha-value used by 
      imagecolorallocate(). The alpha-representation used in PEAR was
-     choosen for consistency with the other RGB values and because it is
-     commonly accepted practise in many other applications
+     chosen for consistency with the other RGB values and because it is
+     commonly accepted practice in many other applications
      (image-processing tools, etc.).
     </para>
    </sect2>
@@ -112,8 +112,8 @@
 ]]>      
      </programlisting>
              
-     Currently the following types are definied, with array-indices from 
-     0..n follwing the colornames listed behind them:
+     Currently the following types are defined, with array-indices from 
+     0..n following the color names listed beside them:
     </para>    
     
     <itemizedlist>
@@ -143,7 +143,7 @@
      Status: Currently Image_Color already offers functions to convert 
      color-names (e.g. "green") and hex-representations-strings (e.g. 
      "#339900") to the PEAR-RGBA-format. We are working to get alpha-
-     channel support added hopefully soon and will later add funtions for 
+     channel support added hopefully soon and will later add functions for 
      CYMK-conversion as well.
     </para>
    </sect2>
http://cvs.php.net/viewvc.cgi/peardoc/en/guide/developers/documentation.xml?r1=1.45&r2=1.46&diff_format=u
Index: peardoc/en/guide/developers/documentation.xml
diff -u peardoc/en/guide/developers/documentation.xml:1.45 peardoc/en/guide/developers/documentation.xml:1.46
--- peardoc/en/guide/developers/documentation.xml:1.45	Thu Jan  3 21:34:28 2008
+++ peardoc/en/guide/developers/documentation.xml	Wed Jan  9 22:11:57 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.45 $ -->
+<!-- $Revision: 1.46 $ -->
  <chapter id="developers.documentation">
 
   <chapterinfo>
@@ -17,7 +17,7 @@
   <titleabbrev>Documentation</titleabbrev>
 
   <para>
-   This chapter provides a detailed description how to write
+   This chapter provides a detailed description of how to write
    documentation using one of the supported formats.
 
    It is aimed at both
@@ -77,8 +77,8 @@
      software on their machine in order to test the validity
      of the documenting efforts.
 
-     A list of the required software and a installation
-     instruction can be found in the
+     A list of the required software and installation
+     instructions can be found in the
      <ulink url="&url.php.manual.howto;">PHP Documentation
      HOWTO</ulink>.
 
@@ -86,7 +86,7 @@
      this HOWTO also provides a ton of other useful
      information that goes far beyond this chapter.
 
-     One is encouraged to completely read it.
+     One is encouraged to read it completely.
      (Chapter II can be skipped, because it only
      contains information that is very PHP specific.)
 
@@ -204,7 +204,7 @@
      <filename>peardoc</filename>.
 
      As a starting point for package
-     documentors <filename>peardoc/en/package/</filename> fits well.
+     documenters <filename>peardoc/en/package/</filename> fits well.
 
      If one has further questions concerning the directory structure, they
      can ask on the <ulink url="mailto:&email.pear.doc;">documentation
@@ -335,7 +335,7 @@
       <para>
        <command>phpdoc</command> generates
        <emphasis>documentation templates</emphasis>. The generated docs are
-       by no mean complete, you need to edit them afterwards!
+       by no means complete, you need to edit them afterwards!
       </para>
      </note>
 
@@ -353,7 +353,7 @@
 
       <para>
         Generating human-readable versions of the DocBook sources requires
-        the existance of the above-mentioned software.
+        the existence of the above-mentioned software.
         The PEAR documentation system uses Unix style makefiles:
       </para>
 
@@ -386,7 +386,7 @@
         <command>./configure --with-dsssl=/sw/share/sgml/dsssl/docbook-dsssl-nwalsh</command>
       </para>
       <para>
-       On Windows, the most easy way to get the DSSSL sheets is to check out
+       On Windows, the easiest way to get the DSSSL sheets is to check out
        the <literal>phpdoc</literal> module on cvs.php.net - they can be
        found in the <filename>dsssl/</filename> subdirectory.
       </para>
@@ -701,7 +701,7 @@
      <listitem>
       <para>
        Provide examples!  Start right away with simple examples that
-       shows the basic feature set -- they will show users how to
+       show the basic feature set -- they will show users how to
        quickly start using the package.
 
        More complex examples will help the users in understanding advanced
@@ -712,12 +712,12 @@
       <para>
        If your package exposes complex interfaces or multiple constants
        that can't be fully explained in one or two examples (which is
-       very likely), do not miss to explain them thoroughly in the
-       documentation.
+       very likely), it is still important to explain them thoroughly 
+       in the documentation.
 
        Document any interfaces that users must use, such
        as a database DSN, command-line arguments for applications,
-       configuration file contents, or any other non-code element.
+       configuration file contents, or any other non-code elements.
       </para>
      </listitem>
      <listitem>
http://cvs.php.net/viewvc.cgi/peardoc/en/guide/developers/packagedef.xml?r1=1.36&r2=1.37&diff_format=u
Index: peardoc/en/guide/developers/packagedef.xml
diff -u peardoc/en/guide/developers/packagedef.xml:1.36 peardoc/en/guide/developers/packagedef.xml:1.37
--- peardoc/en/guide/developers/packagedef.xml:1.36	Tue Apr 10 06:37:05 2007
+++ peardoc/en/guide/developers/packagedef.xml	Wed Jan  9 22:11:57 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.36 $ -->
+<!-- $Revision: 1.37 $ -->
 <!--
      WORK IN PROGRESS, THERE IS PROBABLY LITTLE POINT IN TRANSLATING
      THIS DOCUMENT YET.
@@ -264,7 +264,7 @@
    </sect2>
 
    <sect2 id="developers.packagedef.validating">
-     <title>Validing</title>
+     <title>Validating</title>
 
      <para>
        In order to validate <filename>package.xml</filename> files one
@@ -378,7 +378,7 @@
      single <literal>&lt;file&gt;</literal> tag.
     </para>
     <para>
-     With the knowledge you aquired during this chapter you should now
+     With the knowledge you've acquired from this chapter you should now
      be able to produce a package definition file for your own package.
      If you still have questions concerning the topic, don't hesitate
      to ask on the <ulink url="mailto:&email.pear.general;">mailinglist</ulink>.
@@ -466,7 +466,7 @@
      <example>
       <title><filename>package.xml</filename> with dependencies</title>
       <simpara>
-       The following example shows how to specificy dependencies for
+       The following example shows how to specify dependencies for
        PHP 4.3.0 or better and <classname>XML_Parser</classname> 1.0.
       </simpara>
       <programlisting role="xml">
@@ -600,7 +600,7 @@
          <entry>eq</entry>
          <entry>equal</entry>
          <entry>
-          the the existing capability must exactly match the
+          the existing capability must exactly match the
           version value
          </entry>
          <entry>pkg, ext, php, prog, os, sapi, zend</entry>
http://cvs.php.net/viewvc.cgi/peardoc/en/package/html/html-template-sigma/html-template-sigma/settemplate.xml?r1=1.4&r2=1.5&diff_format=u
Index: peardoc/en/package/html/html-template-sigma/html-template-sigma/settemplate.xml
diff -u peardoc/en/package/html/html-template-sigma/html-template-sigma/settemplate.xml:1.4 peardoc/en/package/html/html-template-sigma/html-template-sigma/settemplate.xml:1.5
--- peardoc/en/package/html/html-template-sigma/html-template-sigma/settemplate.xml:1.4	Wed Oct 20 14:09:59 2004
+++ peardoc/en/package/html/html-template-sigma/html-template-sigma/settemplate.xml	Wed Jan  9 22:11:57 2008
@@ -1,4 +1,4 @@
-<!-- $Revision: 1.4 $ -->
+<!-- $Revision: 1.5 $ -->
 <refentry id="package.html.html-template-sigma.html-template-sigma.settemplate">
    <refnamediv>
     <refname>setTemplate()</refname>
@@ -86,7 +86,7 @@
          <entry><constant>SIGMA_BLOCK_DUPLICATE</constant></entry>
          <entry>The name of a block must be unique within a template. Block 'blockname' found twice.</entry>
          <entry>The <parameter>$template</parameter> contains two blocks sharing the same name</entry>
-         <entry>Check the <parameter>$template</parameter> and rename one of the the blocks to something else</entry>
+         <entry>Check the <parameter>$template</parameter> and rename one of the blocks to something else</entry>
         </row>               
         <row>
          <entry>
http://cvs.php.net/viewvc.cgi/peardoc/en/package/html/html-template-sigma/html-template-sigma/loadtemplatefile.xml?r1=1.4&r2=1.5&diff_format=u
Index: peardoc/en/package/html/html-template-sigma/html-template-sigma/loadtemplatefile.xml
diff -u peardoc/en/package/html/html-template-sigma/html-template-sigma/loadtemplatefile.xml:1.4 peardoc/en/package/html/html-template-sigma/html-template-sigma/loadtemplatefile.xml:1.5
--- peardoc/en/package/html/html-template-sigma/html-template-sigma/loadtemplatefile.xml:1.4	Wed Oct 20 14:09:59 2004
+++ peardoc/en/package/html/html-template-sigma/html-template-sigma/loadtemplatefile.xml	Wed Jan  9 22:11:57 2008
@@ -1,4 +1,4 @@
-<!-- $Revision: 1.4 $ -->
+<!-- $Revision: 1.5 $ -->
 <refentry id="package.html.html-template-sigma.html-template-sigma.loadtemplatefile">
    <refnamediv>
     <refname>loadTemplateFile()</refname>
@@ -98,7 +98,7 @@
          <entry><constant>SIGMA_BLOCK_DUPLICATE</constant></entry>
          <entry>The name of a block must be unique within a template. Block 'blockname' found twice.</entry>
          <entry>The loaded file contains two blocks sharing the same name</entry>
-         <entry>Check the file and rename one of the the blocks to something else</entry>
+         <entry>Check the file and rename one of the blocks to something else</entry>
         </row>               
         <row>
          <entry>
http://cvs.php.net/viewvc.cgi/peardoc/en/package/database/mdb2-schema.xml?r1=1.4&r2=1.5&diff_format=u
Index: peardoc/en/package/database/mdb2-schema.xml
diff -u peardoc/en/package/database/mdb2-schema.xml:1.4 peardoc/en/package/database/mdb2-schema.xml:1.5
--- peardoc/en/package/database/mdb2-schema.xml:1.4	Wed Jun 27 22:44:00 2007
+++ peardoc/en/package/database/mdb2-schema.xml	Wed Jan  9 22:11:57 2008
@@ -1,11 +1,11 @@
 <?xml version="1.0" encoding="ISO-8859-1" ?>
-<!-- $Revision: 1.4 $ -->
-<!-- $Id: mdb2-schema.xml,v 1.4 2007/06/27 22:44:00 ifeghali Exp $ -->
+<!-- $Revision: 1.5 $ -->
+<!-- $Id: mdb2-schema.xml,v 1.5 2008/01/09 22:11:57 saltybeagle Exp $ -->
 <sect1 id="package.database.mdb2-schema">
  <title>MDB2_Schema</title>
 
  <para>
-  PEAR::MDB2_Schema enables users to maintain RDBMS independant schema
+  PEAR::MDB2_Schema enables users to maintain RDBMS independent schema
   files in XML that can be used to create, alter and drop database entities
   and insert data into a database. Reverse engineering database schemas from
   existing databases is also supported. The format is compatible with both
http://cvs.php.net/viewvc.cgi/peardoc/en/package/caching/cache-lite/intro.xml?r1=1.8&r2=1.9&diff_format=u
Index: peardoc/en/package/caching/cache-lite/intro.xml
diff -u peardoc/en/package/caching/cache-lite/intro.xml:1.8 peardoc/en/package/caching/cache-lite/intro.xml:1.9
--- peardoc/en/package/caching/cache-lite/intro.xml:1.8	Sun Nov 19 05:27:50 2006
+++ peardoc/en/package/caching/cache-lite/intro.xml	Wed Jan  9 22:11:57 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.8 $ -->
+<!-- $Revision: 1.9 $ -->
 
 <refentry id="package.caching.cache-lite.intro">
  <refnamediv>
@@ -15,7 +15,7 @@
    anti-corruption tests).
   </para>
   <para>
-   Note : An independant documentation of Cache_Lite is available in chinese
+   Note : An independent documentation of Cache_Lite is available in chinese
    <ulink url="http://rainx.phpmore.com/manual/cache_lite.html">on this
    page</ulink>.
   </para>
http://cvs.php.net/viewvc.cgi/peardoc/en/package/event/event-dispatcher/event-dispatcher/post.xml?r1=1.1&r2=1.2&diff_format=u
Index: peardoc/en/package/event/event-dispatcher/event-dispatcher/post.xml
diff -u peardoc/en/package/event/event-dispatcher/event-dispatcher/post.xml:1.1 peardoc/en/package/event/event-dispatcher/event-dispatcher/post.xml:1.2
--- peardoc/en/package/event/event-dispatcher/event-dispatcher/post.xml:1.1	Sat Apr  2 22:41:15 2005
+++ peardoc/en/package/event/event-dispatcher/event-dispatcher/post.xml	Wed Jan  9 22:11:57 2008
@@ -1,4 +1,4 @@
-<!-- $Revision: 1.1 $ -->
+<!-- $Revision: 1.2 $ -->
 <refentry id="package.event.event-dispatcher.event-dispatcher.post">
    <refnamediv>
     <refname><function>Event_Dispatcher::post</function></refname>
@@ -78,7 +78,7 @@
       </para>
       <para>
        This behaviour can be turned off in order to make sure that only the observers
-       added the the posting dispatcher will be notified. This allows you to differentiate
+       added the posting dispatcher will be notified. This allows you to differentiate
        between global and local notifications.
       </para>
      </listitem>
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/installation/cvs.xml?r1=1.1&r2=1.2&diff_format=u
Index: peardoc/en/chapters/installation/cvs.xml
diff -u peardoc/en/chapters/installation/cvs.xml:1.1 peardoc/en/chapters/installation/cvs.xml:1.2
--- peardoc/en/chapters/installation/cvs.xml:1.1	Sat Nov 25 17:38:55 2006
+++ peardoc/en/chapters/installation/cvs.xml	Wed Jan  9 22:11:57 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.1 $ -->
+<!-- $Revision: 1.2 $ -->
   <sect1 id="installation.cvs">
    <title>CVS installer</title>
 
@@ -51,9 +51,9 @@
     </listitem>
     <listitem>
      <para>
-      Check the <filename>package.xml</filename> file, especially the fileset entries.
+      Check the <filename>package.xml</filename> file, especially the dir and file entries.
       They must match the existing files and directory structure. If they differ, contact
-      the maintainer and ask for an update of <filename>package.xml</filename>.
+      the package maintainer and ask for an update of the <filename>package.xml</filename>.
      </para>
     </listitem>
     <listitem>
@@ -64,7 +64,7 @@
     </listitem>
     <listitem>
      <para>
-      If you have already the package installed: remove it to avoid versions problems:
+      If you have already installed the package: remove it to avoid version conflicts:
       <command>pear uninstall &lt;package&gt;</command>
      </para>
     </listitem>
@@ -74,14 +74,14 @@
       <command>pear install &lt;package-file&gt;</command>
      </para>
      <para>
-      Now, you have an CVS version installed!
+      Now, you have a CVS version installed!
      </para>
     </listitem>
    </orderedlist>
    <para>
-    You should upgrade to a official release of the package as early as possible.
+    You should upgrade to an official release of the package as early as possible.
     Before you install the official release, uninstall the CVS version to avoid
-    version problems.
+    version conflicts.
    </para>
   </sect1>
 <!-- Keep this comment at the end of the file
http://cvs.php.net/viewvc.cgi/peardoc/en/package/xml/xml-serializer/xml-unserializer/unserialize.xml?r1=1.4&r2=1.5&diff_format=u
Index: peardoc/en/package/xml/xml-serializer/xml-unserializer/unserialize.xml
diff -u peardoc/en/package/xml/xml-serializer/xml-unserializer/unserialize.xml:1.4 peardoc/en/package/xml/xml-serializer/xml-unserializer/unserialize.xml:1.5
--- peardoc/en/package/xml/xml-serializer/xml-unserializer/unserialize.xml:1.4	Thu Jan  8 21:53:20 2004
+++ peardoc/en/package/xml/xml-serializer/xml-unserializer/unserialize.xml	Wed Jan  9 22:11:57 2008
@@ -1,4 +1,4 @@
-<!-- $Revision: 1.4 $ -->
+<!-- $Revision: 1.5 $ -->
 <refentry id="package.xml.xml-serializer.xml-unserializer.unserialize">
  <refnamediv>
   <refname><function>XML_Unserializer::unserialize</function></refname>
@@ -47,7 +47,7 @@
     <listitem>
      <para>
       <parameter>array $options</parameter> - Options to override the options that have been set previously.
-      The options will only be used for this unserialization and then reset the the options you set before.
+      The options will only be used for this unserialization and then reset the options you set before.
      </para>
     </listitem>
    </itemizedlist>
http://cvs.php.net/viewvc.cgi/peardoc/en/guide/developers/package2/tasks.xml?r1=1.7&r2=1.8&diff_format=u
Index: peardoc/en/guide/developers/package2/tasks.xml
diff -u peardoc/en/guide/developers/package2/tasks.xml:1.7 peardoc/en/guide/developers/package2/tasks.xml:1.8
--- peardoc/en/guide/developers/package2/tasks.xml:1.7	Mon Oct 22 21:32:43 2007
+++ peardoc/en/guide/developers/package2/tasks.xml	Wed Jan  9 22:11:57 2008
@@ -1,4 +1,4 @@
-<!-- $Revision: 1.7 $ -->
+<!-- $Revision: 1.8 $ -->
 <refentry id="guide.developers.package2.tasks">
  <refnamediv>
   <refname>tasks for &lt;file&gt;s</refname>
@@ -46,7 +46,7 @@
      </listitem>
      <listitem>
       <para>
-       <emphasis>to</emphasis> - Abstract item to use as a replacement for all occurences of
+       <emphasis>to</emphasis> - Abstract item to use as a replacement for all occurrences of
        &quot;from&quot;.  package-info replacements can be one of api-state, api-version, channel,
        date, description, license, license-uri, name, notes, release_date, release-license, release_notes,
        state, summary, time, version, and for some packages extends, providesextension, srcpackage, and srcuri.
http://cvs.php.net/viewvc.cgi/peardoc/en/guide/newmaint/proposal.xml?r1=1.19&r2=1.20&diff_format=u
Index: peardoc/en/guide/newmaint/proposal.xml
diff -u peardoc/en/guide/newmaint/proposal.xml:1.19 peardoc/en/guide/newmaint/proposal.xml:1.20
--- peardoc/en/guide/newmaint/proposal.xml:1.19	Fri Mar 23 03:15:11 2007
+++ peardoc/en/guide/newmaint/proposal.xml	Wed Jan  9 22:11:57 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.19 $ -->
+<!-- $Revision: 1.20 $ -->
  <chapter id="newmaint.proposal">
   <chapterinfo>
    <author>
@@ -10,7 +10,7 @@
     <firstname>Tobias</firstname>
     <surname>Schlitt</surname>
    </author>
-   <date>$Date: 2007/03/23 03:15:11 $</date>
+   <date>$Date: 2008/01/09 22:11:57 $</date>
   </chapterinfo>
   <title>The formal proposal process</title>
   <titleabbrev>Proposing</titleabbrev>
@@ -36,7 +36,7 @@
    do once the proposal is finished.
   </simpara>
   <simpara>
-   After reading this chapter, you will will be able to start a proposal
+   After reading this chapter, you will be able to start a proposal
    for your code right away.
   </simpara>
 
@@ -149,7 +149,7 @@
 
    <simpara>
     For every package you should start a proposal in PEPr 
-    as a draft to initiate dicussion on the <ulink
+    as a draft to initiate discussion on the <ulink
     url="mailto:&email.pear.dev;">developers mailing list</ulink>.
    </simpara>
 
@@ -236,7 +236,7 @@
      it, view it and it is shown up on the PEPr overview page as a
      draft. This stage is for you to play around with PEPr, to shape
      your proposal nicely and to prepare it for the proposal
-     process. You can switch to the next stage when ever you want to
+     process. You can switch to the next stage whenever you want to
      publish your proposal and get feedback from the PEAR community.
     </para>
    </sect2>
@@ -269,7 +269,7 @@
      proposal. Votes are given using the numbers -1, 0 and +1, where
      -1 means <quote>I'm against this package to be added to PEAR in the
      current form,</quote> +1 says
-     <quote>I'm in favour of getting this package
+     <quote>I'm in favor of getting this package
      into PEAR in the current form</quote> and 0 means
      <quote>I have looked at your
      package, but I am undecided.</quote> The time to vote for a package
@@ -280,7 +280,7 @@
     </para>
     <para>
      Votes on proposals can be bound to a condition. These conditional
-     votes indicate that you have to fulfil a certain condition the
+     votes indicate that you have to fulfill a certain condition the
      voters expect to be fulfilled. If there are conditional votes you
      are expected to read and follow them! The conditions on a vote
      will be provided in the votes comment. Each vote
http://cvs.php.net/viewvc.cgi/peardoc/en/package/database/db-table/intro-database.xml?r1=1.6&r2=1.7&diff_format=u
Index: peardoc/en/package/database/db-table/intro-database.xml
diff -u peardoc/en/package/database/db-table/intro-database.xml:1.6 peardoc/en/package/database/db-table/intro-database.xml:1.7
--- peardoc/en/package/database/db-table/intro-database.xml:1.6	Sun Jul  1 03:40:42 2007
+++ peardoc/en/package/database/db-table/intro-database.xml	Wed Jan  9 22:11:57 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="ISO-8859-1" ?>
-<!-- $Revision: 1.6 $ -->
+<!-- $Revision: 1.7 $ -->
 
 <refentry id="package.database.db-table.intro-database">
  <refnamediv>
@@ -1026,7 +1026,7 @@
 </para>
 <para>
 For example, the following code would change the 'on_update' action 
-associated with the the reference from 'PersonPhone' to 'Person' to 
+associated with the reference from 'PersonPhone' to 'Person' to 
 a 'restrict' action:
 <programlisting role="php">
 <![CDATA[<?php
http://cvs.php.net/viewvc.cgi/peardoc/en/package/database/mdb2-schema/intro.xml?r1=1.4&r2=1.5&diff_format=u
Index: peardoc/en/package/database/mdb2-schema/intro.xml
diff -u peardoc/en/package/database/mdb2-schema/intro.xml:1.4 peardoc/en/package/database/mdb2-schema/intro.xml:1.5
--- peardoc/en/package/database/mdb2-schema/intro.xml:1.4	Wed Jun 27 22:43:25 2007
+++ peardoc/en/package/database/mdb2-schema/intro.xml	Wed Jan  9 22:11:57 2008
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="ISO-8859-1" ?>
-<!-- $Revision: 1.4 $ -->
-<!-- $Id: intro.xml,v 1.4 2007/06/27 22:43:25 ifeghali Exp $ -->
+<!-- $Revision: 1.5 $ -->
+<!-- $Id: intro.xml,v 1.5 2008/01/09 22:11:57 saltybeagle Exp $ -->
 <refentry id="package.database.mdb2-schema.intro">
   <refnamediv>
     <refname>Introduction</refname>
@@ -18,7 +18,7 @@
       and Foreign Keys.
     </para>
     <para>
-      It enables users to maintain RDBMS independant
+      It enables users to maintain RDBMS independent
       schema files in XML that can be used to create, alter and
       drop database entities (also called as DDL: Data Definition
       Language) and insert data (also called as DML: Data
http://cvs.php.net/viewvc.cgi/peardoc/en/core/pear/pear/loadextension.xml?r1=1.3&r2=1.4&diff_format=u
Index: peardoc/en/core/pear/pear/loadextension.xml
diff -u peardoc/en/core/pear/pear/loadextension.xml:1.3 peardoc/en/core/pear/pear/loadextension.xml:1.4
--- peardoc/en/core/pear/pear/loadextension.xml:1.3	Tue Oct 14 22:54:02 2003
+++ peardoc/en/core/pear/pear/loadextension.xml	Wed Jan  9 22:11:57 2008
@@ -1,8 +1,8 @@
-<!-- $Revision: 1.3 $ -->
+<!-- $Revision: 1.4 $ -->
   <refentry id="core.pear.pear.loadextension">
    <refnamediv>
     <refname>PEAR::loadExtension()</refname>
-    <refpurpose>OS independant PHP extension load</refpurpose>
+    <refpurpose>OS independent PHP extension load</refpurpose>
    </refnamediv>
    <refsynopsisdiv>
     <funcsynopsis>
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/faq/devs.xml?r1=1.3&r2=1.4&diff_format=u
Index: peardoc/en/chapters/faq/devs.xml
diff -u peardoc/en/chapters/faq/devs.xml:1.3 peardoc/en/chapters/faq/devs.xml:1.4
--- peardoc/en/chapters/faq/devs.xml:1.3	Sat Dec 16 11:40:19 2006
+++ peardoc/en/chapters/faq/devs.xml	Wed Jan  9 22:11:57 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8"?>
-<!-- $Revision: 1.3 $ -->
+<!-- $Revision: 1.4 $ -->
 <sect1 id="faq.devs">
  <title>Developer FAQ</title>
 
@@ -182,7 +182,7 @@
    </para>
   <para>
     Test scripts are recommended when your class has to be compiled,
-    requires special extentions/programs or needs correctly installed
+    requires special extensions/programs or needs correctly installed
     additional files (i.e. templates, graphics). Store them in sub
     directory called 'tests'.
    </para>
http://cvs.php.net/viewvc.cgi/peardoc/en/package/database/db/db-common/limitquery.xml?r1=1.28&r2=1.29&diff_format=u
Index: peardoc/en/package/database/db/db-common/limitquery.xml
diff -u peardoc/en/package/database/db/db-common/limitquery.xml:1.28 peardoc/en/package/database/db/db-common/limitquery.xml:1.29
--- peardoc/en/package/database/db/db-common/limitquery.xml:1.28	Wed Apr 11 04:44:49 2007
+++ peardoc/en/package/database/db/db-common/limitquery.xml	Wed Jan  9 22:11:57 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.28 $ -->
+<!-- $Revision: 1.29 $ -->
 
 <refentry id="package.database.db.db-common.limitquery">
  <refnamediv>
@@ -30,7 +30,7 @@
  <refsect1 id="package.database.db.db-common.limitquery.desc">
   &title.desc;
   <para>
-   Executes a SQL query, but fetches only the the specificed
+   Executes a SQL query, but fetches only the specificed
    count of rows. It is an emulation of the MySQL LIMIT option.
   </para>
  </refsect1>
http://cvs.php.net/viewvc.cgi/peardoc/en/package/database/mdb2/intro-reverse-module.xml?r1=1.4&r2=1.5&diff_format=u
Index: peardoc/en/package/database/mdb2/intro-reverse-module.xml
diff -u peardoc/en/package/database/mdb2/intro-reverse-module.xml:1.4 peardoc/en/package/database/mdb2/intro-reverse-module.xml:1.5
--- peardoc/en/package/database/mdb2/intro-reverse-module.xml:1.4	Fri Jan  4 17:41:05 2008
+++ peardoc/en/package/database/mdb2/intro-reverse-module.xml	Wed Jan  9 22:11:57 2008
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1" ?>
-<!-- $Revision: 1.4 $ -->
+<!-- $Revision: 1.5 $ -->
 
 <refentry id="package.database.mdb2.intro-reverse-module">
  <refnamediv>
@@ -261,7 +261,7 @@
   In addition to the information found in the default output, a notation of the
   number of columns is provided by the <parameter>num_fields</parameter> element
   while the order element provides an array with the column names as the keys
-  and their location index number (corresponding to the keys in the the default
+  and their location index number (corresponding to the keys in the default
   output) as the values.
 
   <example>
http://cvs.php.net/viewvc.cgi/peardoc/en/package/database/mdb/mdb-common/limitquery.xml?r1=1.4&r2=1.5&diff_format=u
Index: peardoc/en/package/database/mdb/mdb-common/limitquery.xml
diff -u peardoc/en/package/database/mdb/mdb-common/limitquery.xml:1.4 peardoc/en/package/database/mdb/mdb-common/limitquery.xml:1.5
--- peardoc/en/package/database/mdb/mdb-common/limitquery.xml:1.4	Wed Aug 13 16:01:02 2003
+++ peardoc/en/package/database/mdb/mdb-common/limitquery.xml	Wed Jan  9 22:11:57 2008
@@ -1,4 +1,4 @@
-<!-- $Revision: 1.4 $ -->
+<!-- $Revision: 1.5 $ -->
 <refentry id="package.database.mdb.mdb-common.limitquery">
  <refnamediv>
   <refname>MDB_Common::limitQuery()</refname>
@@ -29,7 +29,7 @@
  <refsect1 id="package.database.mdb.mdb-common.limitquery.desc">
     &title.desc;
     <para>
-     Executes a SQL query, but fetches only the the specificed
+     Executes a SQL query, but fetches only the specificed
      count of rows. It is an emulation of the MySQL LIMIT option.
     </para>
  </refsect1>