summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorRafael Garcia-Suarez <rgarciasuarez@gmail.com>2006-08-18 16:22:18 +0000
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2006-08-18 16:22:18 +0000
commit6985a70beafa38c8206d8a4fd7bb628e6f69d025 (patch)
tree6e0f5b11a4d5458910a1f8b1aa9db92f9aa7fef8 /pod
parentea5195b749dcc39981859e3ccebcd4b40b26b0bd (diff)
downloadperl-6985a70beafa38c8206d8a4fd7bb628e6f69d025.tar.gz
Phrasing nit in perlxstut (by Ville Koskinen)
p4raw-id: //depot/perl@28736
Diffstat (limited to 'pod')
-rw-r--r--pod/perlxstut.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlxstut.pod b/pod/perlxstut.pod
index d1edf61a76..4f8bbc144b 100644
--- a/pod/perlxstut.pod
+++ b/pod/perlxstut.pod
@@ -293,7 +293,7 @@ while you are still testing extensions that you use "C<make test>". If you
try to run the test script all by itself, you will get a fatal error.
Another reason it is important to use "C<make test>" to run your test
script is that if you are testing an upgrade to an already-existing version,
-using "C<make test>" insures that you will test your new extension, not the
+using "C<make test>" ensures that you will test your new extension, not the
already-existing version.
When Perl sees a C<use extension;>, it searches for a file with the same name