pod: fix usage of affect/effect in doc files

This commit is contained in:
vaitkus 2024-09-04 16:01:05 +03:00 committed by Karl Williamson
parent c97b3f4b8a
commit dfa614ff48
2 changed files with 2 additions and 2 deletions

View File

@ -995,7 +995,7 @@ replaced by C<->, so that F<ext/Data/Dumper/> is now F<ext/Data-Dumper/>,
etc. The names of the extensions as specified to F<Configure>, and as
reported by C<%Config::Config> under the keys C<dynamic_ext>,
C<known_extensions>, C<nonxs_ext> and C<static_ext> have not changed, and
still use C</>. Hence this change will not have any affect once perl is
still use C</>. Hence this change will not have any effect once perl is
installed. However, C<Attribute::Handlers>, C<Safe> and C<mro> have now
become extensions in their own right, so if you run F<Configure> with
options to specify an exact list of extensions to build, you will need to

View File

@ -2124,7 +2124,7 @@ OPs are freed. C<MADPROP>s are now allocated with C<PerlMemShared_malloc()>
=item *
F<makedef.pl> has been refactored. This should have no noticeable affect on
F<makedef.pl> has been refactored. This should have no noticeable effect on
any of the platforms that use it as part of their build (AIX, VMS, Win32).
=item *