[PATCH] Documentation: Fix duplicated words

Wang Zihan posted 1 patch 1 month, 1 week ago
Documentation/networking/switchdev.rst                | 2 +-
Documentation/userspace-api/media/dvb/dmx-reqbufs.rst | 2 +-
Documentation/virt/uml/user_mode_linux_howto_v2.rst   | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
[PATCH] Documentation: Fix duplicated words
Posted by Wang Zihan 1 month, 1 week ago
Remove duplicated words in three documentation files:
- "in in" -> "in" (switchdev.rst)
- "The the" -> "The" (dmx-reqbufs.rst)
- "on on" -> "on" (user_mode_linux_howto_v2.rst)

Signed-off-by: Wang Zihan <3772548978@qq.com>
---
 Documentation/networking/switchdev.rst                | 2 +-
 Documentation/userspace-api/media/dvb/dmx-reqbufs.rst | 2 +-
 Documentation/virt/uml/user_mode_linux_howto_v2.rst   | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/networking/switchdev.rst b/Documentation/networking/switchdev.rst
index 2966b7122..948bce44c 100644
--- a/Documentation/networking/switchdev.rst
+++ b/Documentation/networking/switchdev.rst
@@ -162,7 +162,7 @@ The switchdev driver can know a particular port's position in the topology by
 monitoring NETDEV_CHANGEUPPER notifications.  For example, a port moved into a
 bond will see its upper master change.  If that bond is moved into a bridge,
 the bond's upper master will change.  And so on.  The driver will track such
-movements to know what position a port is in in the overall topology by
+movements to know what position a port is in the overall topology by
 registering for netdevice events and acting on NETDEV_CHANGEUPPER.
 
 L2 Forwarding Offload
diff --git a/Documentation/userspace-api/media/dvb/dmx-reqbufs.rst b/Documentation/userspace-api/media/dvb/dmx-reqbufs.rst
index d2bb1909e..18810f0bb 100644
--- a/Documentation/userspace-api/media/dvb/dmx-reqbufs.rst
+++ b/Documentation/userspace-api/media/dvb/dmx-reqbufs.rst
@@ -72,4 +72,4 @@ appropriately. The generic error codes are described at the
 :ref:`Generic Error Codes <gen-errors>` chapter.
 
 EOPNOTSUPP
-    The  the requested I/O method is not supported.
+    The requested I/O method is not supported.
diff --git a/Documentation/virt/uml/user_mode_linux_howto_v2.rst b/Documentation/virt/uml/user_mode_linux_howto_v2.rst
index c37e8e594..7b08738c3 100644
--- a/Documentation/virt/uml/user_mode_linux_howto_v2.rst
+++ b/Documentation/virt/uml/user_mode_linux_howto_v2.rst
@@ -1092,7 +1092,7 @@ be formatted as plain text.
 
 Developing always goes hand in hand with debugging. First of all,
 you can always run UML under gdb and there will be a whole section
-later on on how to do that. That, however, is not the only way to
+later on how to do that. That, however, is not the only way to
 debug a Linux kernel. Quite often adding tracing statements and/or
 using UML specific approaches such as ptracing the UML kernel process
 are significantly more informative.
-- 
2.54.0
Re: [PATCH] Documentation: Fix duplicated words
Posted by Andrew Lunn 1 month, 1 week ago
On Sat, May 02, 2026 at 07:19:16PM +0800, Wang Zihan wrote:
> Remove duplicated words in three documentation files:
> - "in in" -> "in" (switchdev.rst)
> - "The the" -> "The" (dmx-reqbufs.rst)
> - "on on" -> "on" (user_mode_linux_howto_v2.rst)

https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html

* don’t repost your patches within one 24h period

We have already told you one of the fixes is wrong, but you did not
wait 24 hours, so have not see our feedback.

Also, in general when using a tool, assume it is wrong, and convince
yourself it is correct, before making a change. "The the in this
sentence is the subject." What does the bot make of that? Can you
convince yourself the bot is correct?

    Andrew

---
pw-bot: cr
Re: [PATCH] Documentation: Fix duplicated words
Posted by Björn Persson 1 month, 1 week ago
Wang Zihan wrote:
>  you can always run UML under gdb and there will be a whole section
> -later on on how to do that. That, however, is not the only way to
> +later on how to do that. That, however, is not the only way to

"Later on" is an established English expression. A plain "later" also
works. This isn't a correction of an error; it's a stylistic change.

Björn Persson