summaryrefslogtreecommitdiff
path: root/pod/perlpolicy.pod
diff options
context:
space:
mode:
authorRicardo Signes <rjbs@cpan.org>2010-12-09 16:02:38 -0500
committerRicardo Signes <rjbs@cpan.org>2010-12-09 16:02:38 -0500
commit9e9fdd5de1676d607ddf9b9f10b8df2659af3ded (patch)
treee349161606f092d234ef96cf931161fff4d9c3c2 /pod/perlpolicy.pod
parent1bb8a15505d40cd4fbf8e9e48185ff81c48dd167 (diff)
downloadperl-9e9fdd5de1676d607ddf9b9f10b8df2659af3ded.tar.gz
perlfaq is not the only exception; just say "few"
Diffstat (limited to 'pod/perlpolicy.pod')
-rw-r--r--pod/perlpolicy.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlpolicy.pod b/pod/perlpolicy.pod
index 13ee289f72..a36e1e0579 100644
--- a/pod/perlpolicy.pod
+++ b/pod/perlpolicy.pod
@@ -411,7 +411,7 @@ prose.
In general, documentation should describe what Perl does "now" rather
than what it used to do. It's perfectly reasonable to include notes
in documentation about how behaviour has changed from previous releases,
-but, with the exception of perlfaq, documentation isn't "dual-life" --
+but, with very few exceptions, documentation isn't "dual-life" --
it doesn't need to fully describe how all old versions used to work.