[Po4a-devel][CVS po4a]po4a README.tests,1.1,1.2 po4a-gettextize,1.16,1.17

[Denis Barbier]

Update of /cvsroot/po4a/po4a
In directory haydn:/tmp/cvs-serv28080

Modified Files:
	README.tests po4a-gettextize 
Log Message:
s/repport/report/


Index: README.tests
===================================================================
RCS file: /cvsroot/po4a/po4a/README.tests,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -d -r1.1 -r1.2
--- README.tests	7 Nov 2003 10:11:21 -0000	1.1
+++ README.tests	28 Apr 2004 21:36:31 -0000	1.2
@@ -4,14 +4,14 @@
 I'll try to add a test for each test found in po4a in order to ensure that
 they won't surface again.
 
-If the test suite repports errors, please join enough details so that I can
+If the test suite reports errors, please join enough details so that I can
 fix them. At least, provide me the detailed result of the test suite. For
 that, run the following command:
 
   script -c 'perl Makefile.PL;make clean test TEST_VERBOSE=1'
 
 It will produce a file called 'typescript', containing most of the details I
-need. Please also repport the perl version used, the linux distribution, and
+need. Please also report the perl version used, the linux distribution, and
 all details you think appropriate.
 
 

Index: po4a-gettextize
===================================================================
RCS file: /cvsroot/po4a/po4a/po4a-gettextize,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -d -r1.16 -r1.17
--- po4a-gettextize	28 Apr 2004 09:01:10 -0000	1.16
+++ po4a-gettextize	28 Apr 2004 21:36:31 -0000	1.17
@@ -39,9 +39,9 @@
 it is very important that both file share exactly the same structure.
 
 However, C<po4a-gettextize> will diagnose your death by detecting any
-desyncronisation between files, and repporting where they occur. In that
-case, you should edit manually the files to solve the repported
-disparity. Even if no error were repported, you check carefully that the
+desyncronisation between files, and reporting where they occur. In that
+case, you should edit manually the files to solve the reported
+disparity. Even if no error were reported, you check carefully that the
 generated po file is correct (ie, that each msgstr is the translation of
 the associated msgid, and not the one before or after).