summaryrefslogtreecommitdiff
path: root/Porting
diff options
context:
space:
mode:
authorSmylers <Smylers@stripey.com>2013-04-04 10:04:48 +0100
committerRicardo Signes <rjbs@cpan.org>2013-05-05 15:32:21 -0400
commit0309f1e208d4f052e62e74841d46694fbf14b4a9 (patch)
tree92f7ac591013440cf50d682fb373b336dd50782b /Porting
parent71b6ff970987c685b97b216d2e295ebf840c7411 (diff)
downloadperl-0309f1e208d4f052e62e74841d46694fbf14b4a9.tar.gz
perldelta: "order" is intended word
Diffstat (limited to 'Porting')
-rw-r--r--Porting/perl5180delta.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/Porting/perl5180delta.pod b/Porting/perl5180delta.pod
index 9d5b92789f..3126ae416a 100644
--- a/Porting/perl5180delta.pod
+++ b/Porting/perl5180delta.pod
@@ -46,7 +46,7 @@ experimental.
Changes to the implementation of hashes in perl 5.18.0 will be one of the most
visible changes to the behavior of existing code. For the most part, these
changes will be visible as two distinct hash variables now providing their
-contents in a different variable where it was previously identical. When
+contents in a different order where it was previously identical. When
encountering these changes, the key to cleaning up from them is to accept that
B<hashes are unordered collections> and to act accordingly.