X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlsec.pod;h=212879af93e1243315f57542cec4ca25a9fbe41f;hb=2decb4fb82e001e3c9671c57b61232c651a9c22c;hp=0b22acd9cda88f43b7ceaae9e21dc3563f0cda56;hpb=62f468fcc5ab60fb5a3476c4f51edf76066f5db7;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/pod/perlsec.pod b/pod/perlsec.pod
index 0b22acd..212879a 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.