Fix podcheck errors related to perldelta

Author: thibaultduponchelle

pod/perldelta.pod

@@ -84,9 +84,11 @@ except that they are implemented as direct core operators, and thus perform
 faster, and do not produce an additional subroutine call stack frame for
 invoking the code block.
 
-The feature flags enabling those keywords have been named L<keyword_any>
-and L<keyword_all> to avoid confusion with to the ability of the
-C<feature> module to refer to all of its features by using the C<:all>
+The feature flags enabling those keywords have been named
+L<C<keyword_any>|feature/"The 'keyword_any' feature">
+and L<C<keyword_all>|feature/"The 'keyword_all' feature">
+to avoid confusion with to the ability of the C<feature> module
+to refer to all of its features by using the C<:all>
 export tag.  [L<GH #23104|https://github.com/Perl/perl5/issues/23104>]
 
 The related experimental warning flags are consequently named
@@ -335,7 +337,7 @@ each containing one million "A"s:
 C<my @scalars; push @scalars, ("A" x 1_000_000) for 0..9;>
 
 Now a single buffer is allocated and shared between a CONST OP and
-the ten scalar elements of L<@scalars>.
+the ten scalar elements of C<@scalars>.
 
 Note that any code using this sort of constant to simulate memory leaks
 (perhaps in test files) must now permute the string in order to trigger