cvs: peardoc /en/chapters installation.xml

ohill Fri Feb 6 11:18:06 2004 EDT Modified files: /peardoc/en/chapters installation.xml Log: Fixing typos http://cvs.php.net/diff.php/peardoc/en/chapters/installation.xml?r1=1.15&r2=1.16&ty=u Index: peardoc/en/chapters/installation.xml diff -u peardoc/en/chapters/installation.xml:1.15 peardoc/en/chapters/installation.xml:1.16 --- peardoc/en/chapters/installation.xml:1.15 Fri Feb 6 11:07:16 2004 +++ peardoc/en/chapters/installation.xml Fri Feb 6 11:18:05 2004 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1" ?> -<!-- $Revision: 1.15 $ --> +<!-- $Revision: 1.16 $ --> <!-- WORK IN PROGRESS, THERE IS PROBABLY LITTLE POINT IN TRANSLATING THIS DOCUMENT YET. @@ -381,7 +381,7 @@ </orderedlist> </para> <para> - If you more questions concerning manual installation, you can ask + If you have more questions concerning manual installation, you can ask on the <ulink url="&email.pear.general;">user mailing list</ulink>. </para> @@ -392,18 +392,18 @@ <title>CVS installer</title> <para> - This passage will describe how you install the latest development + This passage will describe how to install the latest development version of a PEAR package from CVS. </para> <para> - It is NOT recommended to run a package from CVS in working enviroments! - Because CVS versions are no regulare releases, this means: + It is NOT recommended to run a package from CVS in working environments! + Because CVS versions are not regular releases, this means: <itemizedlist> <listitem> <simpara>You could get no kind of help from the maintainer or anybody other.</simpara> </listitem> <listitem> - <simpara>Versions in CVS may break the upgrade mechanismen of the PEAR Installer.</simpara> + <simpara>Versions in CVS may break the upgrade mechanism of the PEAR Installer.</simpara> </listitem> </itemizedlist> </para> @@ -439,7 +439,7 @@ </listitem> <listitem> <para> - Check the <filename>package.xml</filename> file, especially the the fileset entries. + Check the <filename>package.xml</filename> file, especially the fileset 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>. </para>