From 61fdef401c6d2b07f19c14118da215874470a301 Mon Sep 17 00:00:00 2001
From: Lukas Mai <lukasmai.403@gmail.com>
Date: Tue, 19 Aug 2025 14:37:08 +0200
Subject: [PATCH] perlfunc/split: fix mangled markup

This was an oversight from 9bdeda4bef42d3cee14f754d72d12a160a52967a,
which used search/replace with a slightly too naive pattern.

Fixes #23600.
---
 pod/perlfunc.pod | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 6e9021157ab1..5baf11db7635 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -8484,7 +8484,7 @@ However, this:
 uses empty string matches as separators; thus, the empty string
 may be used to split EXPR into a list of its component characters.
 
-As a special case for C<split>PATTERNE<sol>,EXPR,LIMIT>,
+As a special case for C<split>,
 the empty pattern given in
 L<match operator|perlop/"m/PATTERN/msixpodualngc"> syntax (C<//>)
 specifically matches the empty string, which is contrary to its usual
@@ -8499,7 +8499,7 @@ C<E<sol>m> and any of the other pattern modifiers valid for C<qr>
 specified explicitly.
 
 As another special case,
-C<split>PATTERNE<sol>,EXPR,LIMIT> emulates the default
+C<split> emulates the default
 behavior of the
 command line tool B<awk> when the PATTERN is either omitted or a
 string composed of a single space character (such as S<C<' '>> or