summaryrefslogtreecommitdiff
path: root/pod/perlsec.pod
diff options
context:
space:
mode:
Diffstat (limited to 'pod/perlsec.pod')
-rw-r--r--pod/perlsec.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlsec.pod b/pod/perlsec.pod
index 0b22acd9cd..212879af93 100644
--- a/pod/perlsec.pod
+++ b/pod/perlsec.pod
@@ -139,7 +139,7 @@ metacharacters, nor are dot, dash, or at going to mean something special
to the shell. Use of C</.+/> would have been insecure in theory because
it lets everything through, but Perl doesn't check for that. The lesson
is that when untainting, you must be exceedingly careful with your patterns.
-Laundering data using regular expression is the I<ONLY> mechanism for
+Laundering data using regular expression is the I<only> mechanism for
untainting dirty data, unless you use the strategy detailed below to fork
a child of lesser privilege.