summaryrefslogtreecommitdiff
path: root/pod/perlhack.pod
diff options
context:
space:
mode:
authorFather Chrysostomos <sprout@cpan.org>2013-11-01 06:24:28 -0700
committerFather Chrysostomos <sprout@cpan.org>2013-11-01 06:24:28 -0700
commit304544527cb54b00be3667b67583c6b9c5d1b0db (patch)
tree6b772b3799f707254d32563b9a4888d03cf85849 /pod/perlhack.pod
parent598bcb826253d06467481559a50ababf94179559 (diff)
downloadperl-304544527cb54b00be3667b67583c6b9c5d1b0db.tar.gz
perlhack.pod: consistent spaces after dots
Diffstat (limited to 'pod/perlhack.pod')
-rw-r--r--pod/perlhack.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index 0da1de8529..a32199a9df 100644
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -92,7 +92,7 @@ Thank you!
=item * Next time
The next time you wish to make a patch, you need to start from the
-latest perl in a pristine state. Check you don't have any local changes
+latest perl in a pristine state. Check you don't have any local changes
or added files in your perl check-out which you wish to keep, then run
these commands:
@@ -235,7 +235,7 @@ volunteers, and be polite.
Changes are always applied directly to the main development branch,
called "blead". Some patches may be backported to a maintenance
-branch. If you think your patch is appropriate for the maintenance
+branch. If you think your patch is appropriate for the maintenance
branch (see L<perlpolicy/MAINTENANCE BRANCHES>), please explain why
when you submit it.