From 02e1e4511d075846a874d09871b45595426ab2df Mon Sep 17 00:00:00 2001
From: Rafael Garcia-Suarez <rgarciasuarez@gmail.com>
Date: Tue, 27 Jun 2006 14:01:30 +0000
Subject: Nits in the perlpragma manpage

p4raw-id: //depot/perl@28435
---
 pod/perlpragma.pod | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

(limited to 'pod/perlpragma.pod')

diff --git a/pod/perlpragma.pod b/pod/perlpragma.pod
index c43ff493a9..12e8124d0c 100644
--- a/pod/perlpragma.pod
+++ b/pod/perlpragma.pod
@@ -34,7 +34,7 @@ functions much like C<use integer;> You'd like this code
     
     no myint;
     print "E: ", $l + $r, "\n";
-   
+
 to give the output
 
     A: 4.6
@@ -71,13 +71,13 @@ this:
     
     1;
 
-Note how we load the user pragma C<myint> with C<()> to prevent its C<import>
-being called.
-
-The interaction with the Perl compile happens inside package C<myint>:
+Note how we load the user pragma C<myint> with an empty list C<()> to
+prevent its C<import> being called.
 
-package myint;
+The interaction with the Perl compilation happens inside package C<myint>:
 
+    package myint;
+    
     use strict;
     use warnings;
     
@@ -117,7 +117,7 @@ for the user's code.
 
 User pragmata store their state by writing to the magical hash C<%^H>,
 hence these two routines manipulate it. The state information in C<%^H> is
-stored in the optree, and can be retrieved at runtime with C<caller>, at
+stored in the optree, and can be retrieved at runtime with C<caller()>, at
 index 10 of the list of returned results. In the example pragma, retrieval
 is encapsulated into the routine C<in_effect()>, which takes as parameter
 the number of call frames to go up to find the value of the pragma in the
-- 
cgit v1.2.1