Porting/release_managers_guide.pod: correct path to perlivp

[perl5.git] / Porting / how_to_write_a_perldelta.pod

diff --git a/Porting/how_to_write_a_perldelta.pod b/Porting/how_to_write_a_perldelta.pod
index 851ed28..04fc972 100644 (file)
--- a/Porting/how_to_write_a_perldelta.pod
+++ b/Porting/how_to_write_a_perldelta.pod
@@ -8,7 +8,7 @@ there, steal it.
 
 =head2 Template
 
-Note there is a file F<Porting/perldelta_template> which contains a
+Note there is a file F<Porting/perldelta_template.pod> which contains a
 skeleton version of a perldelta.pod file, which should normally be copied
 in at the start of a new release.
 
@@ -132,7 +132,7 @@ within F<ext/> and F<lib/> to a number of people.
 B<FIXME> - this could be automated better
 
 If Module::CoreList has been updated, then F<Porting/corelist-perldelta.pl>
-will automatically print out several sections if relevent that can be
+will automatically print out several sections if relevant that can be
 pasted into F<perldelta>:
 
     * New Modules and Pragmata
@@ -147,7 +147,7 @@ Each section will have stub entries following a template like this:
     Upgraded from version 0.01 to 0.02
 
 It does not include modules listed in F<Porting/Maintainers.pl> under
-C<_PERLLIB>, but it's a start.  Where relevent, a summary of changes can be
+C<_PERLLIB>, but it's a start.  Where relevant, a summary of changes can be
 added by hand.
 
 A more adventurous enhancement would be to automate grabbing