summaryrefslogtreecommitdiff
path: root/Porting/how_to_write_a_perldelta.pod
diff options
context:
space:
mode:
Diffstat (limited to 'Porting/how_to_write_a_perldelta.pod')
-rw-r--r--Porting/how_to_write_a_perldelta.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/Porting/how_to_write_a_perldelta.pod b/Porting/how_to_write_a_perldelta.pod
index 851ed286a4..423b42a884 100644
--- a/Porting/how_to_write_a_perldelta.pod
+++ b/Porting/how_to_write_a_perldelta.pod
@@ -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