fwd: Re: [ID 20001105.011] Perl 5.6.0 documentation glitch

Message-ID: <14861.32839.491271.985797@rls.cx>

p4raw-id: //depot/perl@7648

diff --git a/Porting/Contract b/Porting/Contract
index cc91af2..2b619fd 100644 (file)
--- a/Porting/Contract
+++ b/Porting/Contract
@@ -19,7 +19,7 @@ community, mutual respect, trust, and good-faith cooperation.
 
 We recognize that the Perl core, defined as the software distributed with
 the heart of Perl itself, is a joint project on the part of all of us.
->From time to time, a script, module, or set of modules (hereafter referred
+From time to time, a script, module, or set of modules (hereafter referred
 to simply as a "module") will prove so widely useful and/or so integral to
 the correct functioning of Perl itself that it should be distributed with
 Perl core.  This should never be done without the author's explicit

diff --git a/pod/perltoot.pod b/pod/perltoot.pod
index e923673..594cb99 100644 (file)
--- a/pod/perltoot.pod
+++ b/pod/perltoot.pod
@@ -1727,7 +1727,7 @@ as a class or object method is by usage only.  You could accidentally
 call a class method (one expecting a string argument) on an
 object (one expecting a reference), or vice versa.
 
-Z<>From the C++ perspective, all methods in Perl are virtual.
+From the C++ perspective, all methods in Perl are virtual.
 This, by the way, is why they are never checked for function
 prototypes in the argument list as regular builtin and user-defined
 functions can be.