Fix paths of pack.pl in patching.pod

p4raw-id: //depot/perl@29594

diff --git a/Porting/patching.pod b/Porting/patching.pod
index 5114d72..52c60d0 100644 (file)
--- a/Porting/patching.pod
+++ b/Porting/patching.pod
@@ -153,22 +153,22 @@ you have your changes, you would run makepatch as follows:
 
 =item Binary Files
 
-Since the patch(1) utility can not deal with binary files, it's important
-that you either avoid the use of binary files in your patch, generate the files
-dynamically or that you encode any binary files using the C<Porting/pack.pl>
-utility.
+Since the patch(1) utility cannot deal with binary files, it's important
+that you either avoid the use of binary files in your patch, generate the
+files dynamically, or that you encode any binary files using the
+F<pack.pl> utility.
 
-Assuming you needed to include a C<gzip> encoded file for a module's test suite,
-you might do this as follows using the C<Porting/pack.pl> utility:
+Assuming you needed to include a gzip-encoded file for a module's test
+suite, you might do this as follows using the F<pack.pl> utility:
 
-    $ perl Porting/pack.pl -v -D lib/Some/Module/t/src/t.gz
+    $ perl pack.pl -v -D lib/Some/Module/t/src/t.gz
     Writing lib/Some/Module/t/src/t.gz into lib/Some/Module/t/src/t.gz.packed
 
-This will replace the C<t.gz> file with an encoded counterpart. During 
-C<make test>, before any tests are run, Perls Makefile will restore all the
-C<.packed> files mentioned in the C<MANIFEST> to their original name. This 
-means that the test suite does not need to be aware of this packing scheme and
-will not need to be altered.
+This will replace the C<t.gz> file with an encoded counterpart. During
+C<make test>, before any tests are run, perl's Makefile will restore all
+the C<.packed> files mentioned in the MANIFEST to their original name.
+This means that the test suite does not need to be aware of this packing
+scheme and will not need to be altered.
 
 =item Try it yourself