perl-docs-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject cvs commit: modperl-docs/src/docs/general/testing testing.pod
Date Fri, 16 Jan 2004 04:48:29 GMT
stas        2004/01/15 20:48:29

  Modified:    src/docs/general/testing testing.pod
  Log:
  a few language fixes
  Submitted by:	William McKee <william@knowmad.com>
  
  Revision  Changes    Path
  1.28      +2 -2      modperl-docs/src/docs/general/testing/testing.pod
  
  Index: testing.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/general/testing/testing.pod,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -u -r1.27 -r1.28
  --- testing.pod	21 Dec 2003 22:18:55 -0000	1.27
  +++ testing.pod	16 Jan 2004 04:48:28 -0000	1.28
  @@ -361,7 +361,7 @@
   in order to try to detect as many problems as possible during the
   testing process, it's may be useful to run tests in different orders.
   
  -This if of course mosly useful in conjunction with I<-times=N> option.
  +This is of course mostly useful in conjunction with I<-times=N> option.
   
   Assuming that we have tests a, b and c:
   
  @@ -2383,7 +2383,7 @@
     # received: a bad value
     not ok 1
   
  -we can see exactly what's the problem, by visual expecting of the
  +we can see exactly what's the problem, by visual examinination of the
   expected and received values.
   
   It's true that adding a few print statements for each sub tests is
  
  
  

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


Mime
View raw message