From: Paul Gaborit <Paul.Gaborit@enstimac.fr>
Date: Wed, 18 Mar 2009 08:19:48 +0000 (+0100)
Subject: Doc fix: the /k regexp modifier should really be written /p
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=245490700bb744b58c708516d2d3c08f18583dc3;p=p5sagit%2Fp5-mst-13.2.git

Doc fix: the /k regexp modifier should really be written /p
---

diff --git a/pod/perlretut.pod b/pod/perlretut.pod
index 67e0670..0a2d563 100644
--- a/pod/perlretut.pod
+++ b/pod/perlretut.pod
@@ -2133,8 +2133,8 @@ example is
 This style of commenting has been largely superseded by the raw,
 freeform commenting that is allowed with the C<//x> modifier.
 
-The modifiers C<//i>, C<//m>, C<//s>, C<//x> and C<//k> (or any
-combination thereof) can also embedded in
+The modifiers C<//i>, C<//m>, C<//s> and C<//x> (or any
+combination thereof) can also be embedded in
 a regexp using C<(?i)>, C<(?m)>, C<(?s)>, and C<(?x)>.  For instance,
 
     /(?i)yes/;  # match 'yes' case insensitively
@@ -2159,7 +2159,7 @@ that must have different modifiers:
         }
     }
 
-The second advantage is that embedded modifiers (except C<//k>, which
+The second advantage is that embedded modifiers (except C<//p>, which
 modifies the entire regexp) only affect the regexp
 inside the group the embedded modifier is contained in.  So grouping
 can be used to localize the modifier's effects: