cvs: peardoc /en/chapters standards.xml

danielc Thu May 13 00:14:43 2004 EDT Modified files: /peardoc/en/chapters standards.xml Log: s/these/those/. http://cvs.php.net/diff.php/peardoc/en/chapters/standards.xml?r1=1.21&r2=1.22&ty=u Index: peardoc/en/chapters/standards.xml diff -u peardoc/en/chapters/standards.xml:1.21 peardoc/en/chapters/standards.xml:1.22 --- peardoc/en/chapters/standards.xml:1.21 Wed May 12 18:29:14 2004 +++ peardoc/en/chapters/standards.xml Thu May 13 00:14:43 2004 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1" ?> -<!-- $Revision: 1.21 $ --> +<!-- $Revision: 1.22 $ --> <chapter id="standards"> <title>Coding Standards</title> @@ -484,7 +484,7 @@ </para> <para> The example contains many details about writing - Docblock Comments. Following these instructions + Docblock Comments. Following those instructions is important for two reasons. First, when docblocks are easy to read, users and developers can quickly ascertain what your code does. Second, the PEAR @@ -515,7 +515,7 @@ // | Your Name <you@example.com> | // +----------------------------------------------------------------------+ // -// $Id: standards.xml,v 1.21 2004/05/12 22:29:14 danielc Exp $ +// $Id: standards.xml,v 1.22 2004/05/13 04:14:43 danielc Exp $ require_once 'PEAR.php'; @@ -567,7 +567,7 @@ * @category categoryname * @package packagename * @author Original Author <author@example.com> - * @version $Id: standards.xml,v 1.21 2004/05/12 22:29:14 danielc Exp $ + * @version $Id: standards.xml,v 1.22 2004/05/13 04:14:43 danielc Exp $ * @access public * @see NetOther, Net_Sample::Net_Sample() * @since Class available since Release 1.2.0