X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlsub.pod;h=ef5a3c5fa29f293757553f810db58624fdf4d0c7;hb=b988f96b4d2a582eb175809bd8070316bbc37118;hp=95fbb6b3428b4737bfda71849ab4e6f56bad2c65;hpb=b687b08b628449b317ff558f31d9d716ace045de;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/pod/perlsub.pod b/pod/perlsub.pod
index 95fbb6b..ef5a3c5 100644
--- a/pod/perlsub.pod
+++ b/pod/perlsub.pod
@@ -381,7 +381,7 @@ unqualified and unqualifiable.
 This does not work with object methods, however; all object methods have
 to be in the symbol table of some package to be found.
 
-=head2 Peristent Private Variables
+=head2 Persistent Private Variables
 
 Just because a lexical variable is lexically (also called statically)
 scoped to its enclosing block, C<eval>, or C<do> FILE, this doesn't mean that
@@ -825,7 +825,8 @@ if you call it like a builtin function, then it behaves like a builtin
 function.  If you call it like an old-fashioned subroutine, then it
 behaves like an old-fashioned subroutine.  It naturally falls out from
 this rule that prototypes have no influence on subroutine references
-like C<\&foo> or on indirect subroutine calls like C<&{$subref}>.
+like C<\&foo> or on indirect subroutine calls like C<&{$subref}> or
+C<$subref-E<gt>()>. 
 
 Method calls are not influenced by prototypes either, because the
 function to be called is indeterminate at compile time, because it depends