From: Alexandr Ciornii Date: Tue, 24 Apr 2007 00:45:05 +0000 (+0300) Subject: perlre.pod spellcheck X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=c62285acd36452251fb244aaa1ae7cfe0821c1b7;p=p5sagit%2Fp5-mst-13.2.git perlre.pod spellcheck From: "Alexandr Ciornii" Message-ID: <2f1541220704231445w6fa7bfcbl41c9b6f56fb70feb@mail.gmail.com> p4raw-id: //depot/perl@31067 --- diff --git a/pod/perlre.pod b/pod/perlre.pod index 1865232..bd7a1aa 100644 --- a/pod/perlre.pod +++ b/pod/perlre.pod @@ -280,7 +280,7 @@ locale. See L. You may use C<\w>, C<\W>, C<\s>, C<\S>, C<\d>, and C<\D> within character classes, but they aren't usable as either end of a range. If any of them precedes or follows a "-", the "-" is understood literally. If Unicode is in effect, C<\s> matches -also "\x{85}", "\x{2028}, and "\x{2029}". See L for more +also "\x{85}", "\x{2028}", and "\x{2029}". See L for more details about C<\pP>, C<\PP>, C<\X> and the possibility of defining your own C<\p> and C<\P> properties, and L about Unicode in general. @@ -805,7 +805,7 @@ not include it in C<$&>. This effectively provides variable length look-behind. The use of C<\K> inside of another look-around assertion is allowed, but the behaviour is currently not well defined. -For various reasons C<\K> may be signifigantly more efficient than the +For various reasons C<\K> may be significantly more efficient than the equivalent C<< (?<=...) >> construct, and it is especially useful in situations where you want to efficiently remove something following something else in a string. For instance @@ -832,7 +832,7 @@ X<< (?) >> X<(?'NAME')> X X A named capture buffer. Identical in every respect to normal capturing parentheses C<()> but for the additional fact that C<%+> may be used after -a succesful match to refer to a named buffer. See C for more +a successful match to refer to a named buffer. See C for more details on the C<%+> hash. If multiple distinct capture buffers have the same name then the @@ -1454,7 +1454,7 @@ name of the most recently executed C<(*MARK:NAME)> that was involved in the match. This can be used to determine which branch of a pattern was matched -without using a seperate capture buffer for each branch, which in turn +without using a separate capture buffer for each branch, which in turn can result in a performance improvement, as perl cannot optimize C as efficiently as something like C.