From: Markus Heidelberg <m.heidelberg@cab.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: <linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Markus Heidelberg <m.heidelberg@cab.de>
Subject: [PATCH] Documentation: fix spelling, typos, grammar, duplicated words
Date: Fri, 26 Sep 2025 11:53:12 +0200 [thread overview]
Message-ID: <20250926095312.206231-1-m.heidelberg@cab.de> (raw)
Signed-off-by: Markus Heidelberg <m.heidelberg@cab.de>
---
Documentation/bpf/prog_flow_dissector.rst | 4 ++--
Documentation/fb/fbcon.rst | 2 +-
Documentation/filesystems/path-lookup.rst | 2 +-
Documentation/hwmon/lm75.rst | 2 +-
Documentation/kernel-hacking/hacking.rst | 2 +-
Documentation/networking/phy.rst | 8 ++++----
Documentation/process/management-style.rst | 2 +-
7 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/Documentation/bpf/prog_flow_dissector.rst b/Documentation/bpf/prog_flow_dissector.rst
index f24270b8b034..8de1446b278b 100644
--- a/Documentation/bpf/prog_flow_dissector.rst
+++ b/Documentation/bpf/prog_flow_dissector.rst
@@ -68,7 +68,7 @@ Pre-VLAN parsing::
.. code:: c
- skb->data + flow_keys->nhoff point the to first byte of TCI
+ skb->data + flow_keys->nhoff point to the first byte of TCI
flow_keys->thoff = nhoff
flow_keys->n_proto = TPID
@@ -87,7 +87,7 @@ Post-VLAN parsing::
.. code:: c
- skb->data + flow_keys->nhoff point the to first byte of L3_HEADER
+ skb->data + flow_keys->nhoff point to the first byte of L3_HEADER
flow_keys->thoff = nhoff
flow_keys->n_proto = ETHER_TYPE
diff --git a/Documentation/fb/fbcon.rst b/Documentation/fb/fbcon.rst
index a98a5cb0b0d8..b278a8fe7e2b 100644
--- a/Documentation/fb/fbcon.rst
+++ b/Documentation/fb/fbcon.rst
@@ -109,7 +109,7 @@ C. Boot options
available, fb0, adding fbcon=map:1 tells fbcon not to take over the
console.
- Later on, when you want to map the console the to the framebuffer
+ Later on, when you want to map the console to the framebuffer
device, you can use the con2fbmap utility.
3. fbcon=vc:<n1>-<n2>
diff --git a/Documentation/filesystems/path-lookup.rst b/Documentation/filesystems/path-lookup.rst
index 9ced1135608e..4e374f9073f6 100644
--- a/Documentation/filesystems/path-lookup.rst
+++ b/Documentation/filesystems/path-lookup.rst
@@ -1077,7 +1077,7 @@ whether in RCU-walk or REF-walk, the symlink stack needs to contain,
along with the path remnants:
- the ``struct path`` to provide a reference to the previous path
-- the ``const char *`` to provide a reference to the to previous name
+- the ``const char *`` to provide a reference to the previous name
- the ``seq`` to allow the path to be safely switched from RCU-walk to REF-walk
- the ``struct delayed_call`` for later invocation.
diff --git a/Documentation/hwmon/lm75.rst b/Documentation/hwmon/lm75.rst
index c6a54bbca3c5..f05799c53474 100644
--- a/Documentation/hwmon/lm75.rst
+++ b/Documentation/hwmon/lm75.rst
@@ -154,7 +154,7 @@ The LM75 implements one temperature sensor. Limits can be set through the
Overtemperature Shutdown register and Hysteresis register. Each value can be
set and read to half-degree accuracy.
An alarm is issued (usually to a connected LM78) when the temperature
-gets higher then the Overtemperature Shutdown value; it stays on until
+gets higher than the Overtemperature Shutdown value; it stays on until
the temperature falls below the Hysteresis value.
All temperatures are in degrees Celsius, and are guaranteed within a
range of -55 to +125 degrees.
diff --git a/Documentation/kernel-hacking/hacking.rst b/Documentation/kernel-hacking/hacking.rst
index 0042776a9e17..b3d352d2ffcc 100644
--- a/Documentation/kernel-hacking/hacking.rst
+++ b/Documentation/kernel-hacking/hacking.rst
@@ -259,7 +259,7 @@ overruns. Make sure that will be enough.
.. note::
You will know when you are a real kernel hacker when you start
- typoing printf as printk in your user programs :)
+ typing printf as printk in your user programs :)
.. note::
diff --git a/Documentation/networking/phy.rst b/Documentation/networking/phy.rst
index 7f159043ad5a..8d457979a1f1 100644
--- a/Documentation/networking/phy.rst
+++ b/Documentation/networking/phy.rst
@@ -5,7 +5,7 @@ PHY Abstraction Layer
Purpose
=======
-Most network devices consist of set of registers which provide an interface
+Most network devices consist of a set of registers which provide an interface
to a MAC layer, which communicates with the physical connection through a
PHY. The PHY concerns itself with negotiating link parameters with the link
partner on the other side of the network connection (typically, an ethernet
@@ -262,7 +262,7 @@ Some of the interface modes are described below:
encoding. The underlying data rate is 1Gbps, with the slower speeds of
100Mbps and 10Mbps being achieved through replication of each data symbol.
The 802.3 control word is re-purposed to send the negotiated speed and
- duplex information from to the MAC, and for the MAC to acknowledge
+ duplex information to the MAC, and for the MAC to acknowledge
receipt. This does not include "up-clocked" variants such as 2.5Gbps
speeds.
@@ -285,7 +285,7 @@ Some of the interface modes are described below:
Note: 10GBASE-R is just one protocol that can be used with XFI and SFI.
XFI and SFI permit multiple protocols over a single SERDES lane, and
- also defines the electrical characteristics of the signals with a host
+ also define the electrical characteristics of the signals with a host
compliance board plugged into the host XFP/SFP connector. Therefore,
XFI and SFI are not PHY interface types in their own right.
@@ -545,7 +545,7 @@ When phy_register_fixup() or \*_for_uid()/\*_for_id() is called at module load
time, the module needs to unregister the fixup and free allocated memory when
it's unloaded.
-Call one of following function before unloading module::
+Call one of the following functions before unloading the module::
int phy_unregister_fixup(const char *phy_id, u32 phy_uid, u32 phy_uid_mask);
int phy_unregister_fixup_for_uid(u32 phy_uid, u32 phy_uid_mask);
diff --git a/Documentation/process/management-style.rst b/Documentation/process/management-style.rst
index dfbc69bf49d4..0b9e074277d0 100644
--- a/Documentation/process/management-style.rst
+++ b/Documentation/process/management-style.rst
@@ -42,7 +42,7 @@ actually true.
The name of the game is to **avoid** having to make a decision. In
particular, if somebody tells you "choose (a) or (b), we really need you
to decide on this", you're in trouble as a manager. The people you
-manage had better know the details better than you, so if they come to
+manage know the details better than you, so if they come to
you for a technical decision, you're screwed. You're clearly not
competent to make that decision for them.
base-commit: e30917da6074205bb1071a52e325c9d6ffe68ad5
prerequisite-patch-id: 81e067eae729d71e41b653c4f550dd3449003592
prerequisite-patch-id: 21078cbf43929b4a0d56ab4bb4acea907af70d7a
--
2.43.0
next reply other threads:[~2025-09-26 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 9:53 Markus Heidelberg [this message]
2025-09-26 12:32 ` Jonathan Corbet
2025-09-26 14:26 ` Markus Heidelberg
2025-09-26 17:36 ` Randy Dunlap
2025-09-29 9:06 ` Markus Heidelberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250926095312.206231-1-m.heidelberg@cab.de \
--to=m.heidelberg@cab.de \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®