XSUB's doc fix

p5p-msgid: 28804.858012126@eeyore.ibcinc.com

diff --git a/pod/perlcall.pod b/pod/perlcall.pod
index 9a4a886..dc96500 100644 (file)
--- a/pod/perlcall.pod
+++ b/pod/perlcall.pod
@@ -565,7 +565,7 @@ Next, we come to XPUSHs. This is where the parameters actually get
 pushed onto the stack. In this case we are pushing a string and an
 integer.
 
-See the L<perlguts/"XSUB's and the Argument Stack"> for details
+See the L<perlguts/"XSUBs and the Argument Stack"> for details
 on how the XPUSH macros work.
 
 =item 6.

diff --git a/pod/perlguts.pod b/pod/perlguts.pod
index 8c78802..317381d 100644 (file)
--- a/pod/perlguts.pod
+++ b/pod/perlguts.pod
@@ -810,7 +810,7 @@ the mg_type field is changed to be the lower-case letter.
 
 =head1 Subroutines
 
-=head2 XSUB's and the Argument Stack
+=head2 XSUBs and the Argument Stack
 
 The XSUB mechanism is a simple way for Perl programs to access C subroutines.
 An XSUB routine will have a stack that contains the arguments from the Perl
@@ -954,7 +954,7 @@ The most recent development releases of Perl has been experimenting with
 removing Perl's dependency on the "normal" standard I/O suite and allowing
 other stdio implementations to be used.  This involves creating a new
 abstraction layer that then calls whichever implementation of stdio Perl
-was compiled with.  All XSUB's should now use the functions in the PerlIO
+was compiled with.  All XSUBs should now use the functions in the PerlIO
 abstraction layer and not make any assumptions about what kind of stdio
 is being used.
 

diff --git a/pod/perltoc.pod b/pod/perltoc.pod
index eb59cda..e6f751f 100644 (file)
--- a/pod/perltoc.pod
+++ b/pod/perltoc.pod
@@ -1471,7 +1471,7 @@ B<PerlIO_get_base(f)>, B<PerlIO_get_bufsiz(f)>
 
 =over
 
-=item XSUB's and the Argument Stack
+=item XSUBs and the Argument Stack
 
 =item Calling Perl Routines from within C Programs
 

diff --git a/pod/perlxstut.pod b/pod/perlxstut.pod
index 7b9b7c6..e31de33 100644 (file)
--- a/pod/perlxstut.pod
+++ b/pod/perlxstut.pod
@@ -452,7 +452,7 @@ this behavior is tolerated.  The next example will show how to do this.
 
 =head2 EXAMPLE 4
 
-In this example, we'll now begin to write XSUB's that will interact with
+In this example, we'll now begin to write XSUBs that will interact with
 pre-defined C libraries.  To begin with, we will build a small library of
 our own, then let h2xs write our .pm and .xs files for us.