cvs: phpdoc /en/pear standards.xml

tom Sat Aug 18 05:23:08 2001 EDT Modified files: /phpdoc/en/pear standards.xml Log: typo Index: phpdoc/en/pear/standards.xml diff -u phpdoc/en/pear/standards.xml:1.9 phpdoc/en/pear/standards.xml:1.10 --- phpdoc/en/pear/standards.xml:1.9 Thu Aug 16 02:40:22 2001 +++ phpdoc/en/pear/standards.xml Sat Aug 18 05:23:05 2001 @@ -1,4 +1,4 @@ -<!-- $Revision: 1.9 $ --> +<!-- $Revision: 1.10 $ --> <chapter id="pear.standards"> <title>PEAR Coding Standards</title> <note> @@ -296,7 +296,7 @@ <listitem> <simpara> (branch, optional) If you need to make "micro-releases" (for - example 1.2.1 and so on after 1.2, you can use a branch for + example 1.2.1 and so on after 1.2), you can use a branch for that too, if your main trunk is very active and you want only minor changes between your micro-releases. </simpara> @@ -372,8 +372,8 @@ </informaltable> </para> <para> - Private class members (meaning class members that an intented to - be used only from within the same class in which they are + Private class members (meaning class members that are intented + to be used only from within the same class in which they are declared; PHP does not yet support truly-enforceable private namespaces) are preceeded by a single underscore. For example: <informaltable>