diff --git a/pod/perl5180delta.pod b/pod/perl5180delta.pod index 34719b3c4f..39effa730a 100644 --- a/pod/perl5180delta.pod +++ b/pod/perl5180delta.pod @@ -2291,7 +2291,7 @@ C is gone. =item * -The private Perl_croak_no_modify has had its context parameter removed. It is +The private Perl_croak_no_modify has had its context parameter removed. It now has a void prototype. Users of the public API croak_no_modify remain unaffected. @@ -2340,7 +2340,7 @@ C has been deprecated. C now always returns a byte count and C a character count. Previously, C and C were both buggy and would -sometimes returns bytes and sometimes characters. C no longer +sometimes return bytes and sometimes characters. C no longer assumes that its argument is in UTF-8. Neither of these creates UTF-8 caches for tied or overloaded values or for non-PVs any more. diff --git a/pod/perl5200delta.pod b/pod/perl5200delta.pod index ef7b456831..24d75924f6 100644 --- a/pod/perl5200delta.pod +++ b/pod/perl5200delta.pod @@ -1529,7 +1529,7 @@ built-in functions not only on aggregate types, but on references to them. The feature was not deployed to its original intended specification, and now may become redundant to postfix dereferencing. It has always been categorized as an experimental feature, and in -v5.20.0 is carries a warning as such. +v5.20.0 it carries a warning as such. Warnings will now be issued at compile time when these operations are detected. @@ -1971,7 +1971,7 @@ up as /system/bin/sh, and "sh" as /bin/sh. By default, B 4.9 does some optimizations that break perl. The B<-fwrapv> option disables those optimizations (and probably others), so for B 4.3 -and later (since the there might be similar problems lurking on older versions +and later (since there might be similar problems lurking on older versions too, but B<-fwrapv> was broken before 4.3, and the optimizations probably won't go away), F now adds B<-fwrapv> unless the user requests B<-fno-wrapv>, which disables B<-fwrapv>, or B<-fsanitize=undefined>, which diff --git a/pod/perl5260delta.pod b/pod/perl5260delta.pod index f9d5721c45..77920869b2 100644 --- a/pod/perl5260delta.pod +++ b/pod/perl5260delta.pod @@ -2622,7 +2622,7 @@ L<[GH #15657]|https://github.com/Perl/perl5/issues/15657> =item * -Occasionally Cs in a code block within a patterns weren't being +Occasionally Cs in a code block within a pattern weren't being undone when the pattern matching backtracked over the code block. L<[GH #15056]|https://github.com/Perl/perl5/issues/15056> diff --git a/pod/perl5340delta.pod b/pod/perl5340delta.pod index a15c8eceaa..8391a3c68f 100644 --- a/pod/perl5340delta.pod +++ b/pod/perl5340delta.pod @@ -1300,7 +1300,7 @@ operations. C, C, and C now attempt to downgrade the C parameter if its value is being used as input to C or -C calls. A failed downgrade will thrown an exception. +C calls. A failed downgrade will throw an exception. =item * diff --git a/pod/perl5361delta.pod b/pod/perl5361delta.pod index 531d34b8cd..6db300ce3c 100644 --- a/pod/perl5361delta.pod +++ b/pod/perl5361delta.pod @@ -68,7 +68,7 @@ interpreter panic; e.g. =item * An C referring to a lexical sub defined in grandparent scope no -longer produces an assertion failures. +longer produces an assertion failure. [L] =item * diff --git a/pod/perl561delta.pod b/pod/perl561delta.pod index 60cee8e1e2..33ed8a6665 100644 --- a/pod/perl561delta.pod +++ b/pod/perl561delta.pod @@ -2642,7 +2642,7 @@ so it was truncated to the string shown. =item Can't declare class for non-scalar %s in "%s" -(S) Currently, only scalar variables can declared with a specific class +(S) Currently, only scalar variables can be declared with a specific class qualifier in a "my" or "our" declaration. The semantics may be extended for other types of variables in future. diff --git a/pod/perl56delta.pod b/pod/perl56delta.pod index a5062db448..54e72501ec 100644 --- a/pod/perl56delta.pod +++ b/pod/perl56delta.pod @@ -2037,7 +2037,7 @@ so it was truncated to the string shown. =item Can't declare class for non-scalar %s in "%s" -(S) Currently, only scalar variables can declared with a specific class +(S) Currently, only scalar variables can be declared with a specific class qualifier in a "my" or "our" declaration. The semantics may be extended for other types of variables in future. diff --git a/pod/perldebguts.pod b/pod/perldebguts.pod index 52aef07396..a71f05b29e 100644 --- a/pod/perldebguts.pod +++ b/pod/perldebguts.pod @@ -961,7 +961,7 @@ grasp of what happens. Assume that an integer cannot take less than 20 bytes of memory, a float cannot take less than 24 bytes, a string cannot take less than 32 bytes (all these examples assume 32-bit architectures, the -result are quite a bit worse on 64-bit architectures). If a variable +results are quite a bit worse on 64-bit architectures). If a variable is accessed in two of three different ways (which require an integer, a float, or a string), the memory footprint may increase yet another 20 bytes. A sloppy malloc(3) implementation can inflate these diff --git a/pod/perldebug.pod b/pod/perldebug.pod index 02f19120c4..3172f91bd8 100644 --- a/pod/perldebug.pod +++ b/pod/perldebug.pod @@ -654,7 +654,7 @@ Perl debugger, use a leading semicolon, too. X List which methods may be called on the result of the evaluated -expression. The expression may evaluated to a reference to a +expression. The expression may be evaluated to a reference to a blessed object, or to a package name. =item M diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 36c4786b72..f281011d8f 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -8375,7 +8375,7 @@ string's internal encoding. As of Perl 5.39.9 the C default modifier does NOT affect C but does affect C, this means that -C will produces the expected I emulation regardless as +C will produce the expected I emulation regardless as to whether it is used in the scope of a C statement. If you want to split by spaces under C you must do something like C or C instead of C. diff --git a/pod/perlguts.pod b/pod/perlguts.pod index a5d389babe..5732f9347b 100644 --- a/pod/perlguts.pod +++ b/pod/perlguts.pod @@ -1293,7 +1293,7 @@ settable with L<< IO::Handle's untaint() method|IO::Handle/"$io->untaint" >>. =for apidoc Amnh||IOf_FLUSH =for apidoc Amnh||IOf_UNTAINT -The IO object may also contains a directory handle: +The IO object may also contain a directory handle: DIR *IoDIRP(io); diff --git a/pod/perlipc.pod b/pod/perlipc.pod index 290b993a7f..cc407fb31e 100644 --- a/pod/perlipc.pod +++ b/pod/perlipc.pod @@ -1445,7 +1445,7 @@ simultaneously copies everything from standard input to the socket. To accomplish the same thing using just one process would be I harder, because it's easier to code two processes to do one thing than it is to code one process to do two things. (This keep-it-simple principle -a cornerstones of the Unix philosophy, and good software engineering as +is a cornerstone of the Unix philosophy, and good software engineering as well, which is probably why it's spread to other systems.) Here's the code: diff --git a/pod/perlop.pod b/pod/perlop.pod index 2b8c3aab2c..36edd23f63 100644 --- a/pod/perlop.pod +++ b/pod/perlop.pod @@ -2188,7 +2188,7 @@ A string which is (possibly) interpolated and then executed as a system command, via F or its equivalent if required. Shell wildcards, pipes, and redirections will be honored. Similarly to C, if the string contains no shell metacharacters then it will -executed directly. The collected standard output of the command is +be executed directly. The collected standard output of the command is returned; standard error is unaffected. In scalar context, it comes back as a single (potentially multi-line) string, or C if the shell (or command) could not be started. In list context, returns a @@ -3375,7 +3375,7 @@ Bitstrings of any size may be manipulated by the bitwise operators If the operands to a binary bitwise op are strings of different sizes, B<|> and B<^> ops act as though the shorter operand had additional zero bits on the right, while the B<&> op acts as though -the longer operand were truncated to the length of the shorter. +the longer operand was truncated to the length of the shorter. The granularity for such extension or truncation is one or more bytes. diff --git a/pod/perlperf.pod b/pod/perlperf.pod index ad559db929..df8f1cc41e 100644 --- a/pod/perlperf.pod +++ b/pod/perlperf.pod @@ -588,7 +588,7 @@ systems which provide C. It can be started and stopped even by the program being profiled. It's a one-line entry to profile C applications. It's written in C and is probably the fastest profiler available for Perl. The list of coolness just goes on. Enough of that, let's -see how to it works - just use the familiar C<-d> switch to plug it in and run +see how it works - just use the familiar C<-d> switch to plug it in and run the code. $> perl -d:NYTProf wordmatch -f perl5db.pl @@ -1104,7 +1104,7 @@ completely optimized away, and you can't get much more efficient than that. =head1 POSTSCRIPT -This document has provided several way to go about identifying hot-spots, and +This document has provided several ways to go about identifying hot-spots, and checking whether any modifications have improved the runtime of the code. As a final thought, remember that it's not (at the time of writing) possible to diff --git a/pod/perlsub.pod b/pod/perlsub.pod index e99af6cf8b..b3ae8d1ec0 100644 --- a/pod/perlsub.pod +++ b/pod/perlsub.pod @@ -439,7 +439,7 @@ is not important, it may be omitted just as the parameter's name was: } Optional positional parameters must come after all mandatory positional -parameters. (If there are no mandatory positional parameters then an +parameters. (If there are no mandatory positional parameters then the optional positional parameters can be the first thing in the signature.) If there are multiple optional positional parameters and not enough arguments are supplied to fill them all, they will be filled from left diff --git a/pod/perlthrtut.pod b/pod/perlthrtut.pod index 349a6c7663..c07060c3c8 100644 --- a/pod/perlthrtut.pod +++ b/pod/perlthrtut.pod @@ -26,7 +26,7 @@ If you have neither, you don't have any thread support built in. If you have both, you are in trouble. The L and L modules are included in the core Perl -distribution. Additionally, they are maintained as a separate modules on +distribution. Additionally, they are maintained as separate modules on CPAN, so you can check there for any updates. =head1 What Is A Thread Anyway? diff --git a/pod/perlvar.pod b/pod/perlvar.pod index 7db75d72e1..3db0bef06a 100644 --- a/pod/perlvar.pod +++ b/pod/perlvar.pod @@ -821,7 +821,7 @@ C hooks are called in FIFO order, and if the hook returns a code reference those code references will be called in FILO order. In other words if A requires B requires C, then C will be called first for A, then B and then C, and -the post-action code reference will executed first for C, then B and +the post-action code reference will be executed first for C, then B and then finally A. Well behaved code should ensure that when setting up a